Use the JMS Service page in the Admin Console to configure properties to be used by all JMS connections. In the Admin Console, select Configuration>Java Message Service. In the JMS Service page, you can control the following general JMS settings.
Select Startup Timeout interval, which indicates the time that Application Server waits for the JMS service to start before aborting the startup.
Select JMS Service type, which decides whether you manage a JMS Service on a local or a remote host.
Specify Start Arguments to customize the JMS service startup.
Select Reconnect checkbox to specify whether the JMS service attempts to reconnect to a message server (or the list of addresses in the AddressList) when a connection is lost.
Specify Reconnect Interval in terms of number of seconds. This applies for attempts on each address in the AddressList and for successive addresses in the list. If it is too short, this time interval does not give a broker time to recover. If it is too long, the reconnect might represent an unacceptable delay.
Specify the number of reconnect attempts. In the field, type the number of attempts to connect (or reconnect) for each address in the AddressList before the client runtime tries the next address in the list.
Choose the default JMS host.
In the Address List Behavior drop-down list, choose whether connection attempts are in the order of addresses in the AddressList (priority) or in a random order (random).
In the Address List Iterations field, type the number of times the JMS service iterates through the AddressList in an effort to establish (or reestablish) a connection.
In the MQ Scheme and MQ Service fields, type the Message Queue address scheme name and the Message Queue connection service name if a non-default scheme or service is to be used.
Values of all these properties can be updated at run time too. However, only those connection factories that are created after the properties are updated, will get the updated values. The existing connection factories will continue to have the original property values. Also, for almost all of the values to take effect, the application server needs to be restarted. The only property that can be updated without having to restart the application server is the default JMS host.
For detailed descriptions of all the settings and properties mentioned above, you can see the Admin Console Online Help.
Changing the provider and host to a remote system causes all JMS applications to run on the remote server. To use both the local server and one or more remote servers, create a connection factory resource with the AddressList property to create connections that access remote servers.