Resolving problems that occur when connecting the IBM Integration Toolkit and an integration node

Use the advice given here to help you to resolve common problems that can arise when you connect to an integration node.

Your integration node is not recognized by the IBM Integration Toolkit

Procedure

  • Scenario: Your integration node is not recognized by the IBM® Integration Toolkit.
  • Explanation: Integration node names in the workbench are case sensitive.
  • Solution: When you identify an integration node in the IBM Integration Toolkit, make sure that you use the same case that was used when it was created. On some operating systems, the name of the integration node might be folded to uppercase when it was created, even though you entered its name in lowercase.

You cannot connect to the integration node from the IBM Integration Toolkit or command line

Procedure

  • Scenario: Error messages are issued when you try to connect to the integration node from the IBM Integration Toolkit or the command line.
  • Solution: The following table shows the checks to carry out when an error message is issued in the IBM Integration Toolkit, or returned to the command line, when you try to connect to the integration node:
    Error message Actions
    IBM Integration Toolkit Command line
    BIP0914E BIP1921E Check that the integration node and its HTTP listener are running, and that the correct port is specified for the web user interface connection.
    BIP0889E BIP1920E Check that the integration node is running.

    Check the system event log to ensure that the integration node is available for use, and correct all errors that are shown.
    BIP0915E BIP1923E Check that the IBM Integration Toolkit local user ID is created on the integration node system. If it is not, create it.

    Check if the IBM Integration Toolkit local user ID that is created on the integration node system is authorized to connect to the web user interface.
    BIP1291E Remove the -q parameter, and use the -i or -p parameters instead.

You cannot connect to a migrated integration node

Procedure

  • Scenario: You cannot connect from the IBM Integration Toolkit, the IBM Integration Toolkit, or an IBM Integration Toolkit application to an integration node that you have migrated to Version 10.0.
  • Explanation: The connection is failing because the WebSphere® MQ channel does not exist.
    When you migrate an integration node to Version 10.0, the default server connection channel SYSTEM.BKR.CONFIG is created if it does not exist. However, if the integration node shared a queue manager with a Configuration Manager, this channel is deleted when you delete the Configuration Manager.
  • Solution: Re-create the server connection channel SYSTEM.BKR.CONFIG on the queue manager.

You cannot connect to a remote integration node

Procedure

  • Scenario: You have correctly configured your IBM Integration Toolkit to connect to a remote integration node, but attempting to connect to the remote integration node by using the IBM Integration Toolkit results in error MQRC 2059. You can connect to your remote integration node from the same computer without error by completing the following steps:
    1. Set the following environment variable:
      • On Windows: set MQSERVER=ChannelName/TCP/server-address(port)
      • On Linux®: export MQSERVER=ChannelName/TCP/'server-address(port)'
    2. Open an IBM Integration Bus command prompt, and enter the following test command: 
      amqsputc queueName qmgrName
  • Explanation: The network configuration of your IBM Integration Toolkit installation is incorrect.
  • Solution:
    1. In the IBM Integration Toolkit, click Window > Preferences > General > Network Connection.
      The Preferences window opens, and the Network Connections preferences are displayed.
    2. From the Active Provider list, select Direct.
      For more information about the Active Provider setting, see the "Network Connections" topic in the Eclipse product documentation.
      You can now connect to your remote integration node by using the IBM Integration Toolkit.

Connection to the integration node is slow

Procedure

  • Scenario: Connection to the integration node is slow and you cannot complete other actions in the IBM Integration Toolkit when you request the following operations:
    • Creating an integration node
    • Creating an integration server
    • Deploying a BAR file, using the Deploy a BAR File wizard
    • Opening the Administration log editor
  • Solution: Click Cancel on the progress monitor dialog box to cancel the in-progress connection.
    Connection to the integration node is canceled, so that you can perform other actions in the IBM Integration Toolkit. You can then resubmit the canceled operation.