1. Deploying and Managing Oracle Identity Governance on Kubernetes
  2. Installing Oracle Identity Governance 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 Identity Governance (OIG):

  1. Navigate to the following directory:
    • For OIG domains created with WLST:
      cd $WORKDIR/kubernetes/create-oim-domain/domain-home-on-pv/output/weblogic-domains/governancedomain
    • For OIG domains created with WDT:
      cd $WORKDIR/kubernetes/create-oim-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/<domainUID>-adminserver:/u01/oracle/user_projects/domains/<domainUID>/bin/setUserOverrides.sh
    For example:
    kubectl cp setUserOverrides.sh oigns/governancedomain-adminserver:/u01/oracle/user_projects/domains/governancedomain/bin/setUserOverrides.sh
  4. Stop the OIG 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 oigns patch domains governancedomain --type='json' -p='[{"op": "replace", "path": "/spec/serverStartPolicy", "value": "Never" }]'
    The output will look similar to the following:
    domain.weblogic.oracle/governancedomain patched
  5. Check that all the pods are stopped:
    kubectl get pods -n <domain_namespace>
    For example:
    kubectl get pods -n oigns
    The output will look similar to the following:
    NAME                                                 READY   STATUS         RESTARTS   AGE
governancedomain-adminserver                         1/1     Terminating    0          18h
governancedomain-oim-server1                         1/1     Terminating    0          18h
governancedomain-soa-server1                         1/1     Terminating    0          18h
    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 <domainUID> --type='json' -p='[{"op": "replace", "path": "/spec/serverStartPolicy", "value": "IfNeeded" }]'
    For example:
    kubectl -n oigns patch domains governancedomain --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 oigns
    The output will look similar to the following:
    NAME                                        READY   STATUS      RESTARTS   AGE
governancedomain-introspector-jhjtj         1/1     Running     0          8s
    The Administration Server pod will start followed by the OIG 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 oigns -w
    NAME                                                READY   STATUS      RESTARTS   AGE  
governancedomain-adminserver                        1/1     Running     0          6m4s
governancedomain-oim-server1                        1/1     Running     0          3m5s
governancedomain-soa-server1                        1/1     Running     0          3m5s