Administration Console Online Help

Configure Web service
persistence

WebLogic Server provides a default Web service persistence store that
provides a built-in, high-performance storage solution for Web services.
The Web service persistence store is used by advanced features, such as
Web services reliable messaging, to support long running requests and to
survive server restarts.

The following table describes the components of the Web service
persistence store.

Component

Description

Logical store

Provides the business configuration requirements and
connects the Web service to the physical store and buffering
queue.

Physical store

Handles the I/O operations to save and retrieve data from
the physical storage (such as file, DBMS, and so on).

Buffering queue

Stores buffered requests and responses for the Web
service.

You can configure Web service persistence at the following levels:
WebLogic Server and Web service endpoint. The Web service persistence
configured at the server level defines the default persistence store for
all Web services and clients running on that server.

Use one of the following methods to configure Web service persistence
for WebLogic Server:

When creating or extending a domain using Configuration Wizard,
you can apply the WebLogic Advanced Web Services for JAX-WS extension
template (wls_webservices_jaxws.jar) to configure automatically the
resources required to support the Web services persistence store.
Although use of this extension template is not required, it makes the
configuration of the required resources much easier. For detailed
steps, see "Configuring Your Domain for Advanced Web Services
Features" in Getting Started With JAX-WS Web Services for
Oracle WebLogic Server. For a description of the resources that
are created by default, see "Resources Required by Advanced Web Service
Features" in Getting Started With JAX-WS Web Services for
Oracle WebLogic Server..

Manually configure the resources required for Web service
persistence, as described below.

For more information about Web service persistence and its
configurable components, see "Managing the Persistence of Web Services" in
Programming Advanced Features of JAX-WS Web Services for Oracle
WebLogic Server.

To configure Web service persistence manually:

Note: You can name the resources described in the following procedure as
desired, except the Work Manager; it must be named
weblogic.wsee.mdb.DispatchPolicy. You should not modify
the names of resources in a production environment.

If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).

Create a JMS module that defines the JMS resources needed for
advanced Web services. All associated targets (JMS servers targeted to
a server) on this JMS module will be used to support JAX-WS Web
services. All servers to which this module is targeted must have the
proper Web services resources configured.

Note: It is strongly recommended that you configure the JMS
module as a uniform distributed destination (UDD).

Create a physical store that will be used by the WebLogic Server
to handle the I/O operations to save and retrieve data from the
physical storage (such as file, DBMS, and so on). For details, see
Create file
stores or
Create JDBC
stores,
depending on the type of physical store you want to create.

In a single server environment, target the persistent store (for
example, WseeFileStore) to the single WebLogic
Server instance. In a clustered environment, configure a separate
physical store for each Managed Server in the cluster (for example,
WseeFileStore_servername).

Create a JMS server that uses the physical store you created in
the preceding step. For details, see Create JMS
servers.

In a single server environment, target the JMS server (for
example, WseeJaxwsJmsServer) to the single WebLogic
Server instance. In a clustered environment, configure a separate
JMS server for each Managed Server in the cluster (for example,
WseeJaxwsJmsServer_servername).

Create a Store-and-Forward (SAF) agent that uses the physical
store you created in a previous step. A separate SAF agent is
configured on each Managed Server, as specified by server_name.
The SAF agent uses WseeFileStore_server_name
as the physical store. Target the SAF agent to the source WebLogic
Server instance. For details, see Create Store-and-Forward
agents.

In a single server environment, target the SAF agent (for
example, ReliableWseeSAFAgent) to the single
WebLogic Server instance. In a clustered environment, configure a
separate SAF agent for each Managed Server in the cluster (for
example,
ReliableWseeSAFAgent_servername).

In a single-server environment, target the queues to the JMS
server created in a previous step. In a clustered environment,
create a JMS uniform distributed destination (UDD) and target it to
the JMS subdeployment. For details, see Configure JMS system modules
and add JMS resources.

Create a Work Manager named
weblogic.wsee.jaxws.mdb.DispatchPolicy to enable the
Web service to execute multiple work items concurrently within a
container. For details, see Create application-scoped
Work Managers.

To configure
the logical store at the WebLogic Server level:

In the left pane of the Administration Console, select
Environment then Servers.

In the right pane, click the name of the server for which you
want to configure the logical store.

- To create a new logical store, click New and provide
values for the fields. Click Finish to create the new
logical store.

- To edit an existing logical store, click the name of the
logical store in the table, edit property values, as required,
and click Save to save the new configuration values.

- To delete an existing logical store, click the checkbox
next to the logical store(s) that you want to delete, and click
Delete.

To configure the default logical store at the Web service
endpoint (port) level:

In the left pane of the Administration Console, select
Deployments.

In the right pane, navigate within the Deployments
table until you find the Web service for which you want to view
the configuration.

Note: Web services are deployed as part of an
Enterprise application, Web application, or EJB. To understand
how Web services are displayed in the Administration Console,
see View installed Web
services.

In the Deployments table, click the name of the Web
service.

Select Configuration > Ports, then
click the name of the Web service endpoint that you want to
configure.

On the Web service endpoint page, select the
Persistence tab.

Enter the name of the default logical store to use.

Click Save.

To activate these changes, in the Change Center of the Administration Console, click Activate Changes. Not all changes take effect immediately—some require a restart (see Use the Change Center).