IBM Integration Bus, Version 10.0.0.17 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS


Preparing the environment to split processing between IBM Integration Bus and IBM App Connect on IBM Cloud

When you split message flow processing between IBM® Integration Bus and IBM App Connect on IBM Cloud, you must configure a connectivity agent.

Before you begin

These instructions assume that you have IBM Integration Bus version 10.0.0.4 or later installed on premises, and that you have created an App Connect service in IBM Cloud.

About this task

When you split processing between IBM Integration Bus and IBM App Connect on IBM Cloud, your flows communicate by using a Switch server and connectivity agent. The Switch server, which routes data, is managed for you by IBM App Connect on IBM Cloud. The connectivity agent contains the certificates that your flows require to communicate securely with the Switch server. A connectivity agent must be running in the IBM Integration Bus integration server where you have deployed your on-premises message flows.

The diagram shows an application in Integration Bus, and an application in App Connect Enterprise on IBM Cloud.  The CallableFlowInvoke node in a flow in application 1 in Integration Bus uses a Switch server in the cloud to call the CallableInput node of a flow in application 2 in App Connect Enterprise on IBM Cloud.
The diagram shows an application in App Connect Enterprise on Cloud, and an application in IBM Integration Bus.  The CallableFlowInvoke node in a flow in application 1 in the cloud uses a Switch server in the cloud to call the CallableInput node of a flow in application 2 in Integration Bus.

The Switch server is already created in IBM App Connect on IBM Cloud. You must download an agent configuration file from the cloud, and use it to configure the on-premises connectivity agent. Your callable flows use this agent to communicate with each other securely, through the Switch server.

Procedure

To prepare the environment to split processing between IBM Integration Bus and IBM App Connect on IBM Cloud, complete the following steps.

  1. In IBM App Connect on IBM Cloud, open the hamburger menu Icon showing hamburger menu, expand Manage, then click Callable flows.

    If you have not configured callable flows before, the list will be empty, and the status of connectivity is “Connectivity paused”.

  2. Click Connect callable flows.

    A dialog box opens to set up your agent.

  3. Click Download the configuration and save the agent configuration file (agentx.json) to the same computer where IBM Integration Bus is installed.
  4. On the computer where IBM Integration Bus is installed, start an IBM Integration Bus command environment.
  5. To use the downloaded file to configure the connectivity agent on premises, run the following mqsichangeproperties command for the integration server that contains your callable flow.
    • On Windows:
      mqsichangeproperties integrationNodeName -e integrationServerName -o ComIbmIIBSwitchManager -n agentXConfigFile -p filepath\agentx.json
    • On Linux:
      mqsichangeproperties integrationNodeName -e integrationServerName -o ComIbmIIBSwitchManager -n agentXConfigFile -p filepath/agentx.json
  6. In IBM App Connect on IBM Cloud, click Test your agent to check that the on-premises agent can connect to the Switch server.
  7. Click Restart.

    The status of connectivity should now be "Started".

  8. Restart the IBM Integration Bus integration server.

Results

A callable message flow that is deployed to the configured on-premises integration server can now communicate securely with a callable message flow in IBM App Connect on IBM Cloud. For more information about developing these message flows, see Developing synchronously callable message flows.

You can check that your callable flows are registered with the Switch server by using the Callable flows view of IBM App Connect on IBM Cloud.

You can also list the callable flows that are running in the on-premises integration server by using the following mqsireportproperties command:
mqsireportproperties integrationNodeName -e integrationServerName -o CallableFlowManager -r

cl23153_.htm | Last updated 2019-07-13 08:14:11