Introduction 

This article demonstrates how to implement hybrid messaging on the cloud using existing on-premises assets. 

Pre-requisites 

• A webMethods.io Integration tenant.
• Administrator access to the webMethods.io Integration platform  
• create edge runtimes
•  version control configured  
• Universal Messaging server  

Audience 

This article is intended for Integration architects and developers working with  webMethods. 

Use case 

The client has migrated from a self-hosted setup to a cloud platform. Their application uses a messaging solution, and the development team now aims to orchestrate Deploy Anywhere connections to support business needs. 

Existing setup 

To be Setup 

• When the UM server is hosted on the cloud, direct cloud connectivity is available. In this setup, assets can run on Design Runtime (DRT) and submit requests directly to the UM server. 

• If the UM server is hosted on a private cloud, assets must run on Edge Runtime (ERT) within the same network to ensure secure and reliable communication. 

Steps to be followed 

Publishing the message to UM server 

• Pull the code from external repository 

• Orchestrate the flow using flow service or workflow and invoke the package services 

• Configure JNDI and JMS connections on DRT (design runtime) 

• Enable the connections 

Subscribe the message from UM server 

• Configure the JMS connection 

• Create the JMS trigger 

• Create the subscriber flow service 

Pull the code from external repository 

• Configure the version control on your tenant . 

• Pull the assets under the packages tab. 

Refer the below link for more details 

• Tech Bytes IWHI: Import assets from external repository on webMethods.io Integration 

•  Tech Bytes IWHI: Push self hosted assets to external repository and pull them on webMethods.io Integration 

Orchestrate the flow using flow service or workflow and invoke the package services 

• In our case we are using the flow service therefore we have created the orchestration inside the flow service and invoked the packages service.
• As my UM server is accessible from cloud therefore, we run the package service on DRT (design runtime/ cloud design time). 

Refer below link how to orchestrate the package services. 

• Tech Bytes IWHI: Configure the connection and sync with Integration runtimes 

Configure JNDI and JMS connections on DRT (design runtime) 

• When we talk about configuration we need to configure  

• •   JNDI configurations
  • JMS configurations 

JNDI configurations 

•  In our case we need to supply provider URL, service principal and Security credentials.

JNDI API’s 

• We can update the configuration using public API exposed  

          GET JNDI Details

           METHOD: GET

          URL: https://<TenantName>/apis/v1/rest/control-plane/runtimes/<runtimeName>/configurations/jndi/<JNDIName> 

In our case  

JNDIName: DEFAULT_IS_JNDI_PROVIDER 

Runtime: default (we are using design runtime) 

• Now we can use the response of the above get call to update the property of JNDI. If you have the property key available, then we can skip this step. 

METHOD: PUT 

URL:  https://<TenantName>/apis/v1/rest/control-plane/runtimes/<RunTimename>/configurations/jndi/<JNDI Name>?updateRuntime=true 

In our case 

JNDI Name: DEFAULT_IS_JNDI_PROVIDER 

Runtime: default (we are using design runtime) 

Update Runtime: true (sync the changes to the runtime) 

Request Sample : 

{ "assetId": "DEFAULT_IS_JNDI_PROVIDER",  

"type": "jndi", 

"properties":  

[  

{ "propertyKey": "description", 

"value": "updates from API" } 

], 

"enableConnection": true  

} 

JMS configurations 

The way we have updated the JNDI configurations in the similar fashion we can update the JMS configurations as well. 

Automate using API’s 

GET JNDI Details  

METHOD: GET 

URL: https://<TenantName>/apis/v1/rest/control-plane/runtimes/<runtimeName>/configurations/jndi/<JMSConnectionName> 

In our case  

JMS connection name: DEFAULT_IS_JMS_CONNECTION (using default connection with updated connection details) 

Runtime: default (we are using design runtime) 

Now we can use the response of the above  API invoke to update the property of JNDI. If you have the property key available, then we can skip this step. 

METHOD: PUT 

 URL: https://<tenantName>/apis/v1/rest/control-plane/runtimes/<RunTimeName>/configurations/jms/<JMS connection Name>?updateRuntime=true 

• For subscribing the message, the flow service should have input has JMS message body. 

• Once the service gets invoked, we can extract the actual payload from the JMS message and use it for further processing. 

End to end Testing