IBM WebSphere Integration Developer Version 6.2

Advanced Installation Guide

Quick links

For your convenience, here are some quick links to our most popular install topics:

Chapter 1. Overview

Refer to the WebSphere Integration Developer support site for updated documentation and troubleshooting information.

IBM Installation Manager

IBM Installation Manager offers a number of time-saving features. It keeps track of what you are about to install, software components that you have already installed, and components that are available for you to install. It searches for updates so you know that you are installing the latest version of a WebSphere Integration Developer product package. Installation Manager also provides tools for managing licenses for the product packages that it installs. It provides tools for updating and modifying packages. You can also use Installation Manager to uninstall product packages.

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

• The Install Packages wizard walks you through the installation process. You can install a product package by simply accepting the defaults, or you can modify the default settings to create a custom installation. Before you install a product package, you are provided with a complete summary of the selections that you have made throughout the wizard. With the wizard you can install one or more product packages at the same time.
• The Update Packages wizard searches for available updates to product 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.
• With the Modify Packages wizard, you can modify specific elements of a package that you have already installed. During your initial installation of the product package, you select the features 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 product package installation. You can also remove features, and add or remove languages.
• The Manage Licenses wizard helps you to 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. This wizard is not used for the WebSphere Integration Developer packages.
• With the Rollback Packages wizard you can revert to a previously installed version of an eligible package.
• The Uninstall Packages wizard helps you to remove a product package from your computer. You can uninstall more than one package at a time.

Installation quick reference

The following table presents a list of objectives related to managing your WebSphere Integration Developer package, a set of high-level steps for accomplishing each objective, and the result of performing those steps.

Chapter 2. Installation requirements

For the most up-to-date, detailed system requirements, refer to the List of supported software for WebSphere Integration Developer.

Previous versions of WebSphere Integration Developer cannot be upgraded to version 6.2. Different versions of WebSphere Integration Developer can coexist on your workstation, but they must not be installed in the same directory.

Hardware requirements

The following hardware must be installed before you install WebSphere Integration Developer:

• Intel Pentium III 1 GHz processor minimum (Higher is recommended).
• 1 GB RAM minimum (2 GB RAM is recommended).
• Disk space:
  • For a default installation, minimum 3.3 GB of available disk space is required. This includes the temporary disk space required during installation.
  • For a full installation, minimum 7.5 GB of available disk space is required. This includes the temporary disk space required during installation.
• Display resolution:
  • Minimum 1024 x 768 display resolution (1280 x 1024 is recommended).

Software requirements

Operating systems

The following software must be installed before you install WebSphere Integration Developer:

• One of the following operating systems:
  • Windows Server 2003, Enterprise Edition
  • Windows Server 2003, Standard Edition
  • Windows Server 2008, Enterprise Edition
  • Windows Server 2008, Standard Edition
  • Windows Vista Business Edition
  • Windows Vista Enterprise Edition
  • Windows XP Professional SP1, SP2 and SP3
  • Windows XP Professional x64 SP2 (in 32-bit mode)
  • Red Hat Enterprise Linux (RHEL) 4 WS
  • Red Hat Enterprise Linux (RHEL) 5 WS
  • Red Hat Enterprise Linux (RHEL) 4 Desktop
  • Red Hat Enterprise Linux (RHEL) 5 Desktop
  • SUSE Linux Enterprise Server 9 SP1 to SP4
  • SUSE Linux Enterprise Server 10
  • SUSE Linux Enterprise Desktop 9 SP1 to SP4
  • SUSE Linux Enterprise Desktop 10
• The above listed Windows and Linux operating systems support all of the national languages that WebSphere Integration Developer supports.

Other software requirements

• You will need a Web browser to view the release notes and the installation guide.
• You will need the GTK, Version 2.2.1 or later.
• You must have Mozilla 1.4 GTK2, Mozilla 1.5 GTK2 or Mozilla 1.6 GTK2 installed before you can run WebSphere Integration Developer. The version of Mozilla installed on your system varies with your Linux distribution.
• You will need Adobe Flash Player 9.

In order to view certain product overview information, links to tutorials, samples and migration information, a compatible browser must be installed. Follow the steps below to install a compatible version of Mozilla that can be used with WebSphere Integration Developer. These changes will not replace your existing browser.

If you are using SUSE LINUX Enterprise Server, the following environment variable settings are required:

• export MOZILLA_FIVE_HOME=/opt/mozilla/lib
• export LD_LIBRARY_PATH=$LD_LIBRARY:/opt/mozilla/lib

These can be set at the system level, user level, or within a script to launch the product.

To set these environment variables at the user level, add the above lines to your .profile file. In order for this to take effect you will need to logout and login again.

If this does not work or you are using another Linux distribution, use the following steps to install a compatible version of Mozilla that can be used with WebSphere Integration Developer; these changes will not replace your existing browser.

1. Download a precompiled version of the Mozilla browser from the following site: http://ftp.mozilla.org/pub/mozilla.org/mozilla/releases/mozilla1.7.12/contrib/mozilla-i686-pc-linux-gnu-1.7.12-gtk2+xft.tar.gz If this link does not work, look for a Linux (x86) for GTK2 and Xft build from the following site: http://www.mozilla.org/releases/
2. Extract this file to a location on your workstation, for example, as /opt/mozilla-1.7.12-gtk2+xft.
3. Log in as the root user or become the root user by issuing the su command.
4. Open a command prompt and run the following commands:

   cd /opt/mozilla-1.7.12-gtk2+xft/plugins 
   tar xvfz install_flash_player_9_linux.tar.gz
   mv install_flash_player_9_linux/flashplayer.xpt . 
   mv install_flash_player_9_linux/libflashplayer.so . 

   Optional:

   rm -rf install_flash_player_9_linux 

5. Log out as the root user.
6. From a command prompt, run the following commands:

   cd /opt/mozilla-1.7.12-gtk2+xft 
   ./mozilla 

7. Exit WebSphere Integration Developer and restart it with the same workspace directory.
8. Update your .profile file to set these environment variables at the user level. In order for this to take effect you will need to logout and login again.

   export MOZILLA_FIVE_HOME=/opt/mozilla-1.7.12-gtk2+xft
   export LD_LIBRARY_PATH=$LD_LIBRARY:/opt/mozilla-1.7.12-gtk2+xft 

9. When the Welcome is displayed, press the Home icon to refresh the content. If the Welcome is not displayed, open it using Help > Welcome.

For more technical information on compatible browser versions, see http://www.eclipse.org/swt/faq.php#whatisbrowser

User privileges requirements

• Your user ID must not contain double-byte characters.
• Your user ID must not contain letters from the Cyrillic alphabet.
• You do not need to be an administrator to install WebSphere Integration Developer.
• If you want to install as a non-administrator see the information on using the userinst command in the topics Installing from DVD and Installing from an installation image on your workstation.
• If you do want to install as an administrator your user credentials need the following properties. The user privileges required for installing depend on the version of Windows on your computer:
  • You must log in to the Administrator account (or run as Administrator; right-click the program file or shortcut and select Run as Administrator) to perform the following tasks:
    • Install or update IBM Installation Manager (the application that installs and updates WebSphere Integration Developer)
    • Install or update a product offering
  • For other supported Windows versions, you must have a user ID that belongs to the Administrators group.

