Creating an Oracle Java Cloud Service Instance

To create a new Oracle Java Cloud Service instance, use the Provision New Java Cloud Service wizard as described in the following sections.

Invoking the Provision New Java Cloud Service Wizard

To create an Oracle Java Cloud Service instance from the Oracle Java Cloud Service Console, you use the Provision New Java Cloud Service wizard.

To invoke the Provision New Java Cloud Service wizard:
  1. Navigate to the Oracle Java Cloud Service Console.
  2. Click Create Service and select Java Cloud Service.

    If you are using the AppToCloud infrastructure to migrate existing applications to Oracle Java Cloud Service, select Java Cloud Service — AppToCloud. See Creating an Oracle Java Cloud Service Instance with AppToCloud.

    The Provision New Oracle Java Cloud Service wizard is invoked.

Specifying Basic Service Instance Information

Enter basic information for your service instance: service name, service level, metering frequency, software release, and software edition.

Note:

You cannot change the following choices after you have created the service instance:
  • Service Name

  • Description

  • Service Level

  • Metering Frequency

  • Software Release

  • Service Edition

Complete the following fields:

Field Description

Service Name

Specify the name for the Oracle Java Cloud Service instance.

The service instance name:

  • Must contain one or more characters.

  • Must not exceed 50 characters.

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

  • Must contain only ASCII letters or numbers, or hyphens.

  • 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.

Service Level

Select a service level from the drop-down menu.

  • Oracle Java Cloud Service—Virtual Image

    Developer-level service. Supports Oracle Java Cloud Service instance creation and monitoring.

    This service level does not support backup and restoration; patching; or scaling. You cannot provision a domain partition if you specify this service level.

  • Oracle Java Cloud Service

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

  • Oracle Java Cloud Service for Fusion Middleware

    You can select either the WebCenter Portal or Oracle Data Integrator Fusion Middleware product.

    Selecting either product from the menu downloads the installer to /u01/zips/upperstack on the Administration Server VM. You must install the products yourself. See:

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

    You must select software version Enterprise Edition or Enterprise Edition with Coherence if you want to select Oracle Java Cloud Service for Fusion Middleware. Standard Edition is not supported.

You can select a subscription type that you did not purchase as part of your Oracle Java Cloud Service subscription. Making this selection will incur additional charges to your account. For pricing information, go to http://cloud.oracle.com/java and click on the Pricing tab.

Metering Frequency

Select a metering frequency from the drop-down menu.

  • Hourly—Pay only for the number of hours used during your billing period.

  • Monthly—Pay one price for the full month irrespective of the number of hours used.

    Note:

    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.

Service Release

Select the software release from the drop-down menu.

  • 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.0)

You must select either version of Oracle WebLogic Server 12c if you want to use Oracle Coherence in your service instance. Oracle Coherence cannot be enabled for a service instance that runs Oracle WebLogic Server 11g.

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

Service Edition

Select the service edition you want to run on your service instance.

You can select one of the following editions of WebLogic Server:

  • Standard Edition

  • Enterprise Edition

  • Enterprise Edition with Coherence

If you have a non-metered subscription for Oracle Java Cloud Service, you can select a software edition other than the entitlement you specified for your purchase. For example, if you have purchased an entitlement for Enterprise Edition, you can select Standard Edition or Enterprise Edition with Coherence. Your account will be charged for change in your entitlement for a software edition. For pricing, see http://cloud.oracle.com/java.

Specifying the Service Instance Details

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

Configuring Size and Shape

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

Complete the following fields:

Size and Shape Details Description

Compute Shape

Select the compute shape.

The compute shape is the number of Oracle Compute Units (OCPUs) and amount of memory (RAM) that you want to allocate to the VMs that will contain the WebLogic Server Administration Server and Managed Servers.

All-purpose compute shapes include:

  • OC3: 1 OCPU and 7.5 GB memory

  • OC4: 2 OCPUs and 15 GB memory

  • OC5: 4 OCPUs and 30 GB memory

  • OC6: 8 OCPUs and 60 GB memory

  • OC7: 16 OCPUs and 120 GB memory

