Skip navigation.
Downloads | Product Documentation | Support

Administration Console Online Help

# Configure connection factory client parameters

After you configure a connection factory, you can define various client parameters concerning how a JMS server should behave with regard to its clients. For example, you can specify the Client ID a durable subscriber should have when using a connection factory.

To configure client parameters on a connection factory:

1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
2. In the Administration Console, navigate to the connection factory resource that you want to configure:
   - Navigate to JMS Resources in System Modules
   - Navigate to JMS resources in an application module
3. Click the Configuration > Client tab.
4. On the Client page:
   1. In Client ID for Durable Subscribers, specify the Client ID for a durable subscriber that uses this JMS connection factory. Configuring this value prevents more than one JMS client from using a connection from the factory.
   2. In Message Maximum per Session, specify the maximum number of messages that can exist for an asynchronous session and that have not yet been passed to the message listener. When the Prefetch Mode for Synchronous Consumers field is enabled, this value also affects synchronous sessions with a message consumer that will prefetch messages in one server access.
   3. In Multicast Overrun Policy, select the policy to use (Keep Old or Keep New) when the number of outstanding multicast messages reaches the value specified in the Messages Maximum per Session field and some messages must be discarded.
   4. In Allow Close() Within onMessage(), select whether the connection factory creates message consumers that allow a `close()` or `stop()` method to be issued within its onMessage() method call.
   5. In Prefetch Mode for Synchronous Consumers, specify whether a synchronous message consumer will prefetch messages using the maximum number of messages defined in the Message Maximum per Session field.
   6. In Acknowledge Policy, specify the acknowledge policy (All or Previous) for non-transacted sessions that use the `CLIENT_ACKNOWLEDGE` mode.

   For more information about these fields, see Configuration Options.

5. Save your changes:
   - Save Changes to JMS Resources in System Modules
   - Save changes to JMS resources in an application module
6. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
   Not all changes take effect immediately—some require a restart (see Use the Change Center).