Chapter 3. Planning to install

Installation scenarios

The following are some of the factors that might determine your installation scenario:

• The format and method by which you access your installation files (for example, from DVD or files downloaded from IBM Passport Advantage).
• The location for your installation (for example, you can install the product onto your own workstation, or make the installation files available to your enterprise).
• The type of installation (for example, you can use the Installation Manager wizard, or install silently).

These are the typical installation scenarios you might follow:

• Installing from DVD.
• Installing from a downloaded electronic installation image on your workstation.
• Installing from an electronic installation image on a shared drive.

Note also that you can install updates at the same time that you install the base product package.

Installing from DVD

In this installation scenario, you have the DVDs that contains the product package files, and typically you are installing WebSphere Integration Developer on your own workstation. Refer to Installing from DVD for an overview of the steps.

Installing from a downloaded electronic installation image on your workstation

In this scenario, you have downloaded the installation files from IBM Passport Advantage and you will install WebSphere Integration Developer on your own workstation. Refer to Installing from an installation image on your workstation for an overview of the steps.

Installing from an electronic installation image on a shared drive

In this scenario, you will place the electronic installation image on a shared drive so that users in your enterprise can access the installation files for WebSphere Integration Developer from a single location. Refer to Installing from an installation image on a shared drive for an overview of the steps.

Deciding which features to install

When you install the WebSphere Integration Developer product package using IBM Installation Manager, the installation wizard displays the features available in the product package. From the features list, you can select which features 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.

Features

Security considerations

Server security, including administrative security and application security, is automatically enabled for those test environment servers that you choose to install with WebSphere Integration Developer 6.2.

During installation you are prompted for a user name and password to be used for administering server security.

Note that if you disable or enable server security in a server administrative console, you must ensure that these changes are also specified for the same server in the server configuration editor or the Window -> Preferences -> Server -> Security preferences page of WebSphere Integration Developer.

Information about changing the user ID and password, and about disabling or enabling server security, is found in the Security documentation in the WebSphere Integration Developer help: Help -> Help Contents -> WebSphere Integration Developer -> Managing security.

Coexistence considerations

Offering coexistence considerations

Some products are designed to coexist and share function when they are installed in the same package group. A package group is a location where you can install one or more software products or packages to share a common user interface or workbench. When you install each package, you select whether you want to install the package to an existing package group, or whether you want to create a new one. IBM Installation Manager will block products that are not designed to share or do not meet version tolerance 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, its function is 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 functionality 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 functionality available.

If you want WebSphere Integration Developer 6.2 to coexist with a Rational software product (for example, Rational Application Developer for WebSphere Software), the Rational software product must be at version 7.5.1 or higher. When you have an earlier version of the Rational software product you must correct this incompatibility by updating the version to 7.5.1 or higher, or choose a new package group. When you want to add a Rational software product to the same package group as WebSphere Integration Developer 6.2, you must install it directly at the required 7.5.1 (or higher) level by searching for available updates during the Rational installation (using Check for Other Versions and Extensions), or by pointing to the 7.5.1 update repository location along with the base Rational repository location.

Installation repositories

If the WebSphere Integration Developer launchpad is used to start Installation Manager, the default repository information is passed to Installation Manager. If the Installation Manager is started directly, for example from the Start menu, you must specify an installation repositories that contain the product packages that you want to install. See Setting repository preferences in Installation Manager.

By default, IBM Installation Manager uses an embedded URL in each software development product to connect to a repository server over the Internet. Installation Manager then searches for the product packages as well as new features.

Setting repository preferences in Installation Manager

By default, Installation Manager uses an embedded URL in each software development product to connect to a repository server through the Internet and search for installable packages and new features. Your organization may require you to redirect the repository to use intranet sites.

To add, edit, or remove a repository location in Installation Manager:

1. Start Installation Manager.
2. On the Start page of Installation Manager, click File -> Preferences, and then click Repositories. The Repositories page opens, showing any available repositories, their locations, and whether they are accessible.
3. On the Repositories page, click Add Repository.
4. In the Add repository window, type the URL of the repository location or browse to it and set a file path.
5. Click OK. The new or changed repository location is listed. If the repository is not accessible, a red x is displayed in the Accessible column.
6. Click OK to exit.

Package groups and the shared resource directory

Package groups

During the installation process, you must specify a package group for the WebSphere Integration Developer package. A package group represents a directory in which packages share a common user interface or workbench with other packages in the same group. When you install the WebSphere Integration Developer package using Installation Manager, you can create a new package group or install the packages into an existing package group. (Some packages might not be able to share a package group, in which case the option to use an existing package group will be disabled.)

Note that when you install multiple packages at the same time, all the packages are installed into the same package group.

A package group is assigned a name automatically; however, you choose the installation directory for the package group.

After you create the package group by successfully installing a product package, you cannot change the installation directory. The installation directory contains files and resources specific to the WebSphere Integration Developer package installed into that package group. Eclipse plug-ins in the product package that can potentially be used by other package groups are placed in the shared resources directory.

Shared resources directory

The shared resources directory is the directory where Eclipse plug-ins are located so that they can be used by one or more product package groups.

Chapter 4. Preinstallation tasks

Before you install the product, complete these steps:

1. Confirm that your system meets the requirements described in the section Chapter 2. Installation requirements.
2. Confirm that your user ID meets the required access privileges for installing the product. See User privileges requirements.
3. Read the section Chapter 3. Planning to install and give particular attention to the topic Coexistence considerations.
4. If you want to enable the product for use by users other than root, then you must set the umask variable to 0022 before you install the product. To set this variable, log in as root user, start a terminal session, and type umask 0022.

Chapter 5. Installation overview

The following sections provide an overview of the installation scenarios that are described in the section Installation scenarios. You can access detailed instructions from links in the main steps.

Installing from DVD

The following are the general steps for installing from DVDs:

1. Complete the preinstallation steps listed in Chapter 4. Preinstallation tasks.
2. Insert the first installation DVD into your DVD drive.
3. Mount the DVD drive.
4. If auto-run is enabled on your system, the WebSphere Integration Developer launchpad program automatically opens. If auto-run is not enabled and you are installing as an administrative user, start the launchpad program. Refer to Starting the launchpad program for details.
   Note: If IBM Installation Manager is not detected on your workstation, then it is installed at the same time as the WebSphere Integration Developer package.
5. If you are installing as a non-administrative user and the launchpad program is running, stop the launchpad program.
6. If you are installing as a non-administrative user, launch the userinst program. In a command line, change to the root directory of DVD 1 and issue the following command:
   • Run IM_win32\userinst.exe
   • Run IM_linux/userinst
7. Follow the on-screen instructions in the Install Packages wizard to complete the installation.
   Note: If you exit Installation Manager before completing the product installation, you must restart Installation Manager from the launchpad. If you start the Installation Manager directly, it is not preconfigured with the necessary installation repositories.
8. Increase the number of file handles on your workstation. For details, see Chapter 9. Increasing the number of file handles on Linux workstations.

