Dashboard > Pulse v1.1 > ... > Setup and Administration > Changing the Web Application Port
  Pulse v1.1 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 Oct 23, 2006  (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>./startup.sh -p 8000

Configuration file

On startup, pulse™ will look for a configuration file in the $USER_HOME/.pulse/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.

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>./startup.sh -p 8000

Configuration file

On startup, pulse™ will look for a configuration file in the $USER_HOME/.pulse/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.

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