MKS Implementer 2006 Administration Guide

Communications Options
2 Configure Implementer to use MKS Integrity for issue tracking. For details, see
“Implementer and MKS Integrity Integration” on page 196.
3 (Optional) Configure Implementer to use MKS Source archiving. For details, see
“Implementer and MKS Source Integration” on page 259.
Communications Options
Implementer provides three options for communications entries between host and remote
systems:
Use existing communication entries. This is the recommended method, and no
additional set up is required.
Add communication entries to a generic mode description. Using a generic
communications entry provides some additional control over your communication, and
must be specifically set up.
Add communication entries to a specific mode description. You can create an
Implementer-specific mode description that reserves the communication sessions
exclusively for Implementer use. This ensures a session is available to Implementer
when it attempts to communicate with the remote system (unless the maximum
numbers of sessions for the mode are already in use by other Implementer jobs). This
option provides the greatest control over your communications. It requires setup on both
the host and remote systems.
For details on this topic, see “Setting Up Communications Entries” on page 169.
Distribution Methods
Implementer supports software distribution on tape and DVD, as well as the following
distribution methods:
SDMCom. Distributions using Implementer’s own object distribution facility, SDMCom,
provides between 20–35 percent better performance over SNADS distribution. Its
advanced features use compression algorithms and blocking specifically for remote
distributions.
TCP/IP (FTP or tape). Requires additional setup as described in “Setting Up for TCP/IP
Distribution” on page 173.
SNADS. Requires additional setup as described in “Setting Up for SNADS Distribution”
on page 179.
For details on this topic, see “Distribution Methods” on page 164.
61