Access an Application Deployed to an Oracle Java Cloud Service Instance

You can access an application deployed to an Oracle Java Cloud Service instance through a URL in a browser.

If your service instance includes multiple WebLogic Server clusters, see Deploy an Application to an Oracle Java Cloud Service Instance with Multiple Clusters.

To access a deployed application:

1. Navigate to the Oracle Java Cloud Service console.
2. Click the service instance where you deployed the application.
3. If your instance has a load balancer, then make a note of the public IP address of the load balancer. Otherwise, note the public IP address of a WebLogic managed server node that hosts your application.
4. Find the context-root of the application.
   The context-root is defined as a project property, or in the weblogic.xml file. The context-root might or might not be the same as the internal application name.
   1. Click Manage this instance , and select Open WebLogic Server Administration Console.
   2. Sign in using credentials you specified when you created the service instance.
      If you did not create the service instance, ask your administrator for the login credentials.
   3. Select domain > Deployments, where domain is the domain where the application is deployed.
   4. In the Deployments table, click the name of your application.
   5. In the Overview tab, locate the context-root.
5. In a browser, specify the URL of the application, in the following format:
   scheme://host/applicationContextRoot

   • scheme: http or https

     If you created the service instance by using the Oracle Java Cloud Service console, you can access the application through HTTPS only. The HTTP port is disabled by default. You can open the HTTP port on the load balancer manually. See Enable HTTP Access to a Service Instance.

   • host: The public IP address of the load balancer (or the managed server if you’re not using a load balancer)

     If you do not want to specify the IP address when you access the application, you can create a custom domain name. To do this, you can use a third-party DNS provider to map the custom domain name. See Configure a Vanity Domain Name for a Service Instance.

     Note:

     Avoid using IP addresses to access applications running in a production environment. Use a custom domain name, or the default internal host name if a custom domain name has not been provided.

   • applicationContextRoot: The context root that you noted earlier in this procedure.

     If the application is deployed to a cluster that is assigned a path prefix, the context root must also include the path prefix. For example: /cluster1/myapp

     If you want to customize the default URL for your application, see Configure a Custom URL for an Application Deployed to a Service Instance.

6. If you receive a warning, accept the self-signed certificate.
   The application opens in your browser.