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 Datasource for an Application Database
- Set Local VCN Peering for an Application Database
- Configure Tags
- Create the Domain Stack
- Use Your New Domain
Configure WebLogic Instance Parameters
Specify the parameters needed to configure the WebLogic instance domain.
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.
- 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.
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.
- Select Enable Access to Administration Console.
- 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:
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:
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 VCN10.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.
- Specify a CIDR for the new subnet in the WebLogic Server VCN.
- Specify a CIDR for the new subnet in the database VCN.
- Select a shape for the new DNS Forwarder compute instance in each VCN.
Configure Datasource 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 datasource 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 VCN10.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.
- Specify a CIDR for the new subnet in the WebLogic Server VCN.
- Specify a CIDR for the new subnet in the application database VCN.
- 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.
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.
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.
- 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.