Exposing on-premise Integrations to Cloud using webMethods.io Integration

Author: Vivek Kumar (vivk@softwareag.com), Srikanth Prathipati (srpr@softwareag.com)

1. Introduction

This article describes the steps to follow to expose on-premise Integrations running on webMethods Integration Server to Cloud via webMethods.io Integration. webMethods.io Integration is a Hybrid Integration Platform (HIP), allows on-premise solutions to seamlessly and securely integrate with cloud-based applications.  

1.1 Audience

It is assumed that readers of this article understand cloud concepts such as Hybrid Integration and are familiar with the products of the Software AG Integration Suite webMethods. This document is intended for developers who would like to configure the Hybrid Integration setup.

 2. On-Premise Integration Server Configurations

  • Single Node

To configure Hybrid Integration; Please verify “WmCloud” package is installed and enabled in the on premise Integration Server. 

Step 1: Login to Integration server eg: http://<hostname>:<port>

Step 2: Go to webMethods Cloud > Settings

Provide the required details:

User Name: XXXX 

Password: xxxx 

webMethods.io Cloud URL: https://XXXXX.int-XXX-XX.webmethods.io (webMethods.io Integration tenant URL)

Step 3: Go to webMethods Cloud > Accounts

Click on “Create On-Premise Account”. Provide the required details:

General Settings >

Alias Name: The name of the account that will appear on webMethods.io Integration

Description: Add description for this Account

Stage: Leave this value as Development. This value is provided for stage management within older versions of webMethods.io Integration.   

Account Settings >

Maximum Reconnection Attempts: Specify the maximum number of reconnections attempts that Integration Server should make if the connection to Integration Cloud fails.

Request Timeout: Maximum amount of time (in milliseconds) that Integration Cloud waits for the on-premise Integration Server to process a request.

Time to Live: If you are batching the data from the on-premise Integration Server, the length of time in seconds that the execution results remain in the cache of the on-premise Integration Server. The value must be greater than 0. The default is 60 seconds.

Allowed On-Premise Hosts: (Optional.) The on-premise Integration Server might use multiple addresses, depending on which network or proxy it uses to access Integration Cloud. Specify a comma-separated list of IP addresses that can receive requests from Integration Cloud. Only those IP addresses specified can receive requests.

Run As User: Specify the user name you want the on-premise Integration Server to use when running the service. You can select users from the local or central directory.

To delete the Accounts; Go to webMethods Cloud > Accounts. Please refer below

Step 4:

a. Go to webMethods Cloud > Applications

Click on “Define webMethods Cloud Application”. Provide the required values.

Name: Name of the Integration application. 

Description: Description of the application.

Assign Services to Application: Select the services you want to expose to webMethods.io Integration.

Save the changes.

b) Click on upload to upload the application to webMethods.io Integration.

Select the Account to associate with the Application and click on Upload. Please refer below

To verify, log in to your webMethods.io Integration instance and go to Connectors/Applications > On-Premises Applications. The on-premises Applications appears in the list.

To delete the Application; Go to webMethods Cloud > Applications. Please refer below

  • Cluster – Stateful/Stateless

To configure Hybrid Integration in Multi Node Cluster; Please follow the steps defined in above section Single Node for all IS in cluster (Except step 4 b). It does not require to upload the application from all the IS in the cluster. Upload the application from only one IS in the cluster.