Download Programming WebLogic Web Services

Usin g Re lia ble SOA P Mes sag in g
For more information, see Programming WebLogic Enterprise JavaBeans at
http://e-docs.bea.com/wls/docs81/ejb/index.html and Programming WebLogic JTA at
http://e-docs.bea.com/wls/docs81/jta/index.html.
Guidelines for Programming the Java Class That Implements a Reliable Web
Service Operation
When creating a Java class-implemented Web Service whose operations can be invoked reliably,
follow these guidelines when programming the Java class:
z
If you want to roll back the transaction from the Java method, use the Java Transaction
API (JTA) to get the transaction object and then explicitly roll back the transaction.
z
Be aware exceptions thrown by the Java class never roll back the transaction.
For more information, see Programming WebLogic JTA at
http://e-docs.bea.com/wls/docs81/jta/index.html.
Configuring the Transaction
Use the Administration Console to configure the following transaction attributes:
z
Transaction time-out and limits
z
Transaction manager behavior
Configuration settings for JTA transactions are applicable at the domain level. This means that
configuration attribute settings apply to all servers within a domain. For details, see Configuring
Transactions at http://e-docs.bea.com/wls/docs81/ConsoleHelp/jta.html.
Limitations of Reliable SOAP Messaging
z
Only Web Service operations that return void can be configured to be invoked reliably.
z
One-way Web Service operations cannot be configured to be invoked reliably.
Using Reliable SOAP Messaging: Main Steps
The following procedure describes the main steps for configuring reliable SOAP messaging to
invoke a WebLogic Web Service operation. The procedure describes configuration and
code-writing tasks that take place in both the sender and receiver WebLogic Server instances.
10-6
Programming WebLogic Web Services