JMSTransport policy and binding properties
Use the -attributes parameter for the setPolicyType and setBinding commands to specify additional configuration information for the JMSTransport policy and policy set binding. Application policy sets can use the JMSTransport policy and binding.
- Use the -attributes parameter for the getPolicyType and getBinding commands to view the properties for your policy and binding configuration. To get an attribute, pass the property name to the getPolicyType or getBinding command.
- Use the -attributes parameter for the setPolicyType and setBinding commands to add, update, or remove properties from your policy and binding configurations. To add or update an attribute, specify the property name and value. The setPolicyType and setBinding commands update the value if the attribute exists, or adds the attribute and value if the attribute does not exist. To remove an attribute, specify the value as an empty string (""). The -attributes parameter accepts a properties object.

To support a mixed-cell environment, WebSphere Application Server supports Version 7.0 and Version 6.1 bindings. General cell-level bindings are specific to Version 7.0 and later Application-specific bindings remain at the version that the application requires. When the user creates an application-specific binding, the application server determines the required binding version to use for application.
JMSTransport policy properties
Use the JMSTransport policy set to configure JMS transport for applications that use the Java Messaging Service (JMS) to exchange request and response messages.
- requestTimeout
- Specifies the request timeout value. The request timeout value is the amount of time, in seconds, that the client waits for a response after sending the request to the server. The default value is 300 seconds. If you specify an integer value of zero or less, the system sets the requestTimeout property to the default value of 300 seconds. No maximum value exists for this property.
- allowTransactionalAsyncMessaging
- Specifies whether a client uses transactions in one-way or asynchronous two-way requests. The default value for this property is false. Set the value of this property to true to enable transactional messaging. When enabled, the client runtime exchanges SOAP request and response messages with the server over the JMS transport in a transactional manner if the client operates under a transaction.
- 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. Then, the client receives the reply message after the server transaction is committed.
AdminTask.setPolicyType('[-policySet "JMS custom" -policyType JMSTransport
-attributes "[[requestTimeout 300][allowTransactionalAsynMessaging false]]"]')
JMSTransport binding properties
- outRequestBasicAuth:userid
- Specifies the user name or basic authentication of outbound service requests.
- outRequestBasicAuth:password
- Specifies the password for basic authentication of outbound service requests.
AdminTask.setBinding('[-bindingLocation "" -bindingName generalCellWideBind1
-policyType JMSTransport -attributes "[[outRequestBasicAuth:userid myID] [outRequestBasicAuth:password myPW]]"]')