Create a Custom Oracle Java Cloud Service Instance on Oracle Cloud Infrastructure Classic

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.

You can provision Oracle WebCenter Portal and Oracle Data Integrator on your Oracle Java Cloud Service only using the REST API.

Tutorial

Description of jcs_diagram_create_workflow.png follows

Description of the illustration jcs_diagram_create_workflow.png

Prerequisites

Before creating a custom Oracle Java Cloud Service instance:

Review the prerequisites described in Before You Begin with Oracle Java Cloud Service
Review the options described in Design Considerations for an Oracle Java Cloud Service Instance

Procedure

Start the Create New Instance Wizard

This topic does not apply to Oracle Cloud Infrastructure.

To create an service instance from the web console, you use the Create New Instance wizard.

To start the Create New Instance wizard:

Access your service console.
Click Create Instance.

Specify Basic Service Instance Information

This topic does not apply 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, metering frequency, software release, and software edition.

Note:

Except for tags, 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 of any events occurring with the service instance, including whether provisioning has succeeded or failed.
Region	(Available only if your account has regions) Select a region if you want to create the service instance in a specific region, or if you want to use a custom IP network. You must also select a region if you intend to assign reserved IP addresses to your service instance nodes. A region supports either Oracle Cloud Infrastructure or Oracle Cloud Infrastructure Classic. For a list of available regions, see Data Regions for Platform and Infrastructure Services. The database that you intend to associate with your Oracle Java Cloud Service instance must be in the same region. If you select No Preference, Oracle Java Cloud Service will select one of the available Oracle Cloud Infrastructure Classic regions. However, you will not be able to use an IP network or reserved IP addresses for your service instance.
IP Network	(Only if a region is selected) (Not available on Oracle Cloud Infrastructure) Select an IP network if you want to create the service instance in an IP network that you’ve defined. By default, each node in your instance is auto-assigned a public and a private IP address. The IP addresses might change each time the service instance is restarted. You can reserve and assign fixed public IP addresses. In order to select an IP network if you have selected Enable Authentication Using Identity Cloud Service, which automatically configures a managed load balancer, you must first attach an internet-facing load balancer to the IP network. This field is not relevant to Oracle Cloud Infrastructure.
Assign Public IP	(Not available on Oracle Cloud Infrastructure) Choose whether to assign public IP addresses to the nodes in your service instance. You must first select an Oracle Cloud Infrastructure Classic region and specify an IP network. If you select this check box (default), then any node added during instance provisioning, or later added as part of a scaling operation, will have a public IP address assigned to it. You will be able to directly access the nodes from the public Internet. This selection is for use cases where you intend to deploy Java EE applications to the Oracle Java Cloud Service instance and access them from the public Internet. If you deselect this check box, then any node added during instance provisioning, or later added as part of a scaling operation, will not have a public IP address assigned to it. You will not be able to directly access the nodes from the public Internet. This selection is for use cases where you intend to deploy Java EE applications to the Oracle Java Cloud Service instance and access them only within your IP network or from your on-premises data center over a VPN network.
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 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.
Identity Domain	(Not available on Oracle Cloud at Customer) Select the identity domain in Oracle Identity Cloud Service in which to create this service instance. By default, the instance is created in the primary identity domain.
The service security administrator	(Not available on Oracle Cloud at Customer) (Optional) Specify the username for the security administrator for the service instance in the selected identity domain. This user gets rights to administer security artifacts (roles, AppId, OAuth IDs, and so on). The username can be the administrator of the selected identity domain or a user in the selected identity domain. You can leave this field blank only if you are the administrator of the selected identity domain or a user in the selected identity domain.
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. 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.
Software Edition	Select a WebLogic Server software edition: Standard Edition Enterprise Edition High Performance Edition If you purchased a Non-Metered subscription for Oracle Java Cloud Service, you can select a software edition that you did not purchase as part of your subscription. Making this selection will incur additional charges to your account.
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

This topic does not apply to Oracle Cloud Infrastructure.

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

Topics

Specify WebLogic Configuration

