Create a JRF-Enabled Domain

Creating a JRF-enabled domain is similar to creating a basic domain in Oracle WebLogic Server for Oracle Cloud Infrastructure; however, a database in Oracle Cloud Infrastructure is required as the domain is provisioned with the Java Required Files (JRF) components.

From Marketplace, create a stack by entering parameters that automatically create a domain. When creating a JRF-enabled domain, you specify an autonomous database or DB system database. You can also specify a public subnet (either a regional or availability domain-specific) or a private subnet for the domain.

Note:

Oracle WebLogic Server 12c must be specified as the version for a JRF-enabled domain if you intend to use an Oracle Autonomous Transaction Processing database.

Before you create a domain, you must first perform the following tasks:

• Create database in Oracle Autonomous Transaction Processing or Oracle Cloud Infrastructure Database (DB System). See Create a Database.
• Create a compartment for your domain resources, or use the same compartment in which you created the database. See Create a Compartment.
• Create an SSH key. See Create an SSH Key.
• Create an encryption key to use for secrets. See Create an Encryption Key.
• Create secrets for the passwords you want to use for the domain. You will need to enter the OCID of a secret. See Create Secrets for Passwords.
• Identify the pluggable database (PDB) name. This is required only for Oracle Cloud Infrastructure Database (DB System) running Oracle Database 12c or later.
• Create a confidential application in Oracle Identity Cloud Service if you want to use Oracle Identity Cloud Service for authentication in the domain. You will need the client ID and client secret for this confidential application. See Create a Confidential Application. You will also need to create a secret for the client secret and copy the OCID. See Create Secrets for Passwords.

Oracle WebLogic Server for Oracle Cloud Infrastructure can create the virtual cloud network (VCN) and subnets for your new domain. If you want to use an existing VCN or existing subnets for the domain, then they must meet certain requirements. See:

• Create a Virtual Cloud Network
• Create a Subnet for the Oracle WebLogic Server Nodes
• Create a Subnet for the Bastion Node
• Create a Subnet for the Load Balancer (if you want to create a load balancer)

Tutorial (using an autonomous database)

Tutorial (using a DB System database)

Topics:

• Launch a Stack
• Specify Stack Information
• Configure WebLogic Instance Parameters
• Configure Advanced Parameters for a Domain
• Configure Network Parameters
• Configure a WebLogic Console Port
• Configure a Load Balancer
• Create OCI Policies
• Configure WebLogic Authentication
• Configure Database Parameters
• Set Local VCN Peering
• Configure a Data Source for an Application Database
• Set Local VCN Peering for an Application Database
• Configure Tags
• Create the Domain Stack
• Use Your New Domain

Launch a Stack

Use Marketplace to specify initial stack information.

1. Sign in to the Oracle Cloud Infrastructure Console.
2. Click the navigation menu . Under the Solutions and Platform group, go to Marketplace and click Applications.
3. Select an application that matches the edition of Oracle WebLogic Server that you want to provision, and also uses the type of billing you want (Universal Credits or Bring Your Own License).
   • Oracle WebLogic Server Standard Edition BYOL
   • Oracle WebLogic Server Enterprise Edition BYOL
   • Oracle WebLogic Server Enterprise Edition UCM
   • Oracle WebLogic Suite BYOL
   • Oracle WebLogic Suite UCM
4. Select an Oracle WebLogic Server version.
   The latest 12.2.1.4 patch level is the default version.

   If multiple builds are available for the same patch level (.01, .02, .03, and so on), choose the latest build.

   Note:

   To use an Oracle Autonomous Transaction Processing database, you must select a 12c version.
5. Select the compartment in which to create the stack.
   By default the stack compartment is used to contain the domain compute instances and network resources. If later on you specify a network compartment on the Configure Variables page of the Create Stack wizard, then only the compute instances are created in the stack compartment that you select here.
6. Select the Oracle Standard Terms and Restrictions check box, and then click Launch Stack.
   The Create Stack wizard is displayed.

Specify Stack Information

Specify the name, description, and tags for the stack.

