Configuring TIBCO EMS servers

Because the TIBCO EMS server environment can be complex, you can configure the client connection to the server environment in various ways.

1. In the search field, enter ems.
2. From the search results, enter TIBCO EMS Server.
3. Click Add.
4. Define the basic properties - Name, administrative state, and comments.
5. Define the credentials to connect to the server.
   1. In the Username field, specify the username.
   2. From the Password alias list, select the password alias.
6. Define the server environment that can be a single host, a single fault-tolerant pair of host, or a group of hosts. When defined as a group of host, load is distributed to members by using a defined algorithm. Any host in the group can be defined as a fault-tolerate pair.
   When you define a host, enter the hostname or IP address with the listening port of the TIBCO EMS server in the host:port format. Without a port, the value is 7222.

   Single host

   Enter the host in the Host field.

   Group of hosts

   Use the following steps to define the host for load distribution and as needed fault tolerance in the Load-balancing area.

   1. Click Add.
   2. Enter the host for load distribution in the Primary host field.
   3. For fault tolerance of this host, enter a backup host in the Backup host field.
   4. Click Apply to save changes to the running configuration.
   5. Repeat this step to define another host to the group.

7. In the Connection client ID field, enter the string that identifies the connection client
8. When defined as a group of hosts, select the load distribution algorithm.
9. From the TLS client profile list, select the profile to secure connections to the server.
10. Define message criteria.
    1. Set Transactional to enable or disable transactional processing. In a transacted session, a group of related messages is sent and received in a single transaction.
    2. In the Memory threshold field, enter the memory allocation for pending messages.
    3. In the Max message size field, enter the MTU for the current server.
       The MTU defines the maximum size of messages that this server can process. Messages that are larger than the specified value are dropped.
    4. From the Default message type list, select the default message type that defines the message payload. This value is used when the message type cannot be determined from message headers.
11. Define the session and connection limits. When the number of current connections is less than the connection limit, a new session request establishes a new connection.
    1. In the Total connection limit field, enter the maximum number of concurrent, open connections to allow.
    2. In the Max number of sessions per connection field, enter the maximum number of concurrent multiplexed sessions that a single connection supports.
    You define 5 total connections and 20 sessions per connection. With three active connections, a new session request generates the establishment of a fourth connection.
12. Optional: Enable automatic critical error-recovery to reestablish a connection that was closed in response to an error condition.
    1. Set Automatic retry to enable the procedure.
    2. In the Retry interval field, enter the interval between attempts.
13. Set Enable JMS-specific logging to enable or disable the enhanced JMS-specific logging facility.
14. Click Apply to save changes to the running configuration.
15. Click Save to save changes to the persisted configuration.