Create an Oracle Java Cloud Service Instance Attached to a Public Subnet on Oracle Cloud Infrastructure

Oracle Java Cloud Service gives you detailed control over how you create your service instance.

There are several methods that you can use to create instances in Oracle Java Cloud Service. One of the easiest methods to create an instance is to use the Create Instance wizard in the web console. The wizard guides you through a short series of screens that present all the parameters that you can configure for your instance, including the WebLogic Server settings, backup and recovery configuration, load balancer parameters, and so on.

If you need to create an instance on a private subnet rather than on a public subnet, see Create an Oracle Java Cloud Service Instance Attached to a Private Subnet on Oracle Cloud Infrastructure.

Tutorial iconTutorial

Prerequisites

Before creating a custom Oracle Java Cloud Service instance:

Start the Create New Instance Wizard

Only Oracle Cloud Infrastructure This topic applies only to Oracle Cloud Infrastructure.

To create a service instance from the web console, you use the Create New Instance wizard.
To start the Create New Instance wizard:
  1. Access your service console.
  2. Click Create Service and select Java.

Specify Basic Service Instance Information

Only Oracle Cloud Infrastructure This topic applies only to Oracle Cloud Infrastructure.

On the Instance page of the Instance Creation Wizard, enter basic information for your service instance, including service name, service level, software release, and software edition.

Note:

You cannot change any of the following options after you have created the service instance.

Complete the following fields:

Field Description

Instance Name

Specify a name for the Oracle Java Cloud Service instance.

The service instance name:

  • Must contain one or more characters.

  • Must not exceed 30 characters.

  • Must start with an ASCII letter: a to z , or A to Z.

  • Must contain only ASCII letters or numbers.

  • Must not contain a hyphen.

  • Must not contain any other special characters.

  • Must be unique within the identity domain.

Description

(Optional) Enter a short description of the Oracle Java Cloud Service instance.

Notification Email

(Optional) Specify an email address where you would like to receive a notification when the service instance provisioning has succeeded or failed.

Region

Select region us-phoenix-1, us-ashburn-1, eu-frankfurt-1, or uk-london-1. If you select any other region, the instance will be created in Oracle Cloud Infrastructure Classic.

You must select the same region as the one where your Oracle Oracle Autonomous Transaction Processing database, Oracle Cloud Infrastructure database, or Oracle Database Cloud Service deployment resides.

Availability Domain

Select an availability domain. A region can have multiple isolated availability domains, each with separate power and cooling. The availability domains within a region are interconnected using a low-latency network.

You can select any availability domain that's in the same region as the Oracle Autonomous Transaction Processing, Oracle Cloud Infrastructure Database or Oracle Database Cloud Service database.

Subnet

Select the Oracle Cloud Infrastructure subnet to which the nodes of your instance must be attached.

This field provides a No Preference option and a list of the available subnets. Each subnet is shown in the format compartmentName | vcnName | subnetName. A tooltip lists the compartment name, VCN name, subnet name, and the OCID of the subnet.

  • To have the subnet assigned automatically, select No Preference. The subnet ManagedCompartmentForPaaS | svc-vcn | svc-subnet-... is used for your instance.

    Note: You cannot use the No Preference option if you plan to associate an Oracle Cloud Infrastructure Database with your service instance.

  • To assign a subnet explicitly, select a suitable subnet from the available options.

  • If none of the available subnets meets your networking requirements, then cancel the Create Instance wizard. In Oracle Cloud Infrastructure, create the required VCN and subnets, create policies to allow Oracle Java Cloud Service to use the VCN, and select the appropriate subnet while creating your instance. See Prerequisites for PaaS Services on Oracle Cloud Infrastructure in the Oracle Cloud Infrastructure documentation.

Database instances in Oracle Database Cloud Service and Oracle Cloud Infrastructure Database must be in the same region and virtual cloud network (VCN) as the Oracle Java Cloud Service instance. The database and service instance do not need to be in the same subnet. The database and service instance can be on different VCNs only if you configure VCN peering.

Tags

(Optional) Select existing tags or add tags to associate with the service instance.

To select existing tags, select one or more check boxes from the list of tags that are displayed on the pull-down menu.

To create tags, click Click to create a tag to display the Create Tags dialog box. In the New Tags field, enter one or more comma-separated tags that can be a key or a key:value pair.

If you do not assign tags during provisioning, you can create and manage tags after the service instance is created. See Creating, Assigning, and Unassigning Tags.

License Type