To install any of the optional Lotus Forms software included with WebSphere Integration Developer 6.2, refer to Installing Lotus Forms software for instructions.

Installing from an installation image on your workstation

The following are the general steps for installing WebSphere Integration Developer from an electronic installation image:

1. Ensure that your workstation has sufficient space to store both the files you must download from IBM Passport Advantage and the extracted installation image. Refer to Hardware requirements.
2. Download all required parts for the product installation image from IBM Passport Advantage to a temporary directory.
3. Extract the downloaded files to a single directory.
   Note: Do not include spaces in the directory names when extracting the files, or you will not be able to run the launchpad.sh command to start the launchpad from a command line.
4. Continue with the steps in Installing from an installation image below.

Installing from an installation image

1. Complete the preinstallation steps listed in Chapter 4. Preinstallation tasks.
2. To install as an administrative user, start the launchpad program. For details, see Starting the launchpad program.

   If IBM Installation Manager is not detected on your workstation, then it is installed at the same time as the WebSphere Integration Developer package.

3. To install as a non-administrative user, start the userinst program. In a command line, change to the root directory of the installation image and issue the following command:
   • Run IM_win32\userinst.exe
   • Run IM_linux/userinst
4. Follow the on-screen instructions in the Install Packages wizard to complete the installation. For complete details, see Chapter 7. Installing with IBM Installation Manager.
   Note: If you exit Installation Manager before completing the product installation, you must restart Installation Manager from the launchpad. If you start the Installation Manager directly, it is not preconfigured with the necessary installation repositories.
5. Increase the number of file handles on your workstation. For details, see Chapter 9. Increasing the number of file handles on Linux workstations.

To install any of the optional Lotus Forms software included with WebSphere Integration Developer 6.2, refer to Installing Lotus Forms software for instructions.

Installing from an installation image on a shared drive

The following steps are performed by the person who places the installation image on a shared drive.

1. Ensure that your shared drive has sufficient disk space to store both the files you must download from IBM Passport Advantage and the extracted installation image. Refer to Hardware requirements for details.
2. Download all required parts for the product installation image from IBM Passport Advantage to a temporary directory on the shared drive.
3. Extract the installation image from the downloaded files into a single accessible directory on the shared drive.
   Note: Do not include spaces in the directory names when unzipping the files, or you will not be able to run the launchpad.sh command to start the launchpad from a command line.

To install WebSphere Integration Developer from the installation files on the shared drive:

1. Change to the directory containing the installation image on the shared drive.
2. Follow the steps in Installing from an installation image.

Chapter 6. Installing from the product launchpad program

Use the product launchpad program to start the installation of WebSphere Integration Developer in the following cases:

• Installing from the product DVDs
• Installing from an electronic installation image on your local file system
• Installing from an electronic installation image on a shared drive

By starting the installation process from the launchpad program, IBM Installation Manager is automatically installed if it is not already on your computer, and it is automatically configured with the location of the repository that contains the WebSphere Integration Developer package. If you install Installation Manager by itself and then use it to install WebSphere Integration Developer, then you must set the repository locations for WebSphere Integration Developer manually. See Setting repository preferences in Installation Manager for details about how to set repository preferences in Installation Manager.

To install from the launchpad:

1. Complete the preinstallation tasks described in Chapter 4. Preinstallation tasks, if you have not done so already.
2. Start the launchpad program. See Starting the launchpad program.
3. Click Install IBM WebSphere Integration Developer V6.2.

Follow the on-screen instructions in the Install Packages wizard to complete the installation. For complete details, see Chapter 7. Installing with IBM Installation Manager.

Starting the launchpad program

Complete the preinstallation tasks described in Chapter 4. Preinstallation tasks, if you have not done so already.

If you are installing from DVD and auto-run is enabled on your workstation, then the WebSphere Integration Developer launchpad starts automatically when you insert the installation disc into your DVD drive. If you are installing from an electronic installation image, or if auto-run is not configured on your workstation, then you must start the launchpad program manually.

To start the launchpad program:

1. Insert the first WebSphere Integration Developer DVD into your DVD drive. Ensure that you have mounted the DVD drive.
2. If auto-run is enabled on your system, the WebSphere Integration Developer launchpad program automatically opens. If auto-run is not enabled on your system:
   • Run launchpad.exe located in the root directory of the DVD.
   • Run launchpad.sh located in the root directory of the DVD.
3. In the Launchpad window (pictured below), click Install IBM WebSphere Integration Developer V6.2.
   
   IBM Installation Manager will automatically launch or install, and it will already be configured to install this software.
4. Install the product according to the instructions in Chapter 7. Installing with IBM Installation Manager.

For more information on how to install the Lotus Forms software, see Installing Lotus Forms software.

Chapter 7. Installing with IBM Installation Manager

If you are installing this product using the launchpad, then install manager has automatically been started and configured for you, so you may skip directly to Step 4.

1. Start Installation Manager. You will see a window like the one shown here.
   
   Note: If a newer version of Installation Manager is found, you are prompted to confirm that you want to install it before you can continue. Click OK to proceed. Installation Manager automatically installs the new version, restarts, and resumes.
2. Define the repository location according to the instructions in Setting repository preferences in Installation Manager and according to the following settings:

   Extracted installation image on your workstation

   Add the repository \image_directory\disk1\diskTag.inf or /image_directory/disk1/diskTag.inf

   Installation DVD

   Add the repository WID_DVD\diskTag.inf or WID_DVD/diskTag.inf

3. From the Installation Manager Start page, click Install Packages.
4. The Install page of the Install Packages wizard lists all the packages found in the repositories that Installation Manager searched. If two versions of a package are discovered, only the most recent, or recommended, version of the package is displayed.
   • To display all versions of any package found by Installation Manager, select the Show all versions check box.
   • To return to the display of only the recommended packages, clear the Show all versions check box.
5. To search for updates to the WebSphere Integration Developer package, click Check for Other Versions and Extensions.
   Note: For Installation Manager to search the predefined IBM update repository locations for the installed packages, the preference Search the linked repositories during installation and updates on the Repositories preference page must be selected. This preference is selected by default. Internet access is also required.
   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. A progress indicator shows the search is taking place. You can install updates at the same time that you install the base product package.
6. If updates for the WebSphere Integration Developer package are found, then they will be displayed in the Installation Packages list on the Install Packages page below their corresponding product. Only recommended updates are displayed by default.
   • To view all updates found for the available packages, select the Show all versions check box.
   • To display a package description under Details, click on the package name. If additional information about the package is available, such as a readme file or release notes, a More info link is included at the end of the description text. Click the link to display the additional information in a browser. To fully understand the package you are installing, review all information beforehand.
7. Select the WebSphere Integration Developer package and any updates to the package that you want to install. Updates that have dependencies are automatically selected and cleared together. Click Next to continue.
   Note: If you install multiple packages at the same time, then all the packages will be installed into the same package group.
8. On the Licenses page, read the license agreement for the selected package.

   If you selected more than one package to install, there might be a license agreement for each package. On the left side of the License page, click each package version to display its license agreement. The package versions that you selected to install (for example, the base package and an update) are listed under the package name.

   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.
