Before You Begin
This 30-minute tutorial shows you how to create a virtual cloud network (VCN) in Oracle Cloud Infrastructure.
Background
Before you can launch an instance, you need to have a VCN and subnet into which it can launch. A subnet is a subdivision of your VCN that you define in a single availability domain. For additional details, refer to Creating a Virtual Cloud Network and VCNs and Subnets.
What Do You Need?
- The user interface for the Oracle Cloud Infrastructure Console is constantly evolving. For the most up-to-date descriptions and navigation, refer to Using the Console.
- You should have a fundamental understanding of Oracle Cloud Infrastructure. It is highly recommended that you review the extensive collateral information, including training, at this site:
- You must have a subscription and an Administrator account to Oracle Cloud Infrastructure as described at this site:
- To access the Oracle Cloud Infrastructure Console, you must use a supported browser.
Creating
a Virtual Cloud Network
To create a VCN on Oracle Cloud Infrastructure:
- On the Oracle Cloud Infrastructure Console Home page, click
the Navigation Menu in the upper-left
corner.
Navigation Menu - Networking > Virtual Cloud Networks - From the Navigation Menu, in the Networking section, click to select the Virtual Cloud Networks service.
- In the List Scope section in the left panel, use the COMPARTMENT drop-down to select the Compartment you created in the previous step.
- Click the Create Virtual Cloud Network button.
- On Create Virtual Cloud Network, complete the following
fields:
- CREATE IN COMPARTMENT
Use the drop-down to select the Compartment you previously created and which will use this VCN. - NAME
Enter a name for the VCN. In this example, the name given is: jde_vcn
- CREATE IN COMPARTMENT
- Enable the CREATE VIRTUAL CLOUD NETWORK PLUS RELATED RESOURCES option:
- Because the use of DNS is recommended, you should select
the USE DNS HOSTNAMES IN THIS VCN check box.
Note: The Domain Name System (DNS) lets computers use hostnames instead of IP addresses to communicate with each other. For additional details, refer to DNS in Your Virtual Cloud Network.
Important: While on this form, you should also note the value given by the system for the field DNS Label. This value is required as input in the VCN DNS Label field in the Infrastructure Provisioning Console. If you do not provide a value for Name for the VCN, this value is auto-generated by the system. If you did provide a value for the Name for the VCN, the system eliminates special characters and limits the value to a maximum of 15 alphanumeric characters.
Create Virtual Cloud Network Definition - DNS Enabled - Click the Create Virtual Cloud Network button and verify that all VCN resource allocations are complete successfully.
- On the Create Virtual Cloud Network screen that shows the
VCN was successfully created, click the Close
button.
Virtual Cloud Network Created Successfully - On Virtual Cloud Networks in <name> Compartment, click
the link for the VCN you just created. For example, jde_vcn.
Virtual Cloud Network Created Successfully - Under Resources in the left pane, select Security Lists.
- In the Security Lists in <vcn_name>
section, click the link Default
Security List for <vcn_name>.
VCN Details - Resources - Security Lists - On Default Security List for <vcn_name>,
under resources, click the Ingress Rules
resource in the left pane and then the Edit All Rules
button.
VCN Details - Security Lists - Ingress Rules - On Allow Rules for Ingress, three default Stateful
rules are displayed. You can accept the default rules and
click the Edit All Rules button to add specific rules required
for JD Edwards EnterpriseOne.
VCN Details - Security Lists - Default Rules - On Edit Security List Rules, in Allow Rules for Ingress, click the + Add Rule button.
- To create additional rules that are required for JD Edwards
EnterpriseOne One-Click Provisioning, click the Add
Rule button.
Because this VCN is only for the Infrastructure Staging Server, you only need to open port 5901 with a Source CIDR of 0.0.0.0/0. This is the listen port of the VNC Server. - For the new rule for the listen port of the VNC Server:
SOURCE CIDR
Enter this value: 0.0.0.0/0
DESTINATION PORT RANGE
Enter this value: 5901 - Click the Save Security List Rules button to complete the setup for Ingress Rules.
- As shown below, you can accept the default Egress Stateful Rule that allows egress to all destinations, all protocols, and all traffic for all ports.


