Adding MQ Connections

Before you begin

MQ Connection resources and MQ transports require the version 6 WebSphere MQ client library, which is not bundled with the ALSB installer. You can obtain the WebSphere MQ 6.0 client library from the IBM Web site at http://www-306.ibm.com/software/integration/wmq/library/.

To use MQ Connection resources and the native MQ transport in ALSB, you must add the MQ client library to the classpath. One option is to copy it to your DOMAIN_NAME/lib directory, where DOMAIN_NAME is the name of the directory in which you located the domain, typically BEA_HOME\user_projects\domains\DOMAIN_NAME.

To add a MQ Connection resource

  1. If you have not already done so, click Create to create a new session or click Edit to enter an existing session. See Using the Change Center.
  2. Select Project Explorer, then select a project or folder in which to add the MQ Connection resource. The Project/Folder View page is displayed.
  3. From the Create Resource drop-down list, select MQ Connection from under Utility to display the Create a New MQ Connection Resource page.
  4. Specify the connection parameters shown in Table 8-2.

    Table 8-2 MQ Connection Parameters 
    Property
    To create or edit...
    Resource Name
    Enter a unique name for this MQ Connection resource.
    Resource Description
    Enter a description for the MQ Connection resource.
    Connection Type
    Select one of the following modes for connecting to the MQ queue manager:
    • tcp mode-Use TCP/IP to connect to a queue manager that does not reside on the same machine as ALSB.
    • binding mode-Use the bindings mode to connect to a queue manager that is located on the same machine as ALSB.
    MQ Host Name
    For tcp mode connections only:
    Enter the host name of the MQ queue manager.
    MQ Port Number
    For tcp mode connections only:
    Enter the port number of the MQ queue manager listener.
    MQ Queue Manager Name
    Enter the name of the MQ queue manager to which to connect.
    Queue Manager CCSID
    For tcp mode connections only:
    The coded character set identifier (CCSID) to be used when establishing a connection. The CCSID is used mainly for internationalization support.
    MQ Queue Manager Channel Name
    For tcp mode connections only:
    Enter the queue manager server connection channel name.
    SSL Required
    For tcp mode connections:
    Select the check box to use SSL for sending messages. Only server-side SSL will be enabled when the 2-way SSL Required option is not selected.
    Cipher Suite
    This option is available only when the SSL Required check box is selected.
    Select the Cipher Suite algorithm to be used by SSL.
    The Cipher Suite algorithm is used to encrypt and decrypt message communications between the WebSphere MQ server and the WebSphere MQ client. Thus a Cipher Suite algorithm must be specified when using SSL to communicate with a WebSphere MQ server.
    2-way SSL Required
    This option is available only when the SSL Required check box is selected.
    Select the check box to enable both client-side and server-side SSL authentication.
    Reference to the Service Key Provider
    If you selected 2-way SSL Required, you must provide a reference to the service key provider for obtaining the appropriate key store and trust store information.
    Enter the path (project/folder) and name of a service key provider, or click Browse to select one from the Select Service Key Provider page.
    Reference to the Static Service Account
    For tcp mode connections only:
    Required for user name and password authentication. Enter the path (project/folder) and name of a static service account, or click Browse to select service accounts from a browser.
    WebSphere MQ Version
    Select the WebSphere MQ version:
    Connection Pool Size
    Enter the size of the MQ connection pool.
    Connection Timeout
    Enter the time interval in seconds after which unused connections are destroyed.

  5. Click Save. The MQ Connection resource is created and saved in the current session.
  6. To end the session and deploy the configuration to the run time, click Activate under Change Center.