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 2: Understanding <strong>Implementer</strong><br />

36<br />

4 Merge the source members and analyze the results. In NewVersion, use the “Create<br />

Target Source” function to create the new source members. Use the “Merge Reports”<br />

function to verify correct results and resolve object differences.<br />

5 Compile the new source members. In NewVersion, use the “Create Objects” function to<br />

compile the new source members.<br />

6 Test the changes. Use a library list that has the NewVersion target library at the top, with<br />

libraries containing the unmodified version of the objects below it.<br />

7 Promote to the custom modifications environment. The promotion request promotes<br />

from the NewVersion Target library to the custom modification environment. This<br />

promotion request can require resolving conflicts caused by the concurrent<br />

development. For details on concurrent development, see “Concurrent Development:<br />

Scenario 4” on page 21.<br />

Setup Tasks<br />

The setup tasks required for this scenario are as follows:<br />

1 Create an Environment task. Define the following custom Mods environments for this<br />

scenario:<br />

Custom Mods Production, define a production environment. Related environments<br />

set up with modified production above the base production environment allow<br />

automatic selection of the correct version in check out. If all files reside in a single<br />

library, that library is defined as the file library for this environment, as well as for<br />

the vendor base production environment.<br />

Mods Development, define a development environment.<br />

Mods Quality Assurance, define a quality assurance environment.<br />

Define the following Vendor environments for this scenario:<br />

Vendor Base Production, define a production environment. If all files are in a single<br />

library, define that library as the file library for this environment, as well as for the<br />

modified production environment.<br />

Vendor PTF Development, define a development environment.<br />

Vendor Quality Assurance, define a quality assurance environment.<br />

2 Create a User Profile task. The same group of developers and testers are commonly<br />

responsible for custom changes, as well as applying vendor PTFs and new releases.<br />

Developer checks out members/objects, performs development, creates a promotion<br />

request targeting quality assurance, and is allowed to perform concurrent<br />

development. The developer compiles the promotion request in the work library.

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

Saved successfully!

Ooh no, something went wrong!