1. Deploying and Managing Oracle Access Management on Kubernetes
  2. Installing Oracle Access Management on Kubernetes
  3. Post Installation Configuration
  4. Creating a Server Overrides File

10.1 Creating a Server Overrides File

Perform the following steps to create a server overrides file for Oracle Access Management (OAM):

  1. Navigate to the following directory:
    • For OAM domains created with WLST:
      cd $WORKDIR/kubernetes/create-access-domain/domain-home-on-pv/output/weblogic-domains/accessdomain
    • For OAM domains created with WDT:
      cd $WORKDIR/kubernetes/create-access-domain/domain-home-on-pv/
  2. Create a setUserOverrides.sh with the following contents:
    DERBY_FLAG=false
JAVA_OPTIONS="${JAVA_OPTIONS} -Djava.net.preferIPv4Stack=true"
MEM_ARGS="-Xms8192m -Xmx8192m"
  3. Copy the setUserOverrides.sh file to the Administration Server pod:
    chmod 755 setUserOverrides.sh
     kubectl cp setUserOverrides.sh <domain_namespace>/<domain-uid>-adminserver:/u01/oracle/user_projects/domains/<domain-uid>/bin/setUserOverrides.sh
    For example:
     kubectl cp setUserOverrides.sh oamns/accessdomain-adminserver:/u01/oracle/user_projects/domains/accessdomain/bin/setUserOverrides.sh
  4. 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
  5. 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.
  6. 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" }]'
  7. Run the following kubectl 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-introspector-mckp2                          1/1     Running     0          8s
    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:

    Note:

    You can watch the status of the pods by adding the watch flag, for example:
    kubectl get pods -n oamns -w
    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