Configure Replication Groups Configure Migratable Targets for Pinned Services

10-18 Using Clusters for Oracle WebLogic Server 1. Set the DebugConfigInfo parameter in web.xml to ON. 2. Use a Web browser to access the following URL: http:myServer:portplaceholder.jsp?__WebLogicBridgeConfig Where: myServer is the Managed Server on the proxy machine where HttpClusterServlet runs, port is the port number on that server that is listening for HTTP requests, and placeholder.jsp is a file that does not exist on the server. The plug-in gathers configuration information and run-time statistics and returns the information to the browser. For more information, see Parameters for Web Server Plug-ins in Using Web Server Plug-ins With WebLogic Server.

10.2.10 Configure Replication Groups

To support automatic failover for servlets and JSPs, WebLogic Server replicates HTTP session states in memory. You can further control where secondary states are placed using replication groups. A replication group is a preferred list of clustered instances to be used for storing session state replicas. If your cluster will host servlets or stateful session EJBs, you may want to create replication groups of WebLogic Server instances to host the session state replicas. For instructions on how to determine which server instances should participate in each replication group, and to determine each server instances preferred replication group, follow the instructions in Section 6.2.1.2, Using Replication Groups. Then follow these steps to configure replication groups for each WebLogic Server instance: To configure replication groups for a WebLogic Server instance:

1. Open the WebLogic Server Administration Console.

2. Select Environments Servers.

3. In the table, select the name of the server you want to configure.

4. Select the Cluster page.

5. If you have not already done so, click Lock Edit in the top left corner of the

Console. 6. Enter values for the following attribute fields: ■ Replication Group: Enter the name of the replication group to which this server instance belongs. ■ Preferred Secondary Group: Enter the name of the replication group you would like to use to host replicated HTTP session states for this server instance.

7. Click Save to save your changes.

8. Click Activate Changes in the top left corner to activate your changes.

10.2.11 Configure Migratable Targets for Pinned Services

WebLogic Server enables you to configure an optional migratable target, which is a special target that can migrate from one server in a cluster to another. As such, a Setting up WebLogic Clusters 10-19 migratable target provides a way to group pinned services that should move together. When the migratable target is migrated, all services hosted by that target are migrated. Pinned services include JMS-related services for example, JMS servers, SAF agents, path services, and persistent stores or the JTA Transaction Recovery Service. If you want to use a migratable target, configure the target server list before deploying or activating the service in the cluster. If you do not configure a migratable target in the cluster, migratable services can be migrated to any available WebLogic Server instance in the cluster. For more details on migratable targets, see Section 8.1.2, Understanding Migratable Targets In a Cluster.

10.2.12 Configure Clustered JDBC