Memory-intensive compute shapes include:

  • OC1M: 1 OCPUs and 15 GB memory

  • OC2M: 2 OCPU and 30 GB memory

  • OC3M: 4 OCPUs and 60 GB memory

  • OC4M: 8 OCPUs and 120 GB memory

  • OC5M: 16 OCPUs and 240 GB memory

For more information about compute shapes, contact your Oracle Cloud Administrator.

You can select a compute shape that you did not purchase as part of your Oracle Java Cloud Service subscription. Making this selection will incur additional charges to your account. For pricing information, go to http://cloud.oracle.com/java and click on the Pricing tab.

SSH Public Key

Specify the public key for the secure shell (SSH).

This key will be used for authentication when connecting to the Oracle Java Cloud Service instance using an SSH client.

Click Edit to display the Public key input for VM access dialog and specify the public key using one of the following methods:

  • Select Key file name and click Browse to select a file that contains the public key for the secure shell (SSH).

  • Select Key value and paste in the value of the public key.

    If you paste in a value, make sure the value does not contain line breaks or end with a line break.

  • Select Create a New Key to generate a public/private key pair immediately. Use this method if you did not create a key pair before you started provisioning the service instance.

Cluster Size

Select the cluster size — the number of Managed Servers that you want to configure in a cluster. The Valid values include: 1, 2, 4.

  • This field is not valid if you selected WebLogic Server Standard Edition. In this case, one Managed Server is configured, by default.

  • If you configure more than one Managed Server in the cluster, Oracle recommends that you enable the load balancer.

You can also scale out the cluster after provisioning the service instance.

Domain Partitions

Select the number of partitions you want for your service.

The choices are 0, 1, 2, or 4.

If you are configuring an Oracle Java Cloud Service — Virtual Image instance and you select WebLogic Server 12.2.1 as the version, this field will not appear. This field will also not appear if you select Standard Edition as the edition. You cannot create a domain partition in these cases.

Assigning Reserved IP Addresses

If you associate your service instance with an Oracle Database Exadata Cloud Service database deployment, you must assign the previously reserved IP addresses for your Oracle Java Cloud Service instance.

This task is only required if you plan to use an Oracle Database Exadata Cloud Service database deployment for either the Oracle Required Schema or Application Schema databases.

For information on reserving IP addresses, see Using an Oracle Database Exadata Database Cloud Service Database Deployment.

  1. Click the Assign IP Reservations button to open the IP Reservations for WebLogic dialog.
    The IP addresses you requested will appear on the Available list in the dialog.
    Note that the Assign IP Reservations button is inactive until you specify an Oracle Database Exadata Cloud Service database deployment.
  2. On the dialog, move the IP addresses from the Available list to the Selected list.
    The number of IP addresses you select must be equal to the requested Cluster Size. The first IP address you select is used for the Administration Server node. Subsequent IP addresses are assigned to the remaining Managed Sever nodes.
  3. Click the checkbox adjacent to the text Check this box to confirm that selected IP are opened up on the Exadata firewall.
  4. Click Assign.

You will receive an error message if you click Next and have neglected to specify the reserved IP addresses.

If you need to scale out your service at a later time, you will first need to request another IP reservation.

Configuring WebLogic Server Access

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

Complete the following fields:

Access Details Description

Local Administrator Username

Specify the username for the WebLogic Administrator.

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 change the user name through the WebLogic Server Administration Console after the service instance is provisioned.

Password

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

If you have specified an Oracle Database Exadata Cloud Service database deployment, you must specify a strong password conforming to the following requirements:

The 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 use the previous requirements and you do not specify an Oracle Database Exadata Cloud Service database deployment, provisioning will not fail. However, as a best practice, use the strong password requirements.

Previous requirements are:

  • 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 access to Administration Consoles

(Optional) Select this checkbox 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 checkbox, these consoles will not appear as choices in the Menu icon service instance’s menu.

Deploy Sample Application

(Optional) Deploy the sample application.

A sample application, sample-app.war, is deployed automatically to the Managed Servers in your instance and started. If you do not want to automatically deploy the application, deselect the checkbox.

Configuring the Coherence Data Tier

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

Capacity Unit

