If you need to change the default http listener port for the gateway because you have another process running on port 8080
The gateway listens on two ports by default
Default Services on port 8080
Management Services on port 8090
Policy Studio along with other tools from the suite connect to the gateway over http on port 8090 (obviously this is changed for prod deployments to https on a port of your choice bound to a specific IP on the dedicated management network) but if you have 8090 in use on your dev machine or laptop then you’ll need to change it straight off before you can even start on policy design.
How to change the default port for management services
Step 1: connect policy studio to the file based configuration for the gateway
open the file representation of the configuration located at
leaving the passphrase key blank for now….
Note you can connect to a “downloaded” or “shared” configuration in this way, make changes, export configuration fragments – basically everything but deploy to the gateway – it is also a pretty easy way to load up a back up or an archived config for merge/compare (more on that later….)
Step 2: Show the management services
Select window and then preferences from the main menu bar, select management services and check the box that says “show management services”….. and click ok.
If it is not already showing, select the processes configuration section and expand the vordel gateway node, you should now see Management Services listed here.
Expanding the management services node further should reveal an http listener configured as *:8090
Step 3: edit the http listener interface
Selecting the http listener under the management services node displays the properties panel in the central pane – with a hyperlink to “edit” – or alternatively you can right click on the http listener node in the left hand explorer panel and select “edit” from the mouse menu.
Amongst other settings you will see the “Port” set to the default value of 8090 – you can now change this to a suitably free port – to check if the desired port is available try running
netstat -a -b –n
-a = all listening connections and ports
-b = details of process that owns the connection (can make it take a while)
-n = display ports in numerical form (rather than taking a guess at the protocol name)
Once you are happy that you have the right port selected click on the ‘ok’ button and close the configuration tab (the one at the top)…. notice that the changes are applied directly to the file, so there is no “undo” and equally no need to deploy (as we are connecting directly to the file)
you should now be able to start the gateway instance with management services available on the port you just specified …
remember that the settings used to connect to your gateway instance will now need to be updated to reflect the change in port for the management services
INFO 07/Jun/2011:19:22:53.504 [2f18] Adding monitor for proc: http://localhost:8090/runtime
/management/ManagementAgent INFO 07/Jun/2011:19:22:53.511 [2f18] ... monitoring started. INFO 07/Jun/2011:19:22:53.513 [2f18] TCP interface INFO 07/Jun/2011:19:22:53.514 [2f18] checking invariants for interface *:8091 INFO 07/Jun/2011:19:22:53.515 [2f18] listen on address 0.0.0.0/8091
update the connection parameters for the process
and click save
Once you have successfully connected to the gateway with policy studio you can edit the configuration and change the port number for the default services http listener as required – to deploy the changes click the deploy button (or press F6)