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 following commands and parameters in the PolicySetManagement group of AdminTask to customize the policy set configuration.
- Use the attributes parameter for the getPolicyType and getBinding commands to view the properties for the 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 the 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.
If a property name or value supplied with the attributes parameter is not valid, then the setPolicyType and setBinding commands fail with an exception. The property not valid is logged as an error or warning in SystemOut.log. However, the command exception might not contain the detailed information for the property that caused the exception. When the setPolicyType and setBinding commands fail, examine SystemOut.log for any error and warning messages that indicate that the input for the attributes parameter contains one or multiple properties that are not valid.
For transitioning users: In WAS Version 7.0, the security model is enhanced to a domain-centric security model instead of a server-based security model. The configuration of the default global security (cell) level and default server level bindings has also changed in this version of WAS ND. In the WAS V 6.1 Feature Pack for Web Services, we can configure one set of default bindings for the cell and optionally configure one set of default bindings for each server. In V7.0, we can configure one or more general service provider bindings and one or more general service client bindings. After we have configured general bindings, we can specify which of these bindings is the global default binding. We can also optionally specify general binding that are used as the default for an appserver or a security domain. trns
To support a mixed-cell environment, WAS supports V7.0 and V6.1 bindings. General cell-level bindings are specific to V7.0 Application-specific bindings remain at the version that the application requires. When the user creates an application-specific binding, the appserver determines the required binding version to use for application.
The following sections explain the policy and binding properties to configure:
JMSTransport policy properties
Use the JMSTransport policy set to configure JMS transport for applications that use the JMS to exchange request and response messages. Configure the JMSTransport policy by specifying the following attributes with the setPolicyType command:
- requestTimeout
- 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 we 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.
The following setPolicyType example command sets values for each JMSTransport binding property:
AdminTask.setPolicyType('[-policySet "JMS custom" -policyType JMSTransport -attributes "[[requestTimeout 300][allowTransactionalAsynMessaging false]]"]')
JMSTransport binding properties
Set the JMSTransport binding by specifying the following attributes with the setBinding command:
- outRequestBasicAuth:userid
- User name or basic authentication of outbound service requests.
- outRequestBasicAuth:password
- Password for basic authentication of outbound service requests.
The following setBinding example command sets values for each HTTPTransport binding property:
AdminTask.setBinding('[-bindingLocation "" -bindingName generalCellWideBind1 -policyType JMSTransport -attributes "[[outRequestBasicAuth:userid myID] [outRequestBasicAuth:password myPW]]"]')
Related concepts
WSHTTPS default policy set
Related tasks
Set the JMS transport policy
Set application and system policy sets for Web services using scripting
Related
JMS transport bindings
JMS transport policy settings
PolicySetManagement