1. Deploying and Managing Oracle Access Management on Kubernetes
  2. Administering Oracle Access Management on Kubernetes
  3. Patching and Upgrading
  4. Upgrading from Oracle Access Management 12.2.1.4 to 14.1.2
  5. Starting the OAM 14c Deployment

17.2.10 Starting the OAM 14c Deployment

Start the Oracle Access Management (OAM) 14c deployment.
  1. Run the following command to start the OAM domain:
    kubectl patch domain.v9.weblogic.oracle "%DOMAIN_UID%" -n "%NAMESPACE%" \
--type=merge --patch "{\"spec\": {\"serverStartPolicy\": \"IfNeeded\"}}"
    For example:
    kubectl patch domain.v9.weblogic.oracle "accessdomain" -n "oamns" \
--type=merge --patch "{\"spec\": {\"serverStartPolicy\": \"IfNeeded\"}}"
    The output will look similar to the following:
    domain.weblogic.oracle/accessdomain patched
  2. Run the following command to view the pods:
    kubectl get pods -n %NAMESPACE%
    For example:
    kubectl get pods -n oamns
    The output will look similar to the following:
    NAME                                                     READY   STATUS        RESTARTS   AGE
accessdomain-introspector-jwqxw                          1/1     Running     0          10s
    The introspect job will start, followed by the Administration Server pod, and then the OAM server pods. This process will take several minutes, so keep executing the command until all the pods are running with READY status 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          10m
accessdomain-oam-policy-mgr1                             1/1     Running     0          7m35s
accessdomain-oam-server1                                 1/1     Running     0          7m35s
  3. Once everything is running, check the consoles are accessible as per Validating the Domain URLs.
  4. Once you are confident the upgrade is successful, delete the domain-upgrade pod and ConfigMap as follows:
    kubectl delete pod %DOMAIN_UID%-domain-upgrade -n %NAMESPACE%
    kubectl delete configmap %DOMAIN_UID%-domain-upgrade-pod-cm -n %NAMESPACE%
    For example:
    kubectl delete pod accessdomain-domain-upgrade -n oamns
    kubectl delete configmap accessdomain-domain-upgrade-pod-cm -n oamns