Using Web Service Persistence in a Cluster

6-6 Programming Advanced Features of JAX-WS Web Services for Oracle WebLogic Server

6.3.2 Configuring Web Service Persistence for a Web Service Endpoint

By default, Web service endpoints use the Web service persistent store defined for the server. You can override the logical store used by the Web service endpoint using the Administration Console. For more information, see Configure Web service persistence in Oracle WebLogic Server Administration Console Help.

6.3.3 Configuring Web Service Persistence for Web Service Clients

For information about configuring persistence for Web service clients, see Configuring Web Service Clients in Getting Started With JAX-WS Web Services for Oracle WebLogic Server.

6.4 Using Web Service Persistence in a Cluster

The following provides some considerations for using Web services persistence in a cluster: ■ If you create or extend a clustered domain using the WebLogic Advanced Web Services for JAX-WS Extension template wls_webservices_jaxws.jar, the resources required to support Web services persistence in a cluster are automatically created. For more information, see Configuring Your Domain for Advanced Web Services Features in Getting Started With JAX-WS Web Services for Oracle WebLogic Server Response Buffering Queue JNDI Name JNDI name for the response buffering queue. If this property is not set, then the request queue is used, as defined by the Request Buffering Queue JNDI Name property. If you create or extend a domain using the Web service extension template, a buffering queue named weblogic.wsee.RequestBufferedRequestErrorQueue is created by default. Note : This property is ignored if Persistence strategy is set to In Memory. Cleaner Interval Interval at which the logical store will be cleaned. For more information, see Section 6.5, Cleaning Up Web Service Persistence The value specified must be a positive value and conform to the XML schema duration lexical format, PnYnMnDTnHnMnS, where nY specifies the number of years, n M specifies the number of months, nD specifies the number of days, T is the datetime separator, nH specifies the number of hours, nM specifies the number of minutes, and nS specifies the number of seconds. This value defaults to PT10M 10 minutes. Note : This field is available when editing the logical store only. When creating the logical store, the field is set to the default, PT10M 10 minutes. Default Maximum Object Lifetime Default value used as the maximum lifetime of an object. This value can be overridden by the individual objects saved to the logical store. The value specified must be a positive value and conform to the XML schema duration lexical format, PnYnMnDTnHnMnS, where nY specifies the number of years, n M specifies the number of months, nD specifies the number of days, T is the datetime separator, nH specifies the number of hours, nM specifies the number of minutes, and nS specifies the number of seconds. This value defaults to P1D one day. Note : This field is available when editing the logical store only. When creating the logical store, the field is set to the default, P1D one day. Table 6–5 Cont. Configuration Properties for the Logical Store Property Description Managing Web Service Persistence 6-7 ■ To facilitate service migration, it is recommended that the same physical storage resource be used for both persistent state and message buffering. To ensure that the buffering queue and physical store reference the same physical storage resource, you configure the Request Buffering Queue JNDI Name property of the logical store, as described in Section 6.3.1, Configuring the Logical Store . ■ It is recommended that the buffering queues be defined as JMS uniform distributed destinations UDDs. JMS defines a member queue for the UDD on each JMS Server that you identify. Because a logical store is associated with a physical store through the defined buffering queue, during service migration, this allows a logical store to use the new physical stores seamlessly for the member queues that migrate onto the new server. ■ It is recommended that you target the JMS Server, store-and-forward SAF service agent, and physical store file store resources to migrateable targets. For more information, see Resources Required by Advanced Web Service Features in Getting Started With JAX-WS Web Services for Oracle WebLogic Server. For example, consider the two-node cluster configuration shown in Figure 6–2 . The domain resources are configured and targeted using the guidelines provided above. Figure 6–2 Example of a Two-Node Cluster Configuration Before Migration The following figure shows how the resources on Server1 can be easily migrated to Server2 in the event Server1 fails. 6-8 Programming Advanced Features of JAX-WS Web Services for Oracle WebLogic Server Figure 6–3 Example of a Two-Node Cluster Configuration After Migration

6.5 Cleaning Up Web Service Persistence