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.

Converting From DesignTracker to <strong>MKS</strong> Integrity<br />

6 To proceed with the conversion, in the Reply field type G, and press ENTER to perform<br />

the conversion.<br />

To cancel the conversion and return to the <strong>MKS</strong> Integrity Setup panel either: type N in<br />

the Reply field, and press ENTER, press F3=Exit, or F12=Cancel.<br />

After pressing ENTER to continue, the following message displays at the bottom of the<br />

<strong>MKS</strong> Integrity Setup panel: “Successful conversion to <strong>MKS</strong> Integrity.”<br />

The system conversion from DesignTracker to <strong>MKS</strong> Integrity is complete. You are ready to<br />

begin using the new features, as described in the <strong>MKS</strong> <strong>Implementer</strong> <strong>2006</strong> User <strong>Guide</strong>.<br />

Converting With Data Retention<br />

For <strong>MKS</strong> customers that currently use DesignTracker for issue management, the tasks<br />

described in this section perform a conversion that allows you to convert issue management<br />

systems—that is, switch from using DesignTracker to using <strong>MKS</strong> Integrity, and retain<br />

existing DesignTracker data. This conversion method enables the <strong>Implementer</strong> feature<br />

co-existence, which is required when converting DesignTracker data to <strong>MKS</strong> Integrity.<br />

The purpose of co-existence is twofold: It avoids application downtime during the<br />

application conversion project by allowing you to simultaneously use both <strong>MKS</strong> Integrity<br />

and DesignTracker, and it allows you to convert DesignTracker DRs, SRs, and related entity<br />

information to <strong>MKS</strong> Integrity issues using the Convert DT to <strong>MKS</strong> Integrity (ICVTDT)<br />

command. By design, it allows some users to use <strong>MKS</strong> Integrity issues without requiring all<br />

users to switch at the same time. This allows for a gradual transition of development teams<br />

when multiple teams share the same <strong>Implementer</strong> installation.<br />

NOTE For details on the ICVTDT command, see “Converting DesignTracker Data to<br />

<strong>MKS</strong> Integrity” on page 431.<br />

Converting to <strong>MKS</strong> Integrity when you need to retain and convert existing data can be an<br />

involved undertaking simply due to the inherent complexities associated with performing<br />

data conversions. For example, a typical data conversion requires mapping existing files and<br />

fields to new values in the new database. Detailed information on performing a data<br />

conversion begins on page 431.<br />

TIP <strong>MKS</strong> can assist with converting your DesignTracker data to <strong>MKS</strong> Integrity, as<br />

well as assist in defining your business processes and workflow for <strong>MKS</strong> Integrity.<br />

For details, contact <strong>MKS</strong> Customer Care.<br />

Before you perform the actual data conversion, however, you need to determine how the<br />

data conversion will occur. In other words, will you perform a one-time conversion of all<br />

applicable data and users, or will you perform a gradual conversion on subsets of data and<br />

users?<br />

247

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

Saved successfully!

Ooh no, something went wrong!