Connecting to UM from External Clients

Knowledge base
, ,
1

   Introduction

 This article explains how to connect Universal Messaging (UM) from external clients

   Audience

It is assumed that readers of this article know how to create webMethods cloud container solutions in cloud container as well as creating the artifacts on Universal messaging enterprise manager.

 

   Pre-Requisites 

webMethods Cloud Container - Introduction

  1. Create a solution in Webmethods cloud container.
  2. Cloud container solutions should be created on dedicated tenant(not on free trial) and  should contain.
  •  Integration server
  • Universal Messaging should be installed.

3. Integration server should be up and running on you on-premise, As we will use the on-premise Integration server as external client to connect to the cloud container.

 

1023×409 34.8 KB

 

4. Universal Messaging Enterprise Manager should be running

1267×760 42.6 KB

 

 

Set up for External Client

 

  1. Create a Connection factory in UM enterprise Manager.

         Connection Factory Name: shipmentconnectionfactory

1009×550 129 KB

     2. Create a Topic where the publisher will push the message.

        Topic Name: ShipmentTopic

 

1025×380 68.7 KB

    3. Create JNDI setting on your IS server

                  JNDI Alias Name: ShipmentJNDI

       ProviderURL Name: nhps://<TenantID>.container.webmethodscloud.com:9443//<UM name>-<solution Name>

       Shipment URL:  nhps://166261317.container.webmethodscloud.com:9443//um-shipment

       Note: shipment URL uses nhps protocol to connect to cloud UM

       Tenant ID:  166261317 (will vary for each tenant)

       UM name: created in cloud container: um (always in lower case).

       Solution name: shipment (always in lower case)

 

1899×769 58.5 KB

       4. Create JMS Connection Alias

Connection Alias Name:  ShipmentJMSAliasName

Username: <Any>

Password:  <Any>

JNDI alias Name:  shipmentJNDI

1872×917 86.7 KB

 

Deployment on Cloud Container

  1. Create configuration template from SoftwareAG designer
  •  Connect to command central
  •  Open the landscape navigator

946×468 110 KB

  • Right-click on JNDI connection factories within UM and export the configuration in the project. It contains the yaml template which has all the details for UM

726×736 89.1 KB

637×658 72.2 KB

1038×591 129 KB

  • Open the yaml file and replace the connection factory url which we created while doing JNDI setup. In our case it will be

     nhps://166261317.container.webmethodscloud.com:9443//um-shipment

  • Right-click on internal users within UM and create the project. It contains the yaml template where we have to replace the username and password which we have used while setting up JNDI setting.

1081×608 18.2 KB

Note: We can include both the configurations in one project. Just to make them more clear we have created 2 independent projects

  • Please deploy both configurations to your cloud container solutions.

Deploy internal user configurations:

852×689 20.3 KB

 

     Deploy JNDI configurations:

843×699 20.5 KB

  • Connect to cloud container solution and validate the artifacts that can be seen on cloud container UM.

939×407 40.5 KB

        Test Connection to Cloud UM

  • Connect to your IS server and navigate to messaging.
  • Do Test lookup for ShipmentJNDI and if we are able to connect we can verify that connectivity is established between external client and cloud container UM.

1903×768 84.1 KB

  • To test with flow service, create a sample package where we have 2 flow services publish and subscribe.
  • Create publish flow service and use the same connection factory, Topic Name, and JMS alias which are used to set up the connectivity.
  • Publish service flow will push the message and subscribers will subscribe to the message using the JMS trigger.