Transport port conflicts

About the transport port

The ports used for transport between the core application and the transport group leaders are assigned to 8080 by default. Other applications might also bind to port 8080, causing port conflicts. RealNetworks' RealPlayer is one example of this.

To reconfigure the transport port, you need to change it at the core application and at each CDA.

Reconfiguring the transport port on the core application

Two scripts are available for reconfiguring the transport port.

chgports allows you to specify the port to use for transport.
chgtom automatically changes the port to the next available port and displays the new port number

The location of these scripts depends on the operating system of the core application machine:

Under Windows, the ContentDirector\Ccm directory
Under Solaris, the /opt/NTAPccm/bin directory

To reconfigure the transport port, complete the following steps.

Step	Action
1	Stop the ContentDirector service.
2	Navigate to ContentDirector\Ccm (for Windows) or /opt/NTAPccm/bin (for Solaris).
3	At the prompt, run either chgports or chgtom: To run chgports, type: chgports -tn <port number> where <port number> is the new port, then press Enter. To run chgtom, type: chgtom then press Enter.
4	Start the ContentDirector service.
5	Change the ContentDirector port on each CDA to match the new port. See Reconfiguring the transport port on the CDA.

Reconfiguring the transport port on the CDA

When you change the transport port at the core application, you must also change it at each CDA to match the new port. To change the port at the CDA, complete the following steps.

Step	Action
1	From the NetCache Manager utility, select Setup > ContentDirector > Advanced.
2	Under Core Application Port, enter the new port number you configured at the core application.
3	Click Commit Changes.