IBM WebSphere Integration Developer

Installation Guide

Version 6.0.2
Note

Before using this information and the product it supports, read the information in Notices at the end of this book.

Fifth Edition (December 2006)
Copyright International Business Machines Corporation 2006. All rights reserved.
US Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents

Installation requirements for WebSphere Integration Developer
Hardware requirements
Software requirements
Operating systems
Other software requirements
IBM Rational Software Development Platform and shell-sharing
Installing and uninstalling WebSphere Integration Developer on a Windows operating system
Migration, upgrade, and coexistence issues
Installing from the CD-ROM
Installing from electronic images
Creating a network installation image
Invoking a silent installation
Setting up your local images
Silently installing the default features to the default directory
Silently installing to a different directory
Silently installing additional WebSphere Integration Developer features
Starting WebSphere Integration Developer
Using the "-clean" option when starting WebSphere Integration Developer
Uninstalling WebSphere Integration Developer
Silently uninstalling WebSphere Integration Developer
Known problems and limitations
Recovering from failed installation
Uninstalling and reinstalling WebSphere Integration Developer may result in an unusable state
Uninstalling results in a failure
Installation of WebSphere Integration Developer on Windows Server 2003 SP1 or Windows XP SP2 failed
Integrated Test Environment fails to install
Integrated Test Environment fails to uninstall on Windows Server 2003
Installing and uninstalling WebSphere Integration Developer on Linux
Migration, upgrade, and coexistence issues
Installing from the CD-ROM
Installing from electronic images
Creating a network installation image
Invoking a silent installation
Setting up your local images
Silently installing the default features to the default directory
Silently installing to a different directory
Silently installing additional WebSphere Integration Developer features
Increasing the number of available file handles
Starting WebSphere Integration Developer
Using the "-clean" option when starting WebSphere Integration Developer
Uninstalling WebSphere Integration Developer
Silently uninstalling WebSphere Integration Developer
Known problems and limitations
Novell NetWare disk limitation
Uninstalling and reinstalling WebSphere Integration Developer may result in an unusable state
Uninstalling results in a failure
Integrated Test Environment fails to install
Failure to see Business Integration perspective as non-root user
Installing updates
Notices

Installation requirements for WebSphere Integration Developer

Review all hardware and software requirements before installing WebSphere(R) Integration Developer.

Plan your product installation and assess the compatibility of coexistent products. The information provided in IBM Rational Software Development Platform and shell-sharing helps to reduce compatibility issues by providing guidance on installing, updating, troubleshooting, uninstalling, and reinstalling WebSphere Integration Developer and other IBM(R) Rational(R) Software Development Platform (RSDP) products.

Hardware requirements

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

Software requirements

Operating systems

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

Other software requirements

IBM Rational Software Development Platform and shell-sharing

The IBM Rational Software Development Platform is a proven, open, complete, and modular solution that helps teams build, integrate, extend, modernize, and deploy software and software-based systems.

The IBM Rational Software Development Platform (RSDP) is a common development environment that is shared by several products, including:

If you install any of these products, the Rational Software Development Platform is automatically installed as part of the product. If you have more than one of the Rational Software Development Platform products installed, the development platform is installed only once. All of these products have the same user interface, called a workbench, and each product adds functionality to the workbench by contributing plug-ins. A plug-in is a software module that adds function to an existing program or application.

