MKS Implementer 2006 Administration Guide

Chapter 5: MKS Integrity Integration
202
A separate feature allows you to create and submit promotion requests from within
MKS Integrity, without having to use a separate iSeries session. This functionality is
accomplished through Implementer’s command processing capabilities, as well as the event
trigger functionality of MKS Integrity, and Java scripting.
When the state of an issue changes to a specific user-defined state within the workflow, an
MKS Integrity event trigger runs the JavaScript that establishes a connection to the iSeries
and issues the call to the Implementer Add Issue Objects to Clipboard (IADDCBDISS)
command. The IADDCBDISS command adds to the Implementer Clipboard all objects
locked to a specified issue. Once the objects are successfully copied to the Clipboard, the
Implementer Create Request (ICRTRQS) command automatically creates and submits a
request to promote the objects.
All messaging related to promotion processing occurs on the iSeries. If problems occur with a
promotion, e-mail notification is sent to the MKS Integrity user ID for problem analysis and
resolution. This feature has setup requirements in addition to setting up the basic integration.
For MKS Integrity setup, see page 212. For Implementer setup, see page 242.
Assumptions and Requirements
MKS assumes both Implementer and MKS Integrity are configured and working successfully
independently.
The standard requirements for promotion request processing apply to using this feature. For
example, Implementer validates user authorities to ensure the MKS Integrity user who
invokes the script has the capability to create and submit promotion requests in Implementer;
thus, the MKS Integrity user responsible for issuing requests must be defined to an
Implementer user profile. The Implementer user profile is subject to all standard capability
checks, for example, environment authorities and authority to promote.
Similarly, the rules and requirements applicable to each promotion related feature also apply,
such as related object and related request processing.
CAUTION By not associating the MKS Integrity user to an Implementer user profile,
embedded commands in the script fail.
The Implementer and MKS Integrity integration described in this guide 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 details on installing
Implementer, see the MKS Implementer 2006 Installation Guide.
MKS Integrity 2005 or later. This is assumed installed and configured. However, for the
latest features you must have MKS Integrity 2006 or later installed and configured. For
details, see the MKS Integrity Server 2006 Installation Guide.