02.05.2013 Views

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 5: <strong>MKS</strong> Integrity Integration<br />

204<br />

This assessment involves no direct interaction with the software. Instead, you need to spend<br />

some time evaluating the product development process currently followed in your<br />

organization and map it so you can customize your <strong>MKS</strong> Integrity project to suit your needs.<br />

This may take longer for some than for others. But the purpose of the assessment is to avoid<br />

the time-consuming task of redesigning a project that was not well-planned in the first place.<br />

When undertaking this assessment, you should focus on these areas:<br />

your workflow and project state transitions<br />

your current tracking mechanism<br />

the scope of implementation within your organization<br />

the relevant teams and user groups<br />

Once the assessment is complete, you can proceed to customizing your installation and refer<br />

to this assessment when setting up <strong>MKS</strong> Integrity. To set up <strong>MKS</strong> Integrity, you need to<br />

define users, groups, projects, states, types, and fields, as well as set up e-mail notification.<br />

For details on assessing your current product development process or setting up<br />

<strong>MKS</strong> Integrity, see the <strong>MKS</strong> Integrity Server <strong>2006</strong> <strong>Administration</strong> <strong>Guide</strong>.<br />

NOTE Administrative functions such as users, groups, projects, states, types, fields,<br />

and triggers are accessible only from the <strong>MKS</strong> Integrity <strong>Administration</strong> Client<br />

graphical user interface (not from the Web interface).<br />

When you have completed setting up <strong>MKS</strong> Integrity, refer to the following sections for<br />

information specific to setting up <strong>MKS</strong> Integrity for integration with <strong>Implementer</strong>:<br />

“Configure the <strong>MKS</strong> Integrity Server for <strong>Implementer</strong> Server” on page 204.<br />

“Manage States and State-based Capabilities” on page 208.<br />

(Optional) “Enable Promotions From <strong>MKS</strong> Integrity” on page 212.<br />

For a checklist of the tasks required to configure the <strong>Implementer</strong> and <strong>MKS</strong> Integrity<br />

integration, see “<strong>MKS</strong> Integrity Integration Setup: Task Checklist” on page 295.<br />

Configure the <strong>MKS</strong> Integrity Server for <strong>Implementer</strong> Server<br />

The tasks associated with configuring the <strong>MKS</strong> Integrity Server for the <strong>Implementer</strong> Server<br />

include the following:<br />

configure security ACLs (based on your version of <strong>MKS</strong> Integrity Server)<br />

set change package authorities<br />

modify the <strong>MKS</strong> Integrity Server configuration file IntegrityClientSite.rc<br />

The <strong>MKS</strong> Integrity administrator who has knowledge of working with the <strong>MKS</strong> Integrity<br />

administration functions typically performs these tasks.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!