To administer a remote broker
that is deployed on z/OS® by using the WebSphere® Message Broker Toolkit or WebSphere Message Broker Explorer, you must
connect to the broker.
To connect to a remote broker on z/OS:
- In the Navigator view, or Brokers view, right-click the Brokers folder, and click .
- In the Connect to a broker wizard,
enter the following values:
- The value for the Queue Manager name that
your remote broker is using.
- The Host name or IP address of
the machine on which your broker is
running.
- The TCP Port on which the WebSphere MQ queue manager is listening (the
default is 1414). This property must be a valid positive number.
- 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 broker.
You must create the
server-connection channel manually on the queue manager for the
broker 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.
- 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.
- 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.
- 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 Broker
Administration 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 broker.
You can now view properties and configure
your broker by using the WebSphere Message Broker Toolkit or WebSphere Message Broker Explorer.