Migrate
Assistant
The Migrate Assistant
is designed to simplify and automate CA Gen object migration. Integrated
enabling object checking reduces the chance of failed migrates whilst integrated
task management enables easy to use overnight batch processing of the migrates.
The Migrate Assistant is
available for both the host and client/server encyclopaedias. It is designed
to be used as a complementary tool to GuardIEn. Whereas GuardIEn controlled
migrations are designed to manage object migrates as part of a disciplined and
managed development life-cycle, the Migrate Assistant is especially useful for
more ad-hoc, on-demand migrates.
Easier...
- The Migrate is defined
using a simple Graphical User Interface client. Multiple models can be targeted
with a simple click of the mouse.
- There are a variety of
tools to help scope objects into the migrate, for example a fast object list
with full wild card selection, selection based on associations to other objects
and copying from a 'when changed' list.
- The selection tools are
common to GuardIEn and all of the Assist products, thus making it easier to
learn and use.
- The Migrate Assistant
automatically schedules an Assist task (on the HE and CSE) or batch job (on
the HE) to accomplish the migrate.
- Helps determine that
a migrate was successful by checking the encyclopaedia after the migration
job has completed and reporting on any failures.
- Multiple models can be
scoped into a single migration definition, for example, a new common action
block or entity type could be distributed from a shared objects model to multiple
development models by a single Migrate Assistant task.
- Automates cross encyclopaedia
migration for the client/server encyclopaedia.
- A specification migrate
capability has been included to support CBD projects. This will automate the
process of migrating an 'implementation' action block to a 'specification'
or 'catalog' model, automatically removing the action block statements and
local/entity action views. This removes the need to manually download the
implementation action block from a temporary model to convert it into a specification.
Reliable...
- Integrated enabling object
and subset protection checking reduce the number of failed migrates due to
missing or checked-out objects.
- Missing enabling objects
are automatically added and a report is produced detailing the objects that
have been included in the migration.
- Migrations can be submitted
for overnight execution because of the higher confidence that the migration
will succeed, thus reducing prime-time contention on the encyclopaedia.