This topic does not apply 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) If you selected Enable Authentication Using Identity Cloud Service, your instance will be provisioned with an Oracle-managed load balancer. You can add, edit, or delete up to 8 WebLogic clusters for the service instance, with a maximum of 8 servers per cluster. You specify the cluster name, compute shape, and server count. Optionally, you can specify a path prefix, which determines how the managed load balancer routes traffic to different clusters. If you do not specify a path prefix, the cluster name is used as the path prefix. After you specify these values, you can edit them: Click Add to add a new cluster. Select a cluster and click Edit to update its configuration. Click Delete to delete the cluster. If Enable Authentication Using Identity Cloud Service is not selected, then a single cluster is created during instance provisioning. You cannot add clusters using the console, but clusters can be added using the REST API.
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. (Advanced option) When you create multiple WebLogic clusters, you can assign a different compute shape for different clusters. This field displays the compute shape of the selected cluster. 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.
Server Count	Select the initial number of Managed Servers that you want to provision in this service instance. The choices are: `1`, `2`, `4`. This field is not relevant if you selected Standard Edition. In this case, only one Managed Server is configured. 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. (Advanced option) When you create multiple clusters, you can assign a different server count to different clusters. You can configure a maximum of 8 servers per cluster. This field displays the server count for the selected cluster.
Reserved IPs	(Not available on Oracle Cloud Infrastructure) Select reserved IP addresses for the nodes in your cluster, or leave the default value as Assign Automatically if you want Oracle to automatically assign IP addresses to these nodes. The number of IP addresses that you select must equal the number of nodes in the cluster. This option is displayed only if you selected a specific Region for this service instance. You create IP reservations by using the Reserved IPs tab in the Oracle Java Cloud Service Console. If you do not see this tab on the console, click the gear icon next to this field and follow the instructions to create your first IP reservation. After creating IP reservations, you need to restart the instance creation wizard.
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`. This option is also not relevant if you selected Standard Edition as the software edition.
Enable Access to Administration Consoles	(Advanced option) Select this check box if you want to enable access to the WebLogic Service Administration Console, Fusion Middleware Control, and Load Balancer Console for the service instance. If you do not select this option, these consoles will not be externally accessible, and also will not appear as choices in the service instance’s menu . Alternatively, you can enable access to the administration consoles after creating the service instance. See Enable Console Access for a Service Instance If this check box is enabled, the This Source CIDR range field can access Admin Consoles option is displayed. By default, the source CIDR range is `0.0.0.0/0`, so the administration console is accessible from the public internet. You can specify a source CIDR range so that only the IP addresses within the specified range can access the administration console. Note: Enabling access to the administration console through port 7002 allows access to the WebLogic Service Administration console from the pubic internet if a source CIDR range is not specified, else it allows access to the IP addresses only within the specified CIDR range. If you have configured Oracle Traffic Director (OTD) for the service instance, enabling access to the administration console through port 8989 allows access to the Oracle Traffic Director and the Load Balancer console.
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.

Assign Reserved IP Addresses for a Service Instance in a Region

This topic does not apply to Oracle Cloud Infrastructure.

If regions are enabled in your identity domain, you can select a region in which your Oracle Java Cloud Service instance will reside. If a region is selected, you can assign reserved IPs from within that region for your service instance nodes.

Complete the following field:

IP Reservation Details	Description
Reserved IPs	(Not available on Oracle Cloud Infrastructure) Select reserved IP addresses for the nodes in your cluster, or leave the default value as Assign Automatically if you want Oracle to automatically assign IP addresses to these nodes. The number of IP addresses that you select must equal the number of nodes in the cluster. This option is displayed only if you selected a specific Region for this service instance. You create IP reservations by using the Reserved IPs tab in the Oracle Java Cloud Service Console. If you do not see this tab on the console, click the gear icon next to this field and follow the instructions to create your first IP reservation. After creating IP reservations, you need to restart the instance creation wizard.

IP Reservation Details

Description

Reserved IPs

(Not available on Oracle Cloud Infrastructure)

Select reserved IP addresses for the nodes in your cluster, or leave the default value as Assign Automatically if you want Oracle to automatically assign IP addresses to these nodes. The number of IP addresses that you select must equal the number of nodes in the cluster.

This option is displayed only if you selected a specific Region for this service instance.

You create IP reservations by using the Reserved IPs tab in the Oracle Java Cloud Service Console. If you do not see this tab on the console, click the gear icon next to this field and follow the instructions to create your first IP reservation. After creating IP reservations, you need to restart the instance creation wizard.

Assign Reserved IP Addresses for an Oracle Database Exadata Cloud Service Database

This topic does not apply to Oracle Cloud Infrastructure.

If you are provisioning an Oracle Java Cloud Service instance in an Oracle Cloud Infrastructure Classic region, you can associate your service instance with an Oracle Database Exadata Cloud Service database for an infrastructure schema or application database.

The procedure for assigning reserved IP addresses for the Oracle Database Exadata Cloud Service infrastructure schema or application database is the same as the procedure for assigning reserved IP addresses for any other database, except that you must first whitelist the IP addresses you want to assign. See Enabling Network Access to a Compute Node in Administering Oracle Database Exadata Cloud Service.

Configure WebLogic Server Access

This topic does not apply 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.
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 Server 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. If you selected an Oracle Database Exadata Cloud Service database deployment for Database Instance Name, 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) If you did not select an Oracle Database Exadata Cloud Service database deployment, Oracle still recommends following these password requirements as a best practice. However, the following basic password criteria are acceptable: 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.
Enable Authentication Using Identity Cloud Service	Select this check box if you want WebLogic Server to authenticate application users and administrators against Oracle Identity Cloud Service in addition to the local WebLogic Server identity store. This field appears only if your cloud account includes Oracle Identity Cloud Service and Oracle Cloud Infrastructure Load Balancing Classic. By default, the WebLogic Server domain in the service instance is configured to use only the local WebLogic Server identity store to maintain administrators, application users, groups, and roles.

Configure the Coherence Data Tier

This topic does not apply 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 High Performance Edition.
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. 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

This topic does not apply 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 Instance Name	Select an existing Oracle Database Cloud Service (Classic) deployment or Oracle Database Exadata Cloud Service deployment to connect to this service instance. Oracle Java Cloud Service provisions the selected database with the required schemas for running a service instance. The list only includes a database deployment if it meets the following criteria: Is in an active state and not currently in the process of being provisioned Is not configured with a Backup Destination set to `None` (not applicable to Oracle Database Cloud Service — Virtual Image deployments). Note the following additional constraints and limitations: 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. Oracle Java Cloud Service does not support Oracle Database 18c. If you selected an IP Network for this service instance, you must also select an Oracle Database Cloud Service (Classic) database deployment that is attached to an IP network. If the service instance and database deployment are attached to different IP networks, the two IP networks must be connected to the same IP network exchange.
PDB Name	Specify the pluggable database the service instance will connect to. 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	Enter the name of the database administrator that Oracle Java Cloud Service will use to connect to the selected database deployment and to provision the required schemas for this service instance.
Password	Enter the password for the database administrator.
Add Application DB	(Advanced option) Add a up to four database deployments for your application schema. Click Add if you want to specify a separate Oracle Database Cloud Service database deployment or Oracle Database Exadata Cloud Service database 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 database deployment or Oracle Database Exadata Cloud Service database, 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

This topic does not apply 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. This field is not relevant if you selected Oracle Java Cloud Service—Virtual Image.
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 by specifying the URL of a container. The object storage container field in the instance creation wizard is auto-populated with a default container URL in the format `restEndpointUrl/JaaS`, where `restEndpointUrl` is the REST endpoint URL of theOracle Cloud Infrastructure Object Storage Classic service in the account, and `JaaS` is the default container name. You can change the container name. Note that if the account doesn’t include an Oracle Cloud Infrastructure Object Storage Classic service entitlement, then the container field is not auto-populated. If you have a container, specify the URL of the container in Oracle Cloud Infrastructure Object Storage Classic. Format: `rest_endpoint_url/containerName` You can find the REST endpoint URL of the Oracle Cloud Infrastructure Object Storage Classic service instance in the Infrastructure Classic Console. Example: `https://acme.storage.oraclecloud.com/v1/MyService-acme/MyContainer` Note: You can select the Create Object Storage Container check box to have a new container created automatically.
User Name	This field is displayed if Backup Destination is set to Both Remote and Disk Storage, except if you selected Enable Authentication Using Identity Cloud Service. Enter the user name of the Oracle Cloud Infrastructure Object Storage Classic service user who created the container you specified earlier. If the container doesn’t exist, then enter the user name of a service administrator.
Password	This field is displayed only if Backup Destination is set to Both Remote and Disk Storage, except if you selected Enable Authentication Using Identity Cloud Service. Enter the password of the user you specified.
Create Object Storage Container	This option is displayed only if Backup Destination is set to Both Remote and Disk Storage. If the Oracle Cloud Infrastructure Object Storage Classic container that you specified doesn’t exist, or if you aren’t sure whether it exists, then select this check box. If the container doesn’t exist, it will be created automatically.