Important:
WebSphere Integration Developer 6.0.2 is compatible only with products based on Rational Software Development Platform 6.0.1.x (for example, Rational Application Developer 6.0.1.1). If a different version of Rational Application Developer is detected during the installation of WebSphere Integration Developer 6.0.2, you are required to either upgrade Rational Application Developer to 6.0.1.x (available at http://www.ibm.com/support) or uninstall your Rational Application Developer so that WebSphere Integration Developer 6.0.2 can be installed successfully.

Before you install any of the IBM Rational Software Development Platform products, investigate and plan your product installation. First, assess whether you need to install a single product or multiple products. For example, WebSphere Integration Developer might suit all your needs. This product provides business integration capabilities as well as Web, Web services, Java(TM) 2 Enterprise Edition (J2EE), and so on through its customizable Workbench (WebSphere Integration Developer workspace > Window > Preferences > Workbench > Capabilities).

In other cases, you might need to install more than one product, such as when your project includes both portal and Service Component Architecture (SCA) development. Because Portal Toolkit runs in conjunction with Rational Application Developer, you might need to have WebSphere Integration Developer, Rational Application Developer, and Portal Toolkit running in parallel. If you have a limited number of workstations with sufficient resources, consider having the two development environments coexist on a single workstation.

Migration and coexistence

The following chart illustrates what happens when you attempt to install more than one product, common to the Rational Software Development Platform, on the same machine. The vertical axis represents products already installed, while the horizontal axis represents products that you are attempting to install.

Attempt to install WebSphere Integration Developer Rational Software Modeler Rational Web Developer Rational Application Developer Rational Software Architect Rational Functional Tester Rational Performance Tester
WebSphere Integration Developer N/A Share Share Share Share Share Share
Rational Software Modeler Share1 Block2 N/A Share Share Upgrade Share Share
Rational Web Developer Share1 Block2 Share N/A Upgrade Upgrade Share Share
Rational Application Developer Share1 Block2 Share Block N/A Upgrade Share Share
Rational Software Architect Share1 Block2 Block Block Block N/A Share Share
Rational Functional Tester Share1 Block2 Share Share Share Share N/A Share
Rational Performance Tester Share1 Block2 Share Share Share Share Share N/A
Note:
  1. When version 6.0.1.1 of the Rational product is installed.
  2. When a version higher than 6.0.1.x of the Rational product is installed.

Definitions:

Shell-sharing environments

When Rational software products and WebSphere Integration Developer are installed on a single system, they share a single common framework. This approach is known as shell-sharing. The first product that you install also installs the common framework. When you install additional products, the existing framework is used and product-specific plug-ins only are installed. Shell-sharing is enforced and cannot be deactivated.

The common framework saves space and installation time. Workbenches associated with the installed products are integrated together so that you can view and access all the supported functions in a single session.

Shell-sharing demands that all products that you install are based on a compatible level of RSDP. If a product that you are installing is not based on a compatible level, the installation reports that it cannot work with the existing Rational installation, and specifies that you must upgrade the existing installation.

Installation requirement for WebSphere Integration Developer 6.0.2

If you already have Rational Application Developer installed, ensure that you have V6.0.1.x in order to be compatible with WebSphere Integration Developer 6.0.2. If you have an earlier or later version of Rational Application Developer, correct this incompatibility with the IBM Rational Product Updater before you install WebSphere Integration Developer 6.0.2.

Uninstalling and reinstalling in a shell-sharing environment

In a shell-sharing environment, you cannot uninstall and reinstall only one of the products due to limitations with the Rational Product Updater.

The following instructions include steps to manually delete product directories to remove artifacts that can cause an unstable environment after you reinstall the products. The instructions are required regardless of whether WebSphere Integration Developer is the only product installed or it is one of many Rational Software Development Platform products installed.

To uninstall Rational Software Development Platform products, complete the following steps:

  1. Uninstall all shell-sharing products.
  2. Delete all product directories for shell-sharing products, such as for WebSphere Integration Developer, WebSphere Process Server Integrated Test Environment, and Rational Application Developer. Perform this step regardless of whether you have installed the products to separate directories or in one location.
  3. If the WebSphere Process Server Integrated Test Environment fails to uninstall correctly:
    1. Use a text editor to open C:\Documents and Settings\username\.WASRegistry and C:\Documents and Settings\username\.WBIRegistry.
    2. Delete all old paths.
    3. Use a text editor to open C:\Windows\vpd.properties file.
    4. Delete all lines containing old path names. These lines typically start with WSBAA and WSEAA.

      If you do not perform this step, the WebSphere Process Server Integrated Test Environment might not install correctly when you reinstall WebSphere Integration Developer.

  4. Reinstall the products.

When a product is upgraded, it is removed and replaced by the higher-function product. If a newly upgraded product is subsequently uninstalled, the entire product is removed from the system. For example, if you install Rational Application Developer, then upgrade to Rational Software Architect, and later choose to uninstall Rational Software Architect, all plug-ins, including the common user interface, will be uninstalled - you will not revert back to Rational Application Developer. To replace Rational Application Developer, you must reinstall it.

If you have two or more products installed in a sharing scenario, the user interface is left in place until the last product is uninstalled. For example, if you have Rational Application Developer and Rational Performance Tester installed, and you uninstall Rational Application Developer, Rational Performance Tester (and the user interface) will still be on your system.

Note:
The user interface is installed in the installation directory of the first Rational Software Development Platform based product you install. It is not reinstalled with any other products, so if you upgrade your first product, you should not remove your first installation directory after the upgrade has completed, as it will still contain the user interface contents.

Installing and uninstalling WebSphere Integration Developer on a Windows operating system

This section provides the required steps to successfully install or uninstall WebSphere Integration Developer on Windows.

You can install WebSphere Integration Developer either from the CD-ROM or from electronic images that you download. An installation wizard is provided, but you can also install WebSphere Integration Developer either from a command prompt, or perform a silent installation, as outlined later in this documentation.

The installation program can also be run in an interactive console mode, which may be better suited for persons with accessibility requirements. The Accessibility Mode command line option:

-accessibility makes the runtime console mode wizard more friendly for screen reader programs. To run in console mode, run this command from the \setup directory on the first WebSphere Integration Developer installation CD: 

setup.exe -is:javaconsole -log @NONE -accessibility

Follow the prompts to complete the installation. Note that the -is:javaconsole option is critical when specifying the -accessibility option. If you do not specify this option, the installation program will hang. The -log @NONE option turns logging off to eliminate log information being listed in the command prompt window. If you experience any problem during the install, you may want to eliminate this option in order to collect log information.

Migration, upgrade, and coexistence issues

You cannot migrate from WebSphere Studio Application Developer Integration Edition v4.x.x. or 5.0.x to WebSphere Integration Developer. WebSphere Integration Developer can, however, coexist with either of these products. If desired, you can manually migrate workspaces, artifacts, and projects from Rational ClearCase(R), Clear Case LT, and CVS to WebSphere Integration Developer

You can migrate source artifacts from WebSphere Studio Application Developer Integration Edition 5.1.1 to WebSphere Integration Developer, or you can choose to coexist. Refer to the Migration Guide PDF or the Migration topic in the information center for detailed migration information.

Refer to IBM Rational Software Development Platform and shell-sharing for more information about the IBM Rational Software Development Platform and coexistence between other products based on this development platform.

Installing from the CD-ROM

To install WebSphere Integration Developer from the product installation CD, Disk 1, follow these steps:

  1. Read Migration, upgrade, and coexistence issues before you begin the installation procedure.
  2. Ensure that the user ID that you are using does not contain double-byte characters. The product installer will verify this and will display a message if a user ID with double-byte characters is being used.
  3. Insert Disk 1 into your CD drive.
  4. If autorun is enabled on your system, the installation launchpad program automatically opens. If autorun is disabled on your system, run launchpad.exe from the root of Disk 1 to display the WebSphere Integration Developer Launchpad window.
    1. Optional: You can bypass the launchpad and go straight to the WebSphere Integration Developer installation wizard by running setup.exe from the \setup directory on Disk 1. If you want to install WebSphere Integration Developer from a command prompt without using the graphical interface, run the setup.exe -console command from the \setup directory on Disk 1.
      Note:
      Canceling the installation of WebSphere Integration Developer through the console mode is limited. Once the installation of WebSphere Integration Developer begins, the installation cannot be canceled. You can cancel the installation during the preparation steps of the installation process, but there is no supported method of canceling the installation after files have begun to be copied to the hard drive. Clicking Ctrl+C will force the installation process to quit, but this is not recommended.
    WebSphere Integration Developer Launchpad
  5. From the WebSphere Integration Developer Installation Launchpad, select Install IBM WebSphere Integration Developer V6.0.2.
  6. Wait for the installation wizard to open, then click Next to continue the installation.
  7. Follow the on-screen instructions for tasks such as reading the license agreement and specifying the target installation directory.
  8. In the Features window, you can select the WebSphere Integration Developer features that you would like to install. You can return to the installation wizard and install optional features later.
  9. Click Next to display summary information of the WebSphere Integration Developer install.
    Note:
    The disk space requirement shown is the total number of bytes needed for all the files. The actual disk space needed can be considerably greater. In particular, if your disk is formatted as FAT32, the many small files can use disk space inefficiently due to the disk blocking structure that FAT32 uses.
  10. Click Next to install WebSphere Integration Developer.

    If you receive a warning about a problem with registering the license towards the end of the install, follow these steps:

    1. Go to the \logs subdirectory in your installation directory.
    2. Open license.log with a text editor.
    3. If license.log contains either of the following lines: 
      486604803  The requested license has expired
486604805  The start dates for all licenses have not yet occurred
      ensure that your system clock is set correctly, and then start WebSphere Integration Developer.
  11. The installation program takes some time to set up the development environment and initialize Eclipse. Eventually you will see a message confirming that the installation is complete. Click Next to complete the installation. Confirmation of successful WebSphere Integration Developer installation

Note:

Installing from electronic images

There are four downloadable parts for WebSphere Integration Developer. You must download the first three parts at a minimum; the fourth part is optional.

Before you install the product, you must have approximately 4 GB of disk space to store the full set of downloadable images plus another 4 GB of disk space to unpack the images.

To download and create the electronic installation image:

  1. Download all required parts and desired optional parts to the same temporary directory. If any optional parts are needed later, download the additional optional parts and rerun the extraction tool prior to attempting the install.
  2. Launch the Extractor_WID602_Win32.exe file located in your temporary directory. This starts the wizard that creates the installation image.
  3. Follow the instructions in the wizard to specify where you want to create the image and which features you want to include.
  4. After the image is created, if you want to install the product immediately, click Finish. Alternatively, you can clear the Start the installation wizard check box, and run the installation program later by launching disk1\launchpad.exe from the directory where you created the installation image.
  5. Follow the instructions described in the Installing from the CD-ROM section.

Creating a network installation image

You can place a copy of the installation image on a network drive so that users can install across a network.

In order to run the installation program from a network drive, you must either work with a downloaded electronic image of WebSphere Integration Developer or copy the contents of the CDs as described below.

You need approximately 4 GB of disk space to store CD content on the disk. To copy the files from the CDs:

  1. Insert the first WebSphere Integration Developer installation CD into your CD drive.
  2. Create a temporary directory on a network drive where you want to store the image (for example, network_drive:\install_image).
  3. Under the temporary directory, create a subdirectory called disk1. This subdirectory must be called disk1 and it must be in lower case.
  4. Copy all the files and directories on the first installation CD to the disk1 subdirectory in the temporary directory.
  5. Repeat steps 3 and 4 to copy the contents of the other five CDs to subdirectories called disk2, disk3, disk4, disk5 and disk6.

Note:

Invoking a silent installation

The WebSphere Integration Developer installation program can be run silently if you do not want to interact with the installation wizard.

Setting up your local images

Prior to silently installing WebSphere Integration Developer, you must set up your local images:

  1. Read Migration, upgrade, and coexistence issues before you begin the installation procedure.
  2. Ensure that the user ID that you are using does not contain double-byte characters. The product installer will verify this and will display a message if a user ID with double-byte characters is being used.
  3. Create a local or network installation image as described in Creating a network installation image. If you only want to install WebSphere Integration Developer, you only need to copy the information from the first five CDs.

Silently installing the default features to the default directory

The following feature is installed by default when silently installing WebSphere Integration Developer:

To install WebSphere Integration Developer silently with only the default selected features to the default directory system_drive:\Program Files\IBM\WebSphere\ID\602 :

  1. Copy your images as described in Setting up your local images, if you have not done so already.
  2. From the command line, change to the \disk1\setup directory in the temporary directory (for example, network_drive:\install_image\disk1\setup) that you created in the previous step.
  3. Run the following command: 
    setup.exe -silent
  4. Silently installing WebSphere Integration Developer may take a while to complete. To determine when the installation completes, you may monitor the \logs directory in the default installation directory periodically. If the license.log file appears, then the silent installation has completed.

Silently installing to a different directory

By changing the installLocation parameter, you can install WebSphere Integration Developer to a different directory. For example, if you want "d:\my softdev" to be your installation directory, follow the same steps as described in Silently installing the default features to the default directory, but run the following command: 

setup.exe -silent -P installLocation="d:\my softdev"

In this example, only the default features are installed.

Silently installing additional WebSphere Integration Developer features

WebSphere Integration Developer provides you with a sample response file that silently installs all the default features. This response file is called responsefile.txt and it is located in the \disk1\util directory. If you want to change the response file to install other features, it is recommended that you first make a backup copy of responsefile.txt.

You can update the response file to install optional WebSphere Integration Developer features. The following table shows the response file options and their corresponding entries in the response file.

Table 1. List of response file options.
Feature Response file entry
Product installation directory installLocation
Integrated Test Environment
  • WebSphere Process Server V6.0.2 profile
  • WebSphere Enterprise Service Bus V6.0.2 profile
 feature_wps6_win32.active
  • profile_selection_panel_win32.wps
  • profile_selection_panel_win32.esb

To silently install any of the optional features:

  1. Copy responsefile.txt to a new file, for example myresponsefile.txt.
  2. Edit your copy of the response file.
  3. Locate the line containing the installation feature name shown in the above table. For example, if you want to install the Integrated Test Environment, you would locate the following line in the response file:# -P feature_wps6_win32.active=<value>
  4. Make the following changes to this line:
    1. Remove the # in the first column.
    2. Change <value> to true.

    In this example, this line would be changed to: 

       -P feature_wps6_win32.active=true
  5. If the Integrated Test Environment feature is installed, you must enable at least one server profile:
  6. Save your changes.
  7. Copy your images as described in Setting up your local images, if you have not done so already.
  8. From the command line, change to the \disk1\setup directory in the temporary directory (for example, network_drive:\install_image\disk1\setup) that you created in the previous step.
  9. Before a silent install is initiated, it is recommended that you test the response file and verify that its settings are being registered in the installation wizard. If they are not, there is a problem with your response file settings or command syntax. To test the response file, run setup.exe without the -silent option: 
    setup.exe -options "Your_directory\myresponsefile.txt"
    where Your_directory is the fully qualified directory name of where your response file resides.
  10. Run setup.exe with the -silent option: 
    setup.exe -silent -options "Your_directory\myresponsefile.txt"
    where Your_directory is the fully qualified directory name of where your response file resides.
  11. Silently installing WebSphere Integration Developer may take a while to complete. To determine when the installation completes, you can monitor the \logs subdirectory in your installation directory periodically. If the license.log file appears, then the silent installation has completed.

Starting WebSphere Integration Developer

To start WebSphere Integration Developer:

  1. Select Start > Programs > IBM WebSphere >Integration Developer 6.0.2 > WebSphere Integration Developer.
  2. The first time that you start WebSphere Integration Developer, a dialog box opens with the default workspace directory already specified. By default, your work is stored in a directory called workspace, located in C:\Documents and Settings\youruserid\IBM\wid6.0. If you want to save your work somewhere else, you can change the name and location of the workspace.
    Note:
    When creating new workspaces, it is highly recommended that you shorten the default path to as few characters as possible. Otherwise, you may run into problems when your file path lengths exceed the Windows limitation of 256 characters.

    Failure to use short workspace file paths can lead to problems when building, deploying or deleting your applications. It is much easier to start with a short path than to try to correct the problem once it occurs.

  3. By default, the Use this as the default and do not ask again check box is cleared. If you keep the default value, a dialog box opens every time you start WebSphere Integration Developer, allowing you to switch workspaces. You may want to keep this default value, if, for example, you choose to maintain different workspaces for different projects.
    Tip:
    If the Use this as the default and do not ask again check box is selected, the dialog box will not open again, and WebSphere Integration Developer will start using the workspace from the previous session. You can change the default value after you have started the product in the Window > Preferences > Workbench > Startup and Shutdown page.
  4. Click OK. There will be a one-time delay while the workspace structure is created.

The workbench first opens to a series of welcome pages that provide a product overview and information about what's new, plus links to tutorials, samples, and external Web resources. Spend some time exploring these options. Notice as well the sources of information that are available from the Help menu.

By default, the online Help displays only the WebSphere Integration Developer book. The Rational Application Developer online Help can be enabled by clicking the Show all topics icon in the Help browser. Similarly, if you have other Rational Software Development Platform products installed, you can enable their online Help in the same manner.

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

The -clean option can be used on WebSphere Integration Developer startup and it performs several functions.

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 directory where you installed WebSphere Integration Developer (for example, drive:\Program Files\IBM\WebSphere\ID\602)
  2. Run the command wid.exe -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

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 insure 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.

Uninstalling WebSphere Integration Developer

To uninstall WebSphere Integration Developer:

  1. Make sure that your server is stopped.
    1. In the Business Integration perspective, click the Servers tab to open the Servers view.
    2. In the Servers view, right-click your server and select Stop.
    3. In the Status area of the Servers view, ensure that the status of the server is Stopped before you continue with the uninstallation.
  2. Close WebSphere Integration Developer.
  3. Open the Control Panel and then open the Add/Remove Programs window. Select IBM WebSphere Integration Developer 6.0.2 and click Change/Remove to uninstall.

All files in any plug-ins or features directories are automatically deleted, including user data and third-party plug-ins that reside in any of these directories. Your workspace directory, which contains your work, is not deleted. Some other directories remain:

If you try to partially uninstall one or more of the WebSphere Integration Developer required features, you will receive an error message similar to this: 

Invalid selection:
Unable to uninstall ide_required: root is not set for uninstall

To work around this problem, select the WebSphere Integration Developer V6.0.2 check box. The uninstallation panel will be reinitialized so that you may now uninstall WebSphere Integration Developer entirely, or clear the selection of features that you do not want to uninstall.

Silently uninstalling WebSphere Integration Developer

To uninstall WebSphere Integration Developer silently:

  1. Make sure that your server is stopped (see Uninstalling WebSphere Integration Developer).
  2. From a command prompt, go to your installation directory and type 
    wid_prod\_uninst\uninstall.exe -silent

Known problems and limitations

This section covers known problems and limitations with Windows installation and uninstallation of WebSphere Integration Developer. Refer to the product readme file or the online help for information about problems and limitations that affect actual use of the product.

Recovering from failed installation

If your installation fails, you must remove any WebSphere Integration Developer files that have been installed. If the directory where you intended to install WebSphere Integration Developer is empty, then the installation process has already removed any files that were installed and you can delete the empty directory.

Uninstalling and reinstalling WebSphere Integration Developer may result in an unusable state

Uninstalling WebSphere Integration Developer and reinstalling it to the same location may result in an unusable state. There are no error messages during the reinstallation to reflect this problem.

There are two possible solutions to address this problem. After uninstalling WebSphere Integration Developer, you can delete the entire installation directory before reinstalling, or you can reinstall WebSphere Integration Developer to a different location.

Uninstalling results in a failure

When uninstalling WebSphere Integration Developer, the following error message may appear at the end of the uninstall wizard: 

Errors occurred during the uninstallation.
An error occurred and product uninstallation failed.  Look at the log file
wid_install_dir\logs\wid_v602_uninstall.log for details.

This problem occurs because during the uninstallation, the uninstall wizard is unable to remove certain directory paths. This may be caused by a long install path or a process that has a lock on the directories.

To resolve problem, close the uninstall wizard and delete the WebSphere Integration Developer installation directory.

Installation of WebSphere Integration Developer on Windows Server 2003 SP1 or Windows XP SP2 failed

Problem

When installing WebSphere Integration Developer on Microsoft Windows Server 2003 SP1 or Windows XP SP2, you may see an exception similar to the following in the <installdir>/updater/workspace/.metadata/.log file:

!ENTRY org.eclipse.update.core 4 0 May 24, 2006 16:18:53.797
!MESSAGE Unable to remove C:\WID\wid_prod\update\eclipse\features\com.ibm.websphere.integration.developer.update_6.0.2"
from the file system. [java.lang.Exception]
!STACK 0
java.lang.Exception
at org.eclipse.update.internal.core.UpdateManagerUtils.removeEmptyDirectoriesFromFileSystem(UpdateManagerUtils.java:305)
at org.eclipse.update.internal.core.SiteFileContentConsumer.abort(SiteFileContentConsumer.java:239)
at org.eclipse.update.internal.core.FeatureExecutableContentConsumer.abort(FeatureExecutableContentConsumer.java:152)
at org.eclipse.update.core.Feature.install(Feature.java:511)
at org.eclipse.update.internal.core.SiteFile.install(SiteFile.java:78)
at org.eclipse.update.internal.core.ConfiguredSite.install(ConfiguredSite.java:121)
at org.eclipse.update.internal.core.ConfiguredSite.install(ConfiguredSite.java:85)
at org.eclipse.update.internal.operations.InstallOperation.execute(InstallOperation.java:73)
at org.eclipse.update.internal.operations.BatchInstallOperation.execute(BatchInstallOperation.java:85)
at com.ibm.orca.updater.actions.InstallUpdates.installFeatures(InstallUpdates.java:202)
at com.ibm.orca.updater.actions.InstallUpdates$1.run(InstallUpdates.java:156)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101)

