Viewing Existing OAM Instances

12.1 Viewing Existing OAM Instances

The default Oracle Access Management (OAM) deployment starts the Administration Server (AdminServer), one OAM Managed Server (oam_server1) and one OAM Policy Manager server (oam_policy_mgr1).

The deployment also creates, but doesn’t start, four extra OAM Managed Servers (oam-server2 to oam-server5) and four more OAM Policy Manager servers (oam_policy_mgr2 to oam_policy_mgr5).

All these servers are visible in the WebLogic Remote Console by navigating to Environment > Servers.

Run the following command to view the pods in the OAM deployment:

kubectl --namespace <namespace> get pods

For example:

kubectl get pods -n oamns

The output should look similar to the following:

NAME                                                     READY   STATUS      RESTARTS   AGE
accessdomain-adminserver                                 1/1     Running     0          3h29m
accessdomain-oam-policy-mgr1                             1/1     Running     0          3h21m
accessdomain-oam-server1                                 1/1     Running     0          3h21m