Design Considerations for an Oracle Java Cloud Service Instance

Before creating an Oracle Java Cloud Service instance, there are details you should consider in order to create the service instance that best meets your requirements.

Take the following into consideration when designing a service instance:

Details Description

Service Level

You can select one of these service levels:

  • Oracle Java Cloud Service—Virtual Image

    Developer-level service. Supports Oracle Java Cloud Service instance creation and monitoring.

    This service level does not support backup and restoration; patching; or scaling. You cannot provision a domain partition if you specify this service level.

  • Oracle Java Cloud Service

    Production-level service. Supports Oracle Java Cloud Service instance creation and monitoring; domain partitions; backup and restoration; patching; and scaling.


The Oracle Java Cloud Service for Fusion Middleware service level is not supported.

Software Release

You can select one of three Oracle WebLogic Server releases:

See About Oracle Java Cloud Service Offerings and Oracle WebLogic Server Software Releases.

With Oracle Java Cloud Service you can easily apply patches to an existing service instance, but it does not provide automated tooling to upgrade an existing service instance to a newer release of Oracle WebLogic Server.


You can choose one of these Oracle WebLogic Server editions:

  • Standard Edition

  • Enterprise Edition

  • Enterprise Edition with Coherence (Suite)

Certain WebLogic Server capabilities are only supported in specific editions. To learn about these editions see:

Compute Shape

Oracle Java Cloud Service provides a set of compute shapes that are optimized for different use cases. Choose from a set of all-purpose and memory-intensive shapes. The larger the compute shape, the greater the processing power and the more memory that is available.

See About Default Heap Size Settings for Oracle Java Cloud Service Instances.


You select an initial cluster size of 1, 2, or 4 Managed Servers. In general, the larger the cluster the more application requests that can be processed by your service instance. However, with Oracle Java Cloud Service you can also scale in and out this cluster after you create the service instance.

For more information about clusters see:

Domain Partition

A WebLogic Server 12c domain can optionally be organized into multiple partitions. Each partition is dedicated to running specific applications and related resources, and is managed independently of other partitions in the same domain. You can define partitions when you create a service instance, and you can add or remove domain partitions after you create the service instance by using Fusion Middleware Control. These domain partitions will be created with a default resource management policy. Domain partitions also enable you to create different security realms for the overall WebLogic Server domain and for each partition. Each security realm can have its own identity store with users, credentials and groups.

See About WebLogic Server MT in Using WebLogic Server Multitenant.

You cannot configure domain partitions if you select:
  • The Oracle Java Cloud Service—Virtual Image service level

  • The Standard Edition of Oracle WebLogic Server

  • The 11g release of WebLogic Server

Client Access

By default, access to an Oracle Java Cloud Service instance can only be done over secure protocols like HTTPS and SSH. If you plan to access an application through the HTTP port, you can enable this port manually after creating a service instance. See:

The HTTP port is disabled by default only when creating the service instance by using the Oracle Java Cloud Service console. The HTTP port is enabled by default if you create the service instance by using the REST API.

Coherence Data Tier

If you choose to provision an Oracle Coherence data tier in your service instance, Oracle Java Cloud Service creates a second WebLogic Server cluster in the domain to host your in-memory data grid, or cache. This Coherence cluster provides your applications with fast, reliable, and scalable access to frequently used data. You configure the data grid’s initial cache capacity by selecting a predefined capacity unit or by defining your own custom one. The capacity unit controls the size of the cache in GB, the number of VMs in the cluster, and the compute shape of these VMs. See About Capacity Units for Oracle Java Cloud Service—Coherence Instances.

After a service instance is created, you can increase cache capacity by adding one capacity unit at a time. See Scaling the Coherence Data Tier of an Oracle Java Cloud Service Instance.

Oracle Java Cloud Service can only provision a Coherence data tier in your service instance if you select Enterprise Edition with Coherence (Suite).


Oracle Java Cloud Service requires access to an existing relational database that contains the standard Oracle Infrastructure schema. Oracle Java Cloud Service uses Java Database Connectivity (JDBC) to access this database.

Create an Oracle Database Cloud Service database deployment or use an existing on-premises Oracle database. During the service creation process, Oracle Java Cloud Service will provision Oracle Database Cloud Service with the required schema. If you select some other Oracle database, you must manually create this schema prior to creating the Oracle Java Cloud Service instance.

See Creating a Database Deployment in Using Oracle Database Cloud Service.

Load Balancer

The load balancer is an instance of Oracle Traffic Director (OTD). The load balancer routes requests it receives from clients to the WebLogic Servers configured in an Oracle Java Cloud Service instance. Using a load balancer is recommended if you are configuring more than one managed server. A load balancer also gives you the ability to suspend an Oracle Java Cloud Service instance temporarily to perform routine maintenance.

You can configure a second load balancer while provisioning the service instance, or add one later after the service instance is provisioned. Each load balancer is assigned a separate public IP address. A configuration with two active load balancers provides these advantages:

  • High availability if a load balancer becomes unavailable.

  • Multiple load balancers for greater application throughput.

However, in this configuration the client is responsible for utilizing both load balancer nodes, and for failing over to another node should one become unavailable.

You cannot remove the first load balancer after adding it to your Oracle Java Cloud Service instance. You can disable it, but you will be charged for having it in your service instance.