1. On the Stack Information page of the Create Stack wizard, enter a name for your stack.
2. Enter a description for the stack (optional).
3. Specify one or more tags for your stack (optional).
4. Click Next.
   The Configure Variables page opens.

Configure WebLogic Instance Parameters

Specify the parameters needed to configure the WebLogic instance domain.

1. In the WebLogic Server Instance section, enter the resource name prefix.
   The maximum character length is 16.
   This prefix is used by all the created resources.
2. Select the WebLogic Server shape for the compute instances.
   The following shapes are supported:

   • Standard: VM.Standard2.x, VM.Standard.E2.x, BM.Standard2.x, BM.Standard.E2.x

   • Flex: VM.Standard.E3.Flex

   Note:

   In regional subnets, select the WebLogic Server shape that has sufficient service limits for an availability domain, else the provisioning fails.

3. Select the OCPU count for compute instances.

   Note:

   You can specify the OCPU count only for the VM.Standard.E3.Flex shape, and the maximum number of OCPUs that you can specify is 64. The memory, network bandwidth, and number of Virtual Network Interface Cards (VNICs) scale proportionately with the number of OCPUs.

4. Enter the SSH public key, by either uploading the SSH key file or pasting the contents of your SSH public key file.
5. Select the number of managed servers you want to create. You can specify up to 4 if you're using WebLogic Server 11g Standard Edition. For all other editions and versions, you can specify up to 8 nodes, which can be scaled out to 30 when you edit the domain.
   The managed servers will be members of a cluster, unless you selected WebLogic Server Standard Edition.
6. Enter a user name for the WebLogic Server administrator.
7. Enter the OCID of the secret that contains the password for the WebLogic Server administrator. See Create Secrets for Passwords.

Configure Advanced Parameters for a Domain

You can optionally specify additional parameters by selecting WLS Instance Advanced Configuration on the Configure Variables page of the Create Stack wizard.

Select WLS Instance Advanced Configuration if you want to change the default port numbers or remove the sample application.

• Cluster-related parameters are not applicable if you selected WebLogic Server Standard Edition.
• There is no sample application if you selected WebLogic Server Standard Edition 11g.
• The port numbers 9071-9074 are reserved for internal domain communication.

Configure Network Parameters

Define the Virtual Cloud Network (VCN) and subnet configuration for the domain.

1. In the WebLogic Server Network section of the Configure Variables page, select the Network Compartment in which to create the network resources for this domain.
   If you don't specify a network compartment, then all the network resources and the domain compute instances are created in the stack compartment that you selected earlier upon launching the stack. Select a network compartment if you want the network resources to be in a different compartment than the compute instances.
2. Select a Virtual Cloud Network (VCN) strategy:
   • Select Use Existing VCN, and then select the name of the existing VCN.
   • Select Create New VCN, and then enter a name and CIDR for the new VCN.
3. Select one of the following subnet strategies:
   • Select Use Existing Subnet.
   • Select Create New Subnet.

     Note:

     If you're creating a new VCN, you can only create a new regional subnet.
4. Select the Subnet Compartment to use for the existing subnet.

   The subnet compartment is different than the VCN compartment. The subnets for the WebLogic Server nodes, load balancer and the bastion node use this same subnet compartment.

   Note:

   You can specify the subnet compartment only if you're using an existing subnet.

5. For subnet type, select Use Public Subnet or Use Private Subnet.
   Compute instances in a private subnet are not directly accessible from outside of Oracle Cloud.
6. For the WebLogic Server subnet, specify one of the following:
   • If you want to use an existing regional subnet, then choose the name of an existing regional subnet from the list of regional and availability domain-specific subnets.
   • If you are creating a new regional subnet, specify a CIDR for the new subnet.
7. If you selected Use Private Subnet, then configure the bastion compute instance.
   1. Specify one of the following for the bastion subnet:
      • If you want to use an existing regional subnet, then choose the name of an existing regional subnet from the list of regional and availability domain-specific subnets.
      • If you are creating a new regional subnet, then specify a CIDR for the new subnet.
   2. Select a shape for the bastion compute instance.

Configure a WebLogic Console Port

