Configuring connectivity between a calling flow and a callable flow
In your App Connect Designer flows, you can use a Callable flow node to invoke a running callable flow in either IBM® App Connect Enterprise or IBM Integration Bus on premises. To enable your flows to communicate, you must configure secure connectivity between App Connect Designer and App Connect Enterprise or Integration Bus by using a switch server and a connectivity agent.
- To run callable flows, your App Connect Designer instance must be associated with a switch server.
- The Callable flow connector, which calls the running callable flow, requires a switch server that is deployed locally in your cluster, or externally. This switch server is typically created or configured by your administrator.
For more information about callable flows, see Callable message flows in the IBM App Connect Enterprise documentation.
About this task
A switch server is a special kind of an integration server that routes data between the calling and callable flows, and it works with connectivity agents over a secure web sockets connection. A 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 App Connect Enterprise or IBM Integration Bus integration server where your on-premises message flows are deployed. You must download an agent configuration file from your App Connect Designer instance, and use it to configure the on-premises connectivity agent.
If your App Connect Designer instance has been configured with a switch
server, when you access the instance, a Callable flows icon is
included in the navigation pane. You can click this icon to open the Callable
flows
page to configure connectivity.
Procedure
If you are using a local Callable flow connector, you must configure connectivity between a calling flow in your cluster and a callable flow in an on-premises integration server by completing the following steps:
If you experience any connectivity issues, see Troubleshooting switch server connectivity for help in resolving the error.