Quick Start

To create an Oracle Java Cloud Service instance, you must first provision an infrastructure schema database deployment. You may also need to satisfy additional prerequisites depending on your requirements. Be sure to review all the information and complete the necessary tasks before creating your first service instance.

Then perform the tasks described in the Provision Tasks table to use the REST API to create your first Java Cloud Service instance. Note that all documentation is applicable to using the REST API on any deployment option of Oracle Cloud unless otherwise indicated.

Using best practices will ensure that your Oracle Java Cloud Service instances remain compatible with all product features. See Administration Best Practices in Administering Oracle Java Cloud Service.

Account Information

The account creation e-mail you received from Oracle Cloud contains the identity domain, user name, and password for your Oracle Java Cloud Service account. If you do not have this information, contact your Oracle Cloud account administrator or service administrator. See also Obtain Account Information.

Required Oracle Cloud Roles

Oracle Java Cloud Service uses roles to control access to tasks and resources. When your cloud account is first set up, the service administrator is given the Java Administrator role along with additional service roles that are required to work with Oracle Java Cloud Service. See About Oracle Java Cloud Service Roles and User Accounts in Administering Oracle Java Cloud Service.

Secure Shell (SSH) Key Pair

To use SSH to access the VMs that make up your Oracle Java Cloud Service instance, you need a public/private key pair. Generate your own keys prior to creating a service instance, and then provide your public key when you create the instance. See:

Generate a Key Pair with OpenSSH in Administering Oracle Java Cloud Service

Generate a Key Pair with PuTTY in Administering Oracle Java Cloud Service

Oracle Cloud Databases

Every Oracle Java Cloud Service instance must be associated with an existing database in Oracle Cloud. This database contains the required infrastructure schema for Oracle WebLogic Server. Depending on whether you provision the Oracle Java Cloud Service instance on Oracle Cloud Infrastructure or Oracle Cloud Infrastructure Classic, the infrastructure schema database could be deployed on Oracle Autonomous Transaction Processing, Oracle Cloud Infrastructure Database, Oracle Database Cloud Service (Classic) or Oracle Database Exadata Cloud Service.

During provisioning of the Oracle Java Cloud Service instance, the required infrastructure schema is then created in the database deployment you associate the instance with.

If the associated infrastructure schema database deployment is Oracle Database Cloud Service (Classic), you can associate your Oracle Java Cloud Service instance with up to four application schema databases during provisioning. You can also base your Oracle Java Cloud Service instance on a custom PDB.

See Database in the Design Considerations for an Oracle Java Cloud Service Instance topic in Administering Oracle Java Cloud Service.

See also Before You Begin with Oracle Java Cloud Service in Administering Oracle Java Cloud Service.

For database options, see:

• Creating Bare Metal and Virtual Machine DB Systems in the Oracle Cloud Infrastructure documentation
• Provisioning Autonomous Transaction Processing in Using Oracle Autonomous Transaction Processing
• Creating Exadata DB Systems in the Oracle Cloud Infrastructure documentation
• Creating a Customized Database Deployment in Administering Oracle Database Cloud Service
• Creating a Database Deployment in Administering Oracle Database Exadata Cloud Service

Prerequisites for Instances on Oracle Cloud Infrastructure

Oracle Java Cloud Service requires certain networking and storage resources that you must set up before you can create service instances on Oracle Cloud Infrastructure resources.

See:

• Prerequisites for Oracle Platform Services on Oracle Cloud Infrastructure in the Oracle Cloud Infrastructure documentation
• About Java Cloud Service Instances in Oracle Cloud Infrastructure in Administering Oracle Java Cloud Service

Prerequisites for Instances on Oracle Cloud Infrastructure Classic

Depending on your requirements, you might have to complete one or more of the following tasks before creating your first Oracle Java Cloud Service instance.

See also Before You Begin with Oracle Java Cloud Service in Administering Oracle Java Cloud Service.

Prerequisite	More Information
Create an object storage container for your Oracle Java Cloud Service instance backups	If using new subscriptions, be sure to set a replication policy for your Oracle Cloud Infrastructure Object Storage Classic before you create the first container. Creating an object storage container before creating your Oracle Java Cloud Service instance is optional. If you do not create a container before you create your service instance, you can set the boolean parameter createStorageContainerIfMissing to true in your request, and specify a container name that does not yet exist. This enables the provisioning system to create the container for you before it provisions the service instance. See Creating Containers Using the REST API (tutorial)
Create IP networks. This is optional for accounts where regions are supported.	Using an IP network gives you more control over the configuration of the network in which your Oracle Java Cloud Service instance is placed. If you specify an IP network, each underlying VM can be auto-assigned a public and private IP address. When you specify an IP network during provisioning, you must also specify an infrastructure schema database that is on an IP network. If your Oracle Java Cloud Service instance and infrastructure schema database are attached to different IP networks, then the two IP networks must be connected to the same IP network exchange. Access rules required for the communication between the Oracle Java Cloud Service instance and infrastructure schema database are created automatically. See Creating an IP Network in Using Oracle Cloud Infrastructure Compute Classic. If you are provisioning a Java Cloud Service instance with Oracle Identity Cloud Service enabled, a public or Internet-facing load balancer must already be attached to the IP network you intend to use. See Creating a Load Balancer in Using Oracle Cloud Infrastructure Load Balancing Classic.
Create reserved IP addresses. This is optional for accounts where regions are supported.	A consequence of using an IP network is that the auto-assigned IP address could change each time the service instance is started. To assign fixed public IP addresses to service instances attached to the IP network, you can create reserved IP addresses, then provision a service instance that uses persistent IP addresses. See IP Reservations REST Endpoints.
Submit a request to obtain IP reservations (for accounts where regions are not supported)	If you plan to use an Oracle Exadata database with your Oracle Java Cloud Service instance in an account where regions are not supported, you must obtain IP reservations for the Managed Servers you are going to provision before creating the service instance; you will not be able to create the instance without IP reservations. See the My Oracle Support document entitled How to Request Authorized IPs for Provisioning a Java Cloud Service with Database Exadata Cloud Service (MOS Note 2163568.1) to learn how to submit a request for IP reservations.

Provision Tasks

Perform the following tasks to create your first Oracle Java Cloud Service instance using the REST API.

Task	More Information
Install cURL. The examples throughout the documentation use cURL to demonstrate how to access the Oracle Java Cloud Service REST API.	Use cURL
Create the request document, in JSON format, to define the details of your create service instance request.	Create the Request Document
Create your first Oracle Java Cloud Service instance, passing the request document defined previously.	Create Your First Service Instance
View the service instance details after the instance is created.	Review the Details of Your First Service Instance