9. If WebSphere Integration Developer 6.2 is the first package installed using Installation manager, type the path for the shared resources directory in the Shared Resources Directory field on the Location page, or accept the default path. ( 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. Click Next to continue. The default path for an installation by an administrator is:
   • C:\Program Files\IBM\SDPShared
   • /opt/IBM/SDPShared
   The default path for an installation by an non-administrator is:
   • user_home\IBM\SDPShared
   • user_home/IBM/SDPShared
   where user_home is the base directory of the user that is installing WebSphere Integration Developer.
   Important:

   1. You can specify the shared resources directory only the first time that you install a package. 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.
   2. Ensure that your installation path does not contain parenthesis.
10. On the next Location page, you can create a package group to install the WebSphere Integration Developer package into, or use an existing package group. A package group represents a directory in which packages share resources with other packages in the same group. By default, a new package group is created for WebSphere Integration Developer 6.2. If Installation Manager is aware of another package group, the Use the existing package group option is available for selection. To create a new package group:
    1. Select Create a new package group.
    2. Type the path for the installation directory for the package group. Ensure that your installation path does not contain parenthesis. ( Ensure that you do not include any spaces in the directory path.) The name for the package group is created automatically.

       The default path for installation by an administrator is:

       • C:\Program Files\IBM\WID62
       • /opt/IBM/WID62

       The default path for installation by an administrator is:

       • user_home\IBM\WID62
       • user_home/IBM/WID62
    3. Click Next to continue.
11. On the Languages page, choose all the languages that you would like to be able to have supported when you use this software, and click Next.
12. On the Features page, select the package features that you want to install.
    1. Optional: To see the dependency relationships between features, select the Show Dependencies check box.
    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.
13. On the Summary page, review your choices before installing the WebSphere Integration Developer 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.
14. 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 WebSphere Integration Developer to start when you exit.
    3. Click Finish to launch the selected package.

Installation log files

For detailed analysis, you can look at the logs generated in the Installation Manager data area. These logs are available at C:\Documents and Settings\All Users\Application Data\IBM\Installation Manager\logs and /var/ibm/InstallationManager/logs.

Chapter 8. Installing silently

Running Installation Manager in silent mode enables you to use a batch process to install, update, modify and uninstall product packages through scripts.

Note that you must install Installation Manager before you can silently install the WebSphere Integration Developer package. Refer to Working with IBM Installation Manager for details on installing Installation Manager.

There are two main tasks required for silent installation:

1. Create the response file.
2. Run Installation Manager in silent installation mode.

A sample response file is provided for you to use (see Reference: Sample response file).

Installing and running Installation Manager in silent mode

Refer to the Installation Manager Web site for additional documentation on how to run it in silent mode. For example, silently installing from a repository that requires authentication (user ID and password).

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

-vm

-nosplash

--launcher.suppressErrors

-silent

-input

-log

Both the Installation Manager installer and the Installation Manager have an initialization or .ini file silent-install.ini that includes default values for the arguments in the table.

The Installation Manager installer is used to install the Installation Manager. Follow these steps to install the Installation Manager silently.

To install Installation Manager silently, extract the installer and switch to the eclipse subdirectory in the extracted files, then use the following commands:

• installc --launcher.ini silent-install.ini -log <log file path and name> . For example: installc --launcher.ini silent-install.ini -log c:\mylogfile.xml
• 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

After Installation Manager is installed, you can use it to install other products or you can use the Installation Manager installer to install the products.

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

• 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
• 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

If you want to silently install products using the WebSphere Integration Developer installation image, from the eclipse subdirectory in the directory where you installed Installation Manager, enter the following command:

• installc.exe --launcher.ini silent-install.ini -input <response file path and name> -log <log file path and name>. For example: installc --launcher.ini silent-install.ini -input c:\mylog\responsefile.xml -log c:\mylog\silent_install_log.xml
• install --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

When the Installation Manager installer, or Installation Manager runs in silent installation mode; it reads the response file and writes a log file to the directory you specified. While you must have a response file when running in silent installation mode, log files are optional. The result of this execution should be a status of 0 on success and non-zero number on failure.

Searching for and silently installing all available products

To search for and silently install all available products:

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, substituting your own locations for the response file and, optionally, the log file:
   • IBMIMc.exe --launcher.ini silent-install.ini -installAll -log <log file path and name>
   • IBMIM --launcher.ini silent-install.ini -installAll -log <log file path and name>

All available products known to Installation Manager are installed.

Silently installing updates to all currently installed products

To search for and silently install updates for all available products:

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, substituting your own locations for the response file and, optionally, the log file:
   • IBMIMc.exe --launcher.ini silent-install.ini -updateAll -log <log file path and name>
   • IBMIM --launcher.ini silent-install.ini - -updateAll -log <log file path and name>

All available product updates known to Installation Manager are installed.

Creating a response file with Installation Manager

To record a response file for installation (or uninstallation):

1. On a command line, change to the eclipse subdirectory in the directory where you installed Installation Manager. If you installed as an administrator:
   • cd C:\Program Files\IBM\Installation Manager\eclipse
   • cd /opt/IBM/InstallationManager/eclipse
   If you installed as a non-administrator:
   • cd user_home\IBM\Installation Manager\eclipse
   • cd user_home/IBM/InstallationManager/eclipse
   where user_home is the home directory of the user that installed the Installation Manager.
2. On a command line, type the following command to start the Installation Manager, substituting your own file name and location for the response file and (optionally) the log file:
   • IBMIM -record <response file path and name> -log <log file path and name>. For example, IBMIM.exe -record c:\mylog\responsefile.xml -log c:\mylog\record_log.xml
   • You can record a response file without installing or uninstalling a product by adding the optional -skipInstall <agentDataLocation> argument. Note that <agentDataLocation> must be a writable directory. The argument causes the Installation Manager to save the installation data without installing the product. You can use the same <agentDataLocation> in the next recording session to record updates or modifications to the product, or to record license management. Note that the products installed or preferences, including repository settings, that you may have set on install when not using the -skipInstall argument are not be stored. Using -skipInstall will make installation faster because the IM is not installing the product, it is just recording the installation data.

     The syntax for using the skipInstall argument is: IBMIM -record <response file path and name> -skipInstall <a writable directory for agent data location>. For example IBMIM -record c:\mylog\responsefile.xml -skipInstall c:\temp\recordData

   Note: Ensure that the file paths you enter exist; Installation Manager will not create directories for the response file and the log file.
3. Follow the on-screen instructions in the Install Packages wizard to make your installation choices. For details, see Chapter 7. Installing with IBM Installation Manager.
4. Click Finish, then close Installation Manager.

An XML response file is created and resides in the location specified in the command.

Recording a response file with the Installation Manager installer

To record the installation of Installation Manager, follow these steps:

1. Unzip the Installation Manager, then go to the InstallerImage_platform directory.
2. To start recording, enter install -record <response file path and name> -skipInstall <agentDataLocation> -vmargs -Dcom.ibm.cic.agent.hidden=false

Recording a product install with the installer

To start recording a product install with the Installation Manager installer, follow these steps:

1. Go to the IM_platform directory in the location where you extracted the Installation Manager: \IM_win32 and /IM_linux
2. Open the install.ini file and remove the following lines: -input and @osgi.install.area/install.xml
3. Enter the following command: install -record <response file path and name> -skipInstall <agentDataLocation>, for example: install -record
4. Start the Installation Manager and complete the Install Packages wizard.

Response file commands

There are two categories of commands for the response file:

• Preference commands are used to set preferences that are found in Installation Manager under File -> Preferences, such as repository location information.
• Silent installation commands are used to emulate the Install Packages wizard in Installation Manager.

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:

Reference: Sample response file

A sample response file is included as \image_directory\disk1\util\responsefile_win.txt and /image_directory/disk1/util/responsefile_linux.txt in the extracted installation image, and as \WID_DVD\util\responsefile_win.txt and /WID_DVD/util/responsefile_linux.txt on the product DVDs.

Silent installation 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"></offering>

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

</install>

<uninstall modify="true">
<offering profile="profileID"
 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"/> 

<launcher -mode wizard -input 
< response file >

Silent install log files

The silent installation functionality creates an XML-based log file that records the result of the silent install execution (as long as a log file path is specified using -log <your log file path>.xml). If your silent installation session is successful, the log file will contain just the root element of <result> </result>. However, if errors occur during the installation, the silent install log file will contain error elements with messages such as:

<result>
	<error> Cannot find profile: profile id</error>
	<error> some other errors</error>
</result>

For detailed analysis, you can look at the logs generated in the Installation Manager data area. These logs are available at C:\Documents and Settings\All Users\Application Data\IBM\Installation Manager\logs and /var/ibm/InstallationManager/logs. By using a preference command, you can optionally set the data area to your preferred location, as shown in the response file topic.

Working with IBM Installation Manager

This section deals with some common tasks relating to IBM Installation Manager. For more information, see the Installation Manager online help.

Installing Installation Manager on Windows

If you start the installation of your product from the launchpad program, then the installation of IBM Installation Manager is performed automatically if it is not already installed on your workstation. (For more information on this process, refer to Chapter 6. Installing from the product launchpad program.) In other cases, you must manually start the installation of Installation Manager.

To start the installation of Installation Manager manually:

1. Run install.exe from the IM_win32 folder in the installation image.
2. Click Next on the Install Packages page.
3. Review the license agreement on the License Agreement page and select I accept the terms in the license agreement to accept. Click Next.
4. Click the Browse button on the Destination Folder page to change the installation location if required. Click Next.
5. Click Install on the Summary page. When the installation process is complete, a message confirms the success of the process.
6. Click Finish. IBM Installation Manager opens.

Installing Installation Manager on Linux

If you start the installation of your product from the launchpad program, then the installation of IBM Installation Manager is performed automatically if it is not already installed on your workstation. For more information on this process, refer to Chapter 6. Installing from the product launchpad program.

To install Installation Manager manually:

1. Open a terminal window with root user privileges.
2. Run install from the IM_linux folder in the installation image.
3. Click Next on the Install Packages screen.
4. Review the license agreement on the License Agreement page and select I accept the terms in the license agreement to accept. Click Next.
5. If necessary, edit the installation directory location. Click Next.
6. Click Install on the information summary page. When the installation process is complete, a message confirms the success of the process.
7. Click Finish. IBM If you start the installation of your product from the launchpad program, then the installation of IBM Installation Manager is performed automatically if it is not already installed on your workstation. opens.

Starting Installation Manager on Windows

If you start the installation of your product from the launchpad program, then the installation of IBM Installation Manager is performed automatically if it is not already installed on your workstation. This automatic installation starts Installation Manager with a configured repository preference and selected WebSphere Integration Developer packages. If you start Installation Manager directly, then you must set a repository preference and choose product packages manually. For more information, see Chapter 3. Planning to install.

To start Installation Manager manually:

1. Open the Start menu from the Taskbar.
2. Select All Programs -> IBM Installation Manager -> IBM Installation Manager.

Starting Installation Manager on Linux

If you start the installation of your product from the launchpad program, then the installation of IBM Installation Manager is performed automatically if it is not already installed on your workstation. This automatic installation starts Installation Manager with a configured repository preference and selected WebSphere Integration Developer packages. If you start Installation Manager directly, then you must set a repository preference and choose product packages manually. For more information, see Chapter 3. Planning to install.

To start Installation Manager manually:

1. Open a terminal window with root user privileges.
2. Change directory to the installation directory for Installation Manager (by default, /opt/IBM/InstallationManager/eclipse for an installation by a root user; user_home/IBM/InstallationManager/eclipse for an installation by a non-root user) and run IBMIM.

Uninstalling Installation Manager on Windows

To uninstall Installation Manager:

1. Open the Start menu from the Taskbar.
2. Select All Programs -> IBM Installation Manager -> Uninstall IBM Installation Manager.
3. Click Next on the Uninstall page. The Installation Manager is selected for uninstallation.
4. Click Uninstall in the Summary page.

Uninstalling Installation Manager on Linux

IBM Installation Manager must be uninstalled using the package management tool that is included with your Linux version.

To uninstall Installation Manager manually on Linux:

1. Open a terminal window with root user privileges.
2. Change directory to the uninstallation directory of Installation Manager. By default, this is /var/ibm/InstallationManager/uninstall.
3. Run ./uninstall.

Silently installing and uninstalling Installation Manager

Silently installing Installation Manager

To install Installation Manager silently, extract the installer and switch to the InstallerImage_platform subdirectory, then use the following commands:

• installc --launcher.ini silent-install.ini -log <log file path and name> . For example: installc --launcher.ini silent-install.ini -log c:\mylogfile.xml
• 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

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

Silently uninstalling Installation Manager from Windows

To silently uninstall Installation Manager on Windows:

1. From a command line, go to the uninstall directory for the Installation Manager. By default, this is C:\Documents and Settings\All Users\Application Data\IBM\Installation Manager\uninstall.
2. Enter the following command: uninstallc.exe --launcher.ini silent-uninstall.ini

Silently uninstalling Installation Manager on Linux

To silently uninstall Installation Manager on other platforms:

1. From a terminal window, go to the directory uninstallation directory of Installation Manager. By default, this is /var/ibm/InstallationManager/uninstall).
2. Run the following command: uninstall --launcher.ini silent-uninstall.ini

