Add an Ingress Rule to Allow the JDeveloper Connection

After provisioning the Oracle SOA Suite on Marketplace instance, you must set up your JDeveloper environment before you can use it to deploy applications.

To set up JDeveloper for deploying to Oracle SOA Suite on Marketplace:

1. Refer to Access an Oracle SOA Suite on Marketplace Instance and make a note of the public IP address (or addresses in the case of a multinode cluster) associated with each SOA server.
2. Log in to the WebLogic Server Administration Console.
3. On the Summary of Servers page, click each Managed Server name and make a note of the Listen Address value:
   
   

   

   
   

   Be sure to capture the listen addresses for all Managed Servers.

4. On the host on which JDeveloper is running, map the listen address of each Managed Server to the associated SOA server public IP address in the hosts file. For Windows, the hosts file is typically located at C:\Windows\System32\Drivers\etc\hosts. For example:

   129.146.136.141 sobdemo-wls-1.soacsp2pubsubne.soacsp2vcn.oraclevcn.com
   158.101.23.141  sobdemo-wls-2.soacsp2pubsubne.soacsp2vcn.oraclevcn.com
   129.146.136.141 sobdemo-wls-1
   158.101.23.141  sobdemo-wls-2

5. Add the ingress rule to permit traffic from JDeveloper to the SSL listener port of the Managed Server:
   1. Sign in to the Oracle Cloud Infrastructure Console.
   2. Open the navigation menu, click Networking, and then click Virtual Cloud Networks.
   3. Select the compartment where you created the new instance.
   4. In the list of VCNs, select your VCN.
   5. On the Virtual Cloud Network Details page, click Security Lists in the left pane.
   6. Select a security list, and click Add Ingress Rules to open the Add Ingress Rules dialog.
   7. In the Add Ingress Rules dialog, create an ingress rule for port 9074 to access JDeveloper as shown in the following screenshot:
      
      

      

      
      

      Note:

      The source CIDR is the CIDR of the machine where JDeveloper is running.
   8. Add another ingress rule for port 9072, with the same source CIDR as port 9074.

      Important:

      By adding this ingress rule, be aware that you are allowing traffic from the internet (known CIDRs) into WebLogic Server. You must be extra cautious and open traffic to known CIDRs only.

Next step: Create an application server connection.