MKS Implementer 2006 Administration Guide

Chapter 5: MKS Integrity Integration
264
Creating the Integration User
You have the option to create a specific integration user, or designate an existing MKS Source
user profile as the integration user. If you currently use MKS Integrity with Implementer,
you probably already have a designated profile.
TIP To identify your existing MKS Integrity integration user, from the Implementer
Menu select option 47, MKS Integrity Setup, to view the MKS Integrity User ID field
value.
Because of certain authorities the integration user must have, the integration user should be a
user that does not usually sign on to the system or use the product. The primary functions of
the integration user are:
connect to the MKS Integrity Server from the Implementer Server
execute certain commands that a typical user does not have authority to perform
impersonate users to perform work on behalf of the impersonated user
The integration user requires setup in MKS Source and Implementer. In a later task when you
configure Implementer for the integration, you specify this user ID in the MKS Source User ID
field on the MKS Source Setup panel. For details, see “Defining MKS Source Values in
Implementer” on page 275.
Information on setting permissions for the integration user begins on page 268. For details on
creating users in MKS Integrity, see the MKS Integrity Server 2006 Administration Guide.
Creating the Implementer Developer Group
MKS recommends you create a group and add the iSeries users to the group, for example,
implementer developer group is used throughout this documentation. This allows you to
set ACLs and permissions for the group rather than for each individual user. If you use
MKS Integrity with Implementer and you are using the same server for MKS Source
integration, the group profile may already exist.
IMPORTANT During a remote initiated move that updates the host, Implementer uses
the profile MWIPROD to update the host. If you use remote initiated moves with
host updates (remote environment defined with the Remote initiated move and
Updates host fields set to Y) for promotions with MKS Source integration, the
MWIPROD user profile must have an MKS Integrity user ID that is part of the
group to work with MKS Source.
Information on setting permissions for the Implementer Developer group or users begins on
page 268. For details on creating groups or users, see the MKS Integrity Server 2006
Administration Guide.