Oracle Public Cloud – Oracle Service Bus – Opening up a network port for the Service Proxy

This is a brief article on using the Oracle Service Bus capability of SOACS in the Oracle Public Cloud.  If you want to try it out, go ahead and ask for a public trial.  SOACS comes as part of the JCS Trial environment.

SOACS in the Cloud

We have 1 instance of SOACS and 1 instance of Managed File Transfer Servce in the Cloud.  

In this case, we have a single node OSB/BPEL server in a managed server.  The managed server is running on port http (8001) and https (8002).  The Admin server is running the same VM and listening on 7002.

Service Bus Console 12c – sayHello Project

Project created with the sbconsole tool just like being on premise.  Nothing special.

Project accepts a string and then echoes back.

Oracle Service Bus Console 12c : Proxy Service Testing – sayHelloProxy

Oracle Service Bus Console 12c : Proxy Service Testing – sayHelloProxy

Oracle SOA Cloud Service Details – (Private Browsing)

1) Select Consoles

2) Select Compute Cloud Service

Compute Dashboard

Select "Network"

What you will see here are all of the default network settings created at the time you provisioned your instance.

Network Dashboard

Network tab has the Security Rules, Lists, etc..

To get the sayHello OSB proxy to work properly, we need to add a Security Rule.

You will notice that the provisioin of the environment sets up default rules.  

These rules use  security lists and applications.

There are a couple of rules which are needed by default.  For example, https access to WLS Admin / FMW Control consoles and SSH access.

Let’s create a new rule so that our OSB proxy can be accessed on 8001 and 8002 on the managed server.


Create Security Rule

What does this dialog tell you and what do you need to create?

You don’t need to create anything….the SOACS provisioning took care of all of that for you.  You just need to configure.

  1. Descriptive Name
  2. Is this rule Enabled or Disabled?
  3. What Security Application are talking about? This list is defined in the Security Applications and the provisioning predefined the application for you.  The selection opens ports 8001/8002.  These are the ports on the managed server hosting OSB.  We can add, change and edit Security Applicaitons as needed for our circumstances.
  4. Trafiic is coming from where?  We can define and whitelist the traffic for the environment.  In our case, it is coming from the public internet.
  5. Which server is going to get this trafic? The managed server was defined when the SOACS instance was provisioned.

I think this declarative method of managing the access to the servers is a very ppwerfuland iit is all taken care of for you out of the box.  There is alot of flexibility here.

Once created, this rule will show up in the list.



Generate the WSDL for what you need to do…

You now have access to the OSB proxy created by SOACS.

Pretty nice isn’t it?

%d bloggers like this: