MKS Implementer 2006 Administration Guide

Environment Subprojects in Base Environment Project
Implementer and MKS Source Integration
An environment subproject represents the current state of an Implementer environment.
Environment subprojects are subprojects of the Base Environment project you reference
on the MKS Source Setup panel in Implementer. Implementer automatically creates an
environment subproject when you set a product/version/environment’s Archived by
MKS Source field to Y on the Product Version Environment Maintenance panel.
Permissions for each environment subproject are inherited from the base environment
project.
Environment subprojects allow imports and revision updates only; they do not allow
adds or check in. When you promote a member, it is added or checked in to the product
subproject and then imported to update the revision in the environment subproject.
When you close a release, a function in Implementer allows you to create a checkpoint
for associated production environment subprojects. This allows you to review the
project in its current form at any point by viewing the project history using the
checkpoint.
Within each product and environment subproject, the first level subproject is the source
physical file name, the base name of the file is the item name, and the file extension is the
source member type. For example, member MWI0110, member type RPGLE, in source
physical file QALLSRC appears as /MWI0110.RPGLE in subproject QALLSRC. IFS items are
stored in a subproject named ifs.
Assumptions and Requirements
The Implementer and MKS Source integration requires:
Implementer 2006, which requires an iSeries system running OS/400 V5R1 or later, or
i5/OS V5R3 or later. This is assumed installed and configured. For information on
installing Implementer, see the MKS Implementer 2006 Installation Guide.
MKS Integrity Server 2006 or later, and MKS Source 2006 or later. This is assumed
installed and configured. For information on installing MKS Integrity products, see the
MKS Integrity Server 2006 Installation Guide.
The Implementer Server must be configured and active. For details, see “Configuring the
Implementer Server” on page 217. For information on managing Implementer Server,
see page 223.
TCP/IP connectivity between the iSeries running Implementer and the system running
MKS Integrity Server.
NOTE Using MKS Integrity is optional with the Implementer and MKS Source
integration. If using MKS Integrity, you must have MKS Integrity 2005 or later
installed and configured.
261