Chapter 9. Increasing the number of file handles on Linux workstations

Exercise caution when using the following these steps to increase your file descriptors on Linux. Failure to follow the instructions correctly might result in a computer that will not start correctly. For best results, have your system administrator perform this procedure.

To increase your file descriptors:

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
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.
   Important: If you decide to increase the number of file handles, do not leave an empty initscript file on your computer. If you do so, your workstation will not start up the next time that you turn it on or restart.
4. On the first line, type ulimit -n 4096 (the key here is that the number is significantly larger than 1024, the default on most Linux computers).
   CAUTION:
   Do not set this too high because it can seriously impact system-wide performance.
5. On the second line, type eval exec "$4".
6. Save and close the file after making sure you have done steps 4 and 5.
   Note: Ensure you have followed the steps correctly, as not doing this correctly will result in a workstation that does not boot.
7. Optional: Restrict your users or groups by modifying the limits.conf file in the etc 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, you might consider a smaller number in step 4 above (for example, 2048). You need to do this so that most users have a reasonably low limit on the number of allowable open files per process. If you used a relatively low number in step 4, it is less important to do this. However, if you choose to set a high number in step 4, refraining from establishing limits in the limits.conf file can seriously impact computer performance.

   The following is a sample limits.conf file would look that restricts all users and then sets different limits for others afterwards. This sample assumes you set descriptors to 8192 in step 4 earlier.

   *      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 example above 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 descriptors open, while user1 is in between the two. Make sure you read and understand the documentation contained within the limits.conf file before making your modifications.