Configure the Load Balancer

This topic does not apply 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
Provision Local Load Balancer	(Advanced option) Select Yes to provision a load balancer node running Oracle Traffic Director in this service instance. This user-managed load balancer is configured to distribute client requests to the Managed Servers in the service instance. Provisioning a load balancer is recommended if the cluster size is 2 or more. The default value is No. If you selected Enable Authentication Using Identity Cloud Service, then you cannot configure a user-managed load balancer. An Oracle-managed load balancer is provisioned for you automatically. You can also add an Oracle Traffic Director load balancer node to a service instance after creating the service instance.
Compute Shape	This option is displayed only if Provision Local Load Balancer is set to `Yes`. 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. You are billed for load balancer nodes at the same price that you are billed for WebLogic Server nodes in your Oracle Java Cloud Service subscription.
Add Another Active OTD Node	This option is displayed only if Provision Local Load Balancer is set to `Yes`. 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.
Reserved IPs	Select reserved IP addresses for the load balancer nodes in your cluster, or leave the default value as Assign Automatically if you want Oracle to automatically assign IP addresses to these nodes. The number of IP addresses that you select must equal the number of load balancer nodes in the service instance. This option is displayed only if these conditions are true: You selected a specific Region for this service instance. Provision Local Load Balancer is set to `Yes` You create IP reservations by using the Reserved IPs tab in the Oracle Java Cloud Service Console. If you do not see this tab on the console, click the gear icon next to this field and follow the instructions to create your first IP reservation. After creating IP reservations, you need to restart the instance creation wizard. See Managing IP Reservations.
Load Balancing Policy	This option is displayed if you selected Enable Authentication Using Identity Cloud Service or Provision Local Load Balancer. If you selected Provision Local Load Balancer, 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. If you selected Enable Authentication Using Identity Cloud Service, choose one of the following policies: Round Robin— (default) Same as above. IP Hash—The IP Hash policy uses an incoming request's source IP address as a hashing key to route traffic to the same backend server. The load balancer routes requests from the same client to the same backend server as long as that server is available. Least Connection Count—Same as above. You can also use the Load Balancer console to modify this policy after creating the service instance.
Load Balancer Type	This field is displayed only if you have specified an Oracle Cloud Infrastructure Classic region and an IP network, and you have selected Oracle Identity Cloud Service as the authentication provider. Select Public or Private as the load balancer type. Public—Enables access to the service instance from the public Internet. Private—Used to enable access to private workloads over VPN from your on-premises network. This feature is only available forOracle Cloud Infrastructure Classic.

Confirm Your Oracle Java Cloud Service Instance Creation

This topic does not apply 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. If you have selected BYOL license type, a link to BYOL terms appears. Click the link to open the BYOL FAQ.

If you assigned tags to the service instance, the tags are displayed in the Service section.

The compute shape and server count is displayed in the WebLogic Configuration section. If you have multiple clusters, this section displays the compute shape and server count for each cluster. To display the compute shape and server count for all clusters, select Show more.

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 did not select the Enable Access to Administration Consoles option, then in order to use these tools to modify the default configuration or to deploy applications, see Enable Console Access for a Service Instance.
If you selected the Enable Authentication with Oracle Identity Cloud Service option, you can use Oracle Identity Cloud Service to create additional WebLogic Server users. See Use Oracle Identity Cloud Service with Oracle Java Cloud Service.
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.
If you associated an Oracle Real Application Cluster (RAC) database with your service instance, Oracle recommends that you optimize communication between the service instance and the database cluster. See Configure an Oracle Java Cloud Service Instance for an Oracle RAC Database.