The installation process finishes without completing the final step of license registration.

Cause

The problem is caused by the Data Execution Protection (DEP) feature that is included with the Athlon 64 processor (or CPUs with Hardware-Enforced capability) under Microsoft Windows XP SP2 or Windows Server 2003 SP1. Both Advanced Micro Devices(TM) (AMD) and Intel(R) Corporation have defined and shipped Windows-compatible architectures that are compatible with DEP. These CPUs enable data execution protection (also known as no-execute protection) so that Memory Manager can mark pages containing data as no-execute, to prevent execution of the data as code.

This feature can be useful for preventing malicious code from exploiting the computer's system files and Registry; however, it also stops any valid executables from updating them. The result is that users are no longer able to run WebSphere Integration Developer with DEP enabled, since running it requires executing the file wid.exe. It also prevents them from manually enrolling licenses after the installation because it requires running the file enroll.exe.

Here are the options that can be specified in the hidden system file C:\boot.ini to enable and disable DEP:

/NOEXECUTE=OPTIN Enables DEP for core system images and those specified in the DEP configuration dialog.

/NOEXECUTE=OPTOUT Enables DEP for all images except those specified in the DEP configuration dialog.

/NOEXECUTE=ALWAYSON Enables DEP on all images.

/NOEXECUTE=ALWAYSOFF Disables DEP.

