IBM Optim Development Studio, Version 2.2.1.1

Installation Guide

Installing IBM Optim Development Studio

Installation roadmap for IBM Optim Development Studio

This roadmap describes a typical installation using the Installation Manager Install wizard. If you are installing the product silently, see the Silent installation road maps.

Roadmap for installing the product package

Perform these tasks to install the product:

1. Verify that your computer and user ID meet the minimum requirements for installing the product.
2. Review the rest of the planning information .
3. Complete any necessary pre-installation tasks.
4. Install the product using the Installation Manager Install wizard.
5. Perform any necessary post-installation tasks, such as configuring the appropriate product license.

Silent installation road maps

There are two main road maps for performing a silent installation.

1. Use Installation Manager to silently install software packages:
   1. Install Installation Manager using the Installation Manager installer.
   2. Record a response file using Installation Manager, or Create a response file manually, .
   3. Run the Installation Manager in silent mode to perform the operation silently.
2. Use the Installation Manager installer to silently install software packages:
   1. Create a response file manually that includes commands to install Installation Manager and other packages.
   2. Run the Installation Manager installer with the response file.

Installation introduction

Installation terminology

These terms are used in the installation topics.

Admin user

A user who has write administrative privileges. In the context of installing, having write administrative privileges means that the user can write to the default common installation location. On Linux operating systems, this is the "root" or any user who is using "sudo" to start Installation Manager. On a Microsoft Windows XP operating system, a user with write administrative privileges is any user who is a member of the "Administrators" group. On a Microsoft Windows Vista operating system, this is the user who is using "Run As Administrator" to start Installation Manager.

Extension

A type of product package that provides additional function to another product package. You cannot install the extension without also installing the package that it extends.

Installation directory

The location of product artifacts after the package is installed.

Non-admin user

A user who does not have write administrative privileges. In the context of installing, this means that this user can only install into the home directory.

Package

An installable unit of a software product. Software product packages are separately installable units that can operate independently from other packages of that software product.

Package group

A package group represents a directory in which different product packages share resources with other packages in the same group. When you install a package using Installation Manager, you can create a new package group or install the packages into an existing package group. (Some packages cannot share a package group, in which case the option to use an existing package group is disabled.) Sharing a package group is sometimes also referred to as "shell sharing."

Repository

A persistent storage area where packages are available for download. A repository can be disc media, a folder on a local hard disk, or a server or Web location.

Shared resources directory

In some instances, product packages can share resources. These resources are located in a directory that the packages share.

Installation default values and conventions

Planning the installation

Installation Manager overview

Installation Manager provides tools that help you keep packages up to date, modify the packages, manage the licenses for your packages if required, and uninstall the packages from your system.

Version 1.3.0 of Installation Manager is included with the product. You can also download Installation Manager Version 1.3.x directly from www.ibm.com. All instructions in this Installation Guide assume that you are using the included version of Installation Manager. If you upgrade later to a higher version of Installation Manager, some of the instructions might not be accurate. The Installation Manager information center is on the Web at: http://publib.boulder.ibm.com/infocenter/install/v1r2/index.jsp

Installation Manager includes six wizards that make it easy to maintain packages through their life cycles:

• The Install wizard walks you through the installation process. You can install a package by simply accepting the defaults, or you can modify the default settings to create a custom installation. Before you install, you are provided with a complete summary of your selections throughout the wizard. Using the wizard you can install one or more packages at one time.
• The Update wizard will search for available updates to packages that you have installed. An update might be a released fix, a new feature, or a new version of the product. Details of the contents of the update are provided in the wizard. You can choose whether to apply an update
• The Manage Licenses wizard helps you set up the licenses for your packages. Use this wizard to change your trial license to a full license, to set up your servers for floating licenses and to select which type of license to use for each package. Not all product packages require licenses.
• The Roll Back wizard enables you to revert to a previous version of a package.
• The Uninstall wizard will remove a package from your computer. You can uninstall more than one package at a time.
• With the Modify wizard you can modify certain elements of a package that you have already installed. During the first installation of the package, you select the features that you want to install. If you find later that you require other features, you can use the modify packages wizard to add them to your package. You can also remove features and add or remove languages.

Installing IBM Installation Manager

About this task

If you start the installation of the product by using the launchpad from the product DVD, IBM Installation Manager automatically starts even if it is not already installed. You will then install Installation Manager on your computer during the process of installing the product.

The latest version of Installation Manager might be required for your package. Updates are discovered if you have not cleared the Search service repositories for updates check box on Repositories page in the Preferences window of Installation Manager.

Starting IBM Installation Manager

About this task

If you already installed Installation Manager, you can start it manually:

• On Windows systems: Click Start -> All Programs -> IBM Installation Manager -> IBM Installation Manager
• For Linux: Change to Installation Manager directory/eclipse and run IBMIM

Installation requirements

Hardware and software requirements for IBM Optim Development Studio

Before you can install the product, verify that your system meets the minimum hardware requirements.

For the most up to date system requirements, see the technote on the Web: http://www.ibm.com/support/docview.wss?uid=swg27014476

Compatible operating systems

Do not attempt to install the product on operating systems other than those that are listed. Installation Manager might run on other operating systems, but the product package installation can fail. If installation fails, uninstallation sometimes also fails.

Supported operating systems are listed on the product system requirements Web page: http://www.ibm.com/support/docview.wss?uid=swg27014476

User privilege requirements

Your user ID must not contain double-byte characters.

There are two methods of installation: administrative and non-administrative. For information about how to choose between these two options, see the topic: Installing IBM Optim Development Studio with the Installation Manager Install wizard.

Implications of using an admin or non-admin user ID when installing

Additional requirements for Linux operating systems

Environment variable might need setting for Firefox or Mozilla browsers

You might need to set the environment variable MOZILLA_FIVE_HOME to the folder containing your Firefox or Mozilla installation. For example, setenv MOZILLA_FIVE_HOME /usr/lib/firefox-1.5.

Firefox browsers must be dynamically linked

To support the SWT browser widget, your Firefox browser must be dynamically linked, which means it was not downloaded from mozilla.org, but was compiled from source. This is typically the case when the Firefox comes as part of the distribution (that is, it is in a place such as /usr/lib/firefox).

One way to ensure that this is true is to see if it is the browser that is pointed at by /etc/gre.conf. The purpose of this gre.conf file is to point at an embeddable browser.

SUSE Linux might require a fix for invisible text problem

If your operating system is SUSE Linux Enterprise Desktop 10 SP1 or SUSE Linux Enterprise Server 10 SP1, then you might need the following operating system update to resolve a problem with text not being displayed in some editors:http://support.novell.com/techcenter/psdb/44ab155e3202595389c101e6cf7e20f2.html.

Planning what features to install

When you install the product package by using IBM Installation Manager, the installation wizard displays the features in the available product package. From the features list, you can select which to install. A default set of features is selected for you (including any required features). Installation Manager automatically enforces any dependencies between features and prevents you from clearing any required features.

This table shows the features of the product that you can install. Default selections of features to install might vary. If a feature already exists in your shared resources directory, it will not be selected by default and will not be installed again.

Installation considerations

Installation directories

Shared resources directory

The shared resources directory is where some product resources are installed so that they can be used by multiple product package groups. You define the shared resources directory the first time that you install IBM Installation Manager. For best results, use your largest disk drive for shared resources directories. You cannot change the directory location unless you uninstall Installation Manager.

Package groups

During installation, you specify a package group into which to install a product.

