Before using this information and the product it supports, read the information in Notices.
This edition applies to Version 1.2 of IBM Data Studio Administrator (product number 5724-V14) and to all subsequent releases and modifications until otherwise indicated in new editions.
IBM(R) Data Studio Administrator can be installed on Linux(R) and Windows(R) systems.
The installation process includes:
After you have installed Data Studio Administrator, you can customize your user preferences at any time.
The prerequisites for installing Data Studio Administrator include both hardware and software requirements.
Before you install Data Studio Administrator, verify that your system meets the minimum hardware requirements:
The following operating systems are supported for this product:
Data Studio Administrator has the following software requirements on the server platform:
Either product must be installed if you want to unload data by using DB2 High Performance Unload (DB2 HPU) unload commands.
Data Studio Administrator has the following software requirements on the client platform:
The Data Studio Administrator installation program requires IBM Installation Manager. The installation program prompts you to install IBM Installation Manager if it is not already installed.
You must ensure that the DB2 libraries are in the PATH environment variable (Windows) or in the LD_LIBRARY_PATH environment variable (UNIX).
To run Data Studio Administrator, you must use the IBM Java Database Connectivity (JDBC) Type 4 driver. The JDBC Type 4 driver is included in Data Studio Administrator. You can select a different JDBC driver if necessary.
On Linux, if the class location of your JDBC driver (db2jcc.jar and license) is not automatically populated, check your environment. The DB2INSTANCE environment variable should be set to the local DB2 instance name, for example, export DB2INSTANCE=db2inst1 (this is case sensitive). Otherwise, you can specify the location manually.
To run Data Studio Administrator, you must also have connectivity to the DB2 UDB Administration Client (DAC) that is running on the same machine as the database. You need a connection to the DAC to communicate with the IBM Data Server Client. The IBM Data Server Client connectivity libraries can be provided by either of the following ways:
In either case, make sure the bin directory is in the path before you start Data Studio Administrator. (In Linux, this is handled by sourcing $INST_HOME/sqllib/db2profile.) The DB2 UDB Administration Client is available from developerWorks(R) at http://www.ibm.com/developerworks.
For example, to install the IBM Data Server Client on a Linux system, complete the following steps:
Data Studio Administrator can be installed in the same Eclipse integrated development environment (IDE) with other products that are also based on Eclipse so that all of the features of the installed products are available in the same user interface.
During the installation process, you must specify a package group for the Data Studio Administrator package. A package group represents a directory in which packages share resources with other packages in the same group. When you install the Data Studio Administrator package with IBM Installation Manager, you can create a new package group or install the packages into an existing package group.
If you have products on your computer that were previously installed with IBM Installation Manager, sharing a package group is the method that you use to enable shared installations.
You can install Data Studio Administrator into an existing package group only if the product and version in the existing package group is compatible with Data Studio Administrator. In most cases, if the existing product is not compatible, you will see an error and the shared installation will fail. However, in some cases IBM Installation Manager will not block the shared installation of incompatible products, which can cause unpredictable installation results. These products have been tested as being compatible for a shared installation with Data Studio Administrator:
Data Studio Administrator Version 1.2 was developed for use with the Eclipse integrated development environment (IDE) 3.2.2, using JDK 1.5. The Data Studio Administrator installation package includes this level of Eclipse.
If you have installed other Eclipse 3.2.2 based products using a mechanism other than IBM Installation Manager, you can attempt to install Data Studio Administrator into the same Eclipse IDE, using the Extend an existing Eclipse IDE option in IBM Installation Manager. However, be aware that this type of installation will fail if the Eclipse environment is not compatible with Data Studio Administrator Version 1.2. IBM Installation Manager checks that the Eclipse instance that you specify meets the requirements for installing Data Studio Administrator, and the installation will not proceed if the requirements are not met.
You can install Data Studio Administrator on a Windows system or on a Linux system.
The Data Studio Administrator installation program requires IBM Installation Manager. If the installation program cannot find IBM Installation Manager, it prompts you to install IBM Installation Manager, which is included with the installation program.
When you install Data Studio Administrator, you have the option of:
Using a new Eclipse installation is recommended if you are a new user of Data Studio Administrator because it is the simplest and easiest way to install Data Studio Administrator.
When you install products into the same package group, they use shared Eclipse resources and all of the features of the products that you have installed are available in the same user interface. For more information, see Compatibility with other products.
Extending an existing Eclipse installation is recommended only if you have a complete understanding of your environment and requirements. For more information, see Eclipse and JDK requirements.
You can install Data Studio Administrator on a Windows system.
To install Data Studio Administrator on a Windows system, complete the following steps:
If you are installing from a DVD, place the DVD into the DVD-ROM device. The Launchpad program starts automatically if the drive is set for autoplay. If the Launchpad program does not start automatically, use File Manager or Windows Explorer to locate your DVD-ROM drive, and double-click the setup.exe file.
If you are installing from a downloaded package, complete the following steps:
The Welcome panel of the Launchpad program is displayed.
You will be prompted to specify a location for the shared resources if you have not used IBM Installation Manager to install other products. The shared resources are the common set of Eclipse plug-ins that other products that are based on Eclipse, such as Rational Data Architect or Rational Software Architect, can use. The name of the folder must not exceed 80 characters.
If you install Data Studio Administrator into an existing Eclipse installation, the installation directory that you specified on the Location page is ignored because the location will default to the existing Eclipse directory.
You are now ready to start Data Studio Administrator.
You can install Data Studio Administrator on a Linux for xSeries(R) system.
To install Data Studio Administrator on a Linux system, complete the following steps:
You will be prompted to specify a location for the shared resources if you have not used IBM Installation Manager to install other products. The shared resources are the common set of Eclipse plug-ins that other products that are based on Eclipse, such as Rational Data Architect or Rational Software Architect, can use. The name of the folder must not exceed 1024 characters.
Workspace in use, choose a different one.You must click OK and return to the dialog box to specify a valid workspace.
You can install Data Studio Administrator silently using either IBM Installation Manager in silent installation mode or using the IBM Installation Manager installer. When you run IBM Installation Manager in silent mode, the user interface is not available; instead, a response file inputs the commands that are required to install the product package.
For information on how to install silently, see the Installing silently section in the IBM Installation Manager Information Center.
A response file is an XML-based file that is used to specify predefined information such as silent installation preferences, repository locations, installation profiles, and so on. The following figure shows a sample response file for installing Data Studio Administrator:
<?xml version="1.0" encoding="UTF-8"?> <agent-input> <server> <repository location='C:\Documents and Settings\Administrator\Local Settings\Temp\installerRepository30467.tmp'/> <repository location='C:\dsAdmin12\output\dsadm12_20080423_1536_win\disk1\InstallerImage_win32'/> <repository location='C:\dsAdmin12\output\dsadm12_20080423_1536_win\disk1'/> </server> <profile kind='self' installLocation='C:\Program Files\IBM\Installation Manager\eclipse' id='IBM Installation Manager'> <data key='eclipseLocation' value='C:\Program Files\IBM\Installation Manager\eclipse'/> <data key='cic.selector.nl' value='ja,es,ru,en,fr,zh_TW,pl,de,cs,zh_HK,ko,hu,pt_BR,it,da,zh'/> </profile> <install modify='false'> <offering profile='IBM Installation Manager' version='1.1.1000.20080317_1735' features='agent_core,agent_jre' id='com.ibm.cic.agent'/> <offering profile='IBM Data Studio' version='1.2.0.20080423_1537' features='core' id='com.ibm.datastudio.administrator'/> </install> <profile installLocation='C:\Program Files\IBM\DSADM1.2' id='IBM Data Studio'> <data key='eclipseLocation' value='C:\Program Files\IBM\DSADM1.2'/> <data key='cic.selector.nl' value='ja,zh_HK,es,en,fr,zh_TW,ko,pt_BR,it,zh,de'/> </profile> <preference value='C:\Program Files\IBM\DS12Shared' name='com.ibm.cic.common.core.preferences.eclipseCache'/> <preference value='30' name='com.ibm.cic.common.core.preferences.connectTimeout'/> <preference value='30' name='com.ibm.cic.common.core.preferences.readTimeout'/> <preference value='0' name='com.ibm.cic.common.core.preferences.downloadAutoRetryCount'/> <preference value='true' name='offering.service.repositories.areUsed'/> <preference value='false' name='com.ibm.cic.common.core.preferences.ssl.nonsecureMode'/> <preference value='true' name='com.ibm.cic.common.core.preferences.preserveDownloadedArtifacts'/> <preference value='false' name='PassportAdvantageIsEnabled'/> </agent-input>
The ability to run Data Studio Administrator verifies that it was installed correctly.
To verify that you successfully installed Data Studio Administrator, complete the following steps:
To start Data Studio Administrator on a Windows system, click Start -> Programs -> Data Studio Administrator.
To start Data Studio Administrator on a Linux system, enter the command: dsadm.sh
Data Studio Administrator is installed with a 30-day trial license key. When you purchase Data Studio Administrator, a product activation kit is provided, which is used to install the permanent license key. You need to use IBM Installation Manager to install the permanent license key.
If you ordered physical media, the product activation kit is on a CD in the product shipment. Alternatively, you can obtain a product activation kit by downloading it from your Passport Advantage (PA) or Passport Advantage Express (PAX) account. The kit will show up in your PA or PAX account that offers the v1.2 product download itself.
To install the permanent license key, complete the following steps:
For more information on how to manage your licenses by using IBM Installation Manager, see the Managing licenses section in the IBM Installation Manager Information Center.
You can uninstall Data Studio Administrator from your Windows or Linux system.
You can uninstall Data Studio Administrator from a Windows system.
To uninstall Data Studio Administrator, complete the following steps:
You can uninstall Data Studio Administrator from a Linux system.
To uninstall Data Studio Administrator from a Linux system, complete the following steps while logged on as the root user:
You can migrate the data design projects that you created with DB2 Change Management Expert to Data Studio Administrator.
To migrate your data design projects from DB2 Change Management Expert to Data Studio Administrator, complete the following steps:
You can change the default options for some Data Studio Administrator functionality. Specifically, you can set preferences for working with SQL scripts, working with the Data Model Editor, and viewing reports.
You can change your preferences any time after you install and start using Data Studio Administrator. You can also reset the preferences to the default Data Studio Administrator settings.
You can change preferences for how Data Studio Administrator processes SQL scripts.
To change your preference settings for SQL scripts, complete the following steps:
Item | Description |
---|---|
Select an SQL termination character | Sets the character that will be used as the termination character for SQL statements. |
Maximum parser errors for diagnosis | Sets the maximum number of parser errors that are reported when an SQL script file is opened. The value must be an integer that is greater than 0. When SQL script files are large, it can be helpful to limit the number of errors that are diagnosed. |
Maximum parser time for diagnosis | Sets the maximum amount of time for finding errors to report when an SQL script file is opened. The value must be an integer that is greater than 0. When SQL script files are large, it can be helpful to limit the time that is spent diagnosing errors. |
Default DB2 product Default DB2 version |
Sets the level of syntax that is used to parse SQL script files. The Default DB2 product field determines the DB2 product, and the Default DB2 version field determines which version and release of that product. Although DB2 for Linux, UNIX, or Windows is the only product that you can specify, you can specify which version and release to use. |
Ignore semantic errors when reverse engineering | Specifies that semantic errors will be ignored when the models are created from SQL scripts. |
Ignore semantic errors when applying DDL to models | Specifies that semantic errors will be ignored when changing models with SQL scripts. If you choose to ignore errors, you can later validate a model to find problems. |
Default objects used in reverse engineering | When you create SQL scripts from models, specifies the default values that will be used for the statements for implicitly created objects. You can specify values for the partition group, the temporary partition group, the buffer pool, and the table space. |
Forward engineering options | Unchecking the Order the create statements for derived objects option might leave create statements for derived objects such as views, aliases and materialized query tables in the wrong order. If you uncheck this option, remember to inspect the generated change commands to make sure that each derived object is created before it is used by another derived object. |
You can change preferences for the validation options, appearance of the breadcrumb trail, and appearance of the Relationships section in the Data Model Editor.
To change your preference settings for the Data Model Editor, complete the following steps:
Item | Preference | Description |
---|---|---|
Validation Options | On Save | Validate the model when it is saved. |
On Change | Validate the model when it is changed. | |
Disable | Prohibit validation of models. | |
Bread Crumb Trail | Show the bread crumb | Show the path to the current edit object. |
Show the title in the bread crumb | Show the title of the current edit object at the end the breadcrumb trail instead of separately above the breadcrumb trail. | |
Annotate the title | When the title is shown above the breadcrumb trail, show stereotype text and expanded information in the title. For example, the title will include the object type and the name of the model to which the object belongs. | |
Related Objects | Show the relationships | Show the Relationships and Dependents section, which shows the objects, by category, that are related to the current edit object. |
Show the decorators | Show data type and length information in labels. | |
Show the empty relationships | Show all the categories in the relationships section, including those that are empty. | |
Show the parent relationships | Show the parent relationships to the current edit object. |
To access model validation options in general, select Model Validation -> Constraints.
You can change your preferences for viewing the Summary of Changes Report. By default, the generated report is always displayed when you generate change commands.
To change your preference for viewing the Summary of Changes Report, complete the following steps:
(C) Copyright IBM Corporation 2005, 2008. All rights reserved.
Note to U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:
The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:
Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.
The licensed program described in this Documentation and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both:
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Linux is a trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft(R) and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Other company, product or service names, may be trademarks or service marks of others.