OSM Whole Server Migration
(Doc ID 1994962.1)
Last updated on SEPTEMBER 06, 2019
Applies to:Oracle Communications Order and Service Management - Version 7.2.0 to 7.2.4 [Release 7.2]
Information in this document applies to any platform.
This KM Note provides instructions for configuring whole server migration (WSM) for Oracle Communications Order and Service Management (OSM) 7. It is targeted to system integrators and system administrators, who must work together to plan and configure a highly-available OSM solution.
Whole server migration is the mechanism built into Oracle WebLogic Server that makes it possible to move an entire server instance, along with all of its services, to a different physical machine when triggered by a platform failure event.
Whole Server Migration (WSM) is the recommend approach to complete the High Availability (HA) picture for operators of OSM. This is applicable to operators who are already running a RAC Database and a WebLogic Cluster, and who want to ensure High Availability for the entire OSM system. In this context, Whole Server Migration provides the following key functions:
1. Migration of a failed managed server to another machine, allowing the total processing capacity of the OSM system to be maintained.
2. Retrieval of pending JMS messages from a failed managed server, allowing the execution of the associated orders to resume after a successful migration.
This document is applicable for OSM releases up to and including OSM 7.2.4.x. For OSM releases 7.3.0 and higher, please see the OSM Installation Guide.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document