1. Deploying and Managing Oracle Access Management on Kubernetes
  2. Installing Oracle Access Management on Kubernetes
  3. Post Installation Configuration
  4. Restarting the Domain

10.5 Restarting the Domain

You must restart the Oracle Access Management (OAM) domain for the post configuration changes to take effect.

  1. Stop the OAM domain using the following command:
    kubectl -n <domain_namespace> patch domains <domain_uid> --type='json' -p='[{"op": "replace", "path": "/spec/serverStartPolicy", "value": "Never" }]'
    For example:
    kubectl -n oamns patch domains accessdomain --type='json' -p='[{"op": "replace", "path": "/spec/serverStartPolicy", "value": "Never" }]'
    The output will look similar to the following:
    domain.weblogic.oracle/accessdomain patched
  2. Check that all the pods are stopped:
    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     Terminating   0          27m
accessdomain-oam-policy-mgr1                             1/1     Terminating   0          24m
accessdomain-oam-server1                                 1/1     Terminating   0          24m
    The Administration Server pod and Managed Server pods will move to a STATUS of Terminating. After a few minutes, run the command again and the pods should have disappeared.
  3. Start the domain using the following command:
    kubectl -n <domain_namespace> patch domains <domain_uid> --type='json' -p='[{"op": "replace", "path": "/spec/serverStartPolicy", "value": "IfNeeded" }]'
    For example:
    kubectl -n oamns patch domains accessdomain --type='json' -p='[{"op": "replace", "path": "/spec/serverStartPolicy", "value": "IfNeeded" }]'
  4. Run the following kubectl command to view the pods:
    kubectl get pods -n <domain_namespace> -w

    Note:

    The -w flag allows you watch the status of the pods as they change.
    For example:
    kubectl get pods -n oamns -w
    The output will look similar to the following:
    NAME                                                     READY   STATUS      RESTARTS   AGE
accessdomain-introspector-mckp2                          1/1     Running     0          8s
    After the introspect job has run, the Administration Server pod will start followed by the OAM Managed Servers pods. This process will take several minutes, so keep executing the command until all the pods are running with READY status 1/1:
    NAME                                                     READY   STATUS      RESTARTS   AGE  
accessdomain-adminserver                                 1/1     Running     0          5m38s
accessdomain-oam-policy-mgr1                             1/1     Running     0          2m51s
accessdomain-oam-server1                                 1/1     Running     0          2m50s