| Bookmark Name | Actions |
|---|
Deployment Configuration
The deployment configuration properties uses the DEPLOYMENT_CONFIG or deployment_config formalism. They are used to configure links between application tiers (server, database or broker), and also to enable and configure the application services.
Database Wiring
The connection with the database is fully configurable through environment variables.
| Property | Description | Default Value |
|---|---|---|
|
DB_URL |
It specifies the DB connection URL. |
None |
|
DB_USERNAME |
It specifies the DB user. |
None |
|
DB_PASSWORD |
It specifies the DB password. |
None |
|
DB_DRIVER |
It specifies the DB provider. It needs to match the JBoss and JDBC driver name that is defined in the CLI script. |
None Possible values by default: h2, sqljdbc or ora12c |
|
DB_POOL_SIZE |
It specifies the datasource maximum concurrent connection number. |
None |
The following is an example of H2 database:
DB_URL=jdbc:h2:tcp://host.docker.internal:2234/TESTDB;DB_CLOSE_ON_EXIT=FALSE;MODE=Oracle;TRACE_LEVEL_FILE=0;TRACE_LEVEL_SYSTEM_OUT=0;FILE_LOCK=NO;IFEXISTS=TRUE;CACHE_SIZE=8192;MVCC=TRUE;LOCK_TIMEOUT=60000 DB_USERNAME=tafj DB_PASSWORD=tafj DB_DRIVER=h2
The following is an example of MSSQL database:
DB_URL=jdbc:sqlserver://host.docker.internal:1433;databaseName=TESTDB DB_USERNAME=tafjuser DB_PASSWORD=tafjuser1 DB_DRIVER=sqljdbc
The following is an example of ORACLE database:
DB_URL=jdbc:oracle:thin:@host.docker.internal:1521/TESTDB DB_USERNAME=tafj DB_PASSWORD=secret DB_DRIVER=ora12c
JMS Broker Wiring
The connection with the external ActiveMQ broker is fully configurable through environment variables.
| Property | Description | Default Value |
|---|---|---|
|
AMQ_URL |
It specifies the broker connection URL. |
None |
|
AMQ_USERNAME |
It specifies the broker user. |
None |
|
AMQ_PASSWORD |
It specifies the broker password. |
None |
EXAMPLE:
AMQ_URL=failover:(tcp://host.docker.internal:61616?soLinger=0) AMQ_USERNAME=admin AMQ_PASSWORD=admin
It is also possible to connect to Websphere MQ with the following environment variables:
| Property | Description | Default Value |
|---|---|---|
|
MQ_HOSTNAME |
It specifies the broker connection URL. |
None |
|
MQ_PORT |
It specifies the broker user. |
None |
|
MQ_QUEUE_MANAGER |
It specifies the broker password. |
None |
|
MQ_CHANNEL |
?? |
None |
EXAMPLE:
MQ_HOSTNAME= host.docker.internal MQ_PORT=1414 MQ_QUEUE_MANAGER=MQ_T24 MQ_CHANNEL=T24_CHANNEL
JMS Queue Wiring
There are environment variables that are used to define the physical queue mapping at broker level with the fixed JNDI names defined at MicroEE level.
The following environmental variables are used to define the queues for online processing:
ONLINE_QUEUE=t24OFSQueue
ONLINE_REPLY_QUEUE=t24OFSReplyQueue
The above environmental variables mapping should be different per environment or channel definition.
The Phantom queue and management topic are shared and should be the same on each environment.
EXEC_QUEUE=t24EXECQueue
MANAGEMENT_TOPIC=t24ManagementTopic
| Property | Description | Default Value |
|---|---|---|
|
ONLINE_QUEUE |
It specifies the online channel request queue physical name. |
None |
|
ONLINE_REPLY_QUEUE |
It specifies the online channel reply queue physical name. |
None |
|
EXEC_QUEUE |
It specifies the phantom channel queue physical name. |
None |
|
MANAGEMENT_TOPIC |
It specifies the management topic physical name. |
None |
Application Wiring
These properties define what are the services that are available and how they are configured.
| Property | Description | Default Value |
|---|---|---|
|
channel_type |
For online processing, it defines whether it is OFS processing or CALLAT processing (link between TransactedMDB and OFSProcessingBean or CallAtProcessingBean). |
ofs Possible values: ofs or callat |
|
online_active |
It defines whether the online MDB (TransactedMDB) is enabled and listening to AMQ_ONLINE_QUEUE. |
None Possible values: true or false |
|
max_online_session |
It defines the online MDB thread pool (maximum concurrent messages). |
None Integer value |
|
phantom_active |
It defines whether the phantom MDB (PhantomListener) is enabled and listening to AMQ_EXEC_QUEUE. |
None Possible values: true or false |
|
max_phantom_session |
It defines the phantom MDB thread pool (maximum concurrent messages). |
None Integer value |
|
phantom_selector |
It defines the message selector, which applies to the Phantom MDB. If a JMS message contains a JMS property PhantomSelector, then it will be treated in case of phantom_selector=PhantomSelector. This value is also set as PhantomSelector when posting message to AMQ_EXEC_QUEUE. It should be unique per environment. |
None String value |
The following is an example for OFS processing:
channel_type=ofs online_active=true max_online_session=10
NOTE: channel_type is optional since the default value is ofs.
The following is an example for CALLAT processing:
channel_type=callat online_active=true max_online_session=5
NOTE: channel_type is mandatory to infer CALLAT processing instead of OFS.
The following is an example for Phantom processing:
phantom_active=true max_phantom_session=20 phantom_selector=server1
Add Bookmark
save your best linksView Bookmarks
Visit your best links
BACK
Are you sure you want to log-off?