1. Using Oracle Java Cloud Service - SaaS Extension
  2. Getting Started with Oracle Java Cloud Service - SaaS Extension
  3. Getting Started with Your JCS-SaaS Extension Subscription
  4. Provisioning a JCS-SaaS Extension Instance

Provisioning a JCS-SaaS Extension Instance

Once you’ve provisioned an Oracle Database Cloud Schema Service instance, you can provision your JCS-SaaS Extension instance.

  1. From the Infrastructure Classic Console, click Create Instance.
  2. In the JCS-SaaS Extension section of the Create Instance dialog box, click Create Service Instance to open the Create New Oracle Java Cloud Service - SaaS Extension Instance page.
  3. On the Create... page, enter these Instance Details:
    Field Description

    Name

    Enter a name for the Oracle Java Cloud Service — SaaS Extention instance. This name must start with a letter and can contain up to 25 alphanumeric characters. Letters must be lowercase and you cannot use spaces or special characters.

    Identity Domain

    If a Fusion Application instance is detected in any of the domains configured within your account, then the instance creation wizard shows an Identity Domain selection box.

    Select the target domain where you want to create the instance. If you create the instance in the identity domain where the Fusion Application is located, then you can use Single Sign-On (SSO).

    If you do not select an identity domain, a new identity domain is created.

    If you select the wrong identity domain, then you can delete the instance and create a new one.

    Associations

    Select the Database Cloud Schema Service Instance you created in Provisioning a Database Instance. You can also select HCM, CRM, and ERP, provided you have any of these applications in the same account.

    Recommended Associations

    If you have multiple SaaS instances (for example, HCM and ERP) in your account, they will be listed here. Select the application you intend to modify with custom ADF applications and deploy on JCS-SaaS Extension. If you aren't planning to customize any listed instance, then you can leave this field blank.

    Plan
    Select the JCS-SaaS Extension plan to which you’ve subscribed. The “Plan” determines the cluster size of the Oracle Java Cloud Service SaaS Extension. Available Plans are:

    • S1 (Basic):

      • Managed servers: 1 Java EE Server

      • Memory: 1.5GB /Instance

      • Storage: 5 GB

      • Data Transfer: 50GB / Month

    • S2:

      • Managed servers: 2 Java EE Servers

      • Memory: 3GB /Instance

      • Storage: 10GB

      • Data Transfer: 250GB / Month

    • S4:

      • Managed servers: 4 Java EE Servers

      • Memory: 6GB /Instance

      • Storage: 25GB

      • Data Transfer: 500GB / Month
  4. Enter these Administrator Details:
    Field Description

    Email

    Enter the email address for the person who will be the administrator for the instance.

    Use email as user name

    Select this checkbox if you want to use the administrator’s email address as the username for this account.

    User Name

    If you aren’t using the administrator email address as the user name for this instance, enter a user name here (if you selected Use email as user name, this field will not appear).

    First Name

    Enter your first (given) name or the given name of the person who will own this service instance.

    Last Name

    Enter your surname or the surname of the person who will own this service instance.
  5. Click Create and then, on the Confirmation message, click Create again. This will launch the provisioning process and open the Infrastructure Classic Console for Oracle Database Cloud Schema Service. Click Refresh icon to refresh your screen until details of the new database instance appear on the page.

Once the instance is provisioned, not only will the instance appear on the Infrastructure Classic Console, but Oracle Cloud will send a confirming email to the administrator address specified in step 4.

Note:

You won't be able to use the Oracle Java Cloud Service - SaaS Extension Console for a few minutes after you provision a service instance. Meanwhile, you can fully access and use the JCS-SX CLI, which is part of the SDK, to perform all administrative operations on the new service.