IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Connecting to a remote integration node on z/OS

To administer a remote integration node (broker) that is deployed on z/OS® by using the IBM® Integration Toolkit or IBM Integration Explorer, you must connect to the integration node.

Before you start:

Create a broker

To connect to a remote integration node on z/OS:

In the Navigator view, or Integration Nodes view, right-click the Integration Nodes folder, and click Connect to a Remote Integration Node.
In the Connect to an integration node wizard, enter the following values:
1. The value for the Queue Manager name that your remote integration node is using.
2. The Host name or IP address of the machine on which your integration node is running.
3. The TCP Port on which the WebSphere® MQ queue manager is listening (the default is 1414). This property must be a valid positive number.
4. Optional: The name of the server-connection channel in the SVRCONN Channel Name field. The channel has a default name of SYSTEM.BKR.CONFIG.
  You can create more than one server-connection channel and define a different SSL certificate on each channel to enforce; for example, users with view access on to one channel and users with deploy access on to a different channel.
  
  You can then create WebSphere MQ exits on each channel to provide additional authentication of the WebSphere MQ message sent to the integration node.
  You must create the server-connection channel manually on the queue manager for the integration node by using one of the following options:
  - The WebSphere MQ runmqsc command to create a channel with options CHLTYPE(SVRCONN) and TRPTYPE(TCP).
  - The WebSphere MQ Explorer to create a server-connection channel with the transmission protocol set to TCP.
  For more information see your WebSphere MQ documentation.
  The default name of SYSTEM.BKR.CONFIG is assumed if you do not change the name, or attempt to delete it. The name of the server-connection channel is changed only if you enter another name in place of SYSTEM.BKR.CONFIG.
5. Optional: The Class of the Security Exit required to connect to the WebSphere MQ queue manager. This property must be a valid Java™ class name, but you can leave this field blank if it does not apply to your domain connection.
6. Optional: The JAR File Location for the Security Exit required to connect to the WebSphere MQ queue manager. Click Browse to find the file location. You can leave this field blank if it does not apply to your domain connection. You must provide a JAR File Location if you enter a Security Exit Class.
7. Optional: The Cipher Suite, Distinguished Names, CRL Name List, Key Store, and Trust Store parameters are required to enable SSL. For more information, see Implementing SSL authentication. The Cipher Suite field displays available cipher suites. Click More to configure Custom SSL Cipher Suites in the IBM Integration Preferences window. If a Cipher Suite is not specified, all of the other fields in the SSL section are unavailable.
Click Finish to connect to the remote integration node.

You can now view properties and configure your integration node by using the IBM Integration Toolkit or IBM Integration Explorer.

be10210_.htm |

Last updated Friday, 21 July 2017