Targeted Architecture

This section details the deployment of targeted architecture on a standard Wildfly or JBoss EAP installation on premises.

It is important to note that Wildfly or JBoss EAP is required for the dynamic configuration capabilities it offers at runtime by injecting environment variables and system properties within the application server and application configuration.

The main configuration is automated with scripts (JBoss - CLI) and at runtime, environment variables set at orchestrator level are resolved and injected to run the expected setup.

There are different categories of parameters which are used at different level to wire the components altogether and to configure the application. The default JMS broker is ActiveMQ, which is deployed on a separate tier but it can be any other JMS broker. The Wildfly AMQ internal broker is not used since there is no need for a local Exec queue.

To connect to a different broker, you need to define the appropriate “activation config” parameters at jboss-ejb3.xml level.