Home‎ > ‎Oracle Access Manager‎ > ‎Operations‎ > ‎

Infrastructure Changes


OAM leverages the standard Oracle Logging framework (OJDL) framework for logging. This framework leverages the server specific logging configuration stored in $DOMAIN_HOME/config/fmwconfig/servers/<SERVER-NAME>/logging.xml. By default the log file is located at $DOMAIN_HOME/servers/<SERVER-NAME>/logs/SERVER-NAME-diagnostics.log

New Access Server On-boarding

OAM Server addition to support higher volume. The process documented at http://docs.oracle.com/cd/E40329_01/admin.1112/e27239/servers.htm#CIHDEJBF, http://docs.oracle.com/cd/E40329_01/admin.1112/e27239/servers.htm#BCFCGFBH (for using ui for adding new server).

Adding a new managed server to the cluster requires restarting the AdminServer to policy enable uptake. OAM Servers must be restarted to reinitialize Oracle Coherence security configuration with the new server included.

Server protocol security.
server configuration for the mode.
At least one OAM Server instance must be running in the same mode as the agent during agent registration. Otherwise, agent registration fails. After agent registration, however, you can change the communication mode of the OAM Server. Communication between the agent and server would continue to work as long as the Webgate mode is at least at the same level as the OAM Server mode or higher. The agent mode can be higher but cannot be lower. For example, of OAM Server mode is Open, agents can communicate in any of the three modes. If OAM Server mode is Simple, agents can use Simple or Cert mode. If OAM Server mode is Cert, agents must use Cert mode.

New Access Client On-boarding

OAM Client on-boarding -> think about communication mode between OAM Access Clients and servers i.e. open, simple, cert....
client configuration for the mode.