Last updated on MARCH 08, 2017
Applies to:Oracle Access Manager - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
The goal of this document is to cover the use of editOAMServer and displayOAMServer in online mode as the Oracle documentation ( http://docs.oracle.com/cd/E21764_01/web.1111/e13813/custom_infra_security.htm#CHDFEICH ) is not accurate at the time of writing. It contains some facts and examples of use made on a test environment.
Note: Generally speaking, any WLST command related to OAM configuration must be used after the first start of the AdminServer. This phase is required to initialize internal objects and configuration files as explained in the Oracle® Fusion Middleware Administrator's Guide for Oracle Access Management 11g Release 2 (11.1.2) :
Starting the AdminServer the first time can take an unusually long time: 12-15 minutes, for example. This process must not be interrupted or terminated. Otherwise, policy data might be corrupted.
If the startWebLogic.cmd (Windows; or startWebLogic.sh command on Linux) is stopped for any reason (whether accidently or a system crash or a reboot, for example), policy data might be corrupted. This would require removal and recreation of the domain and rerunning the RCU to create the OAM schema.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms