WAS v8.5 > Reference > SetsJMS transport policy settings page
Use this page to configure settings for the JMS transport policy. We can configure a client that is using the JMS transport policy to exchange request and response messages with the server.
To view this dmgr console page:
- Click Services, expand Policy sets, and click Application policy sets.
- Click New to create a new application policy set and provide a name for it in the Name field.
- Under the Policy heading, click Add and select JMS transport.
- Click OK or Apply.
- Click JMS transport to view the JMS transport policy settings panel.
This dmgr console page applies only to JAX-WS applications.
We can only configure a policy through a policy set. Therefore, before we can configure the JMS transport policy, a policy set must exist containing the JMS transport policy.
To customize a policy set containing the JMS transport policy, create a new policy set, import a copy of a policy set from the default repository, or we can import an existing policy set from your specified location. After we have an editable policy set, we can add the JMS transport policy to your policy set.
After you customize values for the JMS transport policy, these values now apply for the policy set containing that customized JMS transport policy. We can attach this policy set containing your customized JMS transport policy to the application, its services, endpoints, or operations. This change affects all JAX-WS applications to which that policy set is attached. To learn more about attaching policy sets to applications, read about managing policy sets for service providers and service clients at the application level.
Client JMS connection properties - Request timeout
Specifies the request timeout value. The request timeout value is the amount of time the client waits for a response after sending the request to the server. Default is 300 seconds.
Client JMS connection properties - Allow transactional messaging for one-way and asynchronous operations
Specifies to enable a client to use transactions in one-way or asynchronous two-way requests. Select this check box to enable transactional messaging.
If this option is selected, the client runtime exchanges SOAP request and response messages with the server over the JMS transport in a transactional manner if the client is operating under a transaction. Therefore, the client transaction is used to send the SOAP request message to the destination queue or topic, and the server receives the request message only after the client commits the transaction. Similarly, the server receives the request message under the control of a container-managed transaction and sends the reply message, if applicable, back to the client using that same transaction. The client then receives the reply message only after the server transaction is committed.
If this option is not selected, the client and server runtimes perform messaging operations in a non-transactional manner.
Transactional messaging operations are not supported for two-way synchronous operations as this leads to a deadlock condition. .
Related
Configure the JMS transport policy
Modify policies
Manage policy sets and bindings for service providers at the application level
Manage policy sets and bindings for service clients at the application level
Manage policy sets
Define and managing policy set bindings
Use SOAP over JMS to transport web services
Reference:
JMS transport bindings
Application policy sets page
Application policy set settings