Before you begin using Oracle Java Cloud Service to create service instances, you must provision an Oracle database. You may also need to satisfy additional prerequisites depending on your requirements.
Oracle Java Cloud Service requires access to an existing relational database that contains the standard Oracle Infrastructure schemas. Oracle Java Cloud Service uses Java Database Connectivity (JDBC) to access this database.
Select one of these options:
Create a database with Oracle Database Cloud Service. See Creating an Oracle Database Cloud Service Database Deployment
Use an on-premises Oracle database.
When you create an Oracle Java Cloud Service instance, you have to provide the following information about the database:
One of the following:
Name of an Oracle Database Cloud Service database deployment
A connection string to an on-premises database in one of these formats:
User name for the database administrator
Password for the database administrator, or the password that was specified when the Oracle Database Cloud Service database deployment was created.
Oracle Java Cloud Service can use Oracle Database Cloud Service to host the Oracle schemas required for Oracle Java Cloud Service.
Prior to creating an 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 Oracle schemas.
For information about subscribing to Oracle Database Cloud Service, provisioning database deployments, and using Oracle RAC database deployments, see Using Oracle Database Cloud Service.
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
Note:To ensure that you can restore the database for an Oracle Java Cloud Service instance without risking data loss for other service instances, 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.
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 private key when you create a service instance. See Generating a Secure Shell (SSH) Public/Private Key Pair.
Oracle Java Cloud Service uses a remote Network File System (NFS) to store Oracle Java Cloud Service instance backups.
The remote NFS share is not permanently attached to the service instance’s WebLogic Server Administration Server virtual machine.
A remote backup destination is not required for service instances created at the Oracle Java Cloud Service—Virtual Image service level.
When creating an Oracle Java Cloud Service instance, you specify the location of the NFS share in one of the following formats:
Note:The backup folder must be owned by
gid=1000, and the permissions
rwx------must be given.
When creating an Oracle Java Cloud Service instance, you must select a public access network and a database network.
Contact your Oracle Cloud Administrator for the names of two networks:
Public Access Network: The network that will be used by clients to access applications running on the service instance. It typically uses the format
/tenant_name/public/EoIB_vNet_name. For example,
Database Network: The network through which the service instance will access the specified Oracle database. For example,