Best Practices for Targeting JMS when Configuring Automatic Service Migration

Service Migration 8-17

8.3.5.1 Special Considerations When Targeting SAF Agents or Path Service

There are some special targeting choices to consider when targeting SAF agents and a path service to migratable targets. For more information, see Section 8.1.2.6, Targeting Rules for SAF Agents and Section 8.1.2.7, Targeting Rules for Path Service.

8.3.6 Step 6: Restart the Administration Server and Managed Servers With Modified Migration Policies

You must restart the Administration Server after configuring your JMS services for automatic service migration. You must also restart any Managed Servers whose migration policies were modified.

8.3.7 Step 7: Manually Migrating JMS Services Back to the Original Server

You may want to migrate a JMS service back to the original primary server once it is back online. Unlike the JTA Transaction Recovery Service, JMS services do not automatically migrate back to the primary server when it becomes available, so you need to manually migrate these services. For instructions on manually migrating the JMS-related services using the Administration Console, see Manually migrate JMS-related services in the Oracle WebLogic Server Administration Console Help. For instructions on manually migrating the JMS-related services using WLST, see WLST Command and Variable Reference in WebLogic Scripting Tool Command Reference.

8.4 Best Practices for Targeting JMS when Configuring Automatic Service Migration

■ In most cases, it is sufficient to use the default migratable target for a server there is one default migratable target per server. An alternative is to configure one migratable target per server. See Section 8.3.3, Step 3: Configure Migratable Targets. ■ Configure one custom store per migratable target and target the store to the migratable target. See Section 8.3.4, Step 4: Configure and Target Custom Stores. ■ When configuring JMS services JMS servers and SAF agents for each migratable target, ensure that the services refer to the corresponding custom store. Then target them to each migratable target. See Section 8.3.5, Step 5: Target the JMS Services. ■ Use JMS system modules rather than deployment modules. The Administration Console only provides the ability to configure system modules. See JMS System Module Configuration in Configuring and Managing JMS for Oracle WebLogic Server. ■ Create one system module per anticipated target set and target the module to a single cluster. For example: If you plan to have one destination that spans a single JMS server and another destination that spans six JMS servers, create two modules and target both of them to the same cluster. ■ Configure one subdeployment per module and populate the subdeployment with a homogenous set of either JMS server of JMS SAF agent targets. Do not include WebLogic Server or cluster names in the subdeployment. ■ Target Connection Factories to cluster for applications running on same cluster you can use default targeting to inherit the module target, target connection 8-18 Using Clusters for Oracle WebLogic Server factory to subdeployment via Advanced Targeting for use by applications running remote to cluster. ■ For other JMS module resources, such as destinations, target using a subdeployment. Do not use default targeting. Subdeployment targeting is available via the advanced targeting choice on the Console. ■ As you add or remove JMS serversSAF agents, remember to also add or remove JMS serversSAF agents to your module subdeployments. ■ Do not target a SAF agent to cluster as it wont be able to migrate. Configure multiple independent SAF agents and target each SAF agent to a migratable target theres a default migratable target per server. Similarly, configure a custom store per SAF agent, and target each custom store to the migratable target that the SAF agent is using. ■ Custom connection factories are used to control client behavior, such as load balancing. They are targeted just like any other resource, but in the case of a connection factory, the target set has a special meaning. You can target a connection factory to a cluster, WebLogic Server, or to a JMS serverSAF agent using a subdeployment. Theres a performance advantage to targeting connection factories to exactly the JMS serversSAF agents that the client will use, as the target set for a connection factories determines the candidate set of host servers for a client connection. Targeting to the JMS serversSAF agents reduces the likelihood that client connections will connect to servers that dont have a JMS serverSAF agent in cases where there isnt a SAF agent on every cluster server. If theres no JMS serverSAF agent on a connection host, the client request must always double-hop the route from the client, to the connection host server, then ultimately on to the JMS serverSAF agent. See also Best Practices for JMS Beginners and Advanced Users in Configuring and Managing JMS for Oracle WebLogic Server.

8.5 Roadmap for Configuring Manual Migration of JMS-related Services