Creating an Oracle Java Cloud Service Instance that has a Coherence Data Tier


Options



Before You Begin

Purpose

In this tutorial, you learn how to create an Oracle Java Cloud Service instance that has Oracle Coherence enabled. Unless otherwise noted, all information and steps are applicable to using Oracle Java Cloud Service on Oracle Public Cloud and Oracle Cloud Machine.

Last Updated

April 2017, Release 17.2

Please note that Oracle develops its cloud services in an agile manner and makes rapid changes to meet our users' needs. Therefore this tutorial may not reflect all of the changes since the last update to this service. For the very latest information see:

Time to Complete

Approximately 20 minutes, plus the time needed for Oracle Java Cloud Service to create and configure your service instance.

Background

By using Oracle Java Cloud Service, you can quickly create and configure an Oracle WebLogic Server domain and set up your Java EE application environment without setting up any infrastructure or platform details yourself. When using the Oracle Java Cloud Service Console to create a service instance, you have the option of enabling Oracle Coherence and adding a Coherence data tier to the domain. Default capacity units are available for configuring the Coherence data tier. You also have the option to create your own capacity unit configuration.

Scenario

You have access to Oracle Java Cloud Service and you want to get started with creating an Oracle Java Cloud Service instance that has a Coherence data tier. This tutorial takes you through that process.

In this tutorial, you will create an Oracle Java Cloud Service instance with the following configuration:

  • Oracle WebLogic Server 12c (12.2.1.x)
  • One Oracle Compute Unit (OCPU) and 7.5 gigabytes of memory allocated for each Virtual Machine (VM)
  • One storage-disabled WebLogic Server cluster with two Managed Servers
  • One storage-enabled WebLogic Server cluster with one Managed Server (this is the Coherence data tier)
  • A load balancer, configured with the policy Least Connection Count

During the creation process on Oracle Public Cloud, you will generate a Secure Shell (SSH) public-private key pair and a Storage Cloud Service container for the service instance. On Oracle Cloud Machine, you will generate the SSH key pair and specify the NFS remote backup location as given to you by your Oracle Cloud Administrator or Tenant Administrator.

What Do You Need

To complete this tutorial, you need:

  • A web browser. Supported browsers include Microsoft Internet Explorer 9 or 10 (with Browser Mode and Document Mode set to IE9 or IE10), Mozilla Firefox 24 or later, Google Chrome 29 or later, and Apple Safari 6 or later.
  • Access to a database that contains the standard Oracle Fusion Middleware schemas required by Oracle Java Required Files (JRF).

    On Oracle Public Cloud, you need a standard service level Oracle Database Cloud Service database deployment that is up and running. The database deployment must have been created by using Oracle Database 12c Release 1 or Oracle Database 11g Release 2. See the tutorial Oracle Database Cloud Service Quick Start. You have to supply the following database deployment information when you create a service instance in Oracle Java Cloud Service:

    • Name of the Oracle Database Cloud Service database deployment.

    • User name for the database administrator user with SYSDBA system privileges.
    • Administration password that was supplied when the Oracle Database Cloud Service database deployment was created.

    On Oracle Cloud Machine, you must have already obtained the following database and public network details from your Oracle Cloud Administrator or Tenant Administrator:

    • Connection string to a database, and the database administrator user name and password
    • NFS URI to a remote networked disk share
    • Path to the network used to access administrative tools (Public Access Network)
    • Path to the network through which the service instance accesses the database (Database Network)
  • Understanding of capacity units as used by Oracle Java Cloud Service to configure the Coherence data tier.

    A capacity unit is a well-defined group of virtual machines (VMs) running a number of JVMs (Managed Coherence Servers). It is preconfigured by properties that specify the processing power of the VMs to provision on the Coherence data tier, and the amount of primary cache storage to allocate for Coherence. When creating an Oracle Java Cloud Service instance, you can choose from a list of default capacity unit definitions (for example, Basic, Small, Medium, or Large) or define a custom capacity unit that meets your resource requirements. You must decide the capacity unit configuration (default or custom) before you create the service instance. After a service instance is created, you cannot change the configuration of the capacity unit you used. On Oracle Public Cloud, see About Capacity Units for Oracle Java Cloud Service—Coherence Instances in Using Oracle Java Cloud Service. On Oracle Cloud Machine, see About Capacity Units for Oracle Java Cloud Service—Coherence Instances in Using Oracle Java Cloud Service on OPCM.

  • Log-in credentials to Oracle Java Cloud Service, comprising a user name, password, and identity domain (on Oracle Public Cloud) or tenant name (on Oracle Cloud Machine). To open the Oracle Java Cloud Service Console, see Accessing Oracle Java Cloud Service in Using Oracle Java Cloud Service. On Oracle Cloud Machine, see Accessing Oracle Java Cloud Service in Using Oracle Java Cloud Service on OPCM.

