<Connector port="8080" protocol="HTTP/1.1" connectionTimeout="20000" URIEncoding="UTF-8"/>
When TEAMS-RDS is installed, whether by itself or through TEAMS-IDE Server, TEAMS-RDS’ Tomcat server is configured to listen on port 80. If and when IIS is installed and enabled, Tomcat won’t be able to listen on port 80, thus you will not have access to the TEAMS-RDS server. This document will cover how to change the Tomcat server port so that it does not conflict with IIS. Giving you access to TEAMS-RDS.
<Connector port="8080" protocol="HTTP/1.1" connectionTimeout="20000" URIEncoding="UTF-8"/>
Typical Scenario: whenever the service agent logs onto the corporate network, a sync is initiated.
Typical scenario: Controlled/Monitored access from customer site.
Typical scenario: When TEAMATE does not have direct access to TEAMS-RDS.
Typical scenario: When TEAMATE does not have direct access to TEAMS-RDS.
If TEAMS-RDS is to be served over HTTPS, then there are two steps required.
This depends on which web-server is being used. For example, for Apache web-server, consult this page, http://httpd.apache.org/docs/current/ssl/. For other web-servers, consult their respective user guides.
After the web-server has been configured for HTTPS, TEAMS_RDS may be accessed over both HTTP and HTTPS. To force use of HTTPS, make the following change to the file %RDS_HOME%/conf/rdsProperties.xml:
Change
to
That is, change http to https. Now, TEAMS-RDS will always be served over HTTPS.
TEAMS-RDS can be setup to encrypt a PackNGo payload before it is sent to the technician, either via email, or via HTTP sync from PackNGo app.
The payload is encrypted using a key derived from the user’s password (using PBKDF2, or more specifically, PBKDF2WithHmacSHA1). The encrypted file can be decrypted on PackNGo by providing the same password used to encrypt the job.
To enable this feature:
Open “%RDS_HOME%/conf/rdsProperties.xml”, and set the following property value to “true”:
Now, TEAMS-RDS will encrypt the job before sending it to PackNGo.
NOTE:
TEAMS-Designer does not require any firewall ports to be opened.
When TEAMS-RDS runs for the first time under a Windows enviroment, the user may be warned by the firewall software that the installed components are trying to access the computer’s internal loopback interface.
The following table lists the default ports used by TEAMS-RDS services on a Windows operating system.
Service | Ports |
---|---|
Tomcat Web Server | 80 (TCP) |
Microsoft SQL Server | 1434 (TCP) |
MySQL Server | 3306 (TCP) |
TEAMATE Server | 8687 (TCP) |
TEAMS-RT Server | 8787 (TCP) |
Test-Design Server | 8377 (TCP) |
In a Linux environment, the following default ports are utilized by the default TEAMS-RDS installation:
Service | Ports |
---|---|
Tomcat Web Server | 80 (TCP) |
MySQL Server | 3306 (TCP) |
TEAMS-RDS Broker | 7377 (TCP) |
Test-Design Server | 8377 (TCP) |
The following ports require access to the internal loopback interface.
Service / Process | Ports |
---|---|
Tomcat Web Server | 8313 (TCP) |
TEAMATE (.exe) | 8687 (TCP) |
Test-Design Server (tdsrvr.exe) | 8377 (TCP) |