• A package group represents a directory in which products might share resources with other products in the same package group. This option is also sometimes called "shell sharing."
• Not all products can share a package group, in which case the option to use an existing package group will be disabled.
• When you install a product using Installation Manager, you either create a package group or install the product into an existing package group. A new package group is assigned a name automatically; however, you choose the installation directory for the package group.
• After you create a package group you cannot change the installation directory. The installation directory contains files and resources shared by the products installed into that package group.
• When you install multiple products at the same time, all products are installed into the same package group.

Coexistence considerations

Package group coexistence considerations

Coexistence within a package group

When you install each product package, you select whether you want to install the product package into an existing package group or whether you want to create a new package group. IBM Installation Manager offers only products that are designed to share a package group and meet version compatibility and other requirements. If you want to install more than one product at a time, the products must be able to share a package group.

Any number of eligible products can be installed to a package group. When a product is installed, the product functions are shared with all of the other products in the package group. If you install a development product and a testing product into one package group, when you start either of the products, you have both the development and testing functions available to you in your user interface. If you add a product with modeling tools, all of the products in the package group will have the development, testing, and modeling functions available.

Coexistence between package groups

Multiple instances of a product package can exist on the same computer and they are automatically installed into separate package groups. The product packages can be at different versions or fix levels.

If you update a product package, you update only that instance of the product.

Compatibility with other products

Eclipse-based products that have been installed with Installation Manager can share a package group with other compatible products that have been installed with Installation Manager.

The following Eclipse 3.4.2-based products are compatible and can share a package group:

• IBM Data Studio Version 2.2.1
• IBM Optim™ Database Administrator Version 2.2.3
• IBM Optim Development Studio Version 2.2.1
• IBM Optim Query Tuner client Version 2.2.1
• IBM InfoSphere™ Data Architect Version 7.5.3

For information about other products that are compatible, see the following technote: http://www-01.ibm.com/support/docview.wss?rs=2042&uid=swg21279139

For the most up to date list of compatible products and more information about known compatibility issues and workarounds, see the following technote:http://www.ibm.com/support/docview.wss?rs=3360&uid=swg27014124

The following limitation exists for shared installations:

• If you install more than one product into a shared package group, when you launch the product, the splash screen of the first installed product is always launched. However, after the splash screen, the correct product opens.

If you have installed other Eclipse 3.4.2-based products using a mechanism other than Installation Manager, you can attempt to install Optim Development Studio into the same Eclipse IDE, using the Extend an existing Eclipse IDE option in Installation Manager. However, be aware that this type of installation will fail if the Eclipse environment is not exactly compatible with this version of Optim Development Studio.

See the support page for additional technotes about extending an Eclipse IDE.

Extending an existing Eclipse IDE

The product package contains a compatible version of the Eclipse IDE or workbench; this bundled workbench is the base platform on top of which the functionality in the product is provided. If you have an Eclipse IDE on your workstation, then you have the option to extend it, that is, add to your current Eclipse IDE the additional functionality provided in the product.

Extending an Eclipse IDE adds the functions of the newly installed product, but maintains your IDE preferences and settings. Previously installed plug-ins are also still available.

Your Eclipse IDE and JRE must be at least at the minimum version levels that the product requires. See the product system requirements for details on the required versions. Installation Manager checks that the Eclipse instance that you specify meets the requirements for the installation package.

Upgrading from another release

You can update Version 2.1 to the current version by using the Update wizard in Installation Manager.

Earlier versions of this product can coexist on the same computer, but you cannot update them to the current version by using the Update wizard and you cannot install them into the same package group.

To update with the Update wizard:

1. Mount the media or unzip the installation program zip file for the current release to a temporary directory.
2. Open Installation Manager and click File -> Preferences.
3. In the Preferences window, click Add Repository.
4. Enter the <media root path>\disk1\diskTag.inf path in the Repositoriesfield, and click OK.
5. Click OK again to close the Preferences window.
6. Click Update to open the Update Packages wizard, and follow the steps of the wizard.

Web-based help content

If your product is configured to use remote help, you can obtain help three ways. One of these options will be best for you, depending on your needs and situation:

• The help content can be accessed on the Web so that you can have the smallest installation footprint and the most up-to-date information.
• The help content can be downloaded and accessed on your computer so that you can work disconnected from the Internet with periodic updates.
• The help content can be deployed on an intranet server so that you can work behind a firewall with administrative updates.

If your help system supports remote help, you can change your access decision any time. If you install multiple products together, you can use different locations for the help for each product, depending on installation footprint, frequency of use, and internet policies. If internet speed is an issue, a longer one-time download and local access might be preferable. Later help updates include only differences.

If you are an administrator and you want users to access help content from an intranet server, see the Installation Manager information center for instructions on how to install the help WAR file on a server.

Pre-installation tasks

Pre-installation checklist

Procedure

Verifying and extracting electronic images

About this task

If you select the Download Director option for downloading the installation files, the Download Director applet automatically verifies the completeness of each file that it processes.

Extracting the files

About this task

When extracting the installation files from the downloaded compressed files, do the following things:

• Ensure that you preserve the directory structure of compressed files when you extract them.
• Extract the contents of all of the compressed files to the same directory. For Linux, do not include spaces in the directory names, or you won't be able to run the command to start the launchpad from a command line.

When you are finished extracting all of the compressed files, the directory where you extracted the contents will have subdirectories with the following names:

Increasing the number of file handles on Linux computers

Before you begin

About this task

Ensure that you complete the following steps correctly. If this procedure is not completed correctly, your computer will not start.

To increase the number of file handles on a Linux computer, complete the following steps:

Procedure

1. Log in as root. If you do not have root access, you will need to obtain it before continuing.
2. Change to the etc directory.
   Attention: If you decide to increase the number of file handles in the next step, do not leave an empty initscript file on your computer. If you do so, your computer will not start the next time that you restart it.
3. Use the vi editor to edit the initscript file in the etc directory. If this file does not exist, type vi initscript to create it.
4. On the first line, type ulimit -n 4096. The point is that 4096 is significantly larger than 1024, the default on most Linux computers.
   Important:
   Do not set the number of handles too high, because doing so can negatively impact system-wide performance.
5. On the second line, type eval exec "$4".
6. Save and close the file after making sure you have completed steps 4 and 5.
7. Optional: Restrict the number of handles available to users or groups by modifying the limits.conf file in the etc/security directory. Both SUSE Linux Enterprise Server (SLES) Version 9 and Red Hat Enterprise Linux Version 4.0 have this file by default. If you do not have this file, consider using a smaller number in step 4 in the previous procedure (for example, 2048). Do this so that most users have a reasonably low limit on the number of open files that are allowed per process. If you use a relatively low number in step 4, it is less important to do this. However, if you set a high number in step 4 earlier and you do not establish limits in the limits.conf file, computer performance can be significantly reduced.

   The following sample limits.conf file restricts all users, and then sets different limits for others afterwards. This sample assumes that you set handles to 8192 in step 4.

   *      soft nofile 1024
   *      hard nofile 2048
   root    soft nofile 4096
   root    hard nofile 8192
   user1   soft nofile 2048
   user1 hard nofile 2048
   

   Note that the * in the preceding example sets the limits for all users first. These limits are lower than the limits that follow. The root user has a higher number of allowable handles open, while number available to user1 is between the two. Make sure that you read and understand the documentation contained in the limits.conf file before making changes.

Mounting a drive

Before you begin

Procedure

To mount a drive in Linux:

