IBM App Connect Enterprise with MQ client running in a container calling to an external MQ service
Learn how to set up an App Connect Enterprise integration that will run in a container and call an external MQ service.
Before you begin
The prerequisites are:
- IBM App Connect Enterprise in a container on a helm release (for example: ibm-ace-server-dev and ibm-ace-server-dev).
- An external MQ service, for example IBM MQ
- App Connect Enterprise with an existing message flow that needs to connect to the external MQ service
Procedure
- Step 1: Create the App Connect Enterprise broker archive (BAR) file that contains an MQ node calling an external MQ service
- Step 2: Set up the security identity as a secret
- Step 3: Configure the ibm-ace-server-dev or ibm-ace-server-prod helm release to use the App Connect Enterprise with MQ client image and reference your MQ credentials
Step 1: Create the App Connect Enterprise broker archive (BAR) file that contains an MQ node calling an external MQ service
Before you begin
This step assumes that you already have access to an external MQ service with existing service credentials
Procedure
Step 2: Set up the security identity as a secret
Before you begin
This step assumes that you have familiarity with creating helm releases (for example, like ibm-ace-dashboard-dev or ibm-ace-dashboard-prod).
Procedure
Step 3: Configure the ibm-ace-server-dev or ibm-ace-server-prod helm release to use the App Connect Enterprise with MQ client image and reference your MQ credentials
Procedure
The process of server configuration is very similar in the non-MQ and the MQ server versions, as outlined in the following steps: