Troubleshooting

Diagnose and resolve issues that arise in IBM® Integration Bus on Cloud.

If you have a problem while using IBM Integration Bus on Cloud, you can use the following information to diagnose the problem.

To check the current operational status of IBM Integration Bus on Cloud and details of planned maintenance, see the status page (IBM Integration Bus on Cloud status).

Diagnosing problems with integrations

  • Look on the Integrations page to find out if your integrations are running.
  • For more detailed information about your integrations, view the runtime log in IBM Integration Bus on Cloud. Go to the History and Logs section of the Integrations page, then click Download Runtime Log.

    If a message flow in your integration contains a Trace node, you can configure that node to write data to the local error log. You can then retrieve that trace information by downloading the runtime log from the Integrations page.

Diagnosing problems with connectivity

  • Look on the Connectivity page to find out if your endpoint configurations are synchronized with the on-premises agent.
  • Check that the Switch server is created and running. The Switch server is used to route data between your integrations and private endpoints, and is created automatically when you configure the on-premises agent. The Switch server is created in a special integration node called IIBSWITCH_NODE. To test that the Switch server is created and running, run the command mqsilist IIBSWITCH_NODE. If the Switch server is running, you see the following response:
    BIP1286I: Integration server 'IIBSWITCH_SERVER' on integration node 'IIBSWITCH_NODE' is running.
  • On the Connectivity page, check that your private endpoints are available to your integrations by clicking Test connection (Test connection icon) next to the appropriate endpoint configuration.
  • For more detailed information about the on-premises connectivity agent, check the log file switchtimestamp.txt. The agent writes errors to this file when it tries to connect.

    You can find this log file in the workpath/common/log directory of your IBM Integration Bus installation. If the workpath directory has not been created by using the mqsicreatebroker command, the default workpath directory on Windows is C:\ProgramData\IBM\MQSI. On Linux®, the default workpath directory is /var/mqsi/common/log.

  • Watch the following video, which demonstrates how to connect securely to private endpoints: IBM Integration Bus on Cloud - Secure connectivity to on-premises systems demo.

Diagnosing problems with callable flows

  • Look on the Callable Flows page to see lists of registered callers (calling flows) and providers (callable flows).
  • Validate your message before it reaches a CallableFlowInvoke node.
  • Ensure that application and endpoint name pairs are unique in a single integration or integration server.
  • Check that your callable flows are registered.
  • Use the Callable Flows tutorial in the IBM Integration Bus Tutorials Gallery to see how callable flows can be used.
For more detailed information, see Resolving problems when you use callable flows.