MKS Implementer 2006 Administration Guide

Modifications to Vendor Software: Scenario 9
Overview
Host System Scenarios
This scenario is for users who have modified vendor-supplied software and at the same time
need to receive PTFs and new releases from the vendor. Several types of development
activities exist in this scenario: modifying the application, applying vendor PTFs, and
applying an entire new release from the vendor. You define each of these activities in detail.
Applying a new release for a large application that has been heavily modified can be a very
large project; however, it can be greatly simplified by using MKS NewVersion with
Implementer.
To receive support from the vendor for the original application, all modifications to the
package reside in separate libraries. This allows duplicating any problems using just the basic
application from the vendor to determine if an issue occurred with a custom modification, or
is part of the base application.
For simplicity, this scenario illustrates making the changes directly to the base, although it is
not required. You can keep modified vendor changes in a separate environment.
This scenario is similar to the scenario for Separate Production Modifications, except there
are external changes received from a vendor or from a common development group that you
must periodically incorporate into the application.
This scenario capitalizes on the concurrent development features of Implementer, and the
source merging capabilities of NewVersion.
Development Tasks
There are multiple development tasks for this scenario:
change a vendor-delivered member/object or create a new member/object
apply vendor PTFs
33