The Lab Management Manager node and the Lab Management subnets need access to the CollabNet TeamForge or CEE site on specific ports.
All of the components of the Manager Server can reside on one machine if you
employ virtual machines. The factors to consider are performance, redundancy, and the
amount of disk space that you have on the Manager node. The O/S repository that
CollabNet supports, for example, is about 130 GB.
-
Allow access to the main site from the Lab Management Manager node and the Lab Management subnets using these ports:
- For TeamForge:
| Port 22 |
ssh, Secure Shell |
| Port 25 |
SMTP, e-mail |
| Port 80 |
HTTP, Web Server |
| Port 443 |
SSL, Secure Web Server |
| Port 2401 |
CVS. If you know that your CEE installation does not
use CVS and only uses Subversion, you can omit this port.
|
| Port 8080 |
SOAP, SourceForge SOAP API |
- For CEE:
| Port 22 |
ssh, Secure Shell |
| Port 25 |
SMTP, e-mail |
| Port 80 |
HTTP, Web Server |
| Port 443 |
SSL, Secure Web Server |
| Port 2401 |
CVS. If you know that your SFEE installation does not
use CVS and only uses Subversion, you can omit this port.
|
| Port 22000 |
xmlrpc, XML-RPC API port |
-
Make sure that your Lab Management Manager
has the proper network access to any additional repository servers that might be
set up for your TeamForge Domain.
Note: Establish an administrator account - site administrator in the TeamForge
site or domain administrator in the CEE site - with a user ID that is
different from any shell account on the Manager node.
-
Ensure that the networks assigned to Lab Management can reach any other defined
repository servers or linked applications set up in TeamForge.