Use an Oracle Cloud Infrastructure Load Balancer

You can remove the Oracle-managed load balancer that's provisioned automatically during the creation of an Oracle Java Cloud Service instance in an Oracle Cloud Infrastructure region, and reconfigure the service instance to use an existing instance of Oracle Cloud Infrastructure Load Balancing.

This topic is applicable to Oracle Java Cloud Service instances that you've originally created by enabling the use of Oracle Identity Cloud Service or by using Oracle Cloud Infrastructure Load Balancing without enabling Oracle Identity Cloud Service.

After you remove the Oracle-managed load balancer that's provisioned automatically, if applicable, you'll need to modify the Open Sample Application URL on the Oracle Java Cloud Service Console.

Remove the Oracle-Managed Load Balancer

You can remove the Oracle-managed instance of Oracle Cloud Infrastructure Load Balancing that's provisioned automatically during the creation of an Oracle Java Cloud Service instance in an Oracle Cloud Infrastructure region.

You can use only the REST API to remove the Oracle-managed instance of Oracle Cloud Infrastructure Load Balancing from a service instance. This remove option is not available from the Oracle Java Cloud Service Console.

The REST API operation can be executed on an Oracle Java Cloud Service instance that has or does not have Oracle Identity Cloud Service enabled.

See Delete the Oracle-Managed Load Balancer in REST API for Oracle Java Cloud Service.

Note:

If the sample application sample-app is deployed to the original Oracle-managed load balancer, the sample application URL that's displayed on the Oracle Java Cloud Service Console no longer works after you remove or replace the load balancer. To change the sample application URL, see Update a Service Instance Configuration in REST API for Oracle Java Cloud Service.

Configure an Oracle Cloud Infrastructure Load Balancer

For the Oracle Cloud Infrastructure Load Balancing instance you plan to use with your existing Oracle Java Cloud Service instance, you have to configure the backend set and listener manually to one or more nodes of the Oracle Java Cloud Service instance.

See Overview of Load Balancing and Managing Backend Servers in the Oracle Cloud Infrastructure documentation.

When you create or configure an instance of Oracle Cloud Infrastructure Load Balancing, be sure to follow these design recommendations:

  • For a service instance that uses Oracle Identity Cloud Service to authenticate Oracle WebLogic Server administrators and application users, the load balancer backend servers must use port 9075.
  • For a service instance that does not have Oracle Identity Cloud Service enabled, the load balancer backend servers use port 8001.
  • The health check policy of the load balancer backend set have the following properties:
    • Protocol: HTTP
    • Port: 0
    • Interval in MS: 30000
    • Timeout in MS: 15000
    • Number of retries: 2
    • Status code: 404
    • URL Path (URI): /
    • Response body regex: .*
  • The listener has the following properties:
    • Protocol: HTTP
    • Port: 443
    • Use SSL: Yes
    • Certificate: Use an SSL/TLS certificate that's issued by a third-party Certificate Authority (CA), or a self-signed certificate that you generate by using tools such as Open SSL. For more information about obtaining a CA certificate, see the documentation provided by your CA. For the steps to generate self-signed certificates, see the documentation for the certificate-generation tool that you want to use.
    • Path Route Set: If the URL matches (Prefix Match) /, direct traffic to the backend set.
    • Rule Set: The Add Request HTTP header WL-PROXY-SSL is set to true.
  • There's communication between the Oracle Java Cloud Service instance nodes and the Oracle Cloud Infrastructure Load Balancing instance if the service instance nodes and the load balancer instance are provisioned in different virtual cloud networks.
  • If the sample application sample-app was deployed to the original Oracle-managed load balancer, use the REST API to change the sample application URL that's displayed on the Oracle Java Cloud Service Console. See Update a Service Instance Configuration in REST API for Oracle Java Cloud Service.
  • When you scale out or scale in an Oracle Java Cloud Service instance that uses a manually configured instance of Oracle Cloud Infrastructure Load Balancing, you must update the backend set manually to add or remove the Oracle WebLogic Server nodes.
  • When you delete an Oracle Java Cloud Service instance that uses a manually configured instance of Oracle Cloud Infrastructure Load Balancing, the load balancer is not removed automatically so you must delete it separately.

Verify Access to the Deployed Sample Application

If the sample application is originally deployed to the Oracle-managed load balancer that you've removed from an Oracle Java Cloud Service instance, make sure you can access the sample application after you've manually configured your own Oracle Cloud Infrastructure Load Balancing instance to use the nodes on the Oracle Java Cloud Service instance.

Use a web browser

To access the sample application in a web browser, enter the following URL:

https://load_balancer_IP_address/sample-app

If Oracle Identity Cloud Service is enabled on your Oracle Java Cloud Service instance, use the following URL:

https://load_balancer_IP_address/__protected/sample-app

Access from the Oracle Java Cloud Service console

After you remove the original Oracle-managed load balancer, the Open Sample Application URL that's displayed on the Oracle Java Cloud Service Console will no longer work. You have to change the URL to use the public IP address of your own Oracle Cloud Infrastructure Load Balancing load balancer that's now configured to the Oracle Java Cloud Service instance nodes. You can make this change by using the REST API to update the SAMPLE_ROOT parameter as described in Update a Service Instance Configuration.