Introduction

This article will explain how the existing IBM MQ use case can be migrated and executed on webMethods.io Integration using the DADA (Develop Anywhere and Deploy Anywhere) capabilities.

Pre-requisite

• webMethods.io Integration tenant with DADA capabilities enabled
• IBM MQ Instance.
• External repository
• Service designer on self-hosted setup.

Audience

•  This article is targeted for technical architects and technical developers of webMethods. 

What is DADA?

https://community.ibm.com/community/user//integration/blogs/john-carter/2023/10/20/what-is-develop-anywhere-deploy-anywhere

What is Integration runtimes?

https://community.ibm.com/community/user/integration/blogs/theo-ezell/2025/03/07/develop-anywhere-deploy-anywhere-what-are-integrat

Use case

In this use case we will discuss how we can migrate the MQ packages from the self hosted setup to the cloud and execute the transaction on webMethods.io Integration by using the DADA capabilities.

• Client is submitting the request to the exposed flow service on self-hosted Integration server.
• Inside the flow service the messages are getting  submitted to IBM MQ instance.
• Messages are submitted to “PurchaseOrder” queue in IBM MQ system.
• On cloud we have MQ listener which listens the message from MQ and process with in the flow service.

Existing use case Architecture

Target Architecture

Steps to achieve the target architecture

• External repository where the existing self-hosted assets will be pushed to it.
• Pull the asset from external repo into webMethods.io Integration project.
• Spin the edge runtime or use the CRT (cloud runtime) \DRT (design runtime).
• In our case we will use DRT.
• Sync the assets.
• Configure the connections and sync the assets 

Push assets to the external repository

• In our case we have the package “webMethodsDADA”. This package contains the business logic to submit the request to IBM MQ end system.
• Link: https://github.ibm.com/Vikash-Sharma5/webMethodsDADA
• We have created the repository in the external repository in our case it is github repository.

Pull the assets from repository

• Inside the project navigate to package tab.
• Provide the url and pull the assets.
• As this package is dependent on IBM MQ adapter so even this got pulled.

Add the external jars

• We need to add the external MQ jars required for MQ adapter.
• Under the package tab navigate to the project and click on library
• Add the external mq jars at the server level.

Orchestration

• Create the flow service  “submitPurchaseOrderMsgToIBMMQ”.
• Select the package service in our case it is “webMethodsDADA”
• Select the service “submitPurchasrOrderToMQFS”.
• Select the runtime in where you want to execute the service in our case we will select “DRT” (cloud design time)
• Save the flow service.

Configure the connection

• Click on connectors tab and navigate to deploy Anywhere.

• In our package we have 2 IBM MQ connection therefore we can see 2 connections.
• Now we need to configure the connections. Click on manage runtimes and add the runtime.
• In our case we are using the DRT (design runtime), therefore we have selected the cloud design time as Integration runtimes.
• Provide the connection details and then click on sync.

Note: When you click on sync, it updates the manifest file with the credentials and other details.

Verification on Integration runtimes.

• To verify whether the connections are synced and got enabled please verify under the Integration runtimes.

• Navigate to the capabilities section and select the connections. Here we can verify the status of the connection deployed on the runtime. 

Configure the MQ listener

• As we are publishing the message, we need listener which can consume the message from the queue and process it.
• In our case we have created the listener in the cloud.
• Navigate to the Events section and click on the listener.
• Select the IBM MQ listener and configure it. 

• Provide the name of the listener, in our case we have given “PurchaseOrderNotificaton”

• Provide the service name which will consume the message and process it. In our case we have created the new service as “ListenAndProcessIncomingMQmessage”.

• Save the connection and enable it.

Note: When we save this connection, it creates the following artefacts.

• MQ Listener.
• Consumer flow service
• Request and reply Document types.

Configure the consumer service

• Under the Integration tab open the service which we have created in the previous step.
• Click on the input and output section and configure the document.

• Add the logic for processing the message.
• In our case we are receiving the message and logging it.

End To end Testing

• Submit the message from the  flow service  “submitPurchaseOrderMessage”

• When we submit message to MQ, listener will lister the message and invoke the consumer service to process it.

Note: Attaching the assets used in the demo flow services for submitting and consuming the message from the IBM MQ