Creating a Service Instance

You create an Oracle Java Cloud Service instance by stepping through a wizard. You add a Coherence data tier to the service instance during the process.

Starting the Create Oracle Java Cloud Service Instance Wizard

To invoke the wizard for creating an Oracle Java Cloud Service instance:

  • On the Oracle Java Cloud Service Console, click Create Service.

    On Oracle Public Cloud, when you click the Create Service button, you will see a dropdown menu. Select Java Cloud Service from the menu.

    Oracle Java Cloud Service console
    Description of this image

The wizard starts. Step through the wizard pages to specify the details you want for your service instance, such as service level, release and edition of software to install, and the cluster size and compute shape of the VMs.

Use the following sections if you need help. Note that the sections may not be presented in the same order as the wizard pages you see in your environment.

Specifying General Service Details (Name and Description)

Use a name that is unique within your identity domain (Oracle Public Cloud) or tenant name (Oracle Cloud Machine).

  1. Service Name: Enter a name that starts with a letter, is up to 50 characters long, contains only letters, numbers, and the hyphen. However, do not use the hyphen in the first eight characters of the name. Special characters are not allowed in the name. The examples shown in this tutorial use the service name Example1Instance.

    The names of the domain, and the storage-disabled and storage-enabled WebLogic Server clusters are generated from the first eight characters of the service instance name.

  2. Description: You can add a description, but it is not required.

Specifying a Service Level, Release, and Software Edition

Specify basic information for your service instance. The field labels you see depends on your environment.

  1. Service Level: For this tutorial, select Oracle Java Cloud Service, which is a production-level service that lets you create and monitor Oracle Java Cloud Service instances, and use tooling for scaling, backup and recovery, and patching.

  2. Metering Frequency or Billing Frequency: Select Hourly or Monthly for the frequency, whichever fits your needs. This selection doesn't affect the service instance's features or performance.

  3. Service Release or Software Release: Select Oracle WebLogic Server 12c (12.2.1.x). This is the WebLogic Server software release to run on your service instance.

  4. Service Edition or Software Edition: Select Enterprise Edition with Coherence. (You must select this edition to enable the Oracle Coherence feature for your service instance.)

    Enterprise Edition with Coherence is an integrated solution for building infrastructures that span web server, application server, and data grid technology tiers. It provides the features and benefits of WebLogic Server Enterprise Edition, plus Oracle Coherence Enterprise Edition on the data grid for high performance and scalability—all the features you may be familiar with from working with on-premises 12c versions of WebLogic Server Enterprise Edition and Oracle Coherence Enterprise Edition.

Generating an SSH Key Pair Automatically

You can use a tool to generate a secure shall (SSH) public/private key pair before you create a service instance, or you can use the service creation wizard to create a key pair, as described here.

  • SSH Public Key: Click Edit, and select Create a New Key to generate a public/private key pair immediately.

    Then click Enter, and click Download to download the generated public/private key pair. Save the file, and click Done.

