Before using this information and the product it supports, read the information in Notices at the end of this book.
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.
The following hardware must be installed before you install WebSphere Integration Developer:
The following software must be installed before you install WebSphere Integration Developer:
cd /opt tar xvfj mozilla-1.6-xft-gtk2-pc-linux.tar.bz2 mv mozilla mozilla-1.6-xft-gtk2-pc-linux cd /opt/ibm/WebSphere/ID/602
LD_LIBRARY_PATH=CURRDIR/eclipse/:/opt/mqm/lib:/opt/mqm/java/lib:/opt/wemps/lib:/opt/mozilla-1.6-xft-gtk2-pc-linux MOZILLA_FIVE_HOME=/opt/mozilla-1.6-xft-gtk2-pc-linux
cd /opt/mozilla-1.6-xft-gtk2-pc-linux/plugins tar xvfz install_flash_player_linux.tar.gz mv install_flash_player_7_linux/flashplayer.xpt . mv install_flash_player_7_linux/libflashplayer.so .Optional:
rm -rf install_flash_player_7_linux
cd /opt/mozilla-1.6-xft-gtk2-pc-linux ./mozilla
For more technical information on compatible browser versions, see http://www.eclipse.org/swt/faq.php#whatisbrowser
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.
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.
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 |
Definitions:
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.
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.
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:
If you do not perform this step, the WebSphere Process Server Integrated Test Environment might not install correctly when you reinstall WebSphere Integration Developer.
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.
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.
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.
To install WebSphere Integration Developer from the product installation CD, Disk 1, follow these steps:
Failure to use a short installation path 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.
If you receive a warning about a problem with registering the license towards the end of the install, follow these steps:
486604803 The requested license has expired 486604805 The start dates for all licenses have not yet occurredensure that your system clock is set correctly, and then start WebSphere Integration Developer.
Errors occurred during the installation - User cancelled installationWhen you attempt to uninstall the product in this state, you may receive the following error:
A suitable JVM could not be found. Please run the program again using the option -is:javahome <JAVA HOME DIR>.To work around this, you must rerun the installation program again to complete the previously canceled modification, and then proceed to uninstall the product.
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:
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:
The wizard cannot continue because of the following error: could not load wizard specified in /wizard.inf(104)The drive will need to be locally mapped by specifying a device name (for example, x:\sharename).
The WebSphere Integration Developer installation program can be run silently if you do not want to interact with the installation wizard.
Prior to silently installing WebSphere Integration Developer, you must set up your local images:
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 :
setup.exe -silent
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.
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.
Feature | Response file entry |
---|---|
Product installation directory | installLocation |
Integrated Test Environment
|
feature_wps6_win32.active
|
To silently install any of the optional features:
In this example, this line would be changed to:
-P feature_wps6_win32.active=true
-W profile_selection_panel_win32.wps=true
-W profile_selection_panel_win32.esb=true
setup.exe -options "Your_directory\myresponsefile.txt"
where Your_directory is the fully qualified
directory name of where your response file resides.setup.exe -silent -options "Your_directory\myresponsefile.txt"
where Your_directory is the fully qualified
directory name of where your response file resides.
To start WebSphere Integration Developer:
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.
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.
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.
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.
To uninstall WebSphere Integration Developer:
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.
To uninstall WebSphere Integration Developer silently:
wid_prod\_uninst\uninstall.exe -silent
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.
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 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.
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.
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.
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.
Method 1
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
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.
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
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.
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.
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.
To install WebSphere Integration Developer from the product installation CD, Disk 1, follow these steps:
If you are still having problems inserting the next CD, follow these steps:
mount CD_device
If you receive a warning about a problem with registering the license towards the end of the install, follow these steps:
486604803 The requested license has expired 486604805 The start dates for all licenses have not yet occurredensure that your system clock is set correctly, and then start WebSphere Integration Developer.
Errors occurred during the installation - User cancelled installationWhen you attempt to uninstall the product in this state, you may receive the following error:
A suitable JVM could not be found. Please run the program again using the option -is:javahome <JAVA HOME DIR>.To work around this, you must rerun the installation program again to complete the previously canceled modification, and then proceed to uninstall the product.
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:
chmod +x Extractor_WID602_Linux.bin
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:
The WebSphere Integration Developer installation program can be run silently if you do not want to interact with the installation wizard.
Prior to silently installing WebSphere Integration Developer, you must copy your local images:
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:
./setup.bin -silent
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.
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.
Feature | Response file entry |
---|---|
Product installation directory | installLocation |
Integrated Test Environment
|
feature_wps6_linux.active
|
To silently install any of the optional features:
In this example, this line would be changed to:
-P feature_wps6_linux.active=true
-W profile_selection_panel_linux.wps=true
-W profile_selection_panel_linux.esb=true
./setup.bin -options "Your_directory/myresponsefile.txt"
where Your_directory is the fully qualified
directory name of where your response file resides../setup.bin -silent -options "Your_directory/myresponsefile.txt"
where Your_directory is the fully qualified
directory name of where your response file resides.
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:
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.
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.
To start WebSphere Integration Developer, follow these steps:
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.
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.
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.
To uninstall WebSphere Integration Developer on Linux, follow these steps:
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.
To uninstall WebSphere Integration Developer silently:
wid_prod/_uninst/uninstall.bin -silent
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.
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.
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.
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.
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:
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:
Following are the steps to find and install product updates and optional features:
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.
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 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.