What are the integration points between Data Studio Administrator and other Data Studio products?
IBM_Optim 27000269HS Visits (2331)
(Updated on 10/08/2008 to fix typos)
You’ve heard a lot about Data Studio’s integration and shell sharing, but might still be wondering exactly what that means in Data Studio Administrator. As my examples show, Data Studio Administrator integrates with both the design and development phases of the data management lifecycle to provide seamless deployment and change management of:
Both Rational Data Architect and Data Studio Development have sophisticated object management tuned for development environments. However, once changes move beyond design and development environments, it’s time to start thinking in terms of change management. In test and production environments you’ll want to assure data is preserved during extended alters (see my previous blog for more about extended alters) and that dependent objects are left in the proper states after the change.
Rational Data Architect is a comprehensive modeling tool that can be used to integrate and model information changes from a variety of different sources. You can promote object changes from a physical data model created in Rational Data Architect into a Data Studio Administrator deployment script. Then the deployment script can be used to manage dependencies, side effects, and impacts of that change. There’s an excellent developerWorks article article that describes this in detail.
Data Studio Developer provides a complete environment for developing and debugging stored procedures, user-defined functions, and database applications. Changes to application code often precipitate changes to the database schema. The Data Object Editor in Data Studio Developer is optimized for iterative development; that is for quickly making one change at a time. When it comes to promoting changes, Data Studio Administrator makes it easy to aggregate and move multiple changes. Once development is done and you’re ready to move on to test, these changes can be imported into Data Studio Administrator directly from the development database, or from scripts.
The two integration points mentioned above do not require shell sharing. If you only have Data Studio Administrator installed, the data architect could email you the model or you could get the Data Design Project directly out of a source code control system etc. You do not need another product installed on your system to migrate changes from a physical data model. Likewise, you don’t need another product installed to aggregate and promote changes initially created by a Data Studio product.
However, if your job description includes data architecture, database application development and/or database administration, you have the option to install these products as a single application i.e. in the same Eclipse shell. This means a smaller memory footprint, one set of connections, the ability to use one workspace, one set of preferences, and more Data Studio features at your finger tips e.g. modeling, diagramming, debugging, object comparison, XML tools, data and object comparison, change management etc. It’s easy to see the tremendous benefits of shelling sharing.
Please use the comment link below or send an email to firstname.lastname@example.org if you have any feedback on this topic or if you want to hear about other specific topics.