Migrate JMS Services

Use the following steps to migrate the JMS Services running on the BIP Cluster to the same migratable target as the previously created custom persistent store.

WARNING:

Ensure that JMS services on bi_server1 and the server itself are shut down so that the migration task is successful. The BIP Scheduler becomes inoperable when the server is shut down.

1. In the Oracle WebLogic Server Administration Console, under the Domain Structure section menu, click Services, Messaging, and JMS Servers from the tree.
2. In the Summary of JMS Servers pane, JMS Servers section, check the check box for the BipJmsServer (Default) if no other JMS servers were created.
3. In the Change Center section of the pane, click Lock & Edit.
4. Select the new custom persistent store that was created in the previous step from the Persistent Store drop-down list.
5. Click Save.

   Note:

   Ignore any error messages about the JMS server or SAF agent that display.
6. Click the Targets tab and select bi_server1 (migratable) from the Target drop-down list to change the target for the JMS server.
7. Click Save.
8. Click Activate Changes.

   Note:

   If there are other JMS services besides the JMS Server that need to be migrated, such as SAF agents and path services, refer to the Oracle WebLogic documentation for their migration process.