5-12 Programming Advanced Features of JAX-WS Web Services for Oracle WebLogic Server
Each of these steps is described in more detail in the following sections. In addition, the following topics are discussed:
■
Section 5.11, Grouping Messages into Business Units of Work Batching
—Describes how to group messages into business units of work—also called batching—to improve performance when using reliable messaging.
■
Section 5.12, Client Considerations When Redeploying a Reliable Web Service
—Describes client considerations for when you deploy a new version of an updated reliable WebLogic Web service alongside an older version of the same
Web service.
■
Section 5.13, Interoperability with WebLogic Web Service Reliable Messaging
—Provides recommendations for interoperating with WebLogic Web services reliable messaging.
5.3 Configuring the Source and Destination WebLogic Server Instances
You need to configure Web service persistence on the destination and source WebLogic Server instances. You deploy the reliable Web service to the destination WebLogic
Server instance, and the client that invokes the reliable Web service to the source WebLogic Server instance.
When using Web services reliable messaging, the Web services reliable messaging sequence is saved to the Web service persistent store any time its state changes.
Examples of state change include:
■
Reliable messaging state is updated creating, created, terminating, terminated, and so on.
■
Security property is updated such as security context token
■
Message is sent on the reliable messaging sequence if message buffering is enabled
■
Acknowledgement when a message arrives You can configure Web service persistence using the Configuration Wizard to extend
the WebLogic Server domain using a Web services-specific extension template. 9
Manage the life cycle of a reliable message sequence.
Optional WebLogic Server provides a client API,
weblogic.wsee.reliability2.api.WsrmClient, for use with the Web service reliable messaging. Use this API to perform common life cycle tasks
such as set configuration options, get the reliable sequence id, and terminate a reliable sequence. See
Section 5.9, Managing the Life Cycle of a Reliable Message Sequence
. 10
Update the build.xml file that is used to compile the
client Web service. Update your build.xml file to include a call to the jwsc Ant task which will
compile the reliable JWS file into a Web service. See Running the jwsc WebLogic Web Services Ant Task in Getting Started With
JAX-WS Web Services for Oracle WebLogic Server for general information about using the jwsc task.
11 Compile and deploy the
Web service client file. Compile your client file by calling the appropriate target and deploy to the
source WebLogic Server. For example: prompt ant build-clientService deploy-clientService
12 Monitor Web services
reliable messaging. Use the Administration Console to monitor Web services reliable messaging.
See Section 5.10, Monitoring Web Services Reliable Messaging
.
Table 5–6 Cont. Steps to Create and Invoke a Reliable Web Service
Step Description
Using Web Services Reliable Messaging 5-13
Alternatively, you can configure the resources required for these advanced features using the Oracle WebLogic Administration Console or WLST. For information about
configuring Web service persistence, see Section 6.3, Configuring Web Service
Persistence. You may also wish to configure buffering for Web services. For considerations and
steps to configure message buffering, see Chapter 7, Configuring Message Buffering
for Web Services.
5.4 Creating the Web Service Reliable Messaging WS-Policy File
