You can now use IBM Integration Bus on Cloud to store and run your callable flows at the same time as giving your IIBoC integrations access to your on-premises endpoints by using endpoint connectivity.

Using callable flows enables you to split processing between your IIB on-premises (IIBoP) integration servers and IIBoC integrations. This gives you more options when spreading your workload between IIBoP and IIBoC, enabling you to create extra capacity when needed (for example, at times of high demand using either your IIBoP or IIBoC resources).

IIBoC Callable Flows
When you upload a BAR file containing a CallableInput node to the cloud, this callable flow will connect automatically to your running IIBoC Switch server, which will be created and maintained for you in the cloud. Any IIBoP integration servers can then be configured to also connect to this Switch. To do this, you download the IIBoC Switch agentx configuration from the cloud, by using the “Set up an agent” wizard on the Callable Flows page, then run the following command on your IIBoP integration server:

mqsichangeproperties IIBoP_NODE_NAME -e IIBoP_SERVER_NAME -o ComIbmIIBSwitchManager -n agentXConfigFile -p filepath/agentx.json (Linux)
mqsichangeproperties IIBoP_NODE_NAME -e IIBoP_SERVER_NAME -o ComIbmIIBSwitchManager -n agentXConfigFile -p filepath\agentx.json (Windows)

Once you have started and stopped your IIBoP integration servers and IIBoC integrations, you will be able to see the callable flows listed on the Callable Flows page in your IIBoC UI as either callers (CallableFlowInvoke nodes) or providers (CallableInput nodes). This means that any callers can then call any registered providers with a matching endpoint name. There is also a property on the CallableFlowInvoke node called “Call Preference”. If this property is set to Prefer local calls, then if there is a matching registered provider in the same IIBoP server or in the same IIBoC integration, this flow will be used in preference to calling out to a remote IIBoP server or another running IIBoC integration that has registered the provider.

IIBoC Endpoint Connectivity
You can then also set up endpoint connectivity by defining your endpoint and then following the endpoint connectivity “Set up an agent” wizard. This wizard creates an IIBoP Switch server, which will then connect to your IIBoC Switch, allowing your IIBoC integrations to access your IIBoP local queue managers and databases.

This setup creates a truly hybrid integration environment.

Extending an Existing IIBoP Callable Flows Environment to use IIBoC Endpoint Connectivity
If you have an existing IIBoP callable flows environment and want to use the IIBoC endpoint connectivity functionality, you can download the agentp configuration from the IIBoC Endpoint Connectivity page and run the following commands against your IIBoP IIBSWITCH_NODE. This command will enable the IIBoP IIBSWITCH_NODE to connect to your IIBoC Switch, giving your cloud integrations the ability to connect to your on-premises endpoints as well as routing your IIBoP Callable Flows.

mqsichangeproperties IIBSWITCH_NODE -e IIBSWITCH_SERVER -o ComIbmIIBSwitchManager -n agentPConfigFile -p filepath\iib-agentp.json

In this scenario, your IIBoC callable flows will NOT be able to access your IIBoP callable flows. If you need this functionality, you can configure your IIBoP Switch to handle your local on-premises endpoint connectivity, and you can configure your IIBoP servers to use your IIBoC Switch by using the callable flows agentx configuration when configuring your IIBoP Servers.

mqsichangeproperties IIBoP_NODE_NAME -e IIBoP_SERVER_NAME -o ComIbmIIBSwitchManager -n agentXConfigFile -p filepath\agentx.json

Callable Flows Tutorial
The IIBoP Tutorials Gallery includes a Callable Flows tutorial, which demonstrates how to use the callable flows nodes to split message flow processing. To access the tutorial, open the IBM Integration Toolkit, click Help, select Tutorials Gallery, then select Callable Flows from the list of tutorials.

Restrictions for IIBoC
If you are running an IIBoC trial, you will only be able to run 1 integration but you can have 5 integrations stored in the cloud. Your integrations will also stop after 3 hours of inactivity. To get around these trial restrictions, you can purchase either a subscription or pay-as-you-go entitlement here IIBoC Marketplace.

Join The Discussion

Your email address will not be published. Required fields are marked *