If you are creating a new VCN with public subnets, then you have the option to disclose the Oracle WebLogic Administration Server Console port in a public subnet.

Oracle does not recommend that you open the WebLogic Administrative port to the internet when the WebLogic Server is in a public subnet. If your WebLogic Server is in a public subnet and you need to access WebLogic Administrative Console, then you can restrict the IP addresses by creating a security rule and open WebLogic Server Administrative port only to a CIDR block. Oracle WebLogic Server for Oracle Cloud Infrastructure can configure this security rule for you during provisioning.

1. Select Enable Access to Administration Console.
2. Specify the CIDR to create a security list to allow access to the WebLogic administration console port to the source CIDR range.

Configure a Load Balancer

You have the option to create a load balancer to distribute application traffic to the WebLogic Managed Servers.

To create a load balancer:

1. Select Provision Load Balancer.
2. Configure the load balancer network.
   • If you chose to use an existing regional subnet for WebLogic Server, then select an existing regional subnet from the list of regional and availability domain-specific subnets. A load balancer can have only one regional subnet, which is shared between both nodes.
   • If you chose to create a regional subnet for WebLogic Server, then specify a CIDR for the new load balancer subnet.
3. Select a minimum and maximum flexible load balancer shape.
   By default, the minimum bandwidth size is set to 10Mbps and maximum to 400Mbps.

   Note:

   You can update the shape to a maximum of 8000Mbps. Before you select the maximum bandwidth, ensure to check the available service limit for the flexible load balancer bandwidth.
4. Select Private Load Balancer if you do not want to assign a public IP address to the load balancer.
   This option is available only if you use a private subnet for WebLogic Server. You cannot create a load balancer in a private subnet.

Create OCI Policies

When you create a JRF-enabled domain, by default the OCI Policies check box is selected and Oracle WebLogic Server for Oracle Cloud Infrastructure creates a dynamic group and relevant root-level (tenancy) policies for you.

If you are not an administrator, the necessary groups and policies must be in place before you can create a domain.

Before you deselect the check box, ask your administrator to create the required dynamic group and relevant policies, as described in Create a Dynamic Group and Create Policies for the Dynamic Group.

Configure WebLogic Authentication

You have the option to use Oracle Identity Cloud Service to authenticate application users for your domain.

This configuration is only available if the domain meets these requirements:

• Running WebLogic Server 12c
• Includes a load balancer

To use Oracle Identity Cloud Service for authentication:

1. Select Enable Authentication Using Identity Cloud Service.
2. Enter your Oracle Identity Cloud Service (IDCS) tenant name, which is also referred to as the instance ID.
   This ID is typically found in the URL that you use to access Oracle Identity Cloud Service, and has the format idcs-<GUID>.
3. Enter the client ID of an existing confidential application in this Oracle Identity Cloud Service instance.
4. Enter the OCID of the secret that contains the client secret of the confidential application.
5. If necessary, you can override the default domain name and port that you use to access Oracle Identity Cloud Service, or the default port that is used for the App Gateway software appliance.

Configure Database Parameters

You must specify a database in Oracle Autonomous Transaction Processing or Oracle Cloud Infrastructure Database (DB System) when you create an Oracle WebLogic Server for Oracle Cloud Infrastructure domain that includes the Java Required Files (JRF) components.

The database you specify is used to contain the required infrastructure schemas for the JRF-enabled domain.

If you are creating a domain for Oracle WebLogic Server 11g:

• Oracle Autonomous Transaction Processing is not supported.
• The database must be running Oracle Database 11g or 12.1.

On the Configure Variables page, select the Provision with JRF checkbox to display the Database options. Then in the Database section, select the Database Strategy for your domain and configure the database parameters.

• If using Autonomous Database Transaction Processing, select or enter the following:
  • The compartment in which you've created the database.
  • The database where you want to create the JRF schemas for this WebLogic domain.
  • The service level that the domain should use to connect to the selected autonomous database.
  • The OCID of the secret that contains the password for the ADMIN user to access the selected autonomous database.
