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 the AdminTask object to customize
your policy set configuration.
- 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.
Note: 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 that is not valid is logged as an
error or warning in the SystemOut.log file. 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 the SystemOut.log file
for any error and warning messages that indicate that the input for
the -attributes parameter contains one or multiple
properties that are not valid.
Note: This topic references one or more of the application server log files. As a
recommended alternative, you can configure the server to use the High Performance Extensible Logging
(HPEL) log and trace infrastructure instead of using SystemOut.log ,
SystemErr.log, trace.log, and
activity.log files on distributed and IBM®
i systems. You can also use HPEL in conjunction with your native z/OS® logging facilities. If you are using HPEL, you can access all of your log and trace
information using the LogViewer command-line tool from your server profile bin directory. See the
information about using HPEL to troubleshoot applications for more
information on using HPEL.
For transitioning users: In WebSphere Application
Server Version 7.0 and later, the security model was 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 the product. In the
WebSphere Application Server Version 6.1 Feature Pack for Web Services, you can configure one set of
default bindings for the cell and optionally configure one set of default bindings for each server.
In Version 7.0 and later, you can configure one or more general service provider bindings and one or
more general service client bindings. After you have configured general bindings, you can specify
which of these bindings is the global default binding. You can also optionally specify general
binding that are used as the default for an application server or a security domain.
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.
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 Java Messaging Service (JMS) to exchange request and response messages.
Configure the JMSTransport policy by specifying
the following attributes with the setPolicyType command:
- 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 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
Configure
the JMSTransport binding by specifying the following attributes with
the setBinding command:
- 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.
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]]"]')