To configure Assure DQ deployed in WildFly to connect to IBM MQ, follow this procedure.
- From the IBM website, download IBM MQ 9.0 resource
adapter (
9.0-IBM-MQ-Java-InstallRA). - Refer to the IBM tech note: http://www-01.ibm.com/support/docview.wss?uid=swg21668491, which
explains the procedure to download the resource adapter. Tip: Customers should download the resource adapter file from IBM after accepting the licensing agreement.
The instructions below explain the procedure to download the adapter file from IBM.
- Go to https://www-945.ibm.com/support/fixcentral
Product Group: WebSphere Select from WebSphere: WebSphere MQ Installed Version: 9.0 Platform: All Click Continue Browse for Fixes Show fixes that apply to this version (9.0) Click Continue Select 9.0.0.0-IBM-MQ-Java-InstallRA Click Continue Accept the license agreement to download the file 9.0.0.0-IBM-MQ-Java-InstallRA.jar
Procedure to Install Resource Adapter File (9.0.0.0-IBM-MQ-Java-InstallRA)
Run the following command from the directory to which you downloaded the file.
java -jar 9.0.0.0-IBM-MQ-Java-InstallRA.jar
where 9.0.0.0-IBM-MQ-Java-InstallRA.jar is the name of the file that was downloaded from Fix Central.
Files Installed
Within the selected directory, a new directory wmq will be created. Inside the wmq directory, the following files are installed:
- wmq.jmsra.ivt.ear
- wmq.jmsra.rar
The file wmq.jmsra.rar is the WebSphere MQ Resource Adapter RAR file.
Procedure to Configure MQ
Add the following properties in the IA.properties file in the directory <install_folder>/Infogix/config/<myConfigName>/IA/ if they do not exist.
The following are WebSphere MQ property descriptions:
| WebSphere MQ Property | Description |
|---|---|
| WEBSPHERE_EXTERNAL_QUEUES | Lists the queues configured externally. A comma separates multiple queues. |
| WEBSPHERE_MQ_QUEUE_MANAGER | Name of the queue manager. |
| WEBSPHERE_MQ_HOST | Host name of the queue manager. |
| WEBSPHERE_MQ_PORT | Connection port number (normally MQ defaults to 1414). |
| WEBSPHERE_MQ_USER | User ID used to connect to the queue manager. |
| WEBSPHERE_MQ_PASSWORD | Password of the above user ID for authentication. |
| WEBSPHERE_MQ_RAR | The .rar archive file downloaded from IBM. |
| WEBSPHERE_MQ_${QUEUE_NAME}_BASEQNAME |
The MQ name of the actual queue. Example setting for IGX_IA_CASAPINPUTQUEUE: WEBSPHERE_MQ_IA_CASAPINPUTQUEUE_BASE_QNAME=IGX_IA_CASAPINPUTQUEUE If not specified, the configuration will use IA_CASAPInputQueue for the queue name. |
Sample Assure DQ Configuration
WEBSPHERE_EXTERNAL_QUEUES=${solution.short.name}_CASAPIInputQueue
WEBSPHERE_MQ_RAR=<install_folder>/Infogix/mq/wmq.jmsra.rar
WEBSPHERE_MQ_HOST=${customer-MQHost}
WEBSPHERE_MQ_PORT=1414
WEBSPHERE_MQ_QUEUE_MANAGER=${customer-QueueManager}
WEBSPHERE_MQ_USER=${customer-MQUser}
WEBSPHERE_MQ_PASSWORD=${customer-MQPassword}
WEBSPHERE_MQ_IA_CASAPIINPUTQUEUE_BASEQNAME=IGX_IA_CASAPIINPUTQUEUE
# Enable Assure API Processors
START_JMS_API_PROCESSORS=true
START_API_PROCESSORS=true
Deploy Assure DQ
Deployment Considerations
- Log in to the WildFly Admin Console of the server where Assure DQ is running.
- Remove IA_CASAPIInputQueue and IA_CASAPIInputQueueCF.
From <install_folder>/Infogix/bin, run the following scripts:
For Windows:
clean.bat –c <myConfigName> <product>
deploy.bat –c <myConfigName> <product>
For UNIX or Linux:
./clean.sh –c <myConfigName> <product>
./deploy.sh –c <myConfigName> <product>
Restart the <product> server.
For WildFly deployments, run the following scripts from <install_folder>/Infogix/bin:
For Windows:
stop-wildfly.bat -c <myConfigName>
start-wildfly.bat -c <myConfigName>
For UNIX or Linux:
./stop-wildfly.sh -c <myConfigName>
./start-wildfly.sh -c <myConfigName>