Solution

Method 1

  1. Change the setting /NOEXECUTE to ALWAYSOFF (or replace /NOEXECUTE=OPTOUT with /EXECUTE=OPTOUT) in the hidden C:\boot.ini system file.
  2. Save the file and restart the computer.
  3. Run WebSphere Integration Developer after the computer restarts.

However, this method will lower the security of the computer by opening it to attacks from other malicious executables. It is important to turn on the firewall and anti-virus software while DEP is disabled.

Method 2

  1. Keep DEP enabled by setting /NOEXECUTE to OPTOUT in the C:\boot.ini file. It enables DEP for all images except those specified in the DEP configuration dialog.
  2. From the desktop, right mouse click on My Computer and choose Properties > Advanced, under Performance click Settings and under the Performance Options dialogue box choose the Data Execution Prevention tab.
  3. Select the radio button that says "Turn on DEP for all programs and services except those I select". Add both <installdir>\wid.exe and <installdir>\setup\lum\wid\enroll.exe to the exception list.

Integrated Test Environment fails to install

If you selected to install the Integrated Test Environment when you installed WebSphere Integration Developer and the installation fails, you will see the following message: 

Installation of the Integrated Test Environment has failed.
IBM WebSphere Integration Developer will still run, but the
Integrated Test Environment may not be available.

