1. Administering Oracle Java Cloud Service
  2. Secure an Oracle Java Cloud Service Instance
  3. Configure Network Security
  4. Enable HTTP Access to a Service Instance

Enable HTTP Access to a Service Instance

If you create an Oracle Java Cloud Service instance by using the web console rather than the REST API or CLI, HTTPS access is enabled by default but HTTP access is disabled. You can enable HTTP access on the load balancer after you have created the 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:

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.

  1. Access the Oracle Java Cloud Service console.
  2. Click menu icon for the desired service instance and select Open Load Balancer Console.
  3. Log in to console using the credentials defined when provisioning your service instance.

    If you created your service instance using the Oracle Java Cloud Service console, the user name and password default to the Oracle WebLogic Server Administration Console user name and password.

  4. Access the load balancer configuration (for example, opc-config):
    • If your service instance is running Oracle Traffic Director 12c, click the Target Navigation icon Target Navigation icon. Expand the Traffic Director folder and click the name of the Traffic Director configuration.
    • If your service instance is running Oracle Traffic Director 11g, click Configurations and then click the name of the Traffic Director configuration.
  5. Navigate to the Listeners in this configuration:

    • If your service instance is running Oracle Traffic Director 12c, click Traffic Director Configuration and select Administration > Listeners.

    • If your service instance is running Oracle Traffic Director 11g, click Listeners in the navigation pane.

  6. Click http-listener-1.
  7. Select the Enabled checkbox.
  8. Activate your changes:

    • If your service instance is running Oracle Traffic Director 12c, click Apply.

    • If your service instance is running Oracle Traffic Director 11g, click Deploy Changes.

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.

  1. Access the Oracle Java Cloud Service console.
  2. Click the Menu icon Menu icon adjacent to the service instance name and select Access Rules.

    The Access Rules page is displayed, showing the list of all access rules.

  3. Click Create Rule.
    The Create Access Rule dialog is displayed.
  4. Specify a unique name for the access rule.

    The name must begin with a letter, and can contain numbers, hyphens, or underscores. The length cannot exceed 50 characters. You cannot use prefixes ora_ or sys_.

  5. Enter Permit public http to OTD server for the description.
  6. Select PUBLIC-INTERNET for the source.
  7. Select OTD for the destination.
  8. Enter 80 as the port and accept the default protocol (TCP).
  9. Click Create.
  10. Refresh the page periodically. The access rule will appear on the Access Rules table after it is created.

You can now access your application by using the default HTTP port:

http://<IP_of_load_balancer>/<context_root>