Changing Ports
Upon installation, when setting ports for Cascade, many clients make the mistake of setting a port that is already in use by another application. To remedy this problem, the port must be changed manually to a port that is both listening and not in-use.
Please note that changing ports is function usually handled by system administrators. There are many reasons for setting ports other than initially setting the port incorrectly. Cascade Server uses ports for communications and administrators are responsible for making port changes. Additionally, it is imperative that administrators shutdown their existing server(s) before making a port change. Doing so allows Cascade to recognize the new port after you have saved the change and restarted the CMS again.
*Please be sure to shutdown Cascade Server before making these changes.*
2) Shutdown the server with either the shutdown.bat file (for windows) or the shutdown.sh (*nix).
3) Navigate out of the /bin/ directory and into the /tomcat/conf/ directory.
4) Navigate to: /CascadeServer5/tomcat/conf/. :
5) Edit the file server.xml<Connector port="8080" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75
enableLookups="false" redirectPort="8443" acceptCount="100
connectionTimeout="20000" disableUploadTimeout="true" />
*Notice, the line to be concerned with is: Connector port="8080" maxHttpHeaderSize="8192". Specifically, connector port="8080" is the port which enables Cascade server to run on. So, for example, if the user's ip address was 10.0.1.2, the CMS would be located at http://10.0.1.2:8080.
6) Restart the server for these changes to take affect by navigating back to the /bin/ directory and executing the startup script via the startup.bat file (Windows) or the startup.sh (*nix) file depending on which operating system cascade is running on.