1. Log in as a user with root authority.
2. Insert the DVD in the drive and enter the following command:mount -t iso9660 -o ro /dev/cdrom /cdrom The /cdrom variable represents the mount point of the DVD.
3. Log out.

What to do next

Some window managers can automatically mount your DVD drive for you. Consult your computer documentation for more information.

Specifying the repository

Before you begin

About this task

This task is only necessary to complete if you are installing from a repository other than the default repository on the Internet or the product media. For example, your organization might require you to redirect the repository to use intranet sites.

To specify a repository, complete the following steps:

Procedure

1. Start IBM Installation Manager.
2. On the Start page, click File -> Preferences.
3. In the Preferences widow, click Repositories. The Repositories page opens, showing available repositories, their locations, and whether they are connected.
4. On the Repositories page, click Add Repository.
5. In the Add repository dialog box, type the URL of the repository location or use Browse to find a .zip or JAR file that contains a repository, a diskTag.inf file, or the repository.config file of an expanded repository; then click OK. The new repository location is listed. If the repository is not connected, a red x is displayed in the Connection column.
   Note:
   Updates to packages can be stored in service repositories, for example IBM support sites or local update repositories, which might be linked to the repositories you have listed in the previous procedure. To search for updated packages in these linked service repositories, make sure Search service repositories during installation and updates is selected. This option is selected by default.
6. Click OK to close the Preferences window.

Installing software

Installing IBM Optim Development Studio with the Installation Manager Install wizard

Before you begin

Complete any necessary pre-installation tasks.

About this task

This information describes how to start the product package installation for a typical installation. You typically install the product package using the installation launchpad and the Installation Manager Install wizard. For information about how to install the product package silently, see the silent installation information.

For products that are installed by IBM Installation Manager, starting the installation process causes IBM Installation Manager to start even if it is not already installed. You will then install Installation Manager on your computer during the process of installing the product package. The installation wizard is pre-configured with the location of the repository that contains the installation package.

Procedure

To install IBM Optim Development Studio with the Installation Manager Install wizard:

1. Insert the product DVD into your DVD drive. For Linux, ensure that you have mounted the DVD drive.

   If autorun is enabled on your computer, the launchpad automatically opens.

   If autorun is not enabled on your computer, follow the next steps below to start the installation manually.

2. Optional: To start the installation manually, complete one of these steps:
   • On Windows systems: Run setup.exe, which is located in the root directory of the DVD.
     Note:
     On Windows Vista or Windows 7 systems, you must run this file as an administrator if you plan to perform an administrative installation.

     The launchpad opens. Select a language and click OK.

   • For Linux: Run setup, which is located in the root directory of the DVD.

     The launchpad opens. Select a language and click OK.

   As an alternative if you have already installed Installation Manager separately, you can also start the installation process by following these steps:

   1. Start Installation Manager.
   2. Configure the Installation Manager repository preferences.
   3. Run the Installation Manager Install wizard to install the product package.

   If you install using this method, the installation can be an administrative or a non-administrative installation, based on whether you installed Installation Manager as an administrative or a non-administrative user.

3. Optional: If you are installing with the launchpad, read the product information.
4. If you are installing with the launchpad, expand Install Product and click on Administrative Installation or Non-Administrative Installation.
5. In the Installation Manager Install wizard, ensure that IBM Optim Development Studio is selected.
6. You can install updates at the same time that you install the base product package, if updates are available. To search for updates to the packages, click Check for Other Versions and Extensions. Installation Manager searches for updates at the predefined IBM update repository for the product package. It also searches any repository locations that you have set manually in the Installation Manager Preferences window.
7. To learn more about the packages that you can install, click the package name. A description of the package is displayed in the Details pane.
8. Click Next.
9. On the Licenses page, read the license agreements for the selected packages. On the left-hand side of the License page, click each package version to display its license agreement.
   1. If you agree to the terms of all of the license agreements, click I accept the terms of the license agreements.
   2. Click Next to continue.
10. If you are installing Installation Manager: On the Location page, type the path for the shared resources directory in the Shared Resources Directory field, or accept the default path. If you are installing on Linux, ensure that you do not include any spaces in the directory path. The shared resources directory contains resources that can be shared by one or more package groups.
    Important:
    You can specify the shared resources directory only at the time that you install Installation Manager. Use your largest disk for this to help ensure adequate space for the shared resources of future packages. You cannot change the directory location unless you uninstall all packages.
11. Click Next to continue.
12. On the Location page, create a package group to install the product package into, or select an package group. A package group represents a directory in which packages share resources with other packages in the same group. To create a new package group:
    1. Click Create a new package group.
    2. Type the path for the installation directory for the package group. (If you are installing on Linux, ensure that you do not include any spaces in the directory path.) The name for the package group is created automatically.
    After you select a package group, click Next.
13. On the next Location page, you can choose to extend an Eclipse IDE already installed on your system, adding the functionality in the packages that you are installing. This page is not available if you selected to share a package group in the last step.
    • If you do not want to extend an Eclipse IDE, click Next to continue.
    • To extend an existing Eclipse IDE:
      1. Select Extend an existing Eclipse.
      2. In the Eclipse IDE field, type or navigate to the location of the folder that contains the eclipse executable file (eclipse.exe or eclipse.bin). Installation manager will check if the Eclipse IDE version is valid for the package that you are installing. The Eclipse IDE JVM field displays the Java Virtual Machine (JVM) for the IDE that you specified.
      3. Click Next to continue.
14. On the Features page under Languages, select the languages for the package group. The corresponding national language translations for the user interface and documentation for the product package will be installed.
15. On the next Features page, select the package features that you want to install.
    1. Optional: To see the dependency relationships between features, select Show Dependencies.
    2. Optional: Click a feature to view its brief description under Details.
    3. Select or clear features in the packages. Installation Manager will automatically enforce any dependencies with other features and display updated download size and disk space requirements for the installation.
    4. When you are finished selecting features, click Next to continue.
16. On the Common Configurations page, specify how you want to access help.

    If you select to download and install the help locally, you will be prompted to do so the first time you start the product.

    You can change this selection later by modifying the Help -> Contents preferences page.

17. On the Summary page, review your choices before installing the product package. If you want to change the choices that you made on previous pages, click Back, and make your changes. When you are satisfied with your installation choices, click Install to install the package. A progress indicator shows the percentage of the installation completed.
18. When the installation process is complete, a message confirms the success of the process.
    1. Click View log file to open the installation log file for the current session in a new window. You must close the Installation Log window to continue.
    2. In the Install Package wizard, select whether you want the product to start when you exit.
    3. Click Finish to launch the selected package. The Install Package wizard closes and you are returned to the Start page of Installation Manager.
19. Close Installation Manager.
20. If you started the installation from the launchpad, close the launchpad.

What to do next

Complete any necessary post-installation tasks.

• Related concepts
• Coexistence considerations
  Coexistence refers to the installed products on the same computer.
• Installation terminology
  Understanding these terms and conventions can help you take full advantage of the installation information and your product.

Installing silently

Silent installation road maps

There are two main road maps for performing a silent installation.

1. Use Installation Manager to silently install software packages:
   1. Install Installation Manager using the Installation Manager installer.
   2. Record a response file using Installation Manager, or Create a response file manually, .
   3. Run the Installation Manager in silent mode to perform the operation silently.
2. Use the Installation Manager installer to silently install software packages:
   1. Create a response file manually that includes commands to install Installation Manager and other packages.
   2. Run the Installation Manager installer with the response file.

Using the Installation Manager installer

