ConfigLab versus Bundling versus Blueprint
By ACShorten on Oct 20, 2009
One of the most common questions I get asked by implementations is around the utilities available for moving data from environment to environment. This confusion is that with the Oracle Utilities Application Framework based products there are a number of tools provided that can be used to transfer data from one environment to another.
There are three main tools that implementations use:
- ConfigLab - A configurable copy facility is metadata aware and therefore understands the relationships between objects and by invoking the relevant maintenance objects validates the data copied. This utility uses the object validation to help ensure data integrity. Basically it is a set of configuration tables and a set of batch jobs to perform the mingration of data.
- Bundling - A configrable release management ool that allows exporting of Advanced Configuration Environment based objects (business services, business objects, UI Maps etc) from one environment to another.
- Blueprint - A Oracle Utilities Software Development Kit (SDK) based tool to import metadata from the development environment to your initial testing environment. The utility is command line based and basically uses a text based configuration file to drive the utility on the source and target sides.
I am asked which one I recommend for data migration. I believe each tool has a role in an implementation but you must be careful to use the right tool for the right job within an implementation. So here is my advice:
- Only use the Blueprint tool for migrating data from your development platform to your initial test environment. The blueprint tool is not designed to move large amounts of data and certainly is risky, if not used correctly, and can potentially break the integrity of your data. The SDK provides the configuration data that it is used for (mainly meta-data). This should not be extended as, while it can perform data migration on any data, it is not efficient and risky for certain types of configuration data.
- Only use Bundling on Maintenance Objects that are authorized for Bundling. There is an indicator on the Maintenance Object definition that decides whether it is "Eligible for Bundling". Bundling has been designed to migrate Advanced Configuration Environment based data and allow third parties to ship Advanced Configuration Environment based solutions to customers in a XML format.
- Use ConfigLab to migrate data from environment to environment. It has been designed with this in mind. It checks that any migration is valid before it applies the change to the target environment. This basically assists in maintaining data integrity. It also allows for Approval and Rejection of individual changes and even has an inbuilt audit trail for afurther analysis of changes. All important considerations for migrating complex data with complex relationships.
When working with data it is not only important that data arrives but that its arrival does not jeopardize data integrity. While the other tools are suitable for the task, ConfigLab is the only one of the tools designed with this in mind.