Connecting to OAM via WLST

13.1 Connecting to OAM via WLST

In order to use WLST to administer the Oracle Access Management (OAM) domain, use must use a helper pod.

Check to see if the helper pod exists by running:

kubectl get pods -n <domain_namespace> | grep helper

For example:

kubectl get pods -n oamns | grep helper

The output should look similar to the following:

helper                                  1/1     Running     0          26h

If the helper pod doesn’t exist, run the following:

If using Oracle Container Registry or your own container registry for the OAM container image:

kubectl run --image=<image_name-from-registry>:<tag> \
--image-pull-policy="IfNotPresent" \
--overrides='{"apiVersion": "v1", "spec":{"imagePullSecrets": [{"name": "orclcred"}]}}' \
helper -n <domain_namespace> \
-- sleep infinity

For example:

kubectl run --image=container-registry.oracle.com/middleware/oam_cpu:14.1.2.1.0-jdk17-ol8-<YYMMDD> \
--image-pull-policy="IfNotPresent" \
--overrides='{"apiVersion": "v1","spec":{"imagePullSecrets": [{"name": "orclcred"}]}}' \
helper -n oamns \
-- sleep infinity

If you are not using a container registry and have loaded the image on each of the worker nodes, run the following command:
```
kubectl run helper --image <image>:<tag> -n oamns -- sleep infinity
```
For example:
```
kubectl run helper --image oracle/oam_cpu:14.1.2.1-jdk17-ol8-<YYDDMM> -n oamns -- sleep infinity
```
The output will look similar to the following:
```
pod/helper created
```

Run the following command to start a bash shell in the helper pod:
```
kubectl exec -it helper -n <domain_namespace> -- /bin/bash
```
For example:
```
kubectl exec -it helper -n oamns -- /bin/bash
```
This will take you into a bash shell in the running helper pod:
```
[oracle@helper ~]$
```

Inside the helper pod, connect to WLST using the following command:

cd $ORACLE_HOME/oracle_common/common/bin

./wlst.sh

The output will look similar to the following:

Initializing WebLogic Scripting Tool (WLST) ...

Jython scans all the jar files it can find at first startup. Depending on the system, this process may take a few minutes to complete, and WLST may not return a prompt right away.

Welcome to WebLogic Server Administration Scripting Shell

Type help() for help on available commands

wls:/offline>

To access t3 for the Administration Server connect as follows:

connect('weblogic','<password>','t3://accessdomain-adminserver:7001')

The output will look similar to the following:

Connecting to t3://accessdomain-adminserver:7001 with userid weblogic ...
Successfully connected to Admin Server "AdminServer" that belongs to domain "accessdomain".

Warning: An insecure protocol was used to connect to the server.
To ensure on-the-wire security, the SSL port or Admin port should be used instead.

wls:/accessdomain/serverConfig/>

Or to access t3 for the OAM Cluster service, connect as follows:

connect('weblogic','<password>','t3://accessdomain-cluster-oam-cluster:14100')

The output will look similar to the following:

Connecting to t3://accessdomain-cluster-oam-cluster:14100 with userid weblogic ...
Successfully connected to managed Server "oam_server1" that belongs to domain "accessdomain".

Warning: An insecure protocol was used to connect to the server.
To ensure on-the-wire security, the SSL port or Admin port should be used instead.

wls:/accessdomain/serverConfig/>