Glad you asked. Below you will find a table of product versions. Each product version will have a link to the Third Party Library Report. The report will contain all third party libraries used and their versions.

Direct Synchronization via VPN

Typical Scenario: whenever the service agent logs onto the corporate network, a sync is initiated.

•  Requires direct web access to TEAMS-RDS.
• • Laptop has to be carried in and out of customer site.
• Models and logs are transferred using web-services (XML over HTTP).
• Requires TEAMATE users to authenticate to TEAMS-RDS.
• Secure communication (HTTPS)  can be be used.

Synchronization via Proxy or Portal

Typical scenario: Controlled/Monitored access from customer site.

• HTTP(S) or FTP server at customer site.
  • Provides transparency to customer IT.
• TEAMS-RDS uploads model files (XML) to the web-server.
• TEAMATE downloads models from the web-server.
• TEAMATE uploads log files (XML) to the web-server.
• TEAMS-RDS reads log files from the web-server.

Offline Synchronization

Typical scenario: When TEAMATE does not have direct access to TEAMS-RDS.

• TEAMS-RDS saves model files to a “Repository”.
• TEAMATE saves log files to a “Repository”.
• Synchronization methods:
  • Repositories kept in sync using third-party sync software.
  • Repository moved using ad-hoc methods.
  • Removable media like USB stick or CD-Rs can also be used.

Synchronization of TEAMATE logs with Email

Typical scenario: When TEAMATE does not have direct access to TEAMS-RDS.

• Used for pushing TEAMATE logs to TEAMS-RDS.
• Logs sent as email attachment to a “dedicated” email address.
• TEAMS-RDS continually monitors this “dedicated” email address.
• Whenever a new email arrives, TEAMS-RDS extracts the attachment from the email, and processed the log attachment.
• Once the log is successfully processed by TEAMS-RDS, the email is deleted.

If TEAMS-RDS is to be served over HTTPS, then there are two steps required.

Configure the web-server for SSL

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.

Configure TEAMS-RDS

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:

1. Only jobs that are emailed by a users to himself/herself, and jobs that are sync’d by PackNGo app (via HTTP sync) are encrypted.
2. Jobs sent via email by the supervisor to a technician are not encrypted.
3. PackNGo session logs sent to TEAMS-RDS, via email or through HTTP sync, are not encrypted.
4. If the technician changes his/her password, TEAMS-RDS will use the updated password to encrypt new PackNGo jobs. However, jobs that are still open and were sent before the technician changed his/her password, will require the old password for decryption.

TEAMS-Designer

TEAMS-Designer does not require any firewall ports to be opened.

TEAMS-RDS Server

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.

In a Linux environment, the following default ports are utilized by the default TEAMS-RDS installation:

TEAMATE

The following ports require access to the internal loopback interface.