WebSphere Message Brokers
File: ae03370_
Writer: Bill Oppenheimer

Task topic

This build: July 31, 2007 21:27:19

Creating a domain connection

This topic describes how to create a domain connection.

Before you start:

You must complete the following tasks:
This topic shows you how to:

To create a domain connection:

  1. Switch to the Broker Administration perspective.
  2. Right-click Domain Connection in the Broker Administration Navigator view.
  3. Click New > Domain Connection to open the Create a Domain Connection wizard.
  4. In the Create a Domain Connection wizard, enter:
    1. The value for the WebSphere MQ Queue Manager Name that the Configuration Manager is using. This property is mandatory.
    2. The Host name or IP address of the machine on which the Configuration Manager is running (the default is localhost). This property is mandatory.
    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 Configuration Manager.

      You must create the server-connection channel manually on the Configuration Manager's queue manager 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.
      Note: The JAR File Location is required if a Security Exit Class is entered.
    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 Broker Administration Preferences window. If a Cipher Suite is not specified, all of the other fields in the SSL section are unavailable.

      You can configure several domain connections in your workspace. Each domain connection has to address a different Configuration Manager, which needs to have a different WebSphere MQ Queue Manager Name, Host name, or TCP Port number. An error message is displayed in the Create a Domain Connection wizard if you try to create a second broker domain using the same Queue Manager Name, Host name, and Port number.

  5. Click Next to begin the domain connection to the Configuration Manager.
  6. If you click Cancel, the Create a Domain Connection wizard closes, forcing disconnection from the domain.
  7. After the domain connection has been made, enter:
    1. The name of your Server Project. The Server Project is the container for your domain connection. If you have not already created a server project, you can specify the name of a new project here. The server project is created with the domain connection.
    2. The Connection name. The Connection name is the name that you give to the .configmgr file that contains the parameters to connect to the Configuration Manager.
  8. Click Finish to create the domain connection.

    The new domain connection is added to the Broker Administration Navigator view, in Domain Connections. The server project holds the .configmgr domain connection file.

    The view of the broker domain is displayed in the Domains view.

Related concepts
Broker domains
Configuration Manager
Security exits
Related tasks
Creating a Configuration Manager
Modifying domain connection properties
Deleting a domain connection
Connecting to and disconnecting from the broker domain
Using security exits
Starting the WebSphere MQ channels and listeners
Implementing SSL authentication
Related reference
Broker Administration perspective
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:27:19

ae03370_ This topic's URL is: