1.6. Fabric Management

When you create child containers in JBoss A-MQ, the containers inherit ports from the parent containers. However, OpenShift Enterprise applications must bind to specific ports. Therefore, you cannot create child containers in the EJBoss A-MQ on OpenShift Enterprise.

The first JBoss A-MQ application that you create contains the ZooKeeper server instance with which each subsequent application authenticates. The ZooKeeper instance includes the user credentials and the environment variables required to run the applications in a fabric.

When you create subsequent applications, make sure to note the following guidelines:

Some Camel components require UDP network traffic routing. However, UDP is not supported in the JBoss A-MQ cartridge.

Normally, you can restrict access to shared file systems such as NFS based on user ID. However, when you run JBoss A-MQ on OpenShift Enterprise, the user ID is dynamically generated at run-time. Therefore, you cannot configure the shared file system to restrict access based on user ID.

The following profiles are not supported when you run JBoss A-MQ on OpenShift Enterprise:

In addition to the unsupported profiles, it is recommended not to deploy non-ActiveMQ profiles in your JBoss A-MQ application.

Normally, when you deploy an application, OpenShift Enterprise creates a Git repository with the source code of the application. However, JBoss A-MQ with fabric creates a standalone Git repository that stores all of the profiles and configuration files. Therefore, the cartridge does not use the Git repository that OpenShift Enterprise creates for the application.