Configuring JMS connector accounts - self-hosted Universal Messaging

Know how to configure JMS connector accounts for self-hosted Universal Messaging, covering connection setup, message delivery, and integration essentials.

1. Go to Projects > Connectors.
   All predefined connectors are listed in the right pane.
2. Type JMS in the Search text box of the right pane.
   The matching connectors are listed.
3. Click JMS.
   The Add account wizard is displayed.
4. Enter the following details under General Settings:

   Name

   Name of the account.

   Description

   Short description about the account.

   Messaging provider template

   Select Universal Messaging for connecting to a self-hosted Universal Messaging server that is publicly accessible.

5. Click Next.
   The Connection Settings tab is displayed.
6. Enter the following details:
   1. In the Provider URL, specify the Universal Messaging realm URL that webMethods Integration uses for looking up JMS objects (destinations and connection factories) in the JNDI directory. To connect to IBM® Universal Messaging, provide the Universal Messaging realm URL in one of the following formats:- nsp://UM_host:UM_port- nsps://UM_host:UM_port - nhp://UM_host:UM_port - nhps://UM_host:UM_port
   2. In Clustered UM, set to one of the following states:
      • Yes - If the realm specified in the Provider URL is part of a cluster setup. A minimum of two URLs is mandatory. Follow the instruction in sub step c and ignore sub step d.
      • No - If the realm specified in the Provider URL is not part of a cluster setup. Follow the instructions mentioned in sub step d that follows and ignore sub step c.
   3. If the realm specified in the Provider URL is not part of a cluster setup, click Add failover node to add a failover Universal Messaging URL that webMethods Integration must connect to if the existing connection is lost.
      Repeat the previous step to add multiple failover nodes. If there is a failover setup, all objects such as queues, topics, and connection factories must be present in all failover nodes. You cannot recover messages if connectivity fails.
   4. Follow the master,
      This setting affects producer and consumer connections created that uses this account. Set one of the following values:

      Option	Description
      Enabled	webMethods Integration always connects to the master realm server in a cluster to send or receive messages. Enabled is the default option.
      Disabled	webMethods Integration connects to one of the servers that are listed to send or receive messages. You can specify the server order in the Connection retry mode option.

   5. Connection retry mode
      Select one of the following values:

      Option	Description
      Retry sequentially	webMethods Integration retries to establish connection with the servers in the order specified in the list.
      Retry randomly	webMethods Integration retries to establish a connection at random to any of the specified servers.

   6. In Connection client ID, specify a value that is used as JMS client identifier for making connection with Universal Messaging.
   7. In the JMS connection factory lookup name, specify the lookup name for the connection factory that you want to use to establish a connection with the Universal Messaging provider specified in this account.
7. Click Next.
   The Security Settings tab is displayed.
8. Enter the following details:

   Security principal

   Username for connecting to Universal Messaging to retrieve JNDI objects.

   Security credentials

   Password for connecting to Universal Messaging to retrieve JNDI objects.

   Same as JNDI credentials

   Select the checkbox if the same username and password that is mentioned under JNDI authentication must be used for Universal Messaging authentication to publish and consume messages. Otherwise, provide the following details:

   User

   Username required for authenticating with Universal Messaging to publish or consume messages.

   Password

   Password required for authenticating with Universal Messaging to publish or consume messages.

   Use SSL

   Drag the switch to right to enable a secure communication between webMethods Integration and Universal Messaging. By default, the option is disabled. Specify the following details if you have enabled SSL in the previous sub step:

   Truststore alias

   Select the truststore that contains the certificate authority (CA) of the certificates for Universal Messaging.

   Keystore alias

   Select the keystore that contains the client certificates that are used by webMethods Integration to connect with Universal Messaging.

   Key alias

   Select the alias for the key that contains the private key for connecting to Universal Messaging securely.

9. Click Next.
   The Producer Settings tab is displayed.
10. Enter the following details:

    Max retry attempts

    The number of times a publisher must retry to publish messages when transient errors are encountered. The default value is five. Setting it to zero indicates that the publisher does not retry to publish the message. You can specify a value in the range from zero to 100.

    Retry interval (in seconds)

    The duration that the publisher waits before retrying the publish action again. The default value is 10 seconds. You can specify a value in the range of 4 to 3600 (four seconds to one hour).

    Cache JMS sessions

    Drag the switch to right to enable caching for JMS sessions. By default, the option is disabled. If you enabled caching, then follow the sub steps d, e, and f.

    Minimum session pool size

    Minimum number of session objects in the session pool. The default value is One. Zero indicates that the caching is disabled.

    Maximum session pool size

    Maximum number of session objects in the session pool. The default value is 30.

    Idle timeout (in seconds)

    Duration after which webMethods Integration removes an inactive session object. A value of zero indicates that pool entries never expire. The default value is 60 seconds.

11. Click Next.
    The Advanced Settings tab is displayed.
12. Set the Create new connection per subscriber button to the right to create a new connection for each subscriber. You can increase the number of connections a subscriber can make by setting the Connection Count property under Message Processing in Subscriber settings.
13. Click Save.