The public key is automatically entered and will be uploaded to your service instance VM during the service creation process. The private key is used when accessing the service instance VM using an SSH client.

Configuring the Cluster Size and Compute Shape

Specify the storage-disabled cluster size and the compute shape of the VMs to provision.

  1. Cluster Size: Select 2 to indicate that your storage-disabled WebLogic Server cluster will contain two Managed Servers. When you select 2 or higher, a load balancer is automatically enabled, as you'll see in a subsequent step. While you can choose not to enable the load balancer, it is strongly recommended for clusters with two or more Managed Servers.

  2. Compute Shape: Select OC3 - 1 OCPU, 7.5 GB RAM to allocate one Oracle Compute Unit (OCPU) and 7.5 gigabytes of memory for each Virtual Machine (VM) in the service instance.

    The larger the compute shape, the greater the processing power. This selection gives you a moderately-sized compute shape to work with.

Configuring the WebLogic Administrator

Configure the local administrator for the service instance. The field labels you see depends on your environment.

  1. Local Administrative Username or Username: Enter a user name for the service instance WebLogic administrator.

  2. Password: Enter a password for the service instance WebLogic administrator.

  3. Reenter the password.

Be sure to make a note of the user name and password you specified. You'll need them later to access the administration consoles to the service instance.

Configuring the Coherence Data Tier

Configure the Managed Servers for the storage-enabled cluster by selecting a capacity unit configuration in the Coherence Data Tier section on the wizard page. A capacity unit is a group of VMs running a number of Managed Coherence Servers, and is meant to scale linearly in the context of your application. You can use a default capacity unit configuration or define your own custom configuration. If you don't select or define a capacity unit, the Oracle Coherence feature will not be enabled for the service instance. In this tutorial, you will use a default capacity unit.

Coherence Data Tier Configuration section on Details page
Description of this image
  1. Capacity Unit: For this tutorial, select Basic - 1 OC3 (1 OCPU), 7.5 GB, one of the default capacity unit configurations. This configuration will create one Managed Server in one node for the Coherence data tier, allocating one OCPU and 7.5 gigabytes of memory for the VM.

    Capacity Unit options for Coherence Data Tier section on Details page
    Description of this image

    Note: The Basic configuration provisions one VM only, a non-HA deployment. The total memory that’s actually used for Managed Server heap configuration is 75% of the remaining memory after reserving 1.5 GB for the operating system. In the example used in this tutorial, the total memory available for Managed Server heap on the Coherence data tier is 4.5 GB.

  2. Cache Size: The total amount of primary cache storage to allocate for Coherence is displayed after you select a capacity unit configuration. This amount is based on the configuration of the capacity unit you declare for the entire service instance, and the general rule of splitting the Managed Server heap size into thirds: using 1/3rd for primary cache storage, 1/3rd for backup storage, and 1/3rd for scratch space. In the example used in this tutorial, the primary cache size will be 1.5 GB (which is 1/3rd of 4.5 GB).

    Coherence Data Tier Configuration section on Details page
    Description of this image

Configuring Domain Partitions, Console Access, and Sample Application Deployment

On Oracle Public Cloud, you can specify domain partitions, administration console access, and sample application deployment. Expand Advanced Settings to locate the settings.

On Oracle Cloud Machine, you can specify domain partitions and sample application deployment only.

  1. Domain Partitions: For this tutorial, select 0 (No Partitions).

  2. Enable access to Administration Consoles: On Oracle Public Cloud only: Select the checkbox to enable the access rules that control external communication to the WebLogic Service Administration Console, Fusion Middleware Control, and Load Balancer Console for the service instance.

    Note: The administration console access checkbox is not available on Oracle Cloud Machine, as access is enabled by default.

  3. Deploy Sample Application: By default the deploy sample checkbox is selected. A sample application will be automatically deployed to the service instance after the instance is created.

Configuring the Database on Oracle Public Cloud

On Oracle Public Cloud, configure the Oracle Required Schema database that will be used with your service instance by completing the fields in the Database Configuration section on the wizard page.

  1. Name: Select an existing database deployment in your Oracle Database Cloud Service (you cannot select a database deployment that is based on Oracle Database 12.2 or the Virtual Image service level).

    Note: Only Oracle Database Cloud Service database deployments that are up and running are available in the list. If your Oracle Database Cloud Service database deployment is in the process of being provisioned, it won't appear in the list.

  2. PDB Name: You can leave this blank. If you don't specify a name, the pluggable database name that was configured when the Oracle Database Cloud Service database deployment was provisioned will be used.

  3. Administrator Username: Enter the user name for the database administrator. This 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.

  4. Password: Enter the password for the database administrator. This is the password that was supplied when the Oracle Database Cloud Service database deployment was created.

Configuring the Database on Oracle Cloud Machine

On Oracle Cloud Machine, configure the Oracle Required Schema database that will be used with your service instance by completing the fields in the Database Configuration section on the wizard page.

  1. Name: Select <enter connection string>.

  2. Connection String: Enter the connection string for an existing relational database that contains the Oracle Fusion Middleware schemas. Use the format host:port:SID or host:port/serviceName.

  3. Administrator Username: Enter the user name for the database administrator. This must be set to a database user with SYSDBA system privileges.

  4. Password: Enter the password for the database administrator.

Configuring the Load Balancer

Configure the load balancer by completing the fields in the Load Balancer section. Earlier, you selected a storage-disabled cluster size of two Managed Servers, so a load balancer is enabled by default.

  1. Provision Load Balancer: Select Yes if it isn't already selected.

  2. Compute Shape: Select the number of Oracle Compute Units (OCPUs) and amount of RAM memory that you want to allocate for the load balancer VM. Larger compute shapes give you greater processing power. For now, select OC3 - 1 OCPU, 7.5 GB RAM.

  3. Add Another Active OTD Node: On Oracle Public Cloud: For this tutorial, you'll use a single load balancer node. (However, for high availability and greater application throughput, you have the option to add a second load balancer node to a service instance.)

    Note: This setting is not available on Oracle Cloud Machine.

  4. Load Balancer Policy: Select the policy to use for routing requests to the load balancer. When you start using Oracle Java Cloud Service for production applications, you can choose a policy that best suits your needs. For now, select Least Connection Count, which 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 receive more connections over time.

Configuring Storage for Backup and Restoration on Oracle Public Cloud

On Oracle Public Cloud, enable backups for your service instance, then configure the Oracle Storage Cloud Service container by completing the fields in the Backup and Recovery Configuration section on the wizard page. Do not use the same Storage container you have used for Oracle Database Cloud Service backups.

  1. Backup Destination: Select Both Cloud Storage and Local Storage if it isn't already selected. This enables scheduled and on-demand backups to be performed.

  2. Cloud Storage Container: Enter the name of the Storage Cloud container that you want to use to provide storage for your Oracle Java Cloud Service instance backups. In this tutorial, use a container name that does not already exist in your Oracle Storage Cloud Service. The container name must be in the format: <storageservicename>-<storageidentitydomain>/<containername>. For example, ExampleStorage-ExampleIdentityDomain/MyExampleStorageContainer.

  3. Username: Enter the user name for the Oracle Storage Cloud Service user who has read/write access.

  4. Password: Enter the password for the Oracle Storage Cloud Service user who has read/write access.

  5. Select the Create Cloud Storage Container checkbox.

When you advance to the next wizard page, the storage container is generated immediately.

Configuring Networks and Backups on Oracle Cloud Machine

On Oracle Cloud Machine, specify the public access and database networks, and the NFS URI of the remote backup in the Networks and Backup Configuration sections, respectively, on the wizard page. Your Oracle Cloud Administrator or Tenant Administrator should have provided you the information to use.

  1. Public Access Network: Select the name of a public access network (in the format /tenant/public/EoIB_vNet).

  2. Database Network: Select the name of a database network.

  3. NFS Remote Backup: Enter the location of the remote networked disk that will be used for service instance backups. Use the format hostname:absolute-path or ip_address:absolute-path

