Administrators can add one or more Managed Servers to the WebLogic Server domain for Oracle Access Management.

When using the WebLogic Configuration Wizard, the OAM Server is automatically registered. However, if the configuration wizard was not used, the OAM Server must be registered manually to open a communication channel.

Alternatively. You can use custom WLST commands for OAM to display, edit, or delete a server registration Any changes are automatically propagated to the Oracle Access Management Console and to every OAM Server in the cluster.

Only OAM Servers are registered with Oracle Access Management. The Oracle Access Management Console (on the WebLogic Administration Server) is not registered with itself.

Regardless of the method used to register an OAM Server, details for each instance are located on the System Configuration tab, Common Configuration section in the Oracle Access Management Console, including:

• Server name, Host, Port

Administrators can search for a specific instance registration, register a newly installed OAM Server, view, modify, or delete server registrations using the Oracle Access Management Console. For more information, see "OAM Server Registration Page".

The OAM Server communication mode can be changed after a successful agent registration. The Webgate mode needs to be at the same level as the OAM Server mode or higher for the server to continue communicating with the agent.

Communication modes for the OAP channel include:

• Open: Use this unencrypted mode if communication security is not an issue in your deployment.

• Simple: Use this Oracle-signed certificate mode if you have some security concerns, such as not wanting to transmit passwords as plain text, but you do not manage your own Certificate Authority (CA).

• Cert: Use if you want different certificates on OAM Servers and WebGates and you have access to a trusted third-party CA.

• HTTP: This mode is auto configured in WebGate user defined parameters (based on the settings in WebGate Load Balancer of Access Manager Settings page). Use this unencrypted communication mode if the paramter OAMServerCommunicationMode is set to HTTP. It is a user defined configuration parameter.

• HTTPS: This mode is auto configured in WebGate user defined parameters (based on the settings in WebGate Load Balancer of Access Manager Settings page). Use this encrypted communication mode if the paramter OAMServerCommunicationMode is set to HTTPS. It is a user defined configuration parameter.

On each individual OAM Server registration, the security mode is defined on the Proxy tab, as described in "OAM Server Registration Page".

Simple and Cert modes also require:

• Security passwords that are common to all OAM Servers and WebGates, as described in "Managing the Access Protocol for OAM Proxy Simple and Cert Mode Security".

• Appropriately signed X.509 digital certificates, as described in Securing Communication.

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.

Most Oracle Access Management functional services take up changes made through the Oracle Access Management Console without restarting OAM Server.

Users with valid Administrator credentials can register a freshly installed Managed Server (OAM Server instance) or modify an existing OAM Server registration using the Oracle Access Management Console.

Alternatively: You can use custom WLST commands to register and manage OAM Server instances. Changes are reflected in the Oracle Access Management Console and are automatically propagated to every OAM Server in the cluster.

See Also:

Access Manager WLST Commands in WebLogic Scripting Tool Command Reference for Identity and Access Management

Figure 6-1 illustrates a typical OAM Server registration page when viewed within the Oracle Access Management Console. To access the OAM Server registration page using the Oracle Access Management Console, click Configuration in the top right of the console and then click the Server Instances link on the Configuration page. From the resulting Server Instances search page, click Create in the Search Results table to display the Create: OAM Server page. See Registering a Fresh OAM Server Instance for details on how to configure this page.

Figure 6-1 OAM Server Registration Page with Proxy Tab Displayed

Description of "Figure 6-1 OAM Server Registration Page with Proxy Tab Displayed "

Individual server registration settings are described in Table 6-2.

Users with valid Administrator credentials can register a new Managed Server (OAM Server) instance using the Oracle Access Management Console. Each OAM Server must be registered to communicate with agents.

1. Install the new Managed Server instance and configure it in the Oracle WebLogic Server domain, but do not start this instance.
2. Log in to the Oracle Access Management Console and click Configuration in the top bar.
3. In the Configuration console, click Server Instances.
4. In the tab that appears, click Create OAM Server.

   The OAM Server registration page illustrated in Figure 6-1 is displayed.

5. On the Create: OAM Server page, enter details for your instance, as described in Table 6-2:

   • Server name

   • Host

   • Port

6. Proxy: Enter or select details for this OAM Proxy instance.

   • Port

   • Proxy Server ID

   • Mode (Open, Simple, or Cert)

     See Also:

     Securing Communication if you are using Simple or Cert mode

7. Click Apply to submit the configuration, which should appear in the navigation tree (or close the page without applying changes).
8. Start the newly registered server.

1. At the top of the Oracle Access Management Console, click Configuration.
2. In the Configuration console, click Server Instances.
3. In the page that appears, click Search, then double-click the target instance to display its configuration, and then proceed as follows:

   • View Only: Close the page when you finish viewing details.

   • Modify: Perform remaining steps to edit the configuration.

4. On the OAM Server page, change details for your instance, as described in Table 6-2.
5. Proxy: Change details for this OAM Proxy instance, as described in Table 6-3.

   See Also:

   Securing Communication if you are using Simple or Cert mode

6. Click Apply to submit the changes (or close the page without applying change).

Users with valid Administrator credentials can delete an OAM server registration, effectively disabling it.

1. At the top of the Oracle Access Management console, click Configuration.
2. In the Configuration console, click Server Instances.
3. In the tab that appears, double-click the target instance to confirm its details, then close the tab.
4. In the list of instances, select the target instance, click Delete in the tool bar, and confirm removal in the dialog that appears.
5. Confirm that the instance has been removed from the instance list.
6. Remove the deleted instance from the WebLogic Server Administration Console.

   The Node Manager on Managed Server host handles the rest automatically.