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.
