Changing SOA Suite HTTP Port

Changing SOA Suite HTTP Port

I just had a call from a colleague asking how to change the HTTP port of a developer install of SOA Suite.  He had a default installation on port 8888 and needed to change it to port 80 so that it would go through a firewall.  So lets look at the steps needed to perform this change.

Process Outline

Basically this process has two steps
  1. Change the port number of the web server
  2. Change any references to that port number elsewhere in the install
Sounds simple enough so lets see how it plays out.  I have to confess that this was easier in 10.1.2 but when the Application Server Control moved to JMX there was a limit on how much functionality could be migrated over in the available timescale, and opmn port changing was one of things that didn't make the release date.

Change the HTTP Listening Port

First we need to change the listener to listen on port 80 instead of the default port 8888 (or whatever port was free on your install).  the OC4J web listening port is set dynamically at run time by OPMN from an available port in a given range.  The range for the HTTP port is always set to be a single port number and this is the port number we must change.
  • Stop the SOA Suite running
    • In directory $ORACLE_HOME/opmn/bin execute command 'opmnctl stopall'
  • Edit the file $ORACLE_HOME/opmn/conf/opmn.xml
    • Find the entry '<port id="default-web-site" range="8888" protocol=HTTP/>'
    • Change the range to port 80
    • Save the file
  • Start the SOA Suite running
    • In directory $ORACLE_HOME/opmn/bin execute command 'opmnctl startall'
Verify that SOA Suite is now running on port 80.  Note that IE has a nasty habit of caching a page even if you do a Control Refresh, and so it may appear that your SOA Suite is running on two ports.  In Firefox hitting Control Refresh causes the old port address to come back with a server not found error.  Score one for Firefox!

Modify BPEL to use new Port Number

BPEL needs to know the port number it is listening on in order to construct SOAP endpoint addresses for use in WSDL and callbacks.  We need to tell BPEL that the port number has changed.
  • Go to BPEL Admin 'http://localhost/BPELAdmin'
  • Log in as 'oc4jadmin'
  • Change the following entries to have port 80
    • soapServerUrl
    • soapCallbackUrl
    • clusterName
  • Click 'apply'
I don't think you really need to change clusterName but it will confuse the heck out of you if you don't!  I would bounce SOA Suite again to make sure the change get picked up.

Reload BPEL Processes

At this point I would reload any deployed processes, making sure that I revalidated them before deploying because any partner links referring to existing processes on this server will now be pointing to the wrong port!

Change Build Parameters

If you plan on using ant to deploy applications then update it to the new port number.
  • Edit $ORACLE_HOME/bpel/utilities/
    • Change the http.port property to the correct value
Now ant will deploy to the correct port on the server.
If you plan on deploying from the samples directory then remember to go through and change all partner link port numbers in the bpel.xml files.

Voila! the Job is Done!

That's all folks - simple really if you know where to look!
For other ways of doing this look in the documentation for 10.1.3 here.


If we choose to change the build file for new port entry, what will happen to already deployed applications. Do we need to reploy the old applications?

Posted by Archana on November 14, 2007 at 06:53 PM MST #

Existing J2EE application don't need redeploying.  However if you have references to other processes in your BPEL processes then they will need redeploying as the references will now point to the wrong port number.

Hope that clarifies things

Posted by Antony Reynolds on December 05, 2007 at 12:14 AM MST #

Post a Comment:
Comments are closed for this entry.

Musings on Fusion Middleware and SOA Picture of Antony Antony works with customers across the US and Canada in implementing SOA and other Fusion Middleware solutions. Antony is the co-author of the SOA Suite 11g Developers Cookbook, the SOA Suite 11g Developers Guide and the SOA Suite Developers Guide.


« February 2016