Confirming and Reviewing Your Oracle Java Cloud Service Instance Creation

To confirm your Oracle Java Cloud Service instance definition and proceed with the creation process:

  1. On the Confirm or Confirmation wizard page, review the selections for your service instance.

    For example, on Oracle Public Cloud, the Confirm page might look similar to the following:

    Confirmation page
    Description of this image

    On Oracle Cloud Machine, the Confirmation page might look similar to the following:

    Confirmation page
    Description of this image
  2. Click Create and look for a message indicating that the create request was accepted.

    Your new service instance name is displayed on the Oracle Java Cloud Service Console. The numbers next to OCPUs, Memory, and Storage are 0 (zero). The Status field shows Creating service... (on Oracle Public Cloud) or In Progress (on Oracle Cloud Machine).

    New service in progress
    Description of this image
  3. To see the progress of the service instance creation, including any errors, click Creating service... or click In Progress.

    Status In Progress link
    Description of this image
  4. Click the service instance name. This will open the service instance Overview page.

    New instance name link
    Description of this image

    When the service instance is created, you will see all details about the instance and the Coherence data tier on the Overview page.

  5. Click Oracle Java Cloud Service to return to your Oracle Java Cloud Service Console.

    Instances button
    Description of this image

    The service instance creation process takes several minutes. When the process is completed, the Status field is no longer displayed, and the numbers configured for Nodes, OCPUs, Memory, and Storage are shown.

    Oracle Java Cloud Service Console, instance created
    Description of this image

    If the creation process is completed, but the service instance was not created successfully, the failure is reported on the Status field. For example:

    Instance creation failed
    Description of this image

    If you cannot successfully create a service instance, try the process again. If you continue to have trouble creating a service instance, contact Oracle Support.

Reviewing Your Service Instance in Oracle Java Cloud Service

After the service instance is created, return to the Overview page to view information about the instance.

  1. On your Oracle Java Cloud Service Console, click the service instance name.

    Click service instance name
    Description of this image

    The Overview page for the selected service instance is displayed.

    On Oracle Public Cloud, all node details are found on the Overview page. For example:

    Overview page
    Description of this image

    On Oracle Cloud Machine, node details are found on the Overview page and the Topology page.

    Overview page
    Description of this image

    Click the Topology tile to go to the Topology page, which shows the node details for the entire instance, including the Coherence data tier details.

    Topology page
    Description of this image
  2. On Oracle Public Cloud and Oracle Cloud Machine: To see the capacity unit details, expand the Coherence Data Tier section by clicking the arrow next to the icon. One or more capacity units are displayed, depending on your Coherence data tier configuration. In this tutorial, you will see one capacity unit, as shown in the following illustration:

    Overview page
    Description of this image
  3. Notice that the names of the domain, and the storage-disabled and storage-enabled WebLogic Server clusters are generated from the first eight characters of the service instance name, as follows:

    • first8charsOfServiceInstanceName_domain, for example, Example1_domain
    • first8charsOfServiceInstanceName_cluster, for example, Example1_cluster
    • first8charsOfServiceInstanceName_DGCluster, for example, Example1_DGCluster

    The names of the Managed Servers for the storage-disabled and storage-enabled clusters are generated from the first eight characters of the service instance domain name, as follows:

    • first8charsOfDomainName_server_n, where n starts with 1 and is incremented by one for each additional Managed Server in the storage-disabled cluster, for example, Example1_server_1 and Example1_server_2.
    • first8charsOfDomainName_server_n_DG, where n continues from the last storage-disabled Managed Server, and is then incremented by one for each additional Managed Server on the Coherence data tier, for example, Example1_server_3_DG, Example1_server_4_DG, and so on.

Want to Learn More?