The Installation Manager installer is a command-line utility. Run the Installation Manager installer to silently install and uninstall Installation Manager. You can also install software packages using the Installation Manager installer.

If you do not already have Installation Manager installed on your computer, you might choose to use the Installation Manager installer to install both Installation Manager and packages together using a single command. This sample response file provides an example for installing Installation Manager and a software package. If you already have Installation Manager installed on your computer, you can simply use Installation Manager to install packages .

Installing Installation Manager silently

About this task

The Installation Manager installer is used to install the Installation Manager. You can install the Installation Manager as an administrator, or in non-administrator modes. Follow the example below to install Installation Manager.

Procedure

1. Unzip the Installation Manager installer. The Installation Manager kit is available from: http://download.boulder.ibm.com/ibmdl/pub/software/rationalsdp/v7/im/. Select the version number that you want to install, for example 130/, then select the zips directory.
2. Switch to the InstallerImage_platform subdirectory.
3. Enter one of the following commands:
   • To install as an administrator on Windows: installc --launcher.ini silent-install.ini -log <log file path and name> For example: installc --launcher.ini silent-install.ini -log c:\mylogfile.xml
   • To install as non-administrator on Windows: userinstc --launcher.ini user-silent-install.ini -log <log file path and name> For example: userinstc --launcher.ini user-silent-install.ini -log c:\mylogfile.xml
   • For other platforms as an administrator: install --launcher.ini silent-install.ini -log <log file path and name> For example, install --launcher.ini silent-install.ini -log /root/mylogs/mylogfile.xml
   • For other platforms as non-administrator: userinst --launcher.ini user-silent-install.ini -log <log file path and name> For example, userinst --launcher.ini user-silent-install.ini -log /root/mylogs/mylogfile.xml

Results

After you install Installation Manager silently, you can use Installation Manager or the Installation Manager installer to silently install packages.

Changing the default installation location

About this task

The Installation Manager installer uses a default response file to install Installation Manager installer. You can modify the file to change the default installation location.

Procedure

1. Go to the InstallerImage_platform directory
2. Locate the response file install.xml
3. Modify the location for installing Installation Manager by adding profile information and using the data key and value attributes to specify the installation location. The installation location must be a directory named eclipse.

Example

Changes were made to the default install.xml response file to change the installation location to C:\IBM\InstallationManager.

<?xml version="1.0" encoding="UTF-8"?>
<agent-input clean='true' temporary='true'>

<!-- add a profile and specify the installation location using the data value attribute. The location must end in \eclipse -->
<profile kind='self' installLocation='C:\IBM\InstallationManager\eclipse' id='IBM Installation Manager'>
<data key='eclipseLocation' value='C:\IBM\InstallationManager\eclipse'/>
</profile>

<server>
<repository location='.'/>
</server>

<!-- add the profile information but do not modify the features, id, and version number -->
<install>
<offering profile='IBM Installation Manager' features='agent_core,agent_jre' id='com.ibm.cic.agent' version='1.2.0.20080624_0100'/>
</install>
</agent-input>

Silently installing packages using the Installation Manager installer

Before you begin

To install software packages using the Installation Manager installer, you must first create a response file.

About this task

You can use the Installation Manager installer to silently install Installation Manager and software packages at the same time. Optionally, use the installer to install Installation Manager, then use Installation Manager to install packages silently.

To silently install packages using the Installation Manager installer, from the InstallerImage_platform directory, enter the following command:

• For Windows as administrator: installc.exe --launcher.ini silent-install.ini -input <response file path and name> -log <log file path and name>. For example: installc.exe --launcher.ini silent-install.ini -input c:\myresponse\responsefile.xml -log c:\mylog\silent_install_log.xml.
• For Windows as non-administrator: userinstc.exe --launcher.ini user-silent-install.ini -input <response file path and name> -log <log file path and name>. For example: userinstc.exe --launcher.ini user-silent-install.ini -input c:\myresponse\responsefile.xml -log c:\mylog\silent_install_log.xml .

• For other platforms as administrator: install --launcher.ini silent-install.ini -input <response file path and name> -log <log file path and name>. For example: install --launcher.ini silent-install.ini -input /root/myresponse/responsefile.xml -log /root/mylog/silent_install_log.xml
• For other platforms as non-administrator: userinst --launcher.ini user-silent-install.ini -input <response file path and name> -log <log file path and name>. For example: userinst --launcher.ini user-silent-install.ini -input /root/myresponse/responsefile.xml -log /root/mylog/silent_install_log.xml

The following table describes the arguments used with the silent installation command:

-vm

-nosplash

--launcher.suppressErrors

-silent

-input

-log

-updateAll

-installAll

--launcher.ini silent-install.ini

--launcher.ini user-silent-install.ini

-accessRights

-accessRights nonAdmin

-accessRights admin

-showProgress

-ShowVerboseProgress

The Installation Manager installer has an initialization or .ini file silent-install.ini (or user-silent-install.ini for non-administrator installations) that includes default values for the arguments in the table. For example, a default silent-install.ini file might look something like this:

-accessRights
admin
-vm
C:\Program Files\IBM\Installation Manager\eclipse\jre_5.0.2.sr5_20070511\jre\bin\java.exe
-nosplash
--launcher.suppressErrors
-silent
-vmargs
-Xquickstart
-Xgcpolicy:gencon

Results

If the installation is successful, it will return a status of "0" an unsuccessful operation will return a non-zero number.

When Installation Manager installer is run, it reads the response file and (optionally) writes to a log file to the directory specified. If you specified a log file and directory, the log file will be empty if operation was successful, for example:

<?xml version="1.0" encoding="UTF-8"?>
<result>
</result>

The log file will contain an error element if the operation was not completed successfully.

A log file for Installation Manager is also available. The default locations for the Installation Manager log file are

• For Windows as non-admin: C:\Documents and Settings\<my id>\Application Data\IBM\Installation Manager\logs
• For Windows as admin: C:\Documents and Settings\All Users\Application Data\IBM\Installation Manager\logs
• For other platforms: /var/ibm/InstallationManager/logs

Installing silently with Installation Manager

If you do not already have Installation Manager installed on your computer, you can also use the Installation Manager installer to install both Installation Manager and packages together silently using a single command.

Silently installing packages using Installation Manager

About this task

After you install Installation Manager, use it in silent mode to install packages. This file explains how to install packages using the Installation Manager.

To run Installation Manager in silent mode, run the following command from the eclipse subdirectory in the directory where you installed Installation Manager:

• For Windows: IBMIMc.exe --launcher.ini silent-install.ini -input <response file path and name> -log <log file path and name>. For example: IBMIMc.exe --launcher.ini silent-install.ini -input c:\mylog\responsefile.xml -log c:\mylog\silent_install_log.xml
• For other platforms: IBMIM --launcher.ini silent-install.ini -input <response file path and name> -log <log file path and name>. For example: IBMIM --launcher.ini silent-install.ini -input /root/mylog/responsefile.xml -log /root/mylog/silent_install_log.xml

The following table describes the arguments that are used with the silent installation command:

-vm

-nosplash

--launcher.suppressErrors

-silent

-input

-log

-updateAll

-installAll

--launcher.ini silent-install.ini

--launcher.ini user-silent-install.ini

-showProgress

-ShowVerboseProgress

-accessRights

-accessRights nonAdmin

-accessRights admin

The Installation Manager has an initialization or .ini file silent-install.ini that includes default values for the arguments in the table. For example, the silent-install.ini file might look something like this:

-accessRights
admin
-vm
C:\Program Files\IBM\Installation Manager\eclipse\jre_5.0.2.sr5_20070511\jre\bin\java.exe
-nosplash
--launcher.suppressErrors
-silent
-vmargs
-Xquickstart
-Xgcpolicy:gencon

Results

If the installation is successful, it will return a status of "0" an unsuccessful operation will return a non-zero number.

When Installation Manager installer is run, it reads the response file and (optionally) writes to a log file to the directory specified. If you specified a log file and directory, the log file will be empty if operation was successful, for example:

<?xml version="1.0" encoding="UTF-8"?>
<result>
</result>

The log file will contain an error element if the operation was not completed successfully.

A log file for Installation Manager is also available. The default locations for the Installation Manager log file are

• For Windows as non-admin: C:\Documents and Settings\<my id>\Application Data\IBM\Installation Manager\logs
• For Windows as admin: C:\Documents and Settings\All Users\Application Data\IBM\Installation Manager\logs
• For other platforms: /var/ibm/InstallationManager/logs

Silently installing all available products using Installation Manager

Procedure

Follow these steps to find and install all available products using Installation Manager in silent mode:

1. On a command line, change to the eclipse subdirectory in the directory where you installed Installation Manager.
2. Enter and run the following command:
   • For Windows: IBMIMc.exe --launcher.ini silent-install.ini -installAll
   • For other platforms: IBMIM --launcher.ini silent-install.ini -installAll

Results

All connected repositories are searched, and all available products that are found are installed.

Silently installing updates to all installed products using Installation Manager

Procedure

Follow these steps to find and install all available updates for products that are installed:

1. On a command line, change to the eclipse subdirectory in the directory where you installed Installation Manager.
2. Enter and run the following command:
   • For Windows: IBMIMc.exe --launcher.ini silent-install.ini -updateAll
   • For other platforms: IBMIM --launcher.ini silent-install.ini -updateAll

Results

All available product updates that are known to Installation Manager are installed.

Silently installing from authenticated repositories with Installation Manager

About this task

Installation Manager uses the Eclipse infrastructure (www.eclipse.org) to save credentials in a file called a key ring file. While the contents of the key ring file are encrypted, you can provide an additional level of security by specifying a password to open the key ring file. For additional information on key ring files, refer to the Eclipse workbench user's guide available from www.eclipse.org.

Procedure

To access authenticated repositories in silent mode, complete the following steps:

1. Start Installation Manager in the user interface (UI) mode and specify the following command-line parameters: -keyring <file> -password <password>. For example, IBMIM -keyring c:\my_directory\im.keyring
2. When you use Installation Manager in UI mode and access a protected repository, a window opens so that you can enter the credentials. Enter the correct credentials and then save them. Ensure that the Save password check box is selected. The credentials are saved into the specified key ring file.
3. Use the -keyring <file> -password <password> command line parameter when starting Installation Manager in silent mode. During silent install, the credentials for the protected repository are retrieved from the key ring file specified in the command line. For example:
   1. On Windows: IBMIMc.exe --launcher.ini silent-install -input <input file path and name> -keyring <key ring file path and name> -password <password>
   2. On other platforms: IBMIM --launcher.ini silent-install -input <input file path and name> -keyring <key ring file path and name> -password <password>

Silently uninstalling Installation Manager

Procedure

The uninstall script is stored in the Installation Manager uninstall directory. Follow these steps to silently uninstall Installation Manager:

1. On a command line, change to the uninstall directory for the Installation Manager.
   • For Windows, the default location for non-administrator is: C:\Documents and Settings\All Users\Application Data\IBM\Installation Manager\uninstall.
   • For Windows, the default location for administrator is: C:\Documents and Settings\<user id>\Application Data\IBM\Installation Manager\uninstall.
   • For other platforms, the default location for non-administrator is: <userhomedirectory>/var/ibm/InstallationManager/uninstall
   • For other platforms, the default location for administrator is: /var/ibm/InstallationManager/uninstall
2. Enter the following command:
   • On Windows as administrator: uninstallc.exe --launcher.ini silent-uninstall.ini
   • On Windows as non-administrator:userinstc.exe --launcher.ini silent-uninstall.ini
   • On other platforms, enter: uninstall --launcher.ini silent-uninstall.ini

Response files

Response files are used by both Installation Manager and the Installation Manager installer to perform installation operations silently. You can record a response file by recording preferences and installation actions in Installation Manager in user interface mode, or you can create one manually using the documented list of response file commands and preferences.

A response file is an XML file that contains data read by Installation Manager in silent mode. Using a response file, you can perform almost any action that you can perform using Installation Manager in wizard mode. For example, with a response file you can specify the location of the repository that contains the packages, which package to install, and which features to install for that package. You can also use a response file to modify your installed package, to apply updates, and to apply a license.Sample response file: Installing Installation Manager and packages

Recording a response file with Installation Manager

About this task

When you are recording a response file, you can choose to perform the actions, for example installing a package, or you can choose to just create a response file without performing the actions. Note that when you are recording a response file, preferences that you set, including repository settings, are not stored.

Procedure

To record a response file, complete the following steps:

1. On a command line, change to the eclipse subdirectory in the directory where you installed Installation Manager. For example:
   • For Windows: cd C:\Program Files\IBM\Installation Manager\eclipse
   • For other platforms: cd /opt/IBM/InstallationManager/eclipse
2. On a command line, type one of the following commands to start the Installation Manager, substituting your own file name and location for the response file and (optionally) the log file. You can record a response file and perform an installation or update at the same time, or you can record a response file without performing an installation or update.
   • To record a response file while performing an installation or update:
     • For Windows: IBMIM -record <response file and path name> -log <log file and path name>. For example, IBMIM.exe -record c:\mylog\responsefile.xml -log c:\mylog\record_log.xml
       Note:
       Ensure the file paths you enter exist; Installation Manager will not create directories for the response file and the log file.
     • For other platforms: IBMIM -record <response file and path name> -log <log file and path name>.
   • To record a response file without performing an installation or update, add the optional -skipInstall <agentDataLocation> argument to the command. For example:

     For Windows: IBMIM -record c:\mylog\responsefile.xml -skipInstall c:\temp\recordData

     When you add the -skipInstall <agentDataLocation>argument:

     1. The packages are not installed or uninstalled. The artifacts are not downloaded and the actions are not executed.
     2. Installation Manager saves the data to the location that you specified.
     3. Recording the response file is faster, because the Installation Manager is not performing actions, it is just recording the data.

     <agentDataLocation> must be a writable directory, with the following additional characteristics:

     • If you are generating a response file for an initial installation of a product, the <agentDataLocation> directory must be empty.
     • If you are generating a response file to record license management, updates, or modifications to the product, you must use the same <agentDataLocation> in the next recording session. These changes are added to the agent data location.
3. Follow the on-screen instructions in the appropriate wizard. If you copied the repository to a new location, you can set the location of the repository using the File -> Preferences -> Repository Location dialog.
4. Click Finish, then close Installation Manager.

Results

An XML response file is created and saved in the location that you specified in the command.

Creating a response file manually

There are two categories of commands for the response file:

• Preference commands are used to set preferences for Installation Manager that you set from the File -> Preferences menu, such as repository location information.
• Wizard commands are used to emulate the install, update, modify, and uninstall wizards in Installation Manager.

Response file commands

<profile 
id="the profile (package group) id" 
installLocation="the install location of
 the profile">
<data key="key1" value="value1"/>
<data key="key2" value="value2"/>

</profile>

