a. Post Install Tasks

Follow these post install configuration steps.

  1. Create a Server Overrides File
  2. Set OIMFrontendURL using MBeans

Create a Server Overrides File

  1. Navigate to the following directory:

    cd <work directory>/weblogic-kubernetes-operator/kubernetes/samples/scripts/create-oim-domain/domain-home-on-pv/output/weblogic-domains/governancedomain

    For example:

    cd /scratch/OIGDockerK8S/weblogic-kubernetes-operator/kubernetes/samples/scripts/create-oim-domain/domain-home-on-pv/output/weblogic-domains/governancedomain

  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 oigns/governancedomain-adminserver:/u01/oracle/user_projects/domains/governancedomain/bin/setUserOverrides.sh

    Where oigns is the OIG namespace and governancedomain is the DOMAIN_NAME/UID.

  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-create-fmw-infra-domain-job-vj69h   0/1     Completed      0          24h
governancedomain-oim-server1                         1/1     Terminating    0          18h
governancedomain-soa-server1                         1/1     Terminating    0          18h
helper                                               1/1     Running        0          41h

    The Administration Server pods 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:

    NAME                                                 READY   STATUS      RESTARTS   AGE
governancedomain-create-fmw-infra-domain-job-vj69h   0/1     Completed   0          24h
helper                                               1/1     Running     0          41h

  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": "IF_NEEDED" }]'

    For example:

    $ kubectl -n oigns patch domains governancedomain --type='json' -p='[{"op": "replace", "path": "/spec/serverStartPolicy", "value": "IF_NEEDED" }]'

    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-create-fmw -infra-domain-job-vj69h  0/1     Completed   0          24h
governancedomain-introspect-domain-job-7qx29         1/1     Running     0          8s
helper                                               1/1     Running     0          41h

    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:

    NAME                                                READY   STATUS      RESTARTS   AGE  
governancedomain-adminserver                        1/1     Running     0          6m4s
governancedomain-create-fmw-infra-domain-job-vj69h  0/1     Completed   0          24h
governancedomain-oim-server1                        1/1     Running     0          3m5s
governancedomain-soa-server1                        1/1     Running     0          3m5s
helper                                              1/1     Running     0          41h

Set OIMFrontendURL using MBeans

  1. Login to Oracle Enterprise Manager using the following URL:

    https://${MASTERNODE-HOSTNAME}:${MASTERNODE-PORT}/em

  2. Click the Target Navigation icon in the top left of the screen and navigate to the following:

    • Expand Identity and Access > Access > OIM > oim
    • Right click the instance oim and select System MBean Browser
    • Under Application Defined MBeans, navigate to oracle.iam, Server:oim_server1, Application:oim > XMLConfig > Config > XMLConfig.DiscoveryConfig > Discovery.

  3. Enter a new value for the OimFrontEndURL attribute, in the format:

    http://<OIM-Cluster-Service-Name>:<Cluster-Service-Port>

    For example:

    http://governancedomain-cluster-oim-cluster:14000

    Then click Apply.

    Note: To find the <OIM-Cluster-Service-Name> run the following command:

    $ kubectl -n oigns get svc

    Your output will look similar to this:

    $ kubectl -n oigns get svc
NAME                             TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)     AGE
governancedomain-adminserver           ClusterIP   None             <none>        7001/TCP    6d23h
governancedomain-cluster-oim-cluster   ClusterIP   10.107.191.53    <none>        14000/TCP   6d23h
governancedomain-cluster-soa-cluster   ClusterIP   10.97.108.226    <none>        8001/TCP    6d23h
governancedomain-oim-server1           ClusterIP   None             <none>        14000/TCP   6d23h
governancedomain-oim-server2           ClusterIP   10.96.147.43     <none>        14000/TCP   6d23h
governancedomain-oim-server3           ClusterIP   10.103.65.77     <none>        14000/TCP   6d23h
governancedomain-oim-server4           ClusterIP   10.98.157.253    <none>        14000/TCP   6d23h
governancedomain-oim-server5           ClusterIP   10.102.19.32     <none>        14000/TCP   6d23h
governancedomain-soa-server1           ClusterIP   None             <none>        8001/TCP    6d23h
governancedomain-soa-server2           ClusterIP   10.96.73.62      <none>        8001/TCP    6d23h
governancedomain-soa-server3           ClusterIP   10.105.198.83    <none>        8001/TCP    6d23h
governancedomain-soa-server4           ClusterIP   10.98.171.18     <none>        8001/TCP    6d23h
governancedomain-soa-server5           ClusterIP   10.105.196.107   <none>        8001/TCP    6d23h