Choose whether you want to leverage the Bring Your Own License (BYOL) option or use your Oracle Java Cloud Service license.

  • The Bring Your Own License (BYOL) option enables you to bring your on-premises Oracle WebLogic Server licenses to Oracle Cloud. BYOL instances are billed at a lower rate than other instances. See Frequently Asked Questions: Oracle BYOL to PaaS.

    You must own a Universal Credits subscription or Government subscription in order to use BYOL. See About Oracle Java Cloud Service Subscriptions and Licenses.

    Note: Before you scale up or scale out a BYOL instance, you must have enough WebLogic Server licenses for the additional OCPUs that will be allocated to the instance after it is scaled.

  • If you choose to use your Oracle Java Cloud Service license, your account will be charged for the new service instance according to your Oracle Java Cloud Service agreement.

If you have both BYOL and Oracle Java Cloud Service entitlements, BYOL is selected by default, but you can change the license type. If you have BYOL entitlements only, BYOL is selected and you cannot change the license type. If you do not have BYOL entitlements, the Oracle Java Cloud Service license option is selected and you cannot change the license type.

Service Level

Select a service level:

  • Oracle Java Cloud Service

    Supports Oracle Java Cloud Service instance creation and monitoring; domain partitions; backup and restoration; patching; and scaling.

  • Oracle Java Cloud Service Fusion Middleware — Oracle WebCenter Portal

    (This service level is not supported for service instances that use an Oracle Autonomous Transaction Processing database)

    Leverages your Oracle WebCenter Portal license on Oracle Java Cloud Service.

    Selecting this option downloads additional installation tools to the location /u01/zips/upperstack on the Administration Server node. You must install the product yourself after creating this service instance. See the Provisioning Oracle WebCenter Portal Cloud Service tutorial.

    You must select Oracle WebLogic Server 12c (12.2.1.2.0) as the software release.

    This service level is unavailable for software release WebLogic Server 12c (12.2.1.3.0).

    You must select Enterprise Edition or Enterprise Edition with Coherence. Standard Edition is not supported.

    Note:

    Patching is not supported for service instances where Oracle Java Cloud Service Fusion Middleware—Oracle WebCenter Portal, Oracle Java Cloud Service Fusion Middleware—Oracle Data Integrator, or any other product that modifies the MW_HOME directory are installed. If you attempt to patch a service instance where any of these products are installed, patching prechecks issue an error message and patching fails.
  • Oracle Java Cloud Service Fusion Middleware — Oracle Data Integrator

    (Unsupported for Oracle Autonomous Transaction Processing databases)

    Leverages your Oracle Data Integrator license on Oracle Java Cloud Service.

    Selecting this option downloads additional installation tools to the location /u01/zips/upperstack on the Administration Server node. You must install the product yourself after creating this service instance. See the Provisioning Oracle Data Integrator Cloud Service tutorial.

    You must select Oracle WebLogic Server 12c (12.2.1.2.0) as the software release.

    This service level is unavailable for software release WebLogic Server 12c (12.2.1.3.0).

    You must select Enterprise Edition or Enterprise Edition with Coherence. Standard Edition is not supported.

    Note:

    Patching is not supported for service instances where Oracle Java Cloud Service Fusion Middleware—Oracle WebCenter Portal, Oracle Java Cloud Service Fusion Middleware—Oracle Data Integrator, or any other product that modifies the MW_HOME directory are installed. If you attempt to patch a service instance where any of these products are installed, patching prechecks issue an error message and patching fails.

Software Release

Select a WebLogic Server software release:

  • Oracle WebLogic Server 11g (11.1.1.7)

    Includes Oracle WebLogic Server 11g (10.3.6) and Oracle Fusion Middleware 11g (11.1.1.7) .

  • Oracle WebLogic Server 12c (12.1.3.0)

  • Oracle WebLogic Server 12c (12.2.1.2)

  • Oracle WebLogic Server 12c (12.2.1.3)

If you want to associate an Oracle Autonomous Transaction Processing database for your Oracle Java Cloud Service instance, you must select Oracle WebLogic Server 12c (12.2.1.3). Other software releases are unsupported.

You must select a version of Oracle WebLogic Server 12c if you want to use Oracle Java Cloud Service to create and manage an Oracle Coherence data tier in your service instance. If you select Oracle WebLogic Server 11g and want to use Oracle Coherence you must configure and start it manually after creating the service instance.

The WebLogic Server software runs on the Oracle Linux 6.6 platform.

Software Edition