<server>
<repository location="http://example/
repository/">
<repository location="file:/C:/
repository/">
<!--add more repositories below-->
<...>
      </server>

<install>
<offering profile= "profile id" 
features= "feature ids" 
id= "offering id" version= "offering 
version" selected="true"></offering>

<!--add more offerings below>
<...>

</install>

<update>
<offering profile= "profile id">
</update>

<modify>
<offering profile= "profile id">
</modify>

<uninstall modify="true">
<offering profile="profile id"
 id="Id" version="Version" 
features="-"/>
</uninstall>

<uninstall>
<offering profile= "profile id" 
features= "feature ids" 
id= "offering id" version= "offering 
version"></offering>

<!--add more offerings below>
<...>

</uninstall>

<rollback>
<offering profile= "profile id"
 id= "offering id" 
version= "offering version">
</offering>

<!--add more offerings below
<...>

</rollback>

<installALL/>

-silent -installAll 

<updateALL/>

-silent -updateAll 

<license policyFile="policy file
 location"/>

<license policyFile="c:\mylicense.opt"/> 

Additional response file attributes

<agent-input clean="true">
</agent-input>

<agent-input clean="true" temporary="false">
</agent-input>

<agent-input acceptLicense="false">
</agent-input>

<agent-input rebootLater="false">
</agent-input>

Silent installation preference commands

When you define preferences in a response file, your XML code will look similar to the following example:

<preference
	name = "the key of the preference"
	value = "the value of the preference to be set">
</preference>

Use the following table to identify keys and their associated values for silent installation preferences:

Sample response files

It can be helpful to record a response file and then tailor the contents to suit your needs. See Recording a response file with Installation Manager for more information on recording a response file.

Sample response files are also included on the product DVD, in the sampleResponseFiles directory.

Sample response file: Installing Installation Manager and packages

<agent-input clean="true" temporary="true">

<!-- add preferences -->
<preference name="com.ibm.cic.common.core.preferences.http.proxyEnabled" 
value="false"/>

<!-- create the profile if it doesn't exist yet -->
<profile id="IBM Software Delivery Platform" installLocation="c:/temp/my_profile"></profile>

<server>
<repository location= 
"http://a.site.com/local/products/sample/20090215_1542/repository/"></repository>
</server>

<!-- add the offerings and features to install. You can install Installation Manager and packages in one response file -->
<install>
<offering id="com.ibm.cic.agent" version="1.3.0.20090114_0637" />
<offering features="com.ibm.rad.sdpcore,com.ibm.rad.jre,com.ibm.rad.webtools_core,com.ibm.rad.pde,com.ibm.rad.data_tools" profile="IBM Software Delivery Platform" id="com.ibm.rational.application.developer" version="7006_20080320_1728"/>
</install>

</agent-input>

Sample response file: Installing a package

<agent-input>

<server>
<repository location= 
"http://a.site.com/local/products/sample/20060615_1542/repository/"></repository>
</server>

<!-- use default installation location and choose the latest version of the offering that is available in the repository -->
<install>
	<offering  features= "core" id= "ies">
	</offering>
</install>

</agent-input>

Running Installation Manager with a response file in wizard mode

Installation Manager can be run in silent mode or wizard mode. To start Installation Manager in wizard mode, enter the following on the command line:IBMIM -mode wizard -input <response> where <response> is the response file path and name.

Based on the commands in your response file, Installation Manager will start in one of the following wizards: install, update, modify, or uninstall. Your response file can only contain commands for one of the Installation Manager wizards. For example, the response file can include either:

• server, preference, and install commands
• server, preference, and update commands
• server, preference, and modify commands
• server, preference, and uninstall commands

Export data for problem analysis

Procedure

1. On a command line, change to the eclipse subdirectory in the directory where you installed Installation Manager.
2. Enter and run the following command:
   • For Windows: IBMIMc.exe --launcher.ini silent-install.ini -exportInstallData <installDataFile>. Where <installDataFile> is the name of the file to be generated that contains the exported data in .zip file format.
   • For other platforms: IBMIM --launcher.ini silent-install.ini -exportInstallData <installDataFile>. Where <installDataFile> is the name of the file to be generated that contains the exported data in .zip file format.

Results

A .zip file that contains the installation data is created.

Using the Installation Manager installer to perform other operations

Installing all available products using the Installation Manager installer

Procedure

To find and install all available products using Installation Manager installer, complete the following steps:

1. Switch to the InstallerImage_platform subdirectory.
2. Enter and run the following command:
   • For Windows as admin: installc.exe --launcher.ini silent-install.ini -installAll
   • For Windows as non-admin: userinstc.exe --launcher.ini user-silent-install.ini -installAll
   • For other platforms: install --launcher.ini silent-install.ini -installAll

Results

All available products found searching the connected repositories are installed.

Silently installing updates to all products using the Installation Manager installer

Procedure

To find and install all available updates for products that are installed, complete the following steps:

1. Switch to the InstallerImage_platform subdirectory.
2. Select, enter and run the appropriate command:
   • For Windows as admin: installc.exe --launcher.ini silent-install.ini -updateAll
   • For Windows as non-admin: userinstc.exe --launcher.ini user-silent-install.ini -updateAll
   • For other platforms: install --launcher.ini silent-install.ini -updateAll

Results

All available product updates known to Installation Manager are installed.

Silently installing from authenticated repositories using the Installation Manager installer

Before you begin

You must have Installation Manager installed to install a software package from an authenticated repository.

About this task

Installation Manager uses the Eclipse infrastructure to save credentials in a file called a key ring file. While the contents of the key ring file are encrypted, you can provide an additional level of security by specifying a password to open the key ring file. For additional information on key ring files, refer to the Eclipse workbench user's guide available from www.eclipse.org.

Procedure

To access authenticated repositories in silent mode, complete the following steps:

1. Start Installation Manager in user interface mode and specify the following command-line parameters: -keyring <file> [-password <password>]. For example, installc -keyring c:\my_directory\im.keyring
2. When you use Installation Manager in wizard mode and access a protected repository, a window opens where you can enter your credentials. Enter the correct credentials and then save them. Ensure that the Save password check box is selected. The credentials are saved into the specified key ring file.
3. From the eclipse directory in the location you installed Installation Manager in silent mode and specify the following command line parameter: -keyring <file> [-password <password>]. During silent install, the credentials for the protected repository are retrieved from the key ring file specified in the command line.
4. On a command line, enter the appropriate command:
   • On Windows as admininstallc.exe --launcher.ini silent-install -input <input file path and name> -keyring <key ring file path and name> -password <password>
   • On Windows as non-adminuserinstc.exe --launcher.ini user-silent-install -input <input file path and name> -keyring <key ring file path and name> -password <password>
   • On other platforms, use install --launcher.ini silent-install -input <input file path and name> -keyring <key ring file path and name> -password <password>

Deploying and installing to the enterprise

The Installation Manager information center contains articles that will help you install your product in an enterprise environment. Visit the information center for Installation Manager 1.3 at http://publib.boulder.ibm.com/infocenter/install/v1r2/index.jsp.

Post-installation tasks

Post-installation checklist

About this task

Review the following information and ensure the post-installation steps are completed as required.

Procedure

Starting the product

Procedure

• For Windows operating systems: Click Start -> All Programs -> package_group_name -> IBM Optim Development Studio .
• To start the product from a command-line interface:
  • On Windows: Type this command: product_installation_directory\eclipse.exe
  • On Linux: Type this command: .product_installation_directory/eclipse

  For more information about the available command-line start options, see Running Eclipse. For example, if you installed multiple national language translations, you can start the product in another locale with the -nl option:

  Example

  To start the product with the English locale, type this command: product_installation_directory\eclipse.exe -nl en_US

