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
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.