MKS Implementer 2006 Administration Guide

Chapter 3: Implementer Administration
Users
72
Add related objects
from path
System Control Maintenance Field Descriptions: Panel 3
Field Description
For requests that target a *QAC environment, specify whether to
automatically add related objects that exist in environments higher on the
promotion path. Allows you to recompile related objects that exist in
production without creating locks for the objects.
Y: Searches the current promotion path to locate related objects not in
the target *QAC environment or on the current promotion request.
Related objects are added to the request and recompiled in the QA
environment (locks are not created for these objects). Requires the
production environment’s Add related objects to rqs field set to Y. For
details, see page 86.
N: Does not search forward on the path to locate related objects. This
is the default value.
Domino server URL For Lotus Domino integration and database signing, specify the Lotus
Domino server URL that Implementer uses when invoking actions that
can only be performed within Domino. Must be a valid URL notation that
includes subdirectories required to find the Implementer utility database,
for example, http://servername.domain:port/subdir.
For details on setting up Domino, see “Lotus Domino Integration” on
page 336.
Default SMTP Server For notifying users of promotion request status through e-mail sent as
request special command. Specify the default SMTP server used by the
ISNDMAIL command. The value must be an IP address or host name,
for example, 127.1.1.1 or localhost. Requires Java 1.3 or later
installed on your iSeries.
Requires the Send eMail Message (ISNDMAIL) command set up as an
Implementer special command. For details, see the MKS Implementer
2006 User Guide.
This task allows you to enroll OS/400 user profiles into Implementer. You must enroll each
user of Implementer before they can access and use the features. When enrolling a user, you
also define the Implementer user authorities that control the features and functions the user
is allowed to perform. For a table of suggested field values for the different roles each type of
user performs, see “Typical Values for Different User Roles” on page 78.
You can enroll users individually or under a group profile. Perform this task during the
initial setup of Implementer or any time after installation when you need to add, change, or
delete a user profile.
NOTE Some user profile fields, as noted, apply to using Implementer with
MKS Integrity for issue tracking. For details, see “User Profile Setup” on page 235.