Managing licenses

About this task

Using the Manage Licenses wizard, you can upgrade trial versions of an offering to a licensed version by importing a product activation kit.

License activation

Licenses for this product are activated by importing a license activation kit.

Activation kits

A license activation kit contains the permanent license key for you product. You purchase the activation kit, download the activation kit compressed file to your computer, and then use IBM Installation Manager to import the activation kit (a .jar file) to activate the license for your product.

Authorized User License

An Authorized User license permits a single, specific individual to use a software product. Purchasers must obtain an Authorized User license for each individual user who accesses the product in any manner. An Authorized User license cannot be reassigned unless the purchaser replaces the original assignee on a long-term or permanent basis.

For example, if you purchase one Authorized User license, you can assign that license to one specific individual, who can then use the software product. The Authorized User license does not entitle a second person to use that product at any time, even if the licensed individual is not actively using it.

Importing a license activation kit

Before you begin

If you have not purchased an activation kit, you must do this first. If you have purchased a product or a product activation kit, insert the appropriate CD or download the activation kit from IBM Passport Advantage to an accessible workstation. The activation kit is packaged as a Java archive (.jar) file. The .jar file contains the permanent license key and must be imported to activate your product.

About this task

To import an activation kit .jar file and enable the new license key, complete the following steps:

Procedure

1. Start IBM Installation Manager.
2. On the main page, click Manage Licenses.
3. Select a package and click the Import Activation Kit button.
4. Click Next. Details for the selected package are shown, including the current license kind and the product version range of the license.
5. Browse to the path on the media CD or download location for the activation kit; then select the appropriate Java archive (JAR) file and click Open.
6. Click Next. The Summary page displays the target install directory for the activation kit, the product the new license applies to, and version information.
7. Click Finish.

Results

The product activation kit with its permanent license key is imported to the product. The Manage Licenses wizard indicates whether the import is successful.

Viewing license information for installed product packages

About this task

To view license information, complete the following steps:

Procedure

1. Start IBM Installation Manager.
2. On the Start page, click Manage Licenses.

Results

The package vendor, current license types, and expiration dates are displayed for each installed product package.

Configuring Web-based help

Accessing Web-based help

Before you begin

During installation, select the option to access help from a remote information center. This is the default selection.

If you did not select this option during installation, change the help access method to specify accessing help from a remote information center.

About this task

Your product help system can retrieve content installed with the product, as well as content from a remote server running an information center. The information center for your product has the most current help content and when your product is configured to retrieve content from a remote information center, the contents of the information center can be accessed by selecting Help -> Help Contents to open your help system.

The information center for your product is available from one of the following URLs:

Procedure

To check your connection to the information center, complete the following steps:

1. Open the Preferences dialog
2. Select Help -> Content
3. Ensure that Include help content from a remote infocenter is selected.
4. Ensure that the URL for your product information center is in the list of available information centers. If your information center is not listed, complete the following steps:
   1. Click Add
   2. In the Name field, enter a name for the connection.
   3. In the Host field, enter publib.boulder.ibm.com
   4. In the Path field, enter one of the following paths, depending on your product:

      Product	Path
      InfoSphere Data Architect	/infocenter/rdahelp/v7r5
      Data Studio (IDE package)	/infocenter/idmhelp/ds-v2r2
      Optim Database Administrator	/infocenter/idmhelp/admin-v2r2
      Optim Development Studio	/infocenter/idmhelp/dev-v2r2
      Optim Query Tuner client	/infocenter/idmhelp/tune-v2r2

   5. Select Use default port
   6. Click OK
5. Select the entry for your product information center.
6. Click Test Connection.

Installing help content locally with the Local Help Updater

Before you begin

During installation, select the help access option, Download help and access the content locally.

If you did not select this option during installation, change the help access method to specify local download and install.

Procedure

To install local help content:

1. Optional: For better performance, download a ZIP file that contains update site files.

   Although this step improves performance during installation, if you install local help this way you will not be automatically notified when updates to your local help are available.

   1. Download the update site for the documentation you want to install from the following Web page: http://download.boulder.ibm.com/ibmdl/pub/software/rationalsdp/documentation/updatesites/
   2. Extract the ZIP file to a temporary directory.
2. With your product open, click Help -> Local Help Updater. The Updater site opens.
3. Specify the location of the help that you want to download.
   • If you downloaded and extracted a ZIP file, add the location of the extracted update site on the Internal Sites tab. Click the Add toolbar button, verify that the Local radio button is checked, then browse to the location of the update site and select the site.xml file.
   • To specify the location of the public update site for your product, select your product name from the list on the Public Sites tab.
4. The Available Features list will be populated with a list of the help that is available for download. If you are using a public update site, this might take a few minutes. Select the help content that you need.
5. Click Install. The help content is downloaded and installed. A progress bar opens and tracks the status of the download.
6. When the download is completed, open the help in the product by selecting Help -> Help Contents.

Results

The help that you selected is installed on your system.

Updating help content

Before you begin

You have installed help content locally, using a public update site.

About this task

Updates are automatically installed each time you start the product, if you have an Internet connection and you used a public update site to install the content locally.

If you downloaded a ZIP file containing an update site for better performance during installation, you will not be notified by the Local Help Updater when new help content is available. You can check for updates at this Web site, or you can monitor the product support page for technotes announcing new help content.

Procedure

To update the help without restarting the product, complete the following steps:

1. Close the product help system window.
2. Open the Local Help Updater by selecting Help -> Local Help Updater. The Updater site opens.
3. Click the Installed Features tab.
4. Click Search for Updates. If updates to the content you have installed are available, they are installed to your system. A progress bar indicates the status of the request.
5. When the update is completed, open the help in the product by selecting Help -> Help Contents.

Removing help content

Before you begin

You have downloaded help features using the Local Help Updater.

Procedure

To remove installed help content, complete the following steps:

1. Close the product help system window.
2. Open the Local Help Updater by clicking Help -> Local Help Updater. The Updater site opens.
3. Click the Installed Features tab.
4. Select the features that you want to remove, then click Remove The help features you selected are removed from your system. A progress bar indicates the status of the request.
5. When the removal is completed, open the help in the product by selecting Help -> Help Contents.

Setting up an intranet server for help content

Before you begin

You have a server available that can be accessed by users behind a firewall.

About this task

See the Installation Manager information center for the instructions for setting up an intranet server for help content.

The WAR file that is needed to set up IBM Optim Development Studio help on an intranet server is located on the product DVD, in the enterprise folder.

Changing the way you access help content

Before you begin

During the installation process, a help content access method was selected. However, you can modify your preferences to change the help content access method at any time. Close the help browser before you change the way you access help content.

Procedure

To change the way that you access help content, complete the following steps:

1. Click Windows -> Preferences. The Preferences window opens.
2. Expand the Help entry, and then click Content. A list of the information center or centers opens. Depending on the access method that was chosen, complete one of the following procedures.
   • To access help content on an intranet server, follow these steps:
   1. Click Add; then name the intranet connection, specify the intranet URL for the server that contains the help content, and then click OK.
   2. Disable any other remote infocenters.
   3. Click OK to close Preferences.
   4. Click Help -> Help Contents, to open your help.
   • To download and access help content locally, follow these steps:
   1. Ensure that Include help content from a remote infocenter is selected.
   2. Enable the Local option, or complete the next step if the Local option is not available.
   3. Click Add; then enter a name for the local help connection. Specify the localhost Host IP address 127.0.0.1 and path /help. Select any unused port number, and then click OK.
   4. Disable any other remote infocenters.
   5. Save any work and close and restart the product.
   6. Follow the instructions in Installing help content locally with the Local Help Updater to download help content.
   • To access help content from an IBM Web site, follow these steps:
   1. Ensure that Include help content from a remote infocenter is selected.
   2. Click Add; then name the connection, specify the Internet URL for the IBM Web site that contains the help content, and then click OK. This URL might already be available in the list of connections. If it is listed, select the connection and click Enable.
   3. Disable any other remote infocenters.
   4. Click OK to close Preferences.
   5. Click Help -> Help Contents, to open your help.

Modifying installed product packages

Before you begin

By default, Internet access is required unless the repository preferences points to a local update site. See the Installation Manager help for more information.

Procedure

To modify an installed product package, complete the following steps:

1. Start IBM Installation Manager.
2. On the Start page, click Modify.
3. In the Modify Packages wizard, select the product package group and click Next.
4. On the Languages page, select the languages for the package group and click Next. The corresponding national language translations for the user interface and documentation for the packages will be installed. Note that your choices apply to all packages installed under this package group.
5. On the Features page, select the features that you want to install or remove. Some products do not have optional features.
   1. To learn more about a feature, click the feature and review the brief description under Details.
   2. If you want to see the dependency relationships between features, select Show Dependencies. When you click a feature, any features that depend on it and any features that are its dependents are shown in the Dependencies window. As you select or exclude features in the packages, Installation Manager will automatically enforce any dependencies with other features and display updated download size and disk space requirements for the installation.
   3. Click Next
6. On the Summary page, review your choices before modifying the installation package and click Modify.
7. Optional: When the modification process completes, click View Log File to see the complete log.
8. Click Finish to close the wizard.

Updating installed product packages

Before you begin

Internet access is required unless your repository preferences points to a local update site.

Each installed package has the location embedded for its default IBM update repository. For Installation Manager to search the IBM update repository locations for the installed packages, the preference Search service repositories during installation and updates on the Repositories preference page must be selected. This preference is selected by default.

See the Installation Manager help for more information.

Procedure

To find and install product package updates, complete the following steps:

1. Start IBM Installation Manager.
2. On the Start page of IBM Installation Manager, click Update.
3. Optional: If a required version of IBM Installation Manager is not detected on your computer, you must continue with the update of Installation Manager. Follow the instructions in the wizard to complete the update.
4. In the Update Packages wizard, select the product package group that you want to update or click the Update All check box and click Next. Installation Manager searches for updates in its repositories and the predefined update sites for the product.
5. On the Update page, if updates for a package are found, they are displayed in the Updates list below their corresponding package and only recommended updates are displayed by default. Complete the following steps:
   1. To display all updates found for the available packages, click Show all.
   2. To learn more about an update, click the update and review its description under Details. If additional information about the update is available, a More info link will be included at the end of the description text. Click the link to display the information in a browser. Review this information before installing the update.
   3. Select the updates that you want to install or click Select Recommended to restore the default selections. Updates that have a dependency relationship are automatically selected or cleared.
   4. Click Next.
6. On the Licenses page, read the license agreements for the selected updates. On the left side of the License page, the list of licenses for the updates you selected is displayed; click each item to display the license agreement text. If you agree to the terms of all the license agreements, click I accept the terms of the license agreements and Click Next.
7. On the Features page, select the features that you want to update and complete the following steps:
   1. To learn more about a feature, click the feature and review the brief description under Details.
   2. If you want to see the dependency relationships between features, select Show Dependencies. When you click a feature, any features that depend on it and any features that are its dependents are shown in the Dependencies window. As you select or exclude features in the packages, Installation Manager will automatically enforce any dependencies with other features and display updated download size and disk space requirements for the installation.
   3. Click Next
8. On the Summary page, review your choices before installing the updates.
   1. If you want to change the choices you made on previous pages, click Back, and make your changes.
   2. When you are satisfied, click Update to download and install the updates. A progress indicator shows the percentage of the installation completed.
9. Optional: When the update process completes, a message that confirms the success of the process is displayed near the top of the page. Click View log file to open the log file for the current session in a new window. You must close the Installation Log window to continue.
10. Click Finish to close the wizard.
11. Optional: Only the features that you already have installed are updated using the Update wizard. If the update contains new features that you would like to install, run the Modify wizard and select the new features to install from the feature selection panel.

Reverting updates to previous versions

Before you begin

During the rollback process, Installation Manager must access files from the earlier version of the package. By default, these files are stored on your computer when you upgrade to a new package. If you have deleted the files that are saved locally for rollback or cleared the Save files for rollback check box in the Preferences page (File > Preferences > Files for Rollback) while upgrading, you will not be able to roll back to the previous version without the media or repositories that were used to install that version of the package.

About this task

Use the rollback feature if you have applied an update to a product package and decide later that you want to remove the update and revert to the earlier version of the product. When you use the rollback feature, Installation Manager uninstalls the updated resources and reinstalls the resources from the previous version. You can only roll back one version level at a time.

For more information, see the Installation Manager online help or Information Center.

Procedure

To revert an update to a previous version, complete the following steps:

1. Start IBM Installation Manager.
2. On the Start page, click Roll Back.
3. In the Roll Back Packages wizard, from the Package Group Name list, select the package that you want to revert to the previous version and click Next.
4. Follow the instructions in the wizard.

Uninstalling software

About this task

For Windows, you can use the Control Panel and, for Linux and UNIX, you can use the Uninstall IBM Installation Manager icon on your computer's desktop to uninstall IBM Installation Manager.

Uninstalling product packages

Before you begin

To uninstall a product package, you must log in to the system by using the same user account that you used to install the product package. You must close the programs that you installed by using IBM Installation Manager.

Procedure

To uninstall a product package, complete the following steps:

1. Start IBM Installation Manager.
2. On the Start page click Uninstall.
3. On the Uninstall Packages page, from the Installation Packages list, select the product package that you want to uninstall and click Next.
4. On the Summary page, review the list of packages that will be uninstalled and click Uninstall. The Complete page is displayed after the packages are removed.
5. Click Finish.

Uninstalling IBM Installation Manager

Before you begin

Before you can uninstall IBM Installation Manager, you must uninstall all of the packages, including products that were installed by IBM Installation Manager. You must close Installation Manager before attempting to uninstall the program. You must log in to the computer by using the same user account that you used to install Installation Manager.

About this task

To uninstall Installation Manager, complete the following steps:

• To uninstall Installation Manager from Windows, complete the following steps: :
  1. Click Start -> Control Panel.
  2. In the Control Panel window, click Add or Remove Programs.
  3. In the Add or Remove Programs window, select IBM Installation Manager and click Remove.
  4. In the Add or Remove Programs dialog box, click Yes to continue with the removal.

• To uninstall Installation Manager from Linux, complete the following steps:
  1. Open a terminal window and run /var/ibm/InstallationManager/uninstall/uninstall if this was an installation by root.
  2. In the IBM Installation Manager Uninstall Packages wizard, click Next; then click Uninstall.

Notices

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.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

Trademarks and service marks

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. These and other IBM trademarked terms are marked on their first occurrence in this information with the appropriate symbol (® or ™), indicating US registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A complete and current list of IBM trademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtml

Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.

Linux is a trademark of Linus Torvalds 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.