The log files in the installdir\logs directory may help determine the cause of the failure, specifically the log file prefixed with wps_v602. Typical failures include missing prerequisites and residual information from previous installations. Once the cause of failure has been determined and corrected, run WebSphere Integration Developer Uninstaller and select only the Integrated Test Environment to be uninstalled. Next, re-run the WebSphere Integration Developer Installer and select the Integrated Test Environment feature again.

Note that, by default, the Integrated Test Environment is installed in the \runtimes\bi_v6 subdirectory where WebSphere Integration Developer is installed.

Integrated Test Environment fails to uninstall on Windows Server 2003

On Windows Server 2003, if Terminal Server is installed and configured, the Integrated Test Environment may not be removed when you uninstall WebSphere Integration Developer. To remove it, run the following command from the directory where you installed the product (for example, C:\Program Files\IBM\WebSphere\ID\602): 

\runtimes\bi_v6\_uninstwbi\uninstall.exe -silent

Installing and uninstalling WebSphere Integration Developer on Linux

This section provides the required steps to successfully install or uninstall WebSphere Integration Developer on Linux.

This section contains information about installing WebSphere Integration Developer on Linux. You can install WebSphere Integration Developer either from the CD-ROM or from electronic images that you download. An installation wizard is provided, but you can also install WebSphere Integration Developer either from a command prompt, or perform a silent installation, as outlined later in this documentation.

The installation program can also be run in an interactive console mode, which may be better suited for persons with accessibility requirements. The Accessibility Mode command line option:

-accessibility makes the runtime console mode wizard more friendly for screen reader programs. To run in console mode, type this command on one line: 

CD_device/setup/setup.bin -is:javaconsole -log @NONE -accessibility

where CD_device by default is /media/cdrom on SuSE and /mnt/cdrom on Red Hat.

Follow the prompts to complete the installation. Note that the -is:javaconsole option is critical when specifying the -accessibility option. If you do not specify this option the installation program will hang. The -log @NONE option turns logging off to eliminate log information being listed in the console window. If you experience any problem during the install, you may want to eliminate this option in order to collect log information.

Important:
WebSphere Integration Developer requires a substantial number of files to run, causing the system to allocate a large number of file handles to it. More file handles will be required for every WebSphere Integration Developer tool that is run. It is not uncommon for the default limit of 1024 file handles per process to be exceeded, resulting in a failure of the tools and possibly the loss of your workspace. In order to avoid this failure, before you work with the product we recommend that users have their system administrator raise the number of file handles available for WebSphere Integration Developer users. Refer to Increasing the number of available file handles for instructions increasing the number of handles.

Migration, upgrade, and coexistence issues

You can migrate source artifacts from WebSphere Studio Application Developer Integration Edition v5.1.1 to WebSphere Integration Developer, or you can choose to coexist with WebSphere Integration Developer. Refer to the Migration Guide PDF or the Migration topic in the information center for detailed migration information.

You cannot migrate from WebSphere Studio Application Developer Integration Edition v4.x.x. or 5.0.x to WebSphere Integration Developer. WebSphere Integration Developer can, however, coexist with any of these products. If desired, you can manually migrate workspaces, artifacts, and projects from Rational ClearCase, Clear Case LT, and CVS to WebSphere Integration Developer.

Refer to IBM Rational Software Development Platform and shell-sharing for more information about the IBM Rational Software Development Platform and coexistence between other products based on this development platform.

Installing from the CD-ROM

Before you install the product, check that the umask setting for the terminal session used to install the product is set to 0022. This setting enables the product for use by users other than root. To set this variable, log in as root user, start a terminal session, and type umask 0022.

Note:
If your system is autorun enabled, ensure that your umask setting is set to 0022 before you attempt to install the product. If your umask setting is not set to 0022, do not install the product from the launchpad automatically opened by your system. Instead, close the launchpad and use the following steps to install the product from the installation CD.

