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 that the instance provides in either type of infrastructure is substantially the same. A few differences exist in the supported capabilities and the instance-creation workflows.
Workflow for Creating an Instance in Oracle Cloud Infrastructure
|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 Cloud database instance in the region where you created the Oracle Cloud Infrastructure resources.
This database is required to store the schema required for Oracle Java Cloud Service.
|Use the appropriate documentation, depending on the Oracle Database service that you want to associate with the Oracle Java Cloud Service instance:
Oracle Database Cloud Service: Create an Oracle Database Cloud Service Database Deployment
Oracle Cloud Infrastructure Database: Managing DB Systems
Oracle Autonomous Transaction Processing: Provision Autonomous Transaction Processing in Using Oracle Autonomous Transaction Processing
|Task 4: Create the Oracle Java Cloud Service instance in the same Oracle Cloud Infrastructure region and virtual cloud network (VCN) as the Oracle Cloud database instance.||Use the appropriate documentation, depending on whether you want to attach the Oracle Java Cloud Service instance to a public subnet or a private subnet:|
Differences Between Instances in Oracle Cloud Infrastructure and Oracle Cloud Infrastructure Classic
|Feature||Oracle Cloud Infrastructure||Oracle Cloud Infrastructure Classic|
|Availability domains||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.||Not applicable|
|Compute shapes||VM.Standard and BM.Standard shapes
Note: The shapes available might vary by region.
|Standard and high memory shapes
Note: The shapes available might vary by region.
|Database options for the infrastructure schema||
|Associating an instance with a RAC database for high availability||Use Oracle Cloud Infrastructure Database||Use Oracle Database Cloud Service|
|Networking||You must attach each instance to a subnet, in a virtual cloud network created in Oracle Cloud Infrastructure. If you specify a private subnet, the nodes of the instance can't be assigned public IP addresses.||You can attach instances to IP networks defined in Oracle Cloud Infrastructure Compute Classic. For such instances, you can choose to not assign public IP addresses.|
|Public IP addresses||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.||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.|
|Private IP addresses||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.||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.|
|Cloning||Supported for all service instances, except instances associated with Oracle Cloud Infrastructure Database or Oracle Autonomous Transaction Processing.||Supported for all service instances.|
|Restrictions when using colocated snapshots||No restrictions for colocated snapshots.||Colocated snapshots (stored in block storage) impose the following restrictions:
|Scaling the shape of a node||Not supported||Supported|
|Autoscaling a cluster||Not supported||Supported|
|Adding block storage||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.||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.|
|Managing access rules||Configure security rules using the Oracle Cloud Infrastructure interfaces.||Use the Oracle Java Cloud Service interfaces to configure access rules.|
|Load balancer options available within Oracle Java Cloud Service||While creating an instance, if you enable Oracle Identity Cloud Service as the identity provider, an Oracle-managed load balancer in Oracle Cloud Infrastructure
Load Balancing is created and configured automatically for the instance.
If you don’t enable Oracle Identity Cloud Service, then you can create an instance with an Oracle-managed load balancer, an Oracle Traffic Director load balancer, or no load balancer. You can also add an Oracle Traffic Director load balancer to an existing instance.
You cannot use Oracle Java Cloud Service to add an Oracle-managed load balancer to an existing service instance.
|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 a user-managed load balancer, either while creating the instance or later. Or you can choose not to configure a load balancer.
You cannot use Oracle Java Cloud Service to add an Oracle-managed load balancer to an existing service instance instance.
|Object storage for backups||You must create the object storage bucket in Oracle Cloud Infrastructure before creating the instance.||You can create the object storage container either before or during instance creation.|
|Virtual Image service level||Not supported||Supported|
|Changing the database association for an instance||Not supported||After creating an instance, you can change the infrastructure database (Oracle Database Cloud Service deployment) that the instance is associated with.|
Migrating to Oracle Cloud Infrastructure
If you provisioned an Oracle Java Cloud Service instance on an Oracle Cloud Infrastructure Classic region, tools are available to help you migrate the service instance to an Oracle Cloud Infrastructure region.