Singleton services offer one of the highest qualities of service (QOS) but are very susceptible to single point of failure. To address this issue, WebLogic Server offers a solution called migration. The process of moving the entire server instance from one physical machine to another upon failure is called Whole Server Migration (WSM). On the other hand, moving only the affected subsystem services from one server instance to another running server instance is called Service Migration. For more information on migration, see here.
In an Oracle SOA Suite domain deployed in Kubernetes cluster, the Whole Server migration is not supported, Service level migration is supported with DB leasing, however Consensus leasing is not supported.
This section describes the steps to perform Java Messaging Service (JMS) automatic service migration (ASM) in an Oracle SOA Suite domain setup. See here for more information on this process.
Log in to the Administration Console URL of the domain.
For example: http://<LOADBALANCER-HOST>:<port>/console
In the home page, click Clusters. Then click the cluster that you want to use for migration. For example, soa_cluster.
Click the Migration tab and then click Lock & Edit in the Change Center panel. Verify that:
Database.ACTIVE.WLSSchemaDataSource) for migration.(Optional) Click New to create a new data source.
Click Save.
Browse to Environment -> Clusters -> Migratable Targets.
For each migratable Managed Server (for example, soa_server1), go to the Migration tab and set Service Migration Policy to Auto-Migrate Exactly-Once-Services.
Click Save.
Click Activate Changes in the Change Center panel.
Restart the entire Oracle SOA Suite domain using these steps.
Note: Do not restart servers from the Administration Console.