For more information on the ulimit command, refer to the man page for ulimit.

Chapter 10. Starting WebSphere Integration Developer

To start WebSphere Integration Developer from the desktop environment:

Click Start -> Programs -> package group name -> IBM WebSphere Integration Developer 6.2 -> WebSphere Integration Developer 6.2. For example, click Start -> Programs -> IBM WebSphere Integration Developer -> IBM WebSphere Integration Developer 6.2 -> WebSphere Integration Developer 6.2

Select the product shortcut on the main menu under package group name -> WebSphere Integration Developer 6.2. For example, click IBM WebSphere Integration Developer -> WebSphere Integration Developer 6.2

To start WebSphere Integration Developer from a command-line:

From the package group installation directory, run the wid.exe command. By default, the package group installation directory is C:\Program Files\IBM\WID62 if you installed as an administrative user, user_home\IBM\WID62 if you installed as a non-administrative user.

From the package group installation directory, run the ./wid.bin command. By default, the package group installation directory is /opt/IBM/WID62 if you installed as an administrative user, user_home/IBM/WID62 if you installed as a non-administrative user.

Note: Ensure that the Windows date and time are correct and match the settings of your BIOS. If the date and time are not correctly set, WebSphere Integration Developer will fail to launch with the following error message:

Exception in org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.start() of bundle org.eclipse.equinox.p2.reconciler.dropins

WebSphere Integration Developer launches. If you chose to install the WebSphere Process Server or WebSphere Enterprise Service Bus test environment and the result of this installation was a partial success, the Test environment issues panel is displayed when you launch WebSphere Integration Developer. The types of error that can lead to a partial success include installation errors and profile creation errors. Read the description of the errors and take any necessary steps to resolve the problems. You can then choose to suppress this message in the future by selecting the issue in the upper pane and clicking Remove. The removal of the issue is not complete until you click OK. This Test environment issues panel is displayed each time you launch WebSphere Integration Developer until all issues have been resolved or removed.

Using the "-clean" option when starting WebSphere Integration Developer

WebSphere Integration Developer is based on the Eclipse Platform which caches all plugin.xml files into a single repository for quicker loading. If you used WebSphere Integration Developer before installing a new plug-in, you should start WebSphere Integration Developer once with the -clean option.

1. From a command line, change to the package group installation directory where you installed WebSphere Integration Developer.
2. Run the command wid.exe -clean or ./wid.bin -clean to start WebSphere Integration Developer.

This -clean option forces WebSphere Integration Developer to rebuild the Eclipse repository. This applies to anything that is installed into Eclipse by unzipping it into its plugins folder. The option also

• removes and regenerates manifest files.
• removes cached binaries and regenerates them from the newly created manifest files.
• removes and regenerates JXE information.
• removes and regenerates the runtime plug-in registry.

Beyond this it is up to each plug-in that is listed in the configuration directory to handle what it does when -clean is used.

It is a good practice to start up WebSphere Integration Developer using the -clean option after applying any Interim Fixes. This will ensure that the plug-in registry is regenerated to reflect any changes from the applied fixes. This only needs to be done once after applying any Interim Fix, as running with -clean takes considerable time in regenerating the plug-in registry.

Enabling the unit test environment for direct deployment

The IT administrator should set up the unit test environment as a test server when five or fewer business users will be testing process deployment. (Note that the license agreement refers to this setup of the unit test environment as the managed test environment.) If a larger number of business users need to test deployment, it is advisable to set up a managed deployment environment using WebSphere Process Server and, optionally, WebSphere Business Monitor.

It is recommended that you use one of

• Windows Server 2008
• SUSE Linux
• Red Hat Linux

as the operating system of your test server and that you have 3 GB RAM on this server. Other operating systems are supported, but as the number of testers increases the memory demands on the server increase and the listed operating systems are the preferred choice. WebSphere Business Monitor is not supported on Linux, if you intend to use both WebSphere Process Server and WebSphere Business Monitor it is recommended that you use Windows Server 2008.

An application is provided to enable the unit test environment for direct deployment. The application is called "TestController62". Take the following steps to install the application and enable your test environment for direct deployment.

1. Verify that TestController62.ear is installed.

   The application is installed automatically the first time that you use the integration test client. Perform the following steps to verify that the application is installed on your test server.

   1. On your test environment server, open the administrative console and browse to Applications -> Enterprise Applications.
   2. Look for the "TestController" application in the list of installed applications.
   3. If the application is installed then you do not need to do anything more.
   If the "TestController" application is not installed, complete the next step to install the application.
2. Install the "TestController" application.
   1. Browse to Applications > Install New Application.
   2. Click Browse and select TestController62.ear application from the WID_install\wid\util directory.
   3. Accept all default settings during installation.
   4. Save your configuration after installation.
3. Start the "TestController" application from the administrative console.

   Select the "TestController" application from the list and click Start.

Your test environment is enabled for direct deployment.

Chapter 11. Installing on Citrix Presentation Server

Follow these instructions to install WebSphere Integration Developer to run on Citrix Presentation Server.

1. When you install WebSphere Integration Developer on the server, ensure that you are logged on as a user with Administrator access.
2. After installing, ensure that the install directory is read-only. This is the product directory, not the shared install directory. This step will ensure that the configuration information is written in the home directory. If this measure is not taken, all users will end up using the same location for their configuration area, which is not supported.
   Note: Ensure that client users are granted write permission of the following directory otherwise the integrated test environment server status cannot be detected:<WID_install_root>\runtimes\base_v62_stub\
3. When launching WebSphere Integration Developer from a client, the workspace is created in a directory specified by the user.
4. In order to use the servers in the test environment, a profile is required for each non-root user. The product installer (who can be a root/Administrator or non-root user) can grant write permission to the appropriate WebSphere Process Server files and directories to other non-root users. The non-root users can then create profiles. Alternatively, the product installer can create a group for users who are authorized to create profiles or give individual users the authority to create profiles. The following example task shows how to create a group that is authorized to create profiles.

Configuring the Citrix Presentation Server

The installer can perform the following steps to create the "profilers" group and give the group appropriate permissions to create a profile.

1. Log on to the WebSphere Integration Developer system as the product installer (the product installer can be a root/Administrator or non-root user).
2. Using operating system commands, do the following:
   1. Create a group named "profilers", which will contain all users who can create profiles.
   2. Create a user named user1, who can create profiles.
   3. Add users product_installer and user1 to the profilers group.
