About Java Cloud Service Instances in Oracle Cloud Infrastructure

When you create an Oracle Java Cloud Service instance, you can choose the infrastructure that the instance must use: Oracle Cloud Infrastructure or Oracle Cloud Infrastructure Classic. The Oracle WebLogic Server environment and other middleware components that your Oracle Java Cloud Service instance provides in either type of infrastructure is substantially the same. A few differences exist in the underlying infrastructure components, due to which there are some differences in the supported capabilities and the instance-creation workflow.

Workflow for Creating an Instance in Oracle Cloud Infrastructure

Task More Information
Task 1: Understand the differences between instances created in Oracle Cloud Infrastructure and in Oracle Cloud Infrastructure Classic. Knowing these differences will help you select an appropriate region while creating your Oracle Java Cloud Service instance. Differences Between Instances in Oracle Cloud Infrastructure and Oracle Cloud Infrastructure Classic
Task 2: Create the required network, object storage, and security resources in the Oracle Cloud Infrastructure region where you intend to create the Oracle Java Cloud Service instance.
Task 3: Create an Oracle Database Cloud Service deployment in the region where you created the Oracle Cloud Infrastructure resources.
Task 4: Create the Oracle Java Cloud Service instance in the same Oracle Cloud Infrastructure region and virtual cloud network (VCN) as the Oracle Database Cloud Service deployment.

Differences Between Instances in Oracle Cloud Infrastructure and Oracle Cloud Infrastructure Classic

Feature Oracle Cloud Infrastructure Classic Oracle Cloud Infrastructure
Availability domains Not applicable Each region has multiple isolated availability domains, with separate power and cooling. The availability domains within a region are interconnected using a low-latency network. When creating an instance, you can select the availability domain that the instance should be placed in.

Compute shapes Standard and high memory shapes

Note: The list of available shapes may vary by region.

VM.Standard and BM.Standard shapes

Note: The list of available shapes may vary by region.

Networking You can attach instances to IP networks defined in Oracle Cloud Infrastructure Compute Classic. You must attach each instance to a subnet, in a virtual cloud network created in Oracle Cloud Infrastructure.

Public IP addresses You can reserve public IP addresses and assign them while creating an instance, or you can have the addresses auto-assigned. With either choice, the public IP addresses won’t change when you restart the nodes or the instance.

You can’t reserve and assign public IP addresses. The addresses are auto-assigned when the service instance is created, but won’t change when you restart the nodes or the instance.
Private IP addresses The private IP addresses are auto-assigned when the service instance is created. The addresses might change when you restart the nodes or the instance. For an instance attached to an IP network, when you restart a node, you can assign a fixed private IP address.

The private IP addresses are auto-assigned when the service instance is created. The addresses will not change when you restart the nodes or the instance.
Restrictions when using snapshots
  • You can’t delete or scale-in an instance that has a snapshot.
  • You can’t delete a snapshot if a clone created from it exists.
  • You can’t create a snapshot of a clone.
No restrictions.
Scaling the shape of a node Supported Not supported

Autoscaling a cluster Supported Not supported

Adding block storage You can perform the add-storage operation up to 6 times for a node. In each operation, you can add from 1 to 2048 GB. You can perform the add-storage operation up to 29 times for a node. In each operation, you can add 50 GB or a multiple of 50.

Managing access rules Use the Oracle Java Cloud Service interfaces to configure access rules. Configure security rules using the Oracle Cloud Infrastructure interfaces.

Using Oracle Identity Cloud Service to control access to applications deployed on the instance In accounts that use Oracle Identity Cloud Service, while creating an instance, you can enable Oracle Identity Cloud Service as the identity provider for applications deployed on the instance.

Not supported
Load balancer options within the service While creating an instance, if you enable Oracle Identity Cloud Service as the identity provider, an Oracle-managed load balancer is created and configured automatically for the instance.

If you don’t enable Oracle Identity Cloud Service, then you can add Oracle Traffic Director as the load balancer for an instance, either while creating the instance or later.

You can add Oracle Traffic Director as the load balancer for an instance, either while creating the instance or later.
Object storage for backups You can create the object storage container either before or during instance creation. You must create the object storage bucket in Oracle Cloud Infrastructure before creating the instance.

Virtual Image service level

Supported Not supported
Associating an instance with a RAC database deployment of Oracle Database Cloud Service

Supported Not supported
Changing the database association for an instance After creating an instance, you can change the infrastructure database (Oracle Database Cloud Service deployment) that the instance is associated with. Not supported