Web Service: Configuration: Port Components: SOAP Over JMS Transport
Configuration Options Related Tasks Related Topics
Using JMS transport as the connection protocol offers the following benefits over HTTP/S: reliability, scalability, and quality of service. As with Web service reliable messaging, if WebLogic Server goes down while the method invocation is still in the queue, it will be dealt with as soon as WebLogic Server is restarted. When a client invokes a Web service, the client does not wait for a response from the invoke, and the execution of the client can continue. Use this page to customize the SOAP over JMS transport configuration on the Web service endpoint.
Name Description Lookup Variant
String value that specifies the method used for looking up the specified destination name. This value must be set to jndi to support JMS transport in this implementation.
String value. Destination Type, specifying the destination type. Valid values include QUEUE(default) and TOPIC.
String value. destinationName, specifying the jndi name of the destination queue or topic.
JNDI Connection Factory Name
String value that specifies the JNDI name of the connection factory that is used for establishing a JMS connection.
JNDI Initial Context Factory Class Name
String value. JNDI InitialContextFactory, specifying the name of the initial context factory class used for JNDI lookup. This value maps to the java.naming.factory.initial property.
String value. The JNDI provider URL.
JNDI Context Parameter
String value. jndiContextParameter, specifying additional JNDI properties. Each property is specified using name-value pairs, separated by semicolons (;). For example: name1=value1;...;nameN=valueN. The properties are added to the java.util.Hashtable sent to the InitialContext constructor for the JNDI provider.
String value. Specify activation configuration properties passed to the JMS provider. Each property is specified using name-value pairs, separated by semicolons (;). For example: name1=value1;...;nameN=valueN
String value. The delivery mode indicates whether the request message is persistent. Valid values are PERSISTENT or NON_PERSISTENT.
Time To Live (milliseconds)
String value. Specify the lifetime, in milliseconds, of the request message. A value of 0 indicates an infinite lifetime. On the service side, timeToLive also specifies the expiration time for each MDB transaction.
Integer value. JMS priority associated with the request and response message. Specify this value as a positive Integer from 0, the lowest priority, to 9, the highest priority.
Reply To Name
String value. Specify the JNDI name of the JMS destination to which the response message is sent. For a two-way operation, a temporary response queue is generated by default. Using the default temporary response queue minimizes the configuration that is required. However, in the event of a server failure, the response message may be lost. This preoperty enables the client to use a previously defined, "permanent" queue or topic rather than use the default temporary queue or topic, for receiving replies. The value maps to the JMSReplyTo JMS header in the request message.
String value. Specify the port component name of the Web service. This value is used by the service implementation to dispatch the service request. If not specified, the service name from the WSDL or @javax.jms.WebService annotation is used. This value maps to the SOAPJMS_targetService JMS message property.
String value. SOAP/JMS Binding Version.
String value. Specify the message type to use with the request message. Valid values are BYTES and TEXT.
Run As Principal
String value. Specify the principal to run the listening MDB.
Run As Role
String value. Specify the role to run the listening MDB.
MDB Per Destination
Boolean value. One MDB instance for each destination - true One MDB instance for each destination - false One MDB instance for each service.
Enable HTTP WSDL Access
Boolean value. enable the HTTP WSDL accessibility.
- Install a Web service
- Start and stop a Web service
- Configure Web services
- Attach a WS-Policy file to a Web service
- View the SOAP message handlers of a Web service
- View the WSDL of a Web service
- Test a Web service
- Monitor SOAP Web services
- Monitor SOAP Web service clients