To install WebSphere Integration Developer from the product installation CD, Disk 1, follow these steps:

  1. Read Migration, upgrade, and coexistence issues before you begin the installation procedure.
  2. Log in as root user.
  3. Start a terminal session.
  4. Type umask 0022 so the product can be used by users other than root.
  5. Insert Disk 1 into your CD drive. During the installation, you will need to insert the next CD. If you cannot open the CD-ROM to insert the next CD, check if:

    If you are still having problems inserting the next CD, follow these steps:

    1. If the installation program is still running, click Cancel.
    2. Log in as root user.
    3. If it is not already installed on your machine, install the psmisc RPM package that is available on the Linux distribution CD.
    4. Start the installation program.
    5. If you still have problems, type /sbin/fuser CD_device from another terminal to display the process using the CD-ROM.
    6. To get the detail of the process, type: ps <process_id>
  6. If the CD-ROM is not mounted, then mount it by typing: 
    mount CD_device
  7. Type: CD_device/launchpad.bin to display the WebSphere Integration Developer Launchpad window.
    1. Optional: You may run CD_device/setup/setup.bin on Disk 1 to launch the install program directly. If you want to install WebSphere Integration Developer from a console or telnet terminal without using the graphical interface, run the CD_device/setup/setup.bin -console command from Disk 1.
      Note:
      Canceling the installation of WebSphere Integration Developer through the console mode is limited. Once the installation of WebSphere Integration Developer begins, the installation cannot be canceled. You can cancel the installation during the preparation steps of the installation process, but there is not a supported method of canceling the installation after files have begun to be copied to the hard drive. Clicking Ctrl+C will force the installation to quit, but this is not recommended.
    WebSphere Integration Developer Launchpad
  8. From the WebSphere Integration Developer Installation Launchpad, select Install IBM WebSphere Integration Developer V6.0.2.
  9. Wait for the installation wizard to open and then click Next to continue the installation.
  10. Follow the on-screen instructions for tasks such as reading the license agreement and specifying the target installation directory.
  11. In the Features window, you can select the WebSphere Integration Developer features that you would like to install. You can return to the installation wizard and install optional features later.
  12. Click Next to display summary information of the WebSphere Integration Developer install.
  13. Click Next to continue installing WebSphere Integration Developer.
  14. When asked for the next CD, follow these steps:
    1. To open the CD-ROM, type: eject CD_device
    2. Insert the next CD into the CD-ROM.
    3. If auto-mount is not enabled, mount the CD-ROM by typing: mount CD_device
    4. Click OK to continue with the installation.

    If you receive a warning about a problem with registering the license towards the end of the install, follow these steps:

    1. Go to the /logs subdirectory of your installation directory.
    2. Open the license.log with a text editor.
    3. If the license.log contains either of the following lines: 
      486604803  The requested license has expired
486604805  The start dates for all licenses have not yet occurred
      ensure that your system clock is set correctly, and then start WebSphere Integration Developer.
  15. When WebSphere Integration Developer is installed, click Next to complete the installation. Confirmation of successful WebSphere Integration Developer installation

Note:

Installing from electronic images

There are four downloadable parts for WebSphere Integration Developer. You must download the first three parts at a minimum; the fourth part is optional.

Before you install the product, you must have approximately 4 GB of disk space to store the full set of downloadable images plus another 4 GB of disk space to unpack the images.

To download and create the electronic installation image:

  1. Download all required parts and desired optional parts to the same temporary directory. If any optional parts are needed later, download the additional optional parts and rerun the extraction tool prior to attempting the install.
  2. Modify the permissions on the Extractor_WID602_Linux.bin file that is located in this temporary directory by typing: 
    chmod +x Extractor_WID602_Linux.bin
  3. Launch the file by typing ./Extractor_WID602_Linux.bin. This starts the wizard that creates the installation image.
  4. Follow the instructions in the wizard to specify where you want to create the image and which features you want to include.
  5. After the image is created, if you want to install the product immediately, click Finish. Alternatively, you can clear the Start the installation wizard check box, and run the installation program later by launching disk1/launchpad.bin from the directory where you created the installation image.
  6. Follow the instructions described in the Installing from the CD-ROM section.

Creating a network installation image

You can place a copy of the installation image on a network drive so that users can install across the network.

In order to run the installation program from a network drive, you must either work with a downloaded electronic image of WebSphere Integration Developer or copy the contents of the CDs as described below.

You need approximately 4 GB of disk space to store CD content on the disk. To copy the files from the CDs:

  1. Log in as root user.
  2. Create a temporary directory (for example, install_image) on a network drive where you want to store the image.
  3. Insert the first WebSphere Integration Developer installation CD into your CD drive.
  4. Under the temporary directory, create a subdirectory called disk1. This subdirectory must be called disk1 and it must be in lower case.
  5. Copy all the files and directories on the first installation CD to the disk1 subdirectory in the temporary directory.
  6. Repeat steps 4 and 5 to copy the contents of the other five CDs to subdirectories called disk2, disk3, disk4, disk5 and disk6.

Note:
If your machine goes into standby mode during an installation from a network installation image, the installation may fail.

Invoking a silent installation

The WebSphere Integration Developer installation program can be run silently if you do not want to interact with the installation wizard.

Setting up your local images

Prior to silently installing WebSphere Integration Developer, you must copy your local images:

  1. Read Migration, upgrade, and coexistence issues before you begin the installation procedure.
  2. Create a local or network installation image as described in Creating a network installation image. If you only want to install WebSphere Integration Developer, you only need to copy the information from the first five CDs.

Silently installing the default features to the default directory

The following feature is installed by default when silently installing WebSphere Integration Developer:

To install WebSphere Integration Developer silently with only the default selected features to the default directory /opt/ibm/WebSphere/ID/602:

  1. Log in as root user.
  2. Copy your images as described in Setting up your local images, if you have not done so already.
  3. From the command line, change to the /disk1/setup directory in the temporary directory (for example, /tmp/install_image/disk1/setup) that you created in a previous section.
  4. Run the following command: 
    ./setup.bin -silent
  5. Silently installing WebSphere Integration Developer may take a while to complete. To determine when the installation completes, you may monitor the /logs subdirectory in your installation directory periodically. If the license.log file appears, then the silent installation has completed.

Silently installing to a different directory

By changing the installLocation parameter, you can install WebSphere Integration Developer to a different directory. For example, if you want "/my_softdev" to be your installation directory, follow the same steps that were just described, but run the following command: 

