Case Study: Moving 12c Oracle Identity Manager to a New Host Using the copyBinary and CHGHOST Utilities
(Doc ID 2417891.1)
Last updated on OCTOBER 08, 2021
Applies to:Identity Manager - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
This document details the steps needed to move an existing Oracle Identity Manager installation and configuration to a new host(s) and considers only the following use case:
- Moving the application binaries and configuration to the new host and pointing them to the existing database.
If you also need to move an existing OIM database to a new host, this will need to be done as a separate exercise. See Note.2584066.1 OIM 12c: Schema Backup and Restoration using Data Pump Client Utility, if needed.
- You cannot change the topology. For example, you cannot add or remove a Managed Server and you cannot change the WebLogic Server domain name. You cannot change the port numbers.
- The paths of both the source and target instances must be the same. You cannot change them.
- You cannot move Oracle Fusion Middleware from one type of operating system to another. You can only move it to the same type of operating system.
- In a multinode environment, you can move or change the network configuration of each node separately. For example, if the Administration Server is on Host A and the Managed Servers are on Host B, you can move or change the network configuration of the Administration Servers, the Managed Servers, or both.
- The chghost utility does not support environments where SSL-only is configured. SSL-only means that either the administration port is enabled or only the SSL port is enabled.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!