Access Resources

Learn how to access the administration console using the tools provided with Oracle WebLogic Server for OKE.

Topics:

Access the Administration Instance

Access the administration compute instance for a Oracle WebLogic Server for OKE.

From the administration compute instance, you can access the shared file system at /u01/shared. It also includes the following software:

kubectl - Deploy and manage pods in the Kubernetes cluster for this stack.
docker - Download, modify and update container images in Oracle Cloud Infrastructure Registry. Use the login command to connect to the registry.
oci - View, create and update resources in Oracle Cloud Infrastructure.

This compute instance is on a private subnet and cannot be directly accessed from the public Internet. You can use the bastion instance, which is on a public subnet, and the proxy option of a secure shell (SSH) utility.

Sign in to the Oracle Cloud Infrastructure Console.
Click the navigation menu , select Developer Services. Under the Resource Manager group, click Stacks.
Select the Compartment in which your domain is created.
Click the stack for your domain.
Click Jobs.
In the Jobs table, click the Apply job for the stack.
Click Application Information.
Identify and make a note of the following IP addresses:
- Bastion Instance Public IP - The public IP address of the bastion compute instance
- Admin Instance Private IP - The private IP address of the administration compute instance
From your computer, create an SSH connection to the administration instance's IP address, and also specify the bastion instance's IP address as a proxy.
Connect as the opc user.

Provide the path to the private key that corresponds to the public key that you specified when you created the stack.

The SSH command format is:
```
ssh -i <path_to_private_key> -o ProxyCommand="ssh -W %h:%p –i <path_to_private_key> opc@<bastion_public_ip>" opc@<admin_ip>
```
For example:
```
ssh -i ~/.ssh/mykey.openssh -o ProxyCommand="ssh -W %h:%p -i ~/.ssh/mykey.openssh opc@203.0.113.13" opc@198.51.100.1
```
On a Windows platform, you can use Windows PowerShell to run the SSH command.
If prompted, enter the passphrase for the private key.

Access the Jenkins Console

Access the Jenkins build engine for a stack that you created with Oracle WebLogic Server for OKE.

Jenkins runs as a pod in the Kubernetes cluster and is accessible from a private load balancer. This load balancer cannot be directly accessed from the public Internet. You can use the bastion instance on a public subnet and dynamic port forwarding with a secure shell (SSH) utility.

Sign in to the Oracle Cloud Infrastructure Console.
Click the navigation menu , select Developer Services. Under the Resource Manager group, click Stacks.
Select the Compartment in which your domain is created.
Click the stack for your domain.
Click Jobs.
Click the Apply job for the stack.
Click Outputs.
Identify the public IP address of the bastion compute instance, bastion_instance_public_ip.
Click Logs.
Search for the attribute jenkins_console_url. Copy the URL.
The URL format is:
```
jenkins_console_url=http://<internal_lb_ip>/jenkins
```
where, internal_lb_ip is the internal load balancer IP address.
Note:

If you provision a domain without a bastion instance, you must obtain the internal load balancer IP address to use in the Jenkins URL.
To get the internal load balancer IP address, access the administration instance for your stack (see Access the Administration Instance) and run the following command:
kubectl get svc -A
The private load balancer is listed with the namespace wlsoke-ingress-nginx and name okename-internal.
From your computer, open an SSH tunnel to an unused port on the bastion compute instance as the opc user.
For example, you can use port 1088 for SOCKS proxy.

Specify the -D option to use dynamic port forwarding. Provide the path to the private key that corresponds to the public key that you specified when you created the domain.

The SSH command format is:
```
ssh -D <port_for_socks_proxy> -fCqN -i <path_to_private_key> opc@<bastion_public_ip>
```
For example:
```
ssh -D 1088 -fCqN -i ~/.ssh/mykey.openssh opc@198.51.100.1
```
On a Windows platform, you can use Windows PowerShell to run the SSH command.
In your browser settings, set up the SOCKS (version 5) proxy configuration. Specify your local computer and the same SOCKS port that you used in your SSH command.
Browse to the Jenkins console URL.
If this is the first time using the Jenkins console, you are prompted to create a new admin user.

Access the WebLogic Console

Access the WebLogic Server Administration Console for a domain that you created with Oracle WebLogic Server for OKE.

Note:

Before you access the WebLogic console, you must have created a WebLogic domain. See Create a WebLogic Domain.
Do not use the WebLogic console to make any configuration changes. All configuration changes should be should done through jobs, this ensure that the changes are persistent.
Security check warnings are displayed at the top of the console. See About the Security Checkup Tool for the warnings and how to handle them.

The domain's administration server runs as a pod in the Kubernetes cluster and is accessible from a private load balancer. This load balancer cannot be directly accessed from the public Internet. You can use the bastion instance on a public subnet and dynamic port forwarding with a secure shell (SSH) utility.

Note:

Any modifications you make to a running domain will be lost when you redeploy the pods for the domain in the Kubernetes cluster.

Sign in to the Oracle Cloud Infrastructure Console.
Click the navigation menu , select Developer Services. Under the Resource Manager group, click Stacks.
Select the Compartment in which your domain is created.
Click the stack for your domain.
Click Jobs.
In the Jobs table, click the Apply job for the stack.
Click Outputs.
Identify and make a note of the public IP address of the bastion compute instance, bastion_instance_public_ip.
Click Logs.
Search for the attribute weblogic_console_url. Copy the URL.
The URL format is:
```
weblogic_console_url=http://<internal_lb_ip2>/<domain-name>/console
```
where, <internal_lb_ip2> is the internal load balancer IP address that is used to access the Jenkins console.
Note:

If you provision a domain without a bastion instance, you must obtain the internal load balancer IP address to use in the WebLogic Console URL.
To get the internal load balancer IP address, access the administration instance for your stack (see Access the Administration Instance) and run the following command:
kubectl get svc -A
The private load balancer is listed with the namespace wlsoke-ingress-nginx and name okename-internal.
Example: This example will help you obtain the WebLogic Console URL.
After you access the administration instance for your stack, run the following command:
```
kubectl get svc -A
```
The output appears as follows:
```
NAMESPACE              NAME                             TYPE           CLUSTER-IP      EXTERNAL-IP      PORT(S)                  AGE
default                kubernetes                       ClusterIP      10.96.0.1       <none>           443/TCP,12250/TCP        9d
service1-operator-ns   weblogic-operator-webhook-svc    ClusterIP      10.96.30.88     <none>           8083/TCP,8084/TCP        9d  
domain1-ns             domain1-cluster-domain1-cluster  ClusterIP      10.96.40.171    <none>           8001/TCP                 2d23h
domain1-ns             domain1-domain1-adminserver      ClusterIP      None            <none>           30012/TCP,7001/TCP       2d23h
domain1-ns             domain1-domain1-managed-server1  ClusterIP      None            <none>           8001/TCP                 2d23h
domain1-ns             domain1-domain1-managed-server2  ClusterIP      None            <none>           8001/TCP                 2d23h
jenkins-ns             jenkins-service                  ClusterIP      10.96.13.193    <none>           8080/TCP,50000/TCP       9d
kube-system            kube-dns                         ClusterIP      10.96.5.5       <none>           53/UDP,53/TCP,9153/TCP   9d
wlsoke-ingress-nginx   service1-internal                LoadBalancer   10.96.190.50    10.10.6.13       80:31149/TCP             9d  
```
Now, look for the EXTERNAL-IP field for the service with the following details:
- NAMESPACE = wlsoke-ingress-nginx
- NAME = <service-name>-internal = service1_internal
- TYPE = LoadBalancer
For this example, service1 is the service name and domain1 is the domain name. The WebLogic Console URL format is http://<internal_lb_ip>/<domain-name>/console. Therefore, as per this example, the console URL is http://10.10.6.13/domain1/console.
From your computer, open an SSH tunnel to an unused port on the bastion compute instance as the opc user.
For example, you can use port 1088 for SOCKS proxy.

Specify the -D option to use dynamic port forwarding. Provide the path to the private key that corresponds to the public key that you specified when you created the stack.

The SSH command format is:
```
ssh -C -D port_for_socks_proxy -i path_to_private_key opc@bastion_public_ip
```
For example:
```
ssh -C -D 1088 -i ~/.ssh/mykey.openssh opc@198.51.100.1
```
On a Windows platform, you can use Windows PowerShell to run the SSH command.
In your browser settings, set up the SOCKS (version 5) proxy configuration. Specify your local computer and the same SOCKS port that you used in your SSH command.
Browse to the console URL.
Sign in using the administrator credentials for your domain.