Network Channels with Java Cloud + SOA Cloud has become a little easier

The cloud services are rapidly changing and are becoming easier all the time. This blog is an example of that.

One of the things that has changed is the network configuration of Oracle Java Cloud Service and Oracle SOA Cloud Service. It’s been a common task to create communication channels with these services to administer the environments. So that means creating specific security rules and typically it is a usual practice of creating different ports specific for the administration network traffic. Now, this already been done for you.

Here’s some of the changes that makes it easier.

#1 – Default Listen Ports

The default listen ports have now changed. These are mapped to 80 and 443. These port numbers seem to be arbitrary and only accessible through 80 and 443. With the other changes, it’s likely that we won’t need to change these configurations. This applies to both the non-secured and secured ports.

#2 – Admin Server Network Channel Additions

The admin server now has some additional network channels pre-defined. Note that configuring access to 7001 / 7002 now doesn’t impact external traffic and specific security rules can be configured. We can do this in the compute cloud service console. There’s also another 9001 pre-defined. Not sure specifically why it’s there. But it’s bound to localhost so I assume it for locally run WLST scripts. Even though it’s not shown in the image – the public address is the external public IP address of the compute instance – this was something that Carlos did in his blogs.

#3 – Managed Server Network Channel Additions

The managed server now also has some additional network channels pre-defined. Note that configuring access to 8001 / 8002 are typically the old network ports used by managed servers and are required for deployments (especially for JDeveloper). So same again – setting security rules can be configured in the compute cloud service cloud. Even though it’s not shown in the image – the public address is the external public IP address of the compute instance.

So … What’s the result?

It just means that things are a little easier to do …

  • The network channels for administration are already available. You will still need to securely expose these ports.
  • No need to muck around with public addresses and modifying the network configuration. What we need is now standard.
  • Connecting JDeveloper or Maven to deploy and test against Java Cloud and SOA Cloud is easier.

Author: Jason Lowe

Also known as: JLo, JSON I'm passionate about how organisations adopt IT quickly and sustainably to achieve a specific and measurable outcome. "How ?" Through creating sustainable platforms that are supported by lean IT practices in operational support and project delivery, and adopting these practices with Oracle technologies. Another area of interest is the use of commodity solutions to reduce the focus on things that the customer doesn't care about and the use of innovative solutions to focus on things that the customer does. I'm looking into how we (as an industry) can disrupt ourselves and others, in our methods of innovation, in our engagement & collaboration and in our expectations of ourselves and others. I'm currently learning and understanding different perspectives and drivers - from enterprise to start-ups, academia to commercial to public sector, cost-sensitive (risk) to value-driven (reward) - all of which influences decisions that organisations make. All of this will (hopefully) lead to understand 'my customers' better so I can 'service' their needs better.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s