Select the default capacity unit that’s right for your environment:

  • Basic—Provides 1.5 GB of primary cache capacity. One VM with shape OC3 (1 OCPU total).

  • Small—Provides 4.5 GB of primary cache capacity. Three VMs with shape OC3 (3 OCPUs total).

  • Medium—Provides 10 GB of primary cache capacity. Three VMs with shape OC4 (6 OCPUs total).

  • Large—Provides 22 GB of primary cache capacity. Three VMs with shape OC5 (12 OCPUs total).

To create a service instance without enabling Coherence, select None.

Cache Size

You can configure a default capacity unit or select Advanced. This selection displays the amount of primary cache storage to allocate for Coherence by one capacity unit, based on the default capacity unit configuration you select or the custom (Advanced) configuration you define, and the general rule of using 1/3 of Managed Server heap for primary cache storage.

Only one capacity unit of VMs and Managed Servers is created and configured upon initial provisioning of a service instance. After a service instance is created, you can increase cache capacity by adding one capacity unit at a time.

Shape

For Advanced configuration only:

Select the number of Oracle Compute Units (OCPUs) and amount of memory (RAM) that you want for the VMs in your custom capacity unit.

Nodes

For Advanced configuration only:

Select the number of VMs you want to be configured by one custom capacity unit. Valid values are 1 to 3.

Select 3 for Coherence high availability. This is because Coherence high availability is maintained when three or more VMs are configured.

Managed Servers Per Node

For Advanced configuration only:

Select the number of Managed Servers to be started on each VM by your custom capacity unit.

Up to 4 Managed Servers are allowed if you use the OC3 shape.

Using more servers can improve concurrency and memory management but can require more processors.

The maximum heap size that will be configured is 16 GB.

Configuring the Databases

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

For Oracle Required Schema — Name

Specify the name of the database deployment you want to use for storing the required schema for your service instance.

The database deployment you choose must not be configured with a Backup Destination set to None. You must select one of the other available backup options in the database deployment prior to creating this service instance. Backup Destination is not applicable to Oracle Database Cloud Service — Virtual Image database deployments.

You can specify an Oracle Database Cloud Service — Virtual Image database deployment only if you are provisioning an Oracle Java Cloud Service— Virtual Image instance. You cannot specify an Oracle Database Cloud Service — Virtual Image database deployment if you are provisioning an Oracle Java Cloud Service instance. You must configure the Oracle Database Cloud —Database Cloud Service environment before you specify the Oracle Database Cloud — Database Cloud Service database deployment to use.

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.

An Oracle Database Cloud Service — Virtual Image instance does not have a backup option.

Only Database Cloud Service database deployments that are up and running are available in the list. If your Database Cloud Service database deployment is In Progress, it will not appear in the list.

Connection String

Specify a connection string.

The Connection String field is displayed only if you are creating an Oracle Java Cloud Service — Virtual Image instance and you are specifying an Oracle Database Cloud Service — Virtual Image database.

The connection string must be in one of the following formats:

  • host:port:SID

  • host:port/service_name

PDB Name

Enter the name of the pluggable database for Oracle Database 12c.

If not specified, the PDB name provided when the Database Cloud Service database deployment was created will be used.

This value does not apply to Database Cloud Service database deployments running Oracle Database 11g.

Administrator Username

Enter the name of the database administrator.

For database deployments associated with Oracle Java Cloud Service instances based on Oracle WebLogic Server 11g (10.3.6), this value must be set to a database user with DBA role. You can use the default user SYSTEM or any user that has been granted the DBA role.

For database deployments associated with Oracle Java Cloud Service instances based on Oracle WebLogic Server 12c (12.1.3) or Oracle WebLogic Server 12c (12.2.1), this value must be set to a database user with SYSDBA system privileges. You can use the default user SYS or any user that has been granted the SYSDBA privilege.

Password

Enter the database administrator password specified when the Database Cloud Service database deployment was created.

For Application Schema — Add

(Optional) Add a database for the application schema.

Click Add if you want to specify a Database Cloud Service database deployment dedicated for use as an application schema. When you add an application database, the software creates a second datasource on the Oracle WebLogic Server instance.

Oracle Java Cloud Service supports database deployments in Oracle Database Cloud Service that are configured with either the Cloud Storage Only or Both Cloud Storage and Block Storage options for Backup Destination. The None backup option is not supported in Oracle Java Cloud Service. Backup Destination is not applicable to database deployments that use the Virtual Image service level of Oracle Database Cloud Service.

Configuring the Load Balancer

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

Select Yes or No to enable or disable the Oracle Traffic Director (OTD) load balancer. This choice defaults to Yes when you configure more than one Managed Server for the Oracle Java Cloud Service.

Compute Shape

Select the number of Oracle Compute Units (OCPUs) and amount of RAM memory that you want to allocate for the VM for the load balancer. The larger the compute shape, the greater the processing power.

Valid compute shapes:

  • OC3: 1 OCPU and 7.5 GB memory

  • OC4: 2 OCPUs and 15 GB memory

  • OC5: 4 OCPUs and 30 GB memory

  • OC6: 8 OCPUs and 60 GB memory

  • OC7: 16 OCPUs and 120 GB memory

Additional shapes are available for more memory-intensive applications:

  • OC1M: 1 OCPU and 15 GB memory

  • OC2M: 2 OCPUs and 30 GB memory

  • OC3M: 4 OCPUs and 60 GB memory

  • OC4M: 8 OCPUs and 120 GB memory

  • OC5M: 16 OCPUs and 240 GB memory

You can also change the compute shape after creating the Oracle Java Cloud Service instance. See Scaling an Oracle Java Cloud Service Node. If you have a non-metered subscription to Oracle Java Cloud Service, you can provision resources up to twice the subscribed capacity. See About Metered and Non-Metered Oracle Java Cloud Service.

For more information about compute shapes, contact your Oracle Cloud Administrator.

Add Another Active OTD Node

(Optional) Add another OTD node during provisioning.

The default is No.

If you don’t add an OTD node during provisioning, you can do so after provisioning.

Load Balancer Policy

Select one of the following policies:

  • Least Connection Count—Passes each new request to the Managed Server with the least number of connections. This policy is useful for smoothing distribution when Managed Servers get bogged down. Managed Servers with greater processing power to handle requests will receive more connections over time.

  • Least Response Time—Passes each new request to the Managed Server with the fastest response time. This policy is useful when Managed Servers are distributed across networks.

  • Round Robin—Passes each new request to the next Managed Server in line, evenly distributing requests across all Managed Servers regardless of the number of connections or response time.

Configuring Backup and Recovery

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

Cloud Storage Container

Enter the name of the Oracle Storage Cloud container used to provide storage for your service instance backups using the following format: storageservicename-storageidentitydomain/containername

By default, all backups are stored in the Oracle Storage Cloud container at this URL.

Cloud Storage Username

Enter the user name for the Oracle Cloud Storage Container administrator.

Your storage username is the same as your MyServices username.

Password

Enter the password for the Oracle Cloud Storage Container administrator. Your password is the same as your MyServices password.

Note: Ensure that your storage user password does not contain special characters.

Create Cloud Storage Container

(Optional) Create a storage cloud container.

Select the checkbox after you have specified a new cloud storage container name. A storage container is generated immediately after you click the Next button on the Service Details page. Use this method if you did not create a storage container before you started creating the service instance.

Confirming Your Oracle Java Cloud Service Instance Creation

On the Confirmation page of the Provision New Java Cloud Service 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.

Note:

When creating a service instance that has Oracle Coherence enabled: Upon creation of the service instance, the initial set of Managed Servers configured for the Coherence data tier is listed as a scale out operation in the Activity section on the Topology page. See Viewing Scaling Requests for information about how to access the Activity section and view details for a specific scaling operation.

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.

After the service instance has been created, you can view the system messages logged during the creation process, including error messages. Click Instance create or 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.

You can view the sample application that was deployed automatically when the service instance was created (unless you elected not to deploy it). See About the Sample Application Deployed to an Oracle Java Cloud Service Instance.

If you have a non-metered Oracle Java Cloud Service subscription, warnings appear on this page if you have selected a software edition or capacity for which you are not entitled. These choices are allowed, but will incur further charges to your account. See About Metered and Non-Metered Oracle Java Cloud.