Select a WebLogic Server software edition:

  • Standard Edition

  • Enterprise Edition

  • Enterprise Edition with Coherence

Note: High Performance Edition is listed a Enterprise Edition with Coherence in the console.

Metering Frequency

This option appears only if you have a traditional metered subscription. If you have a Universal Credits subscription, this field is absent.

Select a metering frequency to determine how you are billed for this service instance:

  • Hourly—Pay only for the number of hours that this service instance was running during your billing period.

  • Monthly—Pay one price for the full month irrespective of the number of hours that this service instance was running.

For services that are started in the middle of a month, the price will be pro-rated; you pay only for the partial month from the day the service instance is created.

Specify the Service Instance Details

Only Oracle Cloud Infrastructure This topic applies only to Oracle Cloud Infrastructure.

You must configure the size, shape, and other important details for your Oracle Java Cloud Service instance.

Specify WebLogic Configuration

Only Oracle Cloud Infrastructure This topic applies only to Oracle Cloud Infrastructure.

On the second page of the Instance Creation Wizard (Service Details), you start by configuring the size and shape of the Oracle Java Cloud Service instance.

Note:

Two tabs, Simple and Advanced, control which fields appear on the page. Fields that appear when you select the Simple tab also appear when you select the Advanced tab, but some fields appear only when you select the Advanced tab.

Complete the following fields:

Size and Shape Details Description

WebLogic Clusters

(Advanced option) You cannot change the value in this field, or add a new cluster, edit the configuration, or delete the cluster.

Compute Shape

Select the compute shape to use for all Administration Server and Managed Server nodes. The compute shape is the number of Oracle Compute Units (OCPUs) and amount of memory (RAM) that you want to allocate to these nodes. The selected shape is not used for Coherence or Load Balancer nodes.

The VM.Standard and BM.Standard shapes are supported.

If you purchased a Universal Credits subscription for Oracle Java Cloud Service, you will pay at the Pay-As-You-Go rate when you exceed your monthly or annual maximum credit. See About Oracle Java Cloud Service Subscriptions and Licenses.

Server Count

Select the initial number of Managed Servers that you want to provision in this service instance. The choices are: 1, 2, 4.

  • If you configure more than one Managed Server in the cluster, Oracle recommends that you also enable the Load Balancer.

  • You can also perform scaling operations to increase or decrease the server count after provisioning the service instance.

Domain Partitions

(Advanced option) Select the initial number of WebLogic Server domain partitions that you want to provision in this service instance. The choices are 0, 1, 2, or 4.

You cannot specify domain partitions if you selected one of the following service levels:
  • Oracle Java Cloud Service—Virtual Image

  • Oracle Java Cloud Service Fusion Middleware—Oracle WebCenter Portal

  • Oracle Java Cloud Service Fusion Middleware—Oracle Data Integrator

Enable Access to Administration Consoles

(Advanced option) Access to the administration consoles is enabled by default; selecting or deselecting this check box has no effect.

Deploy Sample Application

(Advanced option) By default, a sample application, sample-app.war, is deployed automatically to the Managed Servers in your instance. If you do not want to automatically deploy the sample application, deselect this check box.

Configure WebLogic Server Access

Only Oracle Cloud Infrastructure This topic applies only to Oracle Cloud Infrastructure.

On the Service Details page of the Wizard, configure the administrator credentials for the WebLogic Servers.

Complete the following fields:

Access Details Description

SSH Public Key

Specify the public key that will be used for authentication when connecting to a node in your instance by using a Secure Shell (SSH) client.

Click Edit to display the SSH Public Key for VM Access dialog, and then specify the public key using one of the following methods:

  • Select Key file name and use your web browser to select a file on your machine that contains the public key.

  • Select Key value and paste the value of the public key into the text area. Be sure the value does not contain line breaks or end with a line break.

  • Select Create a New Key if you want Oracle to generate a public/private key pair for you. You will be prompted to download these generated keys.

If you choose to create a new key, the generated private key file is in OpenSSH format. Before connecting to a node in this service instance with the PuTTY SSH client, you must first convert the key to PuTTY’s proprietary format. See Convert a Private Key with PuTTY.

Local Administrative User Name

Enter your choice of user name for the WebLogic Server administrator. The default is weblogic. This name is used to access the WebLogic Service Administration Console, Fusion Middleware Control, and Load Balancer Console for the service instance.