• If using Database System, select or enter the following:
  • The compartment in which you've created the database.
  • The compartment in which the database's VCN is found.
  • The VCN on which you've created the database. If this VCN is different than the WebLogic Server VCN, they cannot have overlapping CIDRs. For example, you cannot create a domain on VCN 10.0.0.0/16 that uses a database on VCN 10.0.0.1/24.
  • The DB system to use for this WebLogic domain.
  • The database home within the selected DB system.
  • The database home version.
  • The database within the selected DB system where you want to create the JRF schemas for this domain.
  • The Pluggable database (PDB) name, only if the selected database is running Oracle Database 12c or later.
  • The name of a database user with database administrator (DBA) privileges.
  • The OCID of the secret that contains the password for the database administrator.
  • The database listen port (1521 by default)
• If using Database System, then Oracle WebLogic Server for Oracle Cloud Infrastructure creates a security list in the VCN on which you've created the database. This security list allows the WebLogic Server subnet to access the database port. If this step isn't required or you don't have the correct permissions to modify the database network, clear the Create DB Security List check box.

Set Local VCN Peering

If you selected different VCNs for the WebLogic Server compute instances and the Oracle Cloud Infrastructure Database (DB System), you can either disable the local VCN peering or configure the local VCN peering for the Infrastructure Database.

If the VCNs for WebLogic Server compute instances and the Oracle Cloud Infrastructure Database have been peered before creating the stack for the Oracle WebLogic Server for Oracle Cloud Infrastructure domain. select the InfraDB VCN is Already Peered with the WLS VCN checkbox. See Local VCN Peering to peer the VCNs manually. In this case, the stack is provisioned based on the database private IP address.

If the VCNs for WebLogic Server compute instances and the Oracle Cloud Infrastructure Database system have not been peered, you can use Oracle WebLogic Server for Oracle Cloud Infrastructure to update the two VCNs so that they can communicate.

Oracle WebLogic Server for Oracle Cloud Infrastructure creates a public subnet in each VCN, and then creates a compute instance in each subnet. These compute instances run software to forward DNS requests across the VCNs.

You cannot use existing subnets for the DNS Forwarder compute instances.

1. Specify a CIDR for the new subnet in the WebLogic Server VCN.
2. Specify a CIDR for the new subnet in the database VCN.
3. Select a shape for the new DNS Forwarder compute instance in each VCN.

Configure a Data Source for an Application Database

When you create an Oracle WebLogic Server for Oracle Cloud Infrastructure domain, you can configure the application database to create a data source configuration that enables you to connect to Oracle Autonomous Transaction Processing or Oracle Cloud Infrastructure Database (DB System).

The database that you connect to is used to contain the schemas for the application database.

You can configure the application database only for Oracle WebLogic Server Enterprise Edition and Oracle WebLogic Suite.

If you are creating a domain for Oracle WebLogic Server 11g:

• Oracle Autonomous Transaction Processing is not supported.
• The database must be running Oracle Database 11g or 12.1.

On the Configure Variables page, select the Configure Application Datasource checkbox to display the Database options. Then in the Application Database section, select the Application Database Strategy for your application database and configure the database parameters.

• If using Autonomous Transaction Processing Database, select or enter the following:
  • The compartment in which you've created the application database.
  • The autonomous database where you want to create the schemas for the application database.
  • The name of an autonomous database user to configure the application database.
  • The OCID of the secret that contains the password for the application autonomous database user to access the selected autonomous database.
  • The service level that the domain should use to connect to the application database for the selected autonomous database.
• If using Database System, select or enter the following:
  • The compartment in which you've created the application database.
  • The DB system to use for this application database.
  • The compartment in which the application database's VCN is found.
  • The VCN on which you've created the application database. If this VCN is different than the WebLogic Server VCN, they cannot have overlapping CIDRs. For example, you cannot create a domain on VCN 10.0.0.0/16 that uses a database on VCN 10.0.0.1/24.
  • The database home within the selected application database system.
  • The version of the selected database home.
  • The database within the selected DB system where you want to create the schemas for the application database.
  • The Pluggable database (PDB) name, only if the selected application database is running Oracle Database 12c or later.
  • The name of a database user to configure the application database.
  • The OCID of the secret that contains the password for the application database user.
  • The application database listen port (1521 by default)
• If using Database System, then Oracle WebLogic Server for Oracle Cloud Infrastructure creates a security list in the VCN on which you've created the application database. This security list allows the WebLogic Server subnet to access the application database port. If this step isn't required or you don't have the correct permissions to modify the database network, clear the Create Application Database Security List check box.

Set Local VCN Peering for an Application Database

If you selected different VCNs for the WebLogic Server compute instances and the Oracle Cloud Infrastructure Application Database, you can either disable the local VCN peering or configure the local VCN peering for the Application Database.

If the VCNs for WebLogic Server compute instances and the Oracle Cloud Infrastructure Application Database have been peered before creating the stack for the Oracle WebLogic Server for Oracle Cloud Infrastructure domain. select the Application Database VCN is Already Peered with the WLS VCN checkbox. See Local VCN Peering to peer the VCNs manually. In this case, the stack is provisioned based on the database private IP address.

If the VCNs for WebLogic Server compute instances and the Oracle Cloud Infrastructure Application Database system have not been peered, you can use Oracle WebLogic Server for Oracle Cloud Infrastructure to update the two VCNs so that they can communicate.

Oracle WebLogic Server for Oracle Cloud Infrastructure creates a public subnet in each VCN, and then creates a compute instance in each subnet. These compute instances run software to forward DNS requests across the VCNs.

You cannot use existing subnets for the DNS Forwarder compute instances.

1. Specify a CIDR for the new subnet in the WebLogic Server VCN.
2. Specify a CIDR for the new subnet in the application database VCN.
3. Select a shape for the new DNS Forwarder compute instance in each VCN.

Configure Tags

Oracle WebLogic Server for Oracle Cloud Infrastructure can optionally assign tags to the resources (compute, network, and so on) that it creates for your domain.

Tagging allows you to define keys and values and associate them with resources. You can then use the tags to help you organize and find resources based on your business needs. There are separate fields to tag the stack and to tag the resources created within the stack.

1. To assign an existing tag, enter the Defined Tag Key and Defined Tag Value.
   Specify the name of a defined tag using the format <namespace>.<key>. For example, Operations.CostCenter.
2. To assign a free-form tag, enter the Free-Form Tag Key and Free-Form Tag Value.
   Free-form tag keys and values are case sensitive. For example, costcenter and CostCenter are treated as different tags.

Create the Domain Stack

After you have specified the WebLogic instance variables, finish creating the domain stack.

On the Review page of the Create Stack wizard, review the information you have provided, and then click Create.

The Job Details page of the stack in Resource Manager is displayed. A stack creation job name has the format ormjobyyyymmddnnnnnn. (for example, ormjob20190919165004). Periodically monitor the progress of the job until it is finished. If an email address is associated with your user profile, you will receive an email notification. In the Application Information tab, you can directly access the OCI resources using the WebLogic instance IP and the bastion instance IP.

Note:

If there is an error during the creation of the stack, the compute, network, and other resources in the stack are not automatically deleted. If you want to delete the failed stack, see Delete a Domain.

Use Your New Domain

Access and manage your new domain after creating a stack with Oracle WebLogic Server for Oracle Cloud Infrastructure.

Typical tasks that you might perform after creating a domain:

• View and manage the cloud resources that were created to support your domain. See View the Cloud Resources for a Domain.
• Use the WebLogic Server administration console to configure your domain. Create data sources, JMS modules, Coherence clusters, and so on, or deploy applications. See Access the WebLogic Console.
• Access the sample application that's deployed to your domain. See Access the Sample Application.
• Secure access to your applications using Oracle Identity Cloud Service. See Secure a Domain Using Identity Cloud Service.
• Add your own SSL certificate to the load balancer. See Add a Certificate to the Load Balancer.
• Troubleshoot a problem with your new stack. See Stack Creation Failed.

You can also use the Fusion Middleware Control Console to monitor, configure, and manage a JRF-enabled domain. See Access the Fusion Middleware Control Console.