3. Log off and log back on as the installer to pick up the new group.
4. As the product installer, use operating system tools to change directory and file permissions.
   1. The following example assumes that the variable $WASHOME is the WebSphere Process Server root installation directory /opt/IBM/WebSphere/ProcServer:

      export WASHOME=/opt/IBM/WebSphere/ProcServer
      echo $WASHOME
      echo "Performing chggrp/chmod per WAS directions..."
      chgrp profilers $WASHOME/logs/manageprofiles
      chmod g+wr  $WASHOME/logs/manageprofiles
      chgrp profilers $WASHOME/properties
      chmod g+wr  $WASHOME/properties
      chgrp profilers $WASHOME/properties/fsdb
      chmod g+wr  $WASHOME/properties/fsdb
      chgrp profilers $WASHOME/properties/profileRegistry.xml
      chmod g+wr  $WASHOME/properties/profileRegistry.xml
      chgrp -R profilers $WASHOME/profileTemplates

   2. Issue the following additional command where profile_template_name is default, dmgr, or managed, respectively:

      chmod -R g+wr $WASHOME/profileTemplates/profile_template_name/documents

      The ownership of files is preserved when the files are copied to the profile directory during profile creation. You granted write permission to the profile directory so that files copied to the profile directory can be modified as part of the profile creation process. Files that are already in the profileTemplate directory structure prior to the start of profile creation are not modified during profile creation.
   3. Issue the following additional commands:

      chgrp profilers $WASHOME/properties/Profiles.menu
      chmod  g+wr $WASHOME/properties/Profiles.menu

   4. The following example assumes that the variable $WASHOME is the WebSphere Process Server root installation directory C:\Program Files\IBM\WebSphere\ProcServer. Follow instructions in the Windows documentation to give the profilers group read and write permission to the following directories and their files:

      @WASHOME\logs\manageprofiles
      @WASHOME\properties
      @WASHOME\properties\fsdb
      @WASHOME\properties\profileRegistry.xml

      You might have to change the permissions on additional files if the non-root user encounters permission errors. For example, if the product installer authorizes a non-root user to delete a profile, then product installer might have to delete the following file:
   5. 

      install_root/properties/profileRegistry.xml_LOCK

   6. 

      install_root\properties\profileRegistry.xml_LOCK

      Give write access to the non-root user for the file to authorize the user to delete the file. If the non-root user still cannot delete the profile, then the product installer can delete the profile.

The installer created the profilers group and gave the group proper permissions to certain directories and files to create profiles. These directories and files are the only ones in the installation root of WebSphere Integration Developer to which a non-root user needs to write to create profiles.

Chapter 12. Modifying installations

To modify an installed product package:

1. From the Start page of the Installation Manager, click the Modify Packages icon.
2. In the Modify Packages wizard, select the installation location for the WebSphere Integration Developer product package and click Next.
3. On the Modify page, under Languages, select the languages for the package group, then 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.
4. On the Features page, select the package features that you want to install and/or deselect the features that you want to remove.
   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 the Show Dependencies check box. 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.
5. When you are finished selecting features, click Next.
6. On the Summary page, review your choices before modifying the installation package, and then click Modify.
7. Optional: When the modification process completes, click View Log File to see the complete log.

Chapter 13. Updating WebSphere Integration Developer

By default, Internet access is required unless your repository preferences points to your 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.

To find and install product package updates:

1. From the Start page of the Installation Manager, click Update Packages.
2. If IBM Installation Manager is not detected on your system or if an older version is already installed, then you must continue with the installation of the latest release. Follow the on-screen instructions in the wizard to complete the installation of IBM Installation Manager
3. In the Update Packages wizard, select the location of the package group where the WebSphere Integration Developer product package you want to update is installed or select the Update All check box, and then click Next. Installation Manager searches for updates in its repositories and the predefined update sites for WebSphere Integration Developer. A progress indicator shows the search is taking place.
4. If updates for a package are found, then they are displayed in the Updates list on the Update Packages page below their corresponding package. Only recommended updates are displayed by default. Click Show all to display all updates found for the available packages.
   1. To learn more about an update, click the update and review its description under Details.
   2. 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.
5. 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 and cleared together.
6. Click Next to continue.
7. 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.
   1. If you agree to the terms of all the license agreements, click I accept the terms of the license agreements.
   2. Click Next to continue.
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.
   Note: During the update process, Installation Manager might prompt you for the location of the repository for the base version of the package. If you installed the product from DVD or other media, they must be available when you use the update feature.
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.

Chapter 14. Uninstalling WebSphere Integration Developer

To uninstall the packages, you must log in to the system using the same user account that you used to install the product packages. A package cannot be uninstalled when another package has a dependency on it, unless the dependent package is also selected to be uninstalled.

To uninstall the packages:

1. Close the programs that you installed using Installation Manager.
2. On the Start page click Uninstall Packages.
3. In the Uninstall Packages page, select the WebSphere Integration Developer product package that you want to uninstall. Click Next.
4. In the Summary page, review the list of packages that will be uninstalled and then click Uninstall. The Complete page is displayed after the uninstallation finishes.
5. Click Finish to exit the wizard.

Preparing to reinstall WebSphere Integration Developer after a failed uninstallation

If Installation Manager, WebSphere Integration Developer, or WebSphere Process Server Unit Test Environment is still on your system, then these verification steps do not apply.

To perform a clean uninstallation, complete the following steps:

1. Completely remove IBM Installation Manager files:
   1. Verify that the following directories have been removed from your system:

      Directory	File path
      Application data directory Important: If you used Installation Manager to install other products besides WebSphere Integration Developer, do not delete the application data directory or you will lose the binaries of those products.	C:\Documents and Settings\All Users\Application Data\IBM\Installation Manager
      User-specific application data directory	C:\Documents and Settings\Username\IBM\Installation ManagerInstaller
      User temp directory Note: To determine the location of the temp directory, access the properties of My Computer, select the Advanced tab, and click Environment Variables.	C:\Documents and Settings\Username\Local Settings\Temp

2. Completely remove IBM WebSphere Integration Developer files:
   1. Delete the following directories:
      • C:\Program Files\IBM\WID62
      • C:\Program Files\SDPShared\
        Important: If you used Installation Manager to install other products besides WebSphere Integration Developer, do not delete the SDPShared directory or you will lose the binaries of those products.
3. Completely remove IBM WebSphere Process Server Unit Test Environment files:
   1. Follow the procedure in Preparing for reinstallation after a failed uninstallation on Windows systems (or Preparing for reinstallation after a failed uninstallation on Windows systems if you have WebSphere Process Server installed) to remove WebSphere Process Server Unit Test Environment files.
      Note: If this link fails, you need to install additional documentation. In WebSphere Integration Developer, open the Resource perspective if you are not already there (click Window > Open Perspective > Other > Resource). Then, in the main menu, click Help > Software Updates. In the Software Updates and Add-ons window, select the Available Software tab. Click Add Site and specify the following location: http://publib.boulder.ibm.com/dmndhelp/downloads/v6r2mx/wid/. Expand the results under this repository location, select the documentation that you want, and click Install. You will need to restart WebSphere Integration Developer to see the additional documentation.

