Infrastructure for the automation of the assembly of schema maintenance scripts
A method and apparatus to build a migration package. According to one embodiment of the invention, a plurality of programming elements are developed and stored in a configuration repository. The configuration repository also includes metadata used to describe each of the programming elements. Selected programming elements are placed in a set of one or more migration scripts to be stored in the migration package. The set of migration scripts may include a master configuration file and a driver file.
1. A method comprising:
building a migration package, wherein
building the migration package comprises
accessing one or more programming elements, wherein
the one or more programming elements are configured to perform a software migration; and
storing the one or more programming elements in a configuration repository, wherein
the configuration repository comprises metadata,
the metadata describes the one or more programming elements,
the metadata identifies
a migration process type,
a database version of an end-user platform, and
one or more migration steps needed to perform a software migration for the migration process type and the database version.
2. The method of claim 1 , wherein
the one or more migration steps comprise
a SQL migration step, and
a server command line migration step.
3. The method of claim 1 , wherein
the metadata further identifies
the migration process type as one of
version specific, or
not version specific.
4. The method of claim 1 , wherein
the metadata further identifies
a version of application software that is a target of the software migration.
5. The method of claim 4 , wherein
the version of the application software comprises
one of a base application version and a specialized version, wherein
the base application version refers to a released version of the application software, and
the specialized version refers to a vertical upgrade of the application software.
6. The method of claim 1 , wherein
the metadata comprises
information describing a logical order for performing the software migration.
7. The method of claim 1 , further comprising:
organizing a plurality of programming elements in a logical order for performing the software migration, wherein
the plurality of programming elements comprise
the one or more programming elements.
8. The method of claim 7 , wherein
the organizing the plurality of programming elements comprises
grouping one or more phase-associated migration steps out of the one or more migration steps, wherein
the one or more phase-associated migration steps are associated with a migration phase; and
describing the migration phase, wherein
the migration phase is described in the metadata.
9. The method of claim 8 , wherein
the metadata further comprises
a sequence number defining a sequence in which the migration phase is executed in an associated migration script.
10. The method of claim 8 , wherein
the metadata further comprises
an argument string defining a relationship between the migration phase and the one or more phase-associated migration steps.
11. The method of claim 8 , wherein
the metadata further comprises
identification of the one or more phase-associated migration steps.
12. The method of claim 7 , further comprising:
validating the plurality of programming elements, wherein
the validating comprises
determining whether the plurality of programming elements are organized in the logical order.
13. The method of claim 1 , wherein
the accessing comprises one or more of
receiving at least one of the one or more programming elements, or
developing at least one of the one or more programming elements.
14. A computer program product comprising:
a plurality of instructions, comprising
a first set of instructions, executable on a computer system, configured to access one or more programming elements, wherein
the one or more programming elements are configured to perform a software migration; and
a second set of instructions, executable on the computer system, configured to store the one or more programming elements in a configuration repository, wherein
the configuration repository comprises metadata,
the metadata describes the one or more programming elements,
the metadata identifies
a migration process type,
a database version of an end-user platform, and
one or more migration steps needed to perform a software migration for the migration process type and the database version; and
a non-transitory computer-readable storage medium, wherein
the instructions are encoded in the non-transitory computer-readable storage medium.
15. The computer program product of claim 14 , wherein
the one or more migration steps comprise:
a SQL migration step, and
a server command line migration step.
16. The computer program product of claim 14 , wherein
the metadata further identifies
the migration process type as one of
version specific, or
not version specific.
17. The computer program product of claim 14 , wherein
the metadata further identifies
a version of application software that is a target of the software migration.
18. The computer program product of claim 14 , wherein the instructions further comprise:
a third set of instructions, executable on the computer system, configured to
organize a plurality of programming elements in a logical order for performing the software migration, wherein
the plurality of programming elements comprise the one or more programming elements.
19. The computer program product of claim 18 , wherein the instructions further comprise:
a fourth set of instructions, executable on the computer system, configured to
validate the plurality of programming elements, wherein
the validating comprises
determining whether the plurality of programming elements are organized in the logical order.
20. A system comprising:
one or more processors,
migration configuration logic, wherein
the migration configuration logic configured to
access one or more programming elements, wherein
the one or more programming elements are configured to perform a software migration,
store the one or more programming elements in a configuration repository, and
the migration configuration logic is further configured to be executed using the one or more processors; and
the configuration repository, wherein
the configuration repository comprises metadata,
the metadata describes the one or more programming elements,
the metadata identifies
a migration process type,
a database version of an end-user platform, and
one or more migration steps needed to perform a software migration for the migration process type and the database version.