./setup.bin -silent -P installLocation="/my_softdev"

In this example, only the default features are installed.

Silently installing additional WebSphere Integration Developer features

WebSphere Integration Developer provides you with a sample response file. This response file is called responsefile.txt and it is located in the /disk1/util directory. If you want to change the response file to install other features, it is recommended that you first make a backup copy of responsefile.txt.

You can update the response file to install one or more optional WebSphere Integration Developer features. The following table shows the response file options and their corresponding entries in the response file.

Table 2. List of response file options.
Feature Response file entry
Product installation directory installLocation
Integrated Test Environment
  • WebSphere Process Server V6.0.2 profile
  • WebSphere Enterprise Service Bus V6.0.2 profile
 feature_wps6_linux.active
  • profile_selection_panel_linux.wps
  • profile_selection_panel_linux.esb

To silently install any of the optional features:

  1. Copy responsefile.txt to a new file, for example myresponsefile.txt.
  2. Edit your copy of the response file.
  3. Locate the line containing the installation feature name shown in the above table. For example, if you want to install the Integrated Test Environment, you would locate the following line in the response file: # -P feature_wps6_linux.active=<value>
  4. Make the following changes to this line:
    1. Remove the # in the first column.
    2. Change <value> to true.

    In this example, this line would be changed to: 

       -P feature_wps6_linux.active=true
  5. If the Integrated Test Environment feature is installed, you must enable at least one server profile:
  6. Save your changes.
  7. Log in as root user.
  8. Copy your images as described in Setting up your local images, if you have not done so already.
  9. From the command line, change to the /disk1/setup directory in the temporary directory (for example, /tmp/install_image/disk1/setup) that you created in the previous step.
  10. Before a silent install is initiated, it is recommended that you test the response file and verify that its settings are being registered in the installation wizard. If they are not, there is a problem with your response file settings or command syntax. To test the response file, run ./setup.bin without the -silent option: 
    ./setup.bin -options "Your_directory/myresponsefile.txt"
    where Your_directory is the fully qualified directory name of where your response file resides.
  11. Run ./setup.bin with the -silent option: 
    ./setup.bin -silent -options "Your_directory/myresponsefile.txt"
    where Your_directory is the fully qualified directory name of where your response file resides.
  12. Silently installing WebSphere Integration Developer may take a while to complete. To determine when the installation completes, you may monitor the /logs subdirectory of your installation directory periodically. If the license.log file appears, then the silent installation has completed.

Increasing the number of available file handles

Before you work with the product, it is recommended that you have your system administrator raise the number of file handles available for WebSphere Integration Developer users above the default limit of 1024 file handles per process.

Exercise caution when using the following steps to increase your file descriptors on Linux. Failure to follow the instructions properly could result in a machine that won't boot properly. Preferably, have your system administrator do this for you.

