Scaling Up OAM Servers

12.2 Scaling Up OAM Servers

The number of Oracle Access Management (OAM) managed servers running, or policy managed servers running, is dependent on the replicas parameter configured for the oam-cluster and policy_cluster respectively.

To start more OAM servers perform the following steps:

Run the following command to edit the cluster
- For OAM managed servers:
```
kubectl edit cluster accessdomain-oam-cluster -n <domain_namespace>
```
  For example:
```
kubectl edit cluster accessdomain-oam-cluster -n oamns
```
- For OAM policy manager servers:
```
kubectl edit cluster accessdomain-policy-cluster -n <domain_namespace>
```
  For example:
```
kubectl edit cluster accessdomain-policy-cluster -n oamns
```
Note:
This opens an edit session for the cluster, where parameters can be changed using standard vi commands.
In the edit session, search for spec:, and then look for the replicas parameter under clusterName: <cluster>.
By default the replicas parameter, for both OAM managed servers and policy manager servers, is set to “1” hence one OAM managed server and one policy manager server is started (oam_server1 and oam-policy-mgr1 respectively):
- For oam_cluster:
```
...
spec:
  clusterName: oam_cluster
  replicas: 1
  serverPod:
    env:
    - name: USER_MEM_ARGS
      value: -XX:+UseContainerSupport -Djava.security.egd=file:/dev/./urandom -Xms8192m
        -Xmx8192m
...
```
- For policy_cluster:
```
...
spec:
  clusterName: policy_cluster
  replicas: 1
  serverService:
    precreateService: true
...
```
To start more OAM managed servers or policy manager servers, increase the replicas value as desired.
In the example below, two more OAM managed servers (oam-server2 and oam-server3) will be started by setting replicas to “3” for the oam_cluster:
```
...
spec:
  clusterName: oam_cluster
  replicas: 3
  serverPod:
    env:
    - name: USER_MEM_ARGS
      value: -XX:+UseContainerSupport -Djava.security.egd=file:/dev/./urandom -Xms8192m
        -Xmx8192m
...
```
Save the file and exit (:wq!).
The output will look similar to the following:
```
cluster.weblogic.oracle/accessdomain-oam-cluster edited
```

Run the following command to view the pods:

kubectl get pods -n <domain_namespace>

For example:

kubectl get pods -n oamns

The output will look similar to the following:

NAME                                                     READY   STATUS      RESTARTS   AGE
accessdomain-adminserver                                 1/1     Running     0          3h33m
accessdomain-oam-policy-mgr1                             1/1     Running     0          3h25m
accessdomain-oam-server1                                 1/1     Running     0          3h25m
accessdomain-oam-server2                                 0/1     Running     0          9s
accessdomain-oam-server3                                 0/1     Pending     0          9s

Two new pods (accessdomain-oam-server2 and accessdomain-oam-server3) are started, but currently have a READY status of 0/1. This means oam_server2 and oam_server3 are not currently running but are in the process of starting.

The servers will take several minutes to start so keep executing the command until READY shows 1/1:

Note:

Alternatively, you can add the watch flag, -w, which allows you watch the status of the pods as they change.

NAME                                                     READY   STATUS      RESTARTS   AGE
accessdomain-adminserver                                 1/1     Running     0          3h37m
accessdomain-oam-policy-mgr1                             1/1     Running     0          3h29m
accessdomain-oam-server1                                 1/1     Running     0          3h29m
accessdomain-oam-server2                                 1/1     Running     0          3m45s
accessdomain-oam-server3                                 1/1     Running     0          3m45s

To check what is happening during server startup when READY is 0/1, run the following command to view the log of the pod that is starting:

kubectl logs <pod> -n <domain_namespace>

For example:

kubectl logs accessdomain-oam-server3 -n oamns