Dashboard > Pulse v2.0 > ... > Setup and Administration > Changing the Web Application Port
  Pulse v2.0 Log In | Sign Up   View a printable version of the current page.  
  Changing the Web Application Port
Added by Jason Sankey, last edited by Jason Sankey on Nov 19, 2008  (view change)
Labels: 
(None)

Pulse Manual Index

Changing the Web Application Port

By default, your pulse™ server's web interface will listen on port 8080. If you are unable to use this port for any reason, you have two ways to specify a custom port.

Command line

When starting pulse™, you can specify the port with the -p <port> argument. For example, to make pulse™ listen on port 8000:

PULSE_HOME/bin>./pulse start -p 8000

Configuration file

On startup, pulse™ will look for a configuration file in the $HOME/.pulse2/config.properties file. This file contains properties in the format:

<name>=<value>

To have pulse™ start on a custom port, use the webapp.port property. For example, to make pulse™ listen on port 80:

webapp.port=80

For the change to take effect, you will need to restart your pulse™ server.

Running as a Windows Service.

When you run pulse™as a windows service, there are alternative ways to configure the port.

Command line

Although the command line is not directly accessible, it can be modified by changing the $PULSE_HOME/bin/wrapper.conf file. To set the web application port, you will need to add an extra java parameter as shown below:

Look for the following content in the wrapper.conf file:

# Java Additional Parameters
wrapper.java.additional.1=-Dpulse.home=..
wrapper.java.additional.2=-Djava.awt.headless=true
wrapper.java.additional.3=-Djava.util.logging.config.class=com.zutubi.pulse.logging.ConsoleConfig

And add the following:

wrapper.java.additional.4=-Dwebapp.port=8081

This will tell pulse™ to start on web app port 8081. Set this to which ever port is necessary.

Configuration file

As when running via the pulse script, the configuration file is still available. To locate it, however, you need to find the $HOME directory of the service. If you have set the service to run as a specific user, it will be that user's home. If, however, the service is running as the LocalSystem users, the home directory may be located at either the system profile directory or a <DRIVE>:\.pulse2\config.properties directory, where the <DRIVE> is the drive on which pulse™ has been installed. So, if pulse™ is installed in C:\Program Files\Zutubi\Pulse Server, then the configuration file will be located in C:\.pulse2\config.properties.

Zutubi wiki is Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.2.10 Build:#528 Nov 29, 2006) - Bug/feature request - Contact Administrators