Chapter 15. Rolling back updates

During the rollback process, Installation Manager must access files from the earlier version of the package. By default, these files are stored on your system when you install a package. If the files are not available on your workstation, you must include the location of the repository from which you installed the previous version of the product in your Installation Manager preferences (File > Preferences > Repository). If you installed the product from DVD or other media, they must be available when you use the rollback feature.

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, the 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.

See the help in the Installation Manager for more information on using the Rollback wizard.

To roll back an updated package, complete the following steps:

1. On the Start page, click Roll back Packages to start the Rollback wizard.
2. From the Installation Packages list, select the package that you want to roll back.
3. Complete the wizard according to the on-screen instructions.

Chapter 16. Installing optional software and documentation

Installing Lotus Forms software

The Lotus Forms software that is bundled with WebSphere Integration Developer includes:

• IBM Lotus Forms Designer 3.5
• IBM Lotus Forms Viewer 3.5
• IBM Lotus Forms Server - API 3.5

1. If you have downloaded the Lotus Forms software as individual compressed files, then extract them according to the following information. Otherwise, proceed to Step 2.
   1. Create the following folders, and extract the compressed files into them, where image_directory contains the extracted installation image for WebSphere Integration Developer 6.2.
   • For Lotus Forms Designer, \image_directory\forms_designer\
   • For Lotus Forms Viewer, \image_directory\forms_viewer\
   • For Lotus Forms Server - API, \image_directory\forms_server\ or /image_directory/forms_server/
2. On the Launchpad, select the product you wish to install as shown in this image.

   To begin the installation of each product, select the product on the WebSphere Integration Developer 6.2 Launchpad:

   
   Note: Only IBM Lotus Forms Server - API 3.5 is available for the Linux operating system.
3. Direct the Lotus Forms installation wizards to the folders that contain the installation material. If you are working with downloaded compressed files, then direct the installation wizards to the folders that you created in Step 1. Alternatively, if you have installation media for the Lotus Forms products, insert the DVD into the DVD drive, and direct the installation wizard to the root of the DVD.
4. Follow the on-screen instructions to complete the installation for each Lotus Forms product you choose to install. Note the important considerations documented below.

If you are installing into an existing IBM WebSphere Integration Developer package, and you do not accept the default installation directory presented by the Lotus Forms installation wizard, ensure that you select a valid installation directory where the WebSphere Integration Developer package is installed.

Note that the installation directory for a package is distinct from the directory where shared resources are installed. For example, shared resources are, by default, installed in:

• C:\Program Files\IBM\SDPShared\ for installations by an administrative user,
• user_home\IBM\SDPShared\ for installations by a non-administrative user,
• /opt/IBM/SDPShared/ for installations by an administrative user,
• user_home/IBM/SDPShared/ for installations by a non-administrative user.

Information for Lotus Forms Designer installations

• Select Add Designer to an existing IBM Software Development Platform package for the Installation Type.
  
• Install IBM Lotus Forms Designer 3.5 to the installation directory of WebSphere Integration Developer 6.2. For example, C:\Program Files\IBM\WID62\ if you installed WebSphere Integration Developer as an administrative user.

Information for Lotus Forms Server installations

• You must install the IBM WebSphere Process Server Test Environment package before you install Lotus Forms Server - API 3.5.
• Choose Runtime as the installation type in the installation wizard:
  
• Select the Deploy to WebSphere Application Server or to WebSphere Process Server check box in the installation wizard:
  
• The location of your installed WebSphere Process Server is \runtimes\bi_v62\ inside the installation directory of WebSphere Integration Developer 6.2. For example, C:\Program Files\IBM\WID62\runtimes\bi_v62\ if you installed WebSphere Integration Developer as an administrative user.
• The installation wizard panel that specifies details such as Profile, Cell and Node has a label indicating that these settings apply to WebSphere Application Server. These settings also apply to WebSphere Process Server. The values for these settings are filled in for you automatically.

  If you installed both the IBM WebSphere Process Server profile and the IBM WebSphere Enterprise Service Bus profile for the integrated test environment, select wps for Profile:

  
• For more information on installing Lotus Forms Server 3.5 - API, see Lotus Forms information center.

Installing Asset Repository

Asset Repository can be installed as a feature during the installation of WebSphere Integration Developer. If however, you already have WebSphere Integration Developer installed, and would like to add Asset Repository to it, here is how to proceed.

Follow the instructions in the topic Chapter 12. Modifying installations, and choose Asset Repository from the updates list.

For more information on Asset Repository, see Sharing assets.

Installing optional documentation

You must have started WebSphere Integration Developer and be connected to the Internet to complete these steps.

1. From the main menu change to the resource perspective.

   Click Window -> Open Perspective -> Other -> Resource.

2. Select Help -> Software Updates.
3. In the Software updates and Add-ons window, select the Available Software tab, click on Add Site and specify a location which points to http://publib.boulder.ibm.com/dmndhelp/downloads/wid/ and click OK.
4. Expand the search results and select the documentation features you wish to install. Click Install and complete the Install wizard. It is important that the specified installation directory for each feature selected is the same as the installation directory of WebSphere Integration Developer 6.2. For example, C:\Program Files\IBM\WID62\.

Once you restart WebSphere Integration Developer 6.2, you will see the installed documentation integrated with the WebSphere Integration Developer documentation in Help -> Help Contents. You will also benefit from certain links within the WebSphere Integration Developer help which provide you with additional information from a runtime perspective.

Notices

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 documentation does not grant you any license to these patents. You can send license inquiries, in writing, to:

For license inquiries regarding double-byte character set (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 document 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.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

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.

All IBM prices shown are IBM's suggested retail prices, are current and are subject to change without notice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject to change before the products described become available.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.

Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows:

© (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rights reserved.

If you are viewing this information softcopy, the photographs and color illustrations may not appear.

Programming interface information

Programming interface information, if provided, is intended to help you create application software using this program.

General-use programming interfaces allow you to write application software that obtain the services of this program's tools.

However, this information may also contain diagnosis, modification, and tuning information. Diagnosis, modification and tuning information is provided to help you debug your application software.

Warning: Do not use this diagnosis, modification, and tuning information as a programming interface because it is subject to change.

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. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. 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 current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.

Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.

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

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

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.

Terms of use

Personal Use: You may reproduce these publications for your personal, non commercial use provided that all proprietary notices are preserved. You may not distribute, display or make derivative work of these publications, or any portion thereof, without the express consent of IBM.

Commercial Use: You may reproduce, distribute and display these publications solely within your enterprise provided that all proprietary notices are preserved. You may not make derivative works of these publications, or reproduce, distribute or display these publications or any portion thereof outside your enterprise, without the express consent of IBM.

Except as expressly granted in this permission, no other permissions, licenses or rights are granted, either express or implied, to the publications or any information, data, software or other intellectual property contained therein.

IBM reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use of the publications is detrimental to its interest or, as determined by IBM, the above instructions are not being properly followed.

You may not download, export or re-export this information except in full compliance with all applicable laws and regulations, including all United States export laws and regulations.

IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. THE PUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

© Copyright IBM Corporation 2005, 2008. All Rights Reserved.