To increase your file descriptors:

  1. Login 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 machine, otherwise your machine will not boot the next time.
  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 machines).
    CAUTION:
    Do not set this too high, as it can seriously impact performance system-wide.
  5. On the second line, type eval exec "$4".
  6. Save and close the file after making sure you have done both steps 4 and 5.
    Important:
    Ensure you have followed the steps correctly, as not doing this correctly will result in a machine that does not boot.
  7. (Optional) Restrict your users or groups by modifying the limits.conf file in the etc/security directory. Both SuSE Linux Enterprise Server (SLES) Version 9 and Red Hat Enterprise Linux Version 3.0 have this file by default. If for some reason you do not have this file, you may want to consider a more conservative number in step 4 (like 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, not doing this can seriously impact the performance of your machine.

    Here's how a sample limits.conf file would look that restricts all users and then sets different limits for others afterwards. This sample assumes you used 8192 in step 4 above.

    *      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 is used to set the limits for all users first. These limits are lower than the following ones. 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.

Starting WebSphere Integration Developer

To start WebSphere Integration Developer, follow these steps:

  1. To start WebSphere Integration Developer from a command line, go to your installation directory and run the command: ./wid.bin.
  2. If you are working in Gnome (which is the Red Hat default), the product shortcut will be on the main menu under Programming > WebSphere Integration Developer. If you are working in KDE (which is the SuSE default) the product shortcut will be IBM WebSphere > Integration Developer V6.0.2 > WebSphere Integration Developer V6.0.2.
  3. The first time that you start WebSphere Integration Developer, a dialog box opens with the default workspace directory already specified. By default, your work is stored in a directory called workspace, located in the $HOME/IBM/wid6.0 directory. If you want to save your work somewhere else, you can change the name and location of the workspace.
  4. By default, the Use this as the default and do not ask again check box is cleared. If you keep the default value, a dialog box opens every time you start WebSphere Integration Developer, allowing you to switch workspaces. You may want to keep this default value, if, for example, you choose to maintain different workspaces for different projects.
    Tip:
    If the Use this as the default and do not ask again check box is selected, the dialog box will not open again, and WebSphere Integration Developer will start using the workspace from the previous session. You can change the default value after you have started the product in the Window > Preferences > Workbench > Startup and Shutdown page.

The workbench first opens to a series of welcome pages that provide a product overview and information about what's new, plus links to tutorials, samples, and external Web resources. Spend some time exploring these options. Notice as well the sources of information that are available from the Help menu.

By default, the online Help displays only the WebSphere Integration Developer book. The Rational Application Developer online Help can be enabled by clicking the Show all topics icon in the Help browser. Similarly, if you have other Rational Software Development Platform products installed, you can enable their online Help in the same manner.

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

The -clean option can be used on WebSphere Integration Developer startup and it performs several functions.

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 directory where you installed WebSphere Integration Developer (for example, /opt/ibm/WebSphere/ID/602)
  2. Run the command ./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

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 insure 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.

Uninstalling WebSphere Integration Developer

To uninstall WebSphere Integration Developer on Linux, follow these steps:

  1. Make sure that your server is stopped.
    1. In the Business Integration perspective, click the Servers tab to open the Servers view.
    2. In the Servers view, right-click your server and select Stop.
    3. In the Status area of the Servers view, ensure that the status of the server is Stopped before you continue with the uninstallation.
  2. Close WebSphere Integration Developer.
  3. Log in as root.
  4. Go to the wid_prod/_uninst/ subdirectory in your installation directory.
  5. Uninstall WebSphere Integration Developer by typing this command: ./uninstall.bin. If you are working in a file manager, you can click on the file to launch the uninstaller.

All files or features in any plug-ins or features directories are automatically deleted, including user data and third-party plug-ins that reside in any of these directories. Your workspace directory, which contains your work, is not deleted. Some other directories remain:

If you try to partially uninstall one or more of the WebSphere Integration Developer required features, you will receive an error message similar to this: 

Invalid selection:
Unable to uninstall ide_required: root is not set for uninstall

To work around this problem, select the WebSphere Integration Developer V6.0.2 check box. The uninstallation panel will be reinitialized so that you may now uninstall WebSphere Integration Developer entirely, or clear the selection of features that you do not want to uninstall.

Silently uninstalling WebSphere Integration Developer

To uninstall WebSphere Integration Developer silently:

  1. Make sure that your server is stopped (see Uninstalling WebSphere Integration Developer).
  2. From a command prompt, go to your installation directory and type 
    wid_prod/_uninst/uninstall.bin -silent

Known problems and limitations

This section covers known problems and limitations with Linux installation and uninstallation of WebSphere Integration Developer. Refer to the product readme file or the online help file for information about problems and limitations that affect actual use of the product.

Novell NetWare disk limitation

Uninstalling and reinstalling WebSphere Integration Developer may result in an unusable state

Uninstalling WebSphere Integration Developer and reinstalling it to the same location may result in an unusable state. There are no error messages during the reinstallation to reflect this problem.

There are two possible solutions to address this problem. After uninstalling WebSphere Integration Developer, you can delete the entire installation directory before reinstalling, or you can reinstall WebSphere Integration Developer to a different location.

Uninstalling results in a failure

When uninstalling WebSphere Integration Developer, the following error message may appear at the end of the uninstall wizard: 

Errors occurred during the uninstallation.
An error occurred and product uninstallation failed.  Look at the log file
wid_install_dir/logs/wid_v602_uninstall.log for details.

This problem occurs because during the uninstallation, the uninstall wizard is unable to remove certain directory paths. This may be caused by a long install path or a process that has a lock on the directories.

To resolve problem, close the uninstall wizard and delete the WebSphere Integration Developer installation directory.

Integrated Test Environment fails to install

If you selected to install the Integrated Test Environment when you installed WebSphere Integration Developer and the installation fails, you will see the following message: 

Installation of the Integrated Test Environment has failed.
IBM WebSphere Integration Developer will still run, but the
Integrated Test Environment may not be available.

The log files in the installdir/logs directory may help determine the cause of the failure, specifically the log file prefixed with wps_v602. Typical failures include missing prerequisites and residual information from previous installations. Once the cause of failure has been determined and corrected, run WebSphere Integration Developer Uninstaller and select only the Integrated Test Environment to be uninstalled. Next, re-run the WebSphere Integration Developer Installer and select the Integrated Test Environment feature again.

Note that, by default, the Integrated Test Environment is installed in the /runtimes/bi_v6 subdirectory where WebSphere Integration Developer is installed.

Failure to see Business Integration perspective as non-root user

You may not be able to see the Business Integration perspective if you are using the Linux platform on a restricted user account (non-root user).

To see this perspective, follow these steps:

  1. Shut down the workbench if it is started.
  2. Copy /home/user_id/.eclipse to a backup location, where user_id is the restricted user account.
  3. Launch wid.bin from the WebSphere Integration Developer installation location with the -clean option.

Installing updates

The Rational Product Updater is a tool that keeps track of all Rational Software Development Platform products installed on your system and searches for and installs product updates and optional new features.

The Product Updater is installed automatically with WebSphere Integration Developer (or along with the first Rational Software Development Platform product that you install). All subsequent Rational Software Development Platform products that you install are automatically registered with this tool. For these products, you can search for and automatically install the following kinds of updates:

Any dependencies between updates are automatically enforced. The Product Updater allows you to manage updates to all of your Rational Software Development Platform products from a single location. It will even update itself.

The Product Updater also enables you to perform these tasks:

Refer to the Product Updater's help system for detailed information on using the tool, which can be accessed as follows:

  1. To launch the Product Updater, in WebSphere Integration Developer select Help > Software Updates > IBM Rational Product Updater.
  2. In the Product Updater, select Help > Help Contents.

Following are the steps to find and install product updates and optional features:

  1. To search for available updates, click the Find Updates button. To search for new optional features, click the Find Optional Features button. (The same results are achieved when you first click the Updates tab or the Optional Features tab, respectively.) A progress indicator shows that update sites are being searched.
  2. For product updates:
    1. The Updates page shows the type and number of available updates (each denoted by a Icon for product update icon) for each installed product or feature. You can click on each update to display its description and detailed information. Review the detailed information before installing the update.
    2. Recommended updates are selected by default. Corequisite updates are automatically selected and deselected together. If you change any selections, you can restore the default by clicking the Set Recommended button.
    3. Click Install Updates to install the selected list of updates.
  3. For optional features:
    1. The Optional Features page shows the name and version of any new optional features (each denoted by a Icon for optional feature icon) that are available.
    2. Before installing any new feature, click on its name to review the detailed information.
    3. Select the list of features you want to install. You will receive a warning message if there are product updates that must be installed prior to installing a feature.
    4. Click Install Features to install the optional features you have selected.
  4. A dialog box shows the license agreement for the product updates or optional features that you have selected. Once you have read and accepted the license agreement, click OK to begin the installation. If you selected more than one item to install, you may need to accept more than one license agreement before the installation begins.

When the installation is finished, the progress indicator closes and a message confirming the success of the operation appears in the top pane of Product Updater. The product updates or optional features that you installed are removed from their respective pages and are added to the Installed Products page. Because fix packs are cumulative, only the highest fix pack level is shown. Interim fixes, if any, are listed below the product or feature to which they apply.

Notices

U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this documentation 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(R) 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 documentation. The furnishing of this documentation does not give you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing 
IBM Corporation 
North Castle Drive 
Armonk, NY 10504-1785 
U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku 
Tokyo 106, Japan

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 OR CONDITIONS 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:

Intellectual Property Dept. for WebSphere Integration Developer
IBM Canada Ltd.
8200 Warden Avenue
Markham, Ontario L6G 1C7
Canada

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this documentation and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

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.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples may 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 illustrates 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. 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 IBM's application programming interfaces.

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

(C) (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. (C) Copyright IBM Corp. 2000, 2006. All rights reserved.

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

Programming interface information

Programming interface information 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

See http://www.ibm.com/legal/copytrade.shtml.