Enable HTTP Access to a Service Instance
Note:
This procedure applies only to service instances that include a user-managed load balancer (Oracle Traffic Director). It does not apply to service instances that have an Oracle-managed load balancer (Oracle Cloud Infrastructure Load Balancing or Oracle Cloud Infrastructure Load Balancing Classic).
If there is no load balancer in your service instance, you must instead create an HTTP network channel on all Managed Servers in your Oracle WebLogic Server domain. Refer to these topics in Administering Server Environments for Oracle WebLogic Server:
-
Configuring Network Resources (12.2.1.3)
-
Configuring Network Resources (11.1.1.7)
By default the load balancer in your service instance listens for HTTP traffic on port 8080. However, the load balancer node automatically redirects incoming traffic on port 80 to port 8080.
Tasks:
Enable the HTTP Port on Oracle Traffic Director
You must enable a port on the load balancer (Oracle Traffic Director) to accept HTTP traffic from the public Internet to your Oracle Java Cloud Service instance.
By default, if you created your service instance in an Oracle Cloud Infrastructure Classic region, external access to the load balancer console is disabled for security purposes. If you did not enable console access while provisioning your service instance, see Enabling Console Access in an Oracle Java Cloud Service Instance.
Create an Access Rule for the Oracle Traffic Director HTTP Port
You must create an access rule to allow public access to the load balancer (Oracle Traffic Director) through the HTTP port.
If you provisioned this service instance in an Oracle Cloud Infrastructure region, you must create security lists instead of access rules. See Security Lists in the Oracle Cloud Infrastructure documentation.
You can now access your application by using the default HTTP port:
http://<IP_of_load_balancer>/<context_root>