MKS Implementer 2006 Administration Guide

Chapter 5: MKS Integrity Integration
Export to Implementer
296
Step
Number
Task Description
MKS Source Integration Setup: Task Checklist
1 Modify the MKS Integrity Server configuration file on page 206.
2 Define Implementer state-based capabilities if using MKS Integrity with
MKS Source and Implementer on page 208.
3 Create base projects in MKS Source on page 263.
4 Create the integration user on page 264.
5 Create the Implementer Developer group on page 264.
6 Set MKS Source policies on page 265.
7 Create and set an MKS Integrity ACL and permission on page 267.
8 Create and set MKS Source ACLs and permissions on page 268.
9 Define MKS Source values in Implementer on page 275.
10 Define or modify object codes for archiving in MKS Source on page 278.
11 Product setup and source archiving on page 280.
12 Product version setup and development paths on page 283.
13 Product/version environment setup and environment population on
page 286.
14 Product/version/release setup and checkpoint in MKS Source on page 291.
Check
Complete
The Implementer and MKS Source integration provides Export to Implementer, a Java
application that runs on Windows. The export function allows you to check out and
optionally deploy PC-based software changes, initiated by an MKS Integrity issue and
modified under MKS Source control, to an IFS location under Implementer change
management control on the iSeries.
The export runs using DTBridge, a client application delivered with Implementer. When
activated, the export retrieves a list of MKS Integrity issues for a single or group of issues
based upon the entry of either an issue number or a build number. The bi-directional updates
occur automatically and include the creation of an Implementer change package for each
selected issue. The status of the change packages reflect the current development progress
within Implementer.