Access the WebLogic Console
Use the WebLogic Server Administration Console to access a domain in Oracle WebLogic Server for OCI.
Note:
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.Access the WebLogic Console in a Public Subnet
Oracle WebLogic Server compute instances assigned to a public subnet are accessible from the public Internet.
Access the WebLogic Console in a Private Subnet
Oracle WebLogic Server compute instances assigned to a private subnet are not accessible from the public Internet.
- Bastion instance that's created on a public subnet and dynamic port forwarding with a secure shell (SSH) utility. See Access by Using the Bastion Instance.
- Bastion service and dynamic port forwarding with a secure shell (SSH) utility. See Access by Using the Bastion Service.
By opening an SSH tunnel with dynamic port forwarding, the SSH client becomes a Socket Secure (SOCKS) proxy listening on the port you specify. All traffic that routes to the proxy port is forwarded to its destination through the proxy server. Then when you configure your browser to use a SOCKS proxy, you can access a private domain's administration console.
Access the WebLogic Console Through a Load Balancer
Oracle WebLogic Server compute instances assigned to a private subnet are not accessible from the public Internet. So, if you have created the load balancer manually, you can access the administration console via load balancer's public IP address.
However, it is recommended to access the WebLogic Server Administration Console using the bastion instance that's created on a public subnet and dynamic port forwarding with a secure shell (SSH) utility. See Access the WebLogic Console in a Private Subnet.
Note:
If you created the load balancer in a different network than the Oracle WebLogic Server domain network with nonoverlapping CIDRs, you must create a Local Peering Gateway on both the domain network and load balancer network and add a route table for the subnet for WebLogic domain and the load balancer subnet to use the respective Local Peering Gateway.For SSL connections that terminate at the load balancer, you must
configure the load balancer to include the WL-Proxy-SSL
header in
the rule set and enable the WebLogic Proxy Plugin on the cluster and the
administration server.
To access the WebLogic administration console through the load balancer: