Before You Begin with Oracle Java Cloud Service

If you use a QuickStart template to create an Oracle Java Cloud Service instance, you do not need to fulfill any prerequisites. But in order to create a custom service instance, you must first provision an Oracle Database Cloud Service deployment. You may also need to satisfy additional prerequisites depending on your requirements.

Prerequisites for Instances in Oracle Cloud Infrastructure

Oracle Java Cloud Service instances in Oracle Cloud Infrastructure require certain networking and storage resources that you must create in Oracle Cloud Infrastructure.

To learn about these resources, see Prerequisites for Oracle Platform Services in the Oracle Cloud Infrastructure documentation.

For step-by-step instructions to create these resources, see Tutorial icon Creating the Infrastructure Resources Required for Oracle Platform Services.

To create an instance attached to an IP network, you must first create the required IP network, if it doesn’t exist.

To assign fixed IP addresses to the nodes of an instance, you must first reserve the required number of IP address.

Creating an Oracle Database Cloud Service Database Deployment

Oracle Java Cloud Service uses Oracle Database Cloud Service to host the Oracle schemas required for Oracle Java Cloud Service.

Note:

The database that Oracle Java Cloud Service requires is a deployment in Oracle Database Cloud Service, not Oracle Cloud Infrastructure Database.

Prior to creating a custom Oracle Java Cloud Service instance, use your Oracle Database Cloud Service subscription to create a database deployment. As part of the Oracle Java Cloud Service instance creation process, Oracle Java Cloud Service provisions this database deployment with the required schemas.

It is not necessary to create a database deployment prior to creating an Oracle Java Cloud Service instance from a QuickStart template. See Creating an Oracle Java Cloud Service Instance by Using a QuickStart Template.

For information about subscribing to Oracle Database Cloud Service, provisioning database deployments, and using Oracle RAC database deployments, see Getting Started with Database Cloud Service in Administering Oracle Database Cloud Service.

You can optionally create up to four database deployments for your application schemas. Alternatively, if your database deployment is running Oracle Database 12c , you can create a second pluggable database (PDB) for your application schemas in a single database deployment. You cannot specify an application schema database if your software edition is Oracle Java Cloud Service—Virtual Image.

Oracle Java Cloud Service instances based on WebLogic Server 12.2 support using an Oracle Database 12.2 database deployment as an infrastructure database and/or an application database.

Note:

Oracle Java Cloud Service does not support Oracle Database 18c.

The Oracle Database Cloud Service database deployment on Oracle Cloud Infrastructure must be in the same region and VCN as the Oracle Java Cloud Service instance you are creating on Oracle Cloud Infrastructure. The instances do not need to be on the same subnet.

Note:

To ensure that you can restore the database for an Oracle Java Cloud Service instance without risking data loss for other service instances, Oracle recommends that you do not use the same Oracle Database Cloud Service database deployment with multiple Oracle Java Cloud Service instances. Backups of an Oracle Database Cloud Service database deployment that is used with multiple Oracle Java Cloud Service instances contain data for all the Oracle Java Cloud Service instances. If you restore the database while restoring an Oracle Java Cloud Service instance, data for all the Oracle Java Cloud Service instances is restored.

When you create an Oracle Java Cloud Service instance, you are prompted for the following information about your database deployments:

  • Name of the database deployment that is up and running

  • Pluggable database name (for Oracle Database 12c only)

  • Database administrator user name and password

  • Connection string to the database deployment (for Virtual Image service level only)

  • Application schemas (Optional)

Similar to Oracle Java Cloud Service, Oracle Database Cloud Service supports a standard service level and a Virtual Image service level. The following table summarizes the compatibility between these service levels.

Service Level Database Cloud Service Database Cloud Service—Virtual Image

Oracle Java Cloud Service

Supported

  • This service level must be used if you intend to use an Oracle Real Application Clusters (RAC) database. When creating the database deployment, make sure you select the database edition called Enterprise Edition - Extreme Performance.

  • When creating the database deployment, make sure you do not set the Backup Destination to None; instead you should select one of the other available backup options.

Not supported

Oracle Java Cloud Service—Virtual Image

Supported

Supported

After creating the database deployment, perform the tasks described in Using a Database Cloud Service - Virtual Image Database Deployment

Creating an SSH Key Pair

In order to use Secure Shell (SSH) to access the VMs that make up your Oracle Java Cloud Service instance, you need a public/private key pair.

Choose from one of these options:

  • Let Oracle Java Cloud Service generate the keys for you as part of the process of creating a new service instance. You will be prompted to download the generated public key.

  • Generate your own keys prior to creating a service instance, and then upload your public key when you create a service instance. See Generating a Key Pair with OpenSSH or Generating a Key Pair with PuTTY.

Creating an Object Storage Container

If you enable backups on an Oracle Java Cloud Service instance, backups of the service instance are stored in an object storage container.

The steps for creating an object storage container for an Oracle Java Cloud Service instance vary depending on whether you create the instance in Oracle Cloud Infrastructure Classic or Oracle Cloud Infrastructure.

Oracle Cloud Infrastructure

You must create a storage bucket before you attempt to provision an Oracle Java Cloud Service instance. See Prerequisites for PaaS Services on Oracle Cloud Infrastructure in the Oracle Cloud Infrastructure documentation.

Oracle Cloud Infrastructure Classic

When you create an Oracle Java Cloud Service instance, you are prompted to supply the name of a storage container along with the credentials for an Oracle Cloud user who has read/write access to the container. You can either provide an existing storage container that you previously created, or Oracle Java Cloud Service can create the specified storage container for you.

Before you can create containers and objects, you must have an active subscription to Oracle Cloud Infrastructure Object Storage Classic. Be sure you also select a Replication Policy before you create your first storage container. See Selecting a Replication Policy for Your Service Instance in Using Oracle Cloud Infrastructure Object Storage Classic.

To create a storage container, choose from one of these options:

Note:

  • A storage container is not required if you are creating Oracle Java Cloud Service—Virtual Image instances and using the Virtual Image service level of Oracle Database Cloud Service only.

  • Do not use a storage container that you use for backups of Oracle Java Cloud Service instances for any other purpose. For example, do not use it to back up Oracle Database Cloud Service database deployments. Using the container for multiple purposes can result in billing errors.

Using a Database Cloud Service - Virtual Image Database Deployment

In order to use a Oracle Database Cloud Service - Virtual Image database deployment when creating an Oracle Java Cloud Service - Virtual Image instance, you must set up the Oracle Database Cloud Service environment appropriately. Otherwise, Oracle Java Cloud Service instance provisioning fails.

Note:

This topic is not relevant to Oracle Cloud Infrastructure regions.

This task requires the use of a Secure Shell (SSH). For more information, see Connecting to a Compute Node Through a Secure Shell (SSH) in Administering Oracle Database Cloud Service.

Before attempting the following procedure, you must first create a Oracle Database Cloud Service—Virtual Image database deployment. See Creating a Database using the Virtual Image Service Level in Using Oracle Database Cloud Service.
To set up the database environment:
  1. Use a secure shell (SSH) tool to access a compute node associated with your Oracle Database Cloud Service - Virtual Image database deployment. Log in as the user oracle.
  2. Edit the .bashrc file and add the following entries:

    For 12.2 databases:

    export ORACLE_HOME="/u01/app/oracle/product/12.2.0/dbhome_1"
    export PATH="$ORACLE_HOME/bin:$PATH"

    For 12.1 databases:

    export ORACLE_HOME="/u01/app/oracle/product/12.1.0/dbhome_1"
    export PATH="$ORACLE_HOME/bin:$PATH"

    For 11.2 databases:

    export ORACLE_HOME="/u01/app/oracle/product/11.2.0/dbhome_1"
    export PATH="$ORACLE_HOME/bin:$PATH"
    These are the default values for ORACLE-HOME. If you set a different ORACLE_HOME when you created the database, use that.

    Note:

    Ensure that you add these entries to the .bashrc file, not the bash_profile file.
  3. Ensure that your user has SYSDBA administrator privileges.
  4. Do not set the $ORACLE_SID=ORCL variable in the .bashrc file.

    If ORACLE_SID is set, unset it:

    $ unset ORACLE_SID
  5. Exit your SSH session, then start a new SSH session as user oracle.
  6. Enter the following sqlplus command:
    sqlplus sys/SYS_Password@"DB_Host_Name:port/pdb1" as sysdba

    Where:

    SYS_Password—Password for the SYS administrator

    DB_Host_Name—Name of your Oracle Database Cloud Service - Virtual Image database deployment

    port—Use port 1521

  7. Configure tablespace encryption:
    1. If using an Oracle 12c database, switch to the container database (CDB):
      SQL> ALTER SESSION SET CONTAINER = CDB$ROOT;
    2. Change the tablespace encryption system parameter:
      SQL> ALTER SYSTEM SET ENCRYPT_NEW_TABLESPACES=DDL SCOPE=BOTH;
  8. Exit your SQL*Plus session:
    SQL> EXIT
  9. Exit your SSH session.

You can now successfully create an Oracle Java Cloud Service - Virtual Image instance using the Oracle Database Cloud Service - Virtual Image database deployment.

Using an Oracle Database Exadata Cloud Service Deployment

Not Oracle Cloud Infrastructure This topic does not apply to Oracle Cloud Infrastructure.

You can create an Oracle Java Cloud Service instance that uses an Oracle Database Exadata Cloud Service database deployment. A manual IP reservation procedure is required before you can create your instance.

If you are not familiar with Oracle Database Exadata Cloud Service, see Creating a Database Deployment in Administering Oracle Database Exadata Cloud Service.

Your Oracle Java Cloud Service instance can use an Oracle Database Exadata Cloud Service database deployment for either the Oracle Required Schema or Application Schema databases.
  1. Create an Oracle Database Exadata Cloud Service database deployment if you have not done already.
  2. Determine the initial size for the Oracle WebLogic Server cluster you will define when you create your Oracle Java Cloud Service instance.
  3. Log in to support.oracle.com (My Oracle Support).
  4. File a Service Request to obtain authorized IP addresses for your Oracle Java Cloud Service instance.
    Oracle will provide IP addresses and open up the firewall at these addresses on the Oracle Exadata Cloud Service.
    In the Service Request, specify the following information:
    • Your identity domain

    • Oracle Required Schema database name, which must be the name of the Oracle Exadata Cloud Service database deployment if you are not specifying a database deployment for the Application Schema

    • (Optional) Application Schema database deployment name

    • Desired number of servers in your WebLogic Server cluster

Selecting an IP Network for a Service Instance with a Managed Load Balancer

Not Oracle Cloud Infrastructure This topic does not apply to Oracle Cloud Infrastructure.

Not Oracle Cloud at Customer This topic does not apply to Oracle Cloud at Customer.

To select an IP network for a service instance that includes a managed load balancer, you must first attach an internet-facing load balancer to the IP network.

Enabling authentication with Oracle Identity Cloud Service when you provision a Oracle Java Cloud Service instance automatically configures an instance of Oracle Cloud Infrastructure Load Balancing Classic, a managed load balancer. In this case, you must first attach an internet-facing load balancer to the IP network, if one is not already attached. In order for traffic from outside the Cloud to reach the managed load manager, this traffic must first pass through the internet-facing load balancer.

You must create a public or private load balancer on the IP network before you provision an Oracle Java Cloud Service with a public or private load balancer, respectively.

If the IP network selected for the service instance doesn’t have a load balancer, but is connected to an IP Network Exchange that has another IP network that does have a load balancer, then that load balancer will be used.

The Create New Instance wizard allows you to select an IP network when an internet-facing load balancer does not exist on the IP network, but an error occurs during the provisioning process. Create the internet-facing load balancer before you attempt to provision the Oracle Java Cloud Service instance again.

See Creating a Load Balancer in Using Oracle Cloud Infrastructure Load Balancing Classic.