The name must be between 8 and 128 characters long and cannot contain any of the following characters:

  • Tab

  • Brackets

  • Parentheses

  • These special characters:

    • Left angle bracket (<)

    • Right angle bracket (>)

    • Ampersand (&)

    • Pound sign (#)

    • Pipe symbol (|)

    • Question mark (?)

You can also change the user name through the WebLogic Server Administration Console after the service instance is provisioned.

Password

Specify a password for the WebLogic Server administrator and confirm the password.

As a best practice, this password must start with a letter, be of 8 to 30 characters in length, and contain at least:

  • 1 uppercase character

  • 1 lower case character

  • 1 digit (0 through 9)

  • One of the following special characters: _ (underscore), - (hyphen), or # (pound sign or hash)

The following basic password criteria are acceptable, but Oracle does not recommend them:
  • Starts with a letter

  • Is between 8 and 30 characters long

  • Contains letters, at least one number, and, optionally, any number of these special characters:

    • Dollar sign ($)

    • Pound sign (#)

    • Underscore (_)

      No other special characters are allowed.

Configure the Coherence Data Tier

Only Oracle Cloud Infrastructure This topic applies only to Oracle Cloud Infrastructure.

If you want to create a Coherence Data Tier, provide details on the Service Details page of the Wizard.

Complete the following fields:

Coherence Data Tier Description

Provision Data Grid Cluster

(Advanced option) Select Yes to provision a Coherence data grid cluster in your service instance.

This option is only available if you selected Enterprise Edition with Coherence.

Compute Shape

Select the compute shape to use for all Managed Server nodes in the data grid cluster. The compute shape is the number of Oracle Compute Units (OCPUs) and amount of memory (RAM) that you want to allocate to these nodes.

The VM.Standard and BM.Standard shapes are supported.

This option is displayed only if Provision Data Grid Cluster is set to Yes.

Cluster Size

Set the initial number of Managed Servers that you want to provision in the data grid cluster. Valid values are 1–4.

This option is displayed only if Provision Data Grid Cluster is set to Yes.

The number of nodes in the data grid cluster is determined by Cluster Size / Managed Servers Per Node. If this ratio is a fraction, the number of nodes is rounded up to the next integer.

You can also perform scaling operations to increase or decrease the number of Coherence nodes after provisioning the service instance.

You cannot specify multiple data grid clusters.

Managed Servers Per Node

Set the number of Coherence Managed Servers to run on each node in the data grid cluster. Valid values are 1–8.

This option is displayed only if Provision Data Grid Cluster is set to Yes.

Configure the Databases

Only Oracle Cloud Infrastructure This topic applies only to Oracle Cloud Infrastructure.

On the Service Details page of the Wizard, provide details about the database(s) to use for the Oracle Java Cloud Service instance.

Complete the following fields:

Database Details Description

Database Type

Select the type of database you want to associate with your service instance:

  • Oracle Autonomous Transaction Processing
  • Oracle Cloud Infrastructure Database
  • Oracle Database Cloud Service (Classic)

Compartment

Select the compartment where the Oracle Autonomous Transaction Processing database or Oracle Cloud Infrastructure Database resides.

The Oracle Java Cloud Service console shows only compartments that are directly under the root compartment.

Database Instance Name

Select an Oracle Cloud Infrastructure Database or Oracle Database Cloud Service (Classic) deployment that you want to associate as the infrastructure schema database for your service instance.

The list only includes a database deployment if it is in an active state and not currently in the process of being provisioned.

Database instances in Oracle Database Cloud Service and Oracle Cloud Infrastructure Database must be in the same region and virtual cloud network (VCN) as the Oracle Java Cloud Service instance. The database and service instance do not need to be in the same subnet or availability domain. The database and service instance can be on different VCNs only if you configure VCN peering.

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 associate the same infrastructure schema database (or the same pluggable database) with multiple service instances. Backups of a database that is used with multiple Oracle Java Cloud Service instances contain data for all the instances. Therefore, if you restore the database from a backup, data for all the service instances is restored, which might not be the intended result.

Note the following additional constraints and limitations for Oracle Cloud Infrastructure databases:

  • To use a Bare Metal database, you must create the service instance with the Oracle Java Cloud Service REST API or CLI. The web console supports only VM and Exadata databases.
  • Service instances running WebLogic Server 12.1.3 are not supported with Oracle Cloud Infrastructure Database instances running Oracle Database 12.2.

Note the following additional constraints and limitations for Oracle Database Cloud Service (Classic) deployments:

  • You cannot use a database deployment running Oracle Database 18c as the infrastructure schema database.
  • You can use a database deployment running Oracle Database 12.2 as the infrastructure schema database, but only for service instances running Oracle WebLogic Server 12.2.1 or later.
  • Create Oracle Database Cloud Service deployments with a backup option other than NONE. This configuration enables Oracle Java Cloud Service to coordinate backups across your service instance and the database. Coordinated backups are not supported for other database services.

Database Instance

Select the PDB that you created for the Oracle Autonomous Transaction Processing database.

Note the following additional constraints and limitations:

  • Only the Oracle WebLogic Server 12.2.1.3 release is supported
  • The Oracle Java Cloud Service Fusion Middleware – Oracle WebCenter Portal and Oracle Java Cloud Service Fusion Middleware – Oracle Data Integrator service levels are not supported
  • The Oracle Java Cloud Service – Virtual Image service level is not supported

PDB Name

Select the pluggable database the service instance will connect to.

Note: The PDB value doesn't apply to databases running Oracle Database 11g.

  • For Oracle Cloud Infrastructure databases, the PDB name is populated if you selected the Oracle WebLogic Server 12c software release.
  • For Oracle Database Cloud Service (Classic) databases, if you don't specify a PDB name, Oracle Java Cloud Service uses the default Oracle Database 12c PDB name that was provided when the Oracle Database Cloud Service (Classic) database deployment was originally created.

Administrator User Name

Specify the name of the database administrator that Oracle Java Cloud Service will use to connect to the selected database and to provision the required schemas for this service instance.

This value is set automatically for:

  • Oracle Autonomous Transaction Processing database: ADMIN
  • Oracle Cloud Infrastructure Database: SYS

For Oracle Database Cloud Service (Classic) database deployments:

  • If you selected the software release Oracle WebLogic Server 11g (11.1.1.7), you can specify the default user SYS or any user that has been granted the DBA role.

  • If you selected the software release Oracle WebLogic Server 12c (any version), you can specify the user SYS or any user that has been granted the SYSDBA privilege.

Password

Enter the password for the database administrator.

Add Application Schema

(Optional) Add up to four Oracle Database Cloud Service (Classic) databases for your application schema . You cannot add Oracle Autonomous Transaction Processing or Oracle Cloud Infrastructure databases.

Click Add if you want to specify a separate Oracle Database Cloud Service (Classic) database deployment dedicated for your application schema. When you add an application database, the Oracle Java Cloud Service creates an additional data source in your Oracle WebLogic Server domain to connect to this database.

Use the Add Database Configuration dialog to select the name of an existing Oracle Database Cloud Service (Classic) deployment, and to provide a user name and password for this database.

Click Add and repeat this process for up to three more database deployments.

Configure Backup and Recovery

Only Oracle Cloud Infrastructure This topic applies only to Oracle Cloud Infrastructure.

On the Service Details page of the Wizard, specify details on the storage used for backup and recovery.

Complete the following fields:

Backup and Recovery Details Description

Backup Destination

(Advanced option) Select Both Remote and Disk Storage if you want to enable automated and on-demand backups for this service instance. Backups will be saved to object storage and to block storage volumes that are attached to the nodes of the instance.

The default value is None, meaning that you cannot use Oracle Java Cloud Service to take backups of this service instance. You can configure backups on a service instance after creating it.

Object Storage Container

This field is displayed only if Backup Destination is set to Both Remote and Disk Storage.

Enter the object storage location where backups of the service instance must be stored.

Enter the URL of a bucket in Oracle Cloud Infrastructure Object Storage. See Prerequisites for PaaS Services on Oracle Cloud Infrastructure in the Oracle Cloud Infrastructure documentation.

Format: https://swiftobjectstorage.region.oraclecloud.com/v1/namespace/bucket

To find out your namespace, sign in to the Oracle Cloud Infrastructure web console, click the tenancy name, and look for the Object Storage Namespace field.

Example: https://swiftobjectstorage.us-phoenix-1.oraclecloud.com/v1/myCompany/myBucket

User Name

This field is displayed only if Backup Destination is set to Both Remote and Disk Storage.

Enter the user name of the Oracle Cloud Infrastructure Object Storage user who created the bucket you specified earlier.

Object Storage Password

This field is displayed only if Backup Destination is set to Both Remote and Disk Storage.

Enter the Auth Token generated in Oracle Cloud Infrastructure for the user you specified. See Prerequisites for PaaS Services on Oracle Cloud Infrastructure in the Oracle Cloud Infrastructure documentation.

Configure the Load Balancer

Only Oracle Cloud Infrastructure This topic applies only to Oracle Cloud Infrastructure.

On the Service Details page of the Wizard, specify details to configure the load balancer(s) for the Oracle Java Cloud Service instance.

Complete the following fields:

Load Balancer Details Description

Load Balancer

Select one of the following load balancer options:

  • Oracle Traffic Director: One or two Oracle Traffic Director nodes within your service instance.

    Note: The dual-node configuration is in active-active mode, but failover to the second node is not automatic.

  • None: No load balancer will be configured for this instance.

Provisioning a load balancer is recommended if the cluster size is 2 or more.

If you have selected Oracle Traffic Director and configured one Oracle Traffic Director node, you can also add a second Oracle Traffic Director node to a service instance after creating the service instance. If you configured two Oracle Traffic Director nodes during provisioning, you cannot add another Oracle Traffic Director node.

If you have selected None, then you can add an Oracle Traffic Director load balancer after creating the service instance.

Compute Shape

This option is displayed only if Oracle Traffic Director is selected as the load balancer.

Select the compute shape to use for all the load balancer nodes in the service instance. The compute shape is the number of Oracle Compute Units (OCPUs) and amount of memory (RAM) that you want to allocate to these nodes.

The VM.Standard.* shapes and BM.Standard.* shapes are supported.

You are billed for Oracle Traffic Director nodes at the same price that you are billed for WebLogic Server nodes in your Oracle Java Cloud Service subscription. See About Oracle Java Cloud Service Subscriptions and Licenses.

Add Another Active OTD Node

This option is displayed only if Oracle Traffic Director is selected as the load balancer.

Select this check box to provision a second load balancer node running Oracle Traffic Director (OTD) in this service instance. Both load balancer nodes route traffic to the cluster of WebLogic Managed Servers.

You can also add a second load balancer node to a service instance after creating the service instance.

Load Balancing Policy

This option is displayed only if you have selected Oracle Traffic Director as the load balancer.

Select a load balancing policy.

If you selected Oracle Traffic Director, choose one of the following policies:

  • Least Connection Count (default)—Passes each new request to the Managed Server with the least number of connections. This policy is useful for smoothing distribution when a Managed Server receives more requests than it can handle efficiently.

  • Least Response Time—Passes each new request to the Managed Server with the fastest response time.

  • Round Robin—Evenly distributes requests across all Managed Servers, regardless of the number of connections or response times.

You can also use the Load Balancer console to modify this policy after creating the service instance.

Confirm Your Oracle Java Cloud Service Instance Creation

Only Oracle Cloud Infrastructure This topic applies only to Oracle Cloud Infrastructure.

On the Confirmation page of the provisioning wizard, review the service details.

If you need to change the service details, use the navigation bar or Back button at the top of the wizard to step back through the pages in the wizard. Click Cancel to cancel out of the wizard without creating a new service instance. If you are satisfied with your choices on the Confirmation page, click Create.

Sample of Options Displayed

If you selected the Bring Your Own License option, the Confirmation page will display a message alerting you to the fact that you have chosen to use an existing license. Check to make sure you have the appropriate entitlements.

The compute shape and server count is displayed in the WebLogic Configuration section.

Download the Instance Attributes in JSON Format

(Not available on Oracle Cloud at Customer)

Click Download JSON download icon to download a JSON-format file containing the parameters you specified in the provisioning wizard. You can use the JSON-formatted file as a sample to construct the request body for creating instances using the REST API.

Note that the file contains placeholders for passwords.

After Confirmation

After the Confirmation page closes, the Oracle Java Cloud Service console opens. Optionally, you can click on the service instance name to view status messages. If provisioning of your service instance fails but there are no fatal errors, the software automatically retries provisioning, after a lag time of 60 minutes. Messages about the auto-retry process and failed compute resources are displayed.

If you provided your email address for the Notification Email option, you will receive an email notification when the service instance provisioning has succeeded or failed.

Next Steps

  • After the service instance has been created, you can view the system messages logged during the creation process, including error messages. Click Instance Create and Delete History, then click the service instance name or Details.

  • If the provisioning process retried provisioning automatically, some failed resources might still exist. To clean up these failed resources, click the Complete Cleanup button. If you click the button once and not all failed resources are cleaned up, the Complete Cleanup button will remain. If this is the case, click the button again and wait. Repeat this process until the button is not longer displayed and all failed resources are cleaned up.

  • If you selected the Deploy Sample Application option, and want to test the sample application, see About the Sample Application Deployed to an Oracle Java Cloud Service Instance.