02.05.2013 Views

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

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

280<br />

Product Setup and Source Archiving<br />

Products are a component of <strong>Implementer</strong>’s release control feature. Release control allows<br />

you to internally manage your software release process as a fundamental part of your daily<br />

change management operation that includes software versioning at the product, version,<br />

release and environment level. It provides for additional management, control, and<br />

orientation by release name or release number, allowing you to effectively manage<br />

production environments.<br />

With release control you can name each release of software before rolling out to production.<br />

While preparing a release for rollout, you automatically “freeze” the environments that<br />

manage the release to ensure unplanned changes are not subsequently promoted beyond a<br />

user-specified cutoff period. After rollout you can view the release history for that release<br />

and other releases as part of the post-project assessment.<br />

In <strong>Implementer</strong> Menu option 51, Products, you must define each product associated with<br />

<strong>MKS</strong> Source archiving. You have the option to use existing products or create new products.<br />

You then activate <strong>MKS</strong> Source archiving for the product, which automatically creates the<br />

product’s subproject in <strong>MKS</strong> Source. <strong>Implementer</strong>’s Product Maintenance panel allows you<br />

to establish product archiving in <strong>MKS</strong> Source. When the Archived by <strong>MKS</strong> Source field value<br />

is N, field entry is not allowed. To change the value to Y and create the product subproject in<br />

<strong>MKS</strong> Source, you use the function F6=Enable <strong>MKS</strong> Source Archiving.<br />

NOTE For details on release management and deployment, see the <strong>MKS</strong> <strong>Implementer</strong><br />

<strong>2006</strong> Release Management <strong>Guide</strong>.<br />

Requirements and Considerations<br />

Each product corresponds to the product subproject directory in <strong>MKS</strong> Source. For this<br />

reason, the product names you use must conform to a naming convention that is<br />

representable on the file system of the operating system that hosts the server for<br />

<strong>MKS</strong> Source. Generally, the product name must start with a letter A–Z and continue<br />

with a contiguous sequence of letters A–Z, numbers 0–9, or underscores ‘_’. The product<br />

name allows 10 characters consisting of letters and numbers only (no special characters),<br />

for example, ACCTRVCV06 is allowed, ACCTRCV-06 is not allowed. (This requirement<br />

also applies to the names of versions, releases, and environments.)<br />

Multiple products cannot archive the same environment—only one product can archive<br />

an environment in <strong>MKS</strong> Source.<br />

The base product project must exist in <strong>MKS</strong> Source before performing the following task.<br />

To work with products and enable <strong>MKS</strong> Source archiving to create product subprojects<br />

1 From the <strong>Implementer</strong> Menu, type option 51, Products, and press ENTER. The Work with<br />

Products panel displays.

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

Saved successfully!

Ooh no, something went wrong!