Creating an Oracle Java Cloud Service Instance with AppToCloud

In order to import your source domain configuration and applications into Oracle Java Cloud Service, you must associate a new service instance with the files that you previously generated with the AppToCloud tools.

Most of the steps that you use to create a service instance with AppToCloud are the same as those you use to create a standard service instance (see Creating a Custom Oracle Java Cloud Service Instance on Oracle Cloud Infrastructure Classic). However, there are some additional inputs:
  • You must provide the location of your AppToCloud JSON file on cloud storage.

  • You must associate each Data Source in your original WebLogic Server domain with an existing Oracle Database Cloud Service database deployment.

  • You may need to configure properties (such as URL and credentials) for the following types of resources if found in the original WebLogic Server domain:

    • Foreign Java Naming and Directory Interface (JNDI) Providers

    • Java Mail Sessions

    • Foreign Java Message Service (JMS) Servers

    • Remote Store and Forward (SAF) Contexts

    • JMS Messaging Bridge Destinations

Before creating an Oracle Java Cloud Service instance, Oracle recommends that you review the options described in Design Considerations for an Oracle Java Cloud Service Instance.

  1. Navigate to the Instances page in the Oracle Java Cloud Service console.
  2. Click Create Instance and select the Java — AppToCloud option.
  3. Provide details about the JSON file generated by the Export tool:
    Field Description

    Exported .json File

    Enter the URL of the JSON file that was uploaded to Oracle Cloud Infrastructure Object Storage Classic. If you used the Export tool to upload this file to cloud storage, the Export tool provided this URL in its output.

    Format: rest_endpoint_url/containerName/fileName.json

    You can also find the REST endpoint URL of the Oracle Cloud Infrastructure Object Storage Classic service instance in the Oracle Cloud My Services portal. See Finding the REST Endpoint URL for Your Service Instance in Using Oracle Cloud Infrastructure Object Storage Classic.

    Example: https://foo.storage.oraclecloud.com/v1/MyService-bar/MyContainer/mydomain.json

    The corresponding AppToCloud ZIP file must be in the same location as the JSON file in cloud storage.

    AppToCloud does not currently support the creation of a service instance from a JSON file in an Oracle Cloud Infrastructure Object Storage bucket.

    Cloud Storage User Name

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

    Cloud Storage Password

    Enter the password of the user you specified in the previous field.

  4. Click OK.
  5. Complete the Instance page:
    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

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

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

    The Oracle Database Cloud Service deployment that you intend to associate with your Oracle Java Cloud Service instance must be in the same region that you select in this field.

    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.

    Availability Domain

    (Available only on Oracle Cloud Infrastructure)

    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.

    Note that the Oracle Database Cloud Service deployment that you intend to associate with your Oracle Java Cloud Service instance can be in a different availability domain within the region.

    Subnet

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

    Note: The subnet that you select for your Oracle Java Cloud Service instance and the subnet of the Oracle Database Cloud Service deployment that you intend to associate must be in the same virtual cloud network (VCN).

    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.

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

      Note: Don’t select ManagedCompartmentForPaaS | svc-vcn | lb-subnet-... even if it is displayed.

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

    IP Network

    (Only if a region is selected) Select an IP network if you want to create the service instance in an IP network that you’ve defined. See Creating an IP Network in Using Oracle Cloud Infrastructure Compute Classic.

    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 with Oracle Identity Cloud Service, which automatically configures a managed load balancer, you must first attach an internet-facing load balancer to the IP network. See Selecting an IP Network for a Service Instance with a Managed Load Balancer.

    This field is not relevant to Oracle Cloud Infrastructure.

    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.

    Bring Your Own 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 in order to use BYOL. See About Oracle Java Cloud Service Subscriptions and Licenses.

    BYOL is enabled by default. If you deselect this option, your account will be charged for the new service instance according to your Oracle Java Cloud Service agreement.

    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.

    Software Release

    Select a WebLogic Server software release for this service instance:

    • Oracle WebLogic Server 12c (12.1.3.0)

    • Oracle WebLogic Server 12c (12.2.1.2)

    • Oracle WebLogic Server 12c (12.2.1.3) (Not available on Oracle Cloud at Customer)

    The Oracle WebLogic Server 11g software release option is not available. All service instances created with AppToCloud will be provisioned with Oracle WebLogic Server 12c, even if your source domain was running 11g.

    Software Edition

    Select a WebLogic Server software edition:

    • Enterprise Edition

    • Enterprise Edition with Coherence

    The Standard Edition option is not supported for a service instance created with AppToCloud.

    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.

  6. Click Next.
    The Instance Details page is displayed.
  7. If you want to configure any of the advanced options, including Backup and Recovery, click Advanced.
    You cannot provision a Coherence data tier for service instances created with AppToCloud.
  8. Complete the WebLogic Configuration section of the Instance Details page:
    Field Description

    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 list of available shapes varies depending on whether you selected an Oracle Cloud Infrastructure Classic or Oracle Cloud Infrastructure region.

    (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. See About Oracle Java Cloud Service Subscriptions and Licenses.

    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 Converting a Private Key with PuTTY.

    Server Count

    You can only edit this field if the source domain contains a single cluster.

    Select the initial number of Managed Servers that you want to provision in this service instance. The default value is the number of Managed Servers in the source domain. Additional 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 cluster size after provisioning the service instance.

    WebLogic Clusters

    You can only edit this field if the source domain contains multiple clusters. (Not available on Oracle Cloud Infrastructure)

    Configure the initial number of Managed Servers that you want to provision in each cluster. Select a cluster from the list, and then click Edit cluster. The default value is the number of Managed Servers in the source domain. Additional choices are: 1, 2, 4. You can also perform scaling operations to increase or decrease the cluster size after provisioning the service instance.

    You cannot remove existing clusters from the service instance, or add new clusters to the service instance.

    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 Menu icon.

    Alternatively, you can enable access to the administration consoles after creating the service instance. See Enabling Console Access in an Oracle Java Cloud Service

    If you are creating this service instance in Oracle Cloud Infrastructure, 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.

    Reserved IPs

    (Available only on Oracle Cloud Infrastructure Classic)

    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. See Managing IP Reservations.

  9. Complete the WebLogic Access section of the Instance Details page:
    Field Description

    Local Administrative Username

    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.

    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 with Oracle 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. See Using Oracle Identity Cloud Service with Oracle Java Cloud Service.

    This check box is automatically selected for you if the source domain contains multiple clusters, and you cannot change it. (Not available on Oracle Cloud Infrastructure)

  10. Complete the Database Configuration section of the Instance Details page:
    Field Description

    Database Instance Name

    Select an existing Oracle Database Cloud Service deployment or Oracle Database Exadata Cloud Service database 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 constraints and limitations:

    • Oracle recommends that you 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.

    • Oracle Java Cloud Service does not support Oracle Database 18c.

    • You cannot select an Oracle Cloud Infrastructure database. You can select only an Oracle Database Cloud Service database deployment.

    • If you are provisioning the Oracle Java Cloud Service instance in Oracle Cloud Infrastructure, then the instance and the associated Oracle Database Cloud Service database deployment must be in the same VCN.

    • If you selected an IP Network for this service instance, you must also select an Oracle Database Cloud Service 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.

    • If you selected the Oracle Java Cloud Service— Virtual Image service level, you can select an Oracle Database Cloud Service — Virtual Image database deployment. However, you must configure the Oracle Database Cloud Service — Virtual Image environment before you create this service instance. See Using a Database Cloud Service - Virtual Image Database Deployment.

    PDB Name

    Enter the name of the Oracle Database 12c pluggable database (PDB) to which the service instance should connect. This value does not apply to Oracle Database Cloud Service database deployments running Oracle Database 11g.

    If not specified, Oracle Java Cloud Service uses the default PDB name that was provided when the Oracle Database Cloud Service database deployment was originally created.

    Administrator Username

    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.

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

  11. Complete the Backup and Recovery Configuration section of the Instance Details page:

    This section is displayed only if you clicked Advanced.

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

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

    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 the Oracle 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 Object Storage service entitlement or if the region selected is an Oracle Cloud Infrastructure region, then the container field is not autopopulated.

    • Oracle Cloud Infrastructure Classic: Enter the URL of a 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 Oracle Cloud My Services portal. See Finding the REST Endpoint URL for Your Cloud Account in Using Oracle Cloud Infrastructure Object Storage Classic.

      Example: https://acme.storage.oraclecloud.com/v1/MyService-acme/MyContainer

      Note: You can select the Create Cloud Storage Container check box to have a new container created automatically.

    • Oracle Cloud Infrastructure: 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

    Username

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

    In Oracle Cloud Infrastructure Classic regions only, this field is not displayed if you selected Enable Authentication with Oracle Identity Cloud Service.

    • Oracle Cloud Infrastructure Classic: 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.

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

    Password

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

    In Oracle Cloud Infrastructure Classic regions only, this field is not displayed if you selected Enable Authentication with Oracle Identity Cloud Service.

    • Oracle Cloud Infrastructure Classic: Enter the password of the user you specified.

    • Oracle Cloud Infrastructure: 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.

    Create Cloud 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.

    This option is not relevant to Oracle Cloud Infrastructure. The specified Oracle Cloud Infrastructure Object Storage bucket must exist prior to creating a service instance.

  12. Complete the Load Balancer section of the Service Details page:
    Field Description

    Provision Local Load Balancer

    (Advanced option) Select Yes to provision a load balancer node running Oracle Traffic Director in this service instance. This load balancer is configured to distribute client requests to the Managed Servers in the service instance.

    Provisioning a local load balancer is recommended if the cluster size is 2 or more. The default value is No.

    You cannot configure a local load balancer if you specify Yes for Enable Access to Oracle Identity Cloud Service Users.

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

    Compute Shape

    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.

    This option is displayed only if Provision Local Load Balancer is set to Yes.

    The list of available shapes varies depending on whether you selected an Oracle Cloud Infrastructure Classic or Oracle Cloud Infrastructure region.

    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. See About Oracle Java Cloud Service Subscriptions and Licenses.

    Add Another Active OTD Node

    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.

    This option is displayed only if Provision Local Load Balancer is set to Yes.

    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.

    This feature is not relevant to Oracle Cloud Infrastructure.

    Load Balancer Policy

    Select a local load balancer policy:

    • 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. This policy is unavailable for a managed load balancer.

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

    This option is displayed only if Provision Local Load Balancer is set to Yes.

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

  13. Click Next.

    The Additional Details page is displayed if your source domain contains resources that may require additional configuration. Otherwise skip to step 18.

  14. Expand Application Data Source and select the first data source. Update the data source’s configuration:
    Field Description

    DataSource Name

    The name of the data source you selected. This field is read-only.

    Source DataSource Type

    The type of this data source in the original source domain (Generic, Multi, or GridLink). This field is read-only.

    DBCS Instance

    Select an existing Oracle Database Cloud Service database deployment. Oracle Java Cloud Service will configure the selected data source to connect to this database deployment.

    Oracle Database Exadata Cloud Service database deployments are not currently supported.

    Target DataSource Type

    The type of this data source (Generic, Multi, or GridLink) that will be configured in the service instance. This field may be read-only or a select box, depending on the Software Edition you chose for this service instance, and whether or not you selected a RAC-enabled database deployment in DBCS Instance:

    • If the database deployment does not use Oracle RAC, the type must be Generic.

    • If the database deployment uses Oracle RAC and the service instance is running Enterprise Edition, the type must be Multi.

    • If the database deployment uses Oracle RAC and the service instance is running Enterprise Edition with Coherence, the type can either be Multi or GridLink.

    Username

    Enter the name of a valid user in the selected Oracle Database Cloud Service database deployment. This data source will connect to the database as this user.

    Password

    Enter the database user’s password.

    PDB

    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.

  15. Click OK to accept your changes or click Disable to remove this data source from the service instance. Repeat the previous step for each additional data source in the Application Data Source list.

    A check mark icon indicates a data source that you have already configured.

  16. Update the configuration for any other resources found on the Additional Details page:
  17. Click Next.

    The Confirmation page is displayed.

  18. If you are satisfied with your choices click Create.

    If you need to change the service instance details, use the navigation bar or Back button at the top of the wizard to step back through the pages in the wizard. Similarly, if you disabled a resource on the Additional Details page and now want to include it in the service instance, select the resource and click Enable.

    Click Cancel to cancel out of the wizard without creating a new service instance.

    You can also review the log messages that were generated by the AppToCloud Export tool for the source domain. Expand Export/Activity Log Messages.

  19. Expand the Instance Create or Delete History section of the page, and then click the service instance name or Details.
  20. Monitor the progress and status of the creation of your service instance.

After your service instance is provisioned and is running, you are ready to import the AppToCloud artifacts into the service instance. See Importing Applications into a Service Instance.

Note:

The AppToCloud import operation can only be performed on a new and unmodified service instance. Do not perform any scaling operations, modify the domain configuration or otherwise change the service instance prior to importing the AppToCloud resources.

If you did not select the Enable access to Administration Consoles option, you will not be able to access these administration consoles after creating this service instance. See Enabling Console Access in an Oracle Java Cloud Service.