Configure Network Parameters

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

Based on your configuration in the Stack Configuration section, you can configure network parameters for an existing VCN or a new VCN.

• If you select Create a Virtual Cloud Network option, see Configure Network for New VCN.
• If you do not select Create a Virtual Cloud Network option, see Configure Network for Existing VCN.

  Note:

  During provisioning, by default, the existing network is validated using the validation script, network_validation.sh. See Validate Existing Network Setup.

Note:

Ensure that you have set up the user group polices and dynamic group polices that are applicable for the configuration. See User Group Policies and Dynamic Group Policies.

Configure Network for New VCN

Specify the parameters to configure a new VCN.

1. 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. Enter a name and CIDR for the new VCN.

Configure Network for an Existing VCN

1. 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 the name of the existing VCN.
3. Specify the subnet configuration as follows:
   • For existing VCN and new subnets:
     1. Select Create New Subnets.
   • For existing VCN and existing subnets:
     1. Do not select the Create New Subnets option.
     2. 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.
     3. Keep the default Use Private Subnet selection.

        Compute instances in a private subnet are not directly accessible from outside of Oracle Cloud. So, you must configure a bastion compute instance on a public subnet. See Configure a Bastion.

        You can also select Use Public Subnet for the domain.

        For a public subnet, ensure to limit the CIDR range to access WebLogic administration console ports, the default ports are 7001 and 7002 for http and https respectively.

        Note:

        The Provision Bastion Instance option is not available when you use a public subnet.
     4. Select the regional subnet or availability domain-specific subnet.
     5. Select Existing Network Security Groups to use existing Network Security Groups (NSGs) in the VCN, to secure your resources created by the stack.

        You can specify network security groups for administration server node, managed server node, bastion instance, load balancer, and file storage.