Before using this information and the product it supports, be sure to read the general information under Notices.
This edition applies to version 6, release 1, of WebSphere Integration Developer.
This installation guide provides instructions for installing, updating and uninstalling WebSphere Integration Developer using IBM Installation Manager.
Refer to http://www.ibm.com/software/integration/wid/support/ for updated documentation and troubleshooting information.
IBM Installation Manager is a program that helps you install the WebSphere Integration Developer packages on your workstation. It also helps you update, modify, and uninstall this and other packages that you install. A package can be a product, a group of components, or a single component that is designed to be installed by the Installation Manager.
IBM Installation Manager offers a number of time-saving features. It keeps track of what you are about to install, software components that you have already installed, and components that are available for you to install. It searches for updates so you know that you are installing the latest version of a WebSphere Integration Developer product package. Installation Manager also provides tools for managing licenses for the product packages that it installs. It provides tools for updating and modifying packages. You can also use Installation Manager to uninstall product packages.
IBM Installation Manager comprises six wizards that make it easy to maintain your product packages through their lifecycles:
Managing your WebSphere Integration Developer package installation involves several different tasks, for example installing the package, applying updates, and adding additional features to the package.
The following table presents a list of objectives related to managing your WebSphere Integration Developer package, a set of high-level steps for accomplishing each objective, and the result of performing those steps.
Installation objective | Installation steps | Result |
---|---|---|
Install WebSphere Integration Developer as a stand-alone product. | Install the WebSphere Integration Developer package
into its own package group:
|
WebSphere Integration Developer product does not share a user interface or workbench with other Eclipse-based products. |
Install WebSphere Integration Developer into an existing
package group of compatible product(s).
Note: Installing WebSphere Integration
Developer into an existing Eclipse-only workbench environment is not supported. |
Install WebSphere Integration Developer into a package
group with other compatible Eclipse-based products:
|
WebSphere Integration Developer shares a user interface, or workbench, with all products installed in the same package group. |
Install WebSphere Integration Developer with the intention to install additional Eclipse-based products (for example, WebSphere Business Modeler) using Installation Manager in the future. | Install WebSphere Integration Developer into its own
package group:
|
WebSphere Integration Developer is installed first. Additional Eclipse-based product packages are installed later and share a user interface or workbench with WebSphere Integration Developer. |
Install WebSphere Process Server Test Environment after installing WebSphere Integration Developer | Install the WebSphere Process Server Test Environment
package:
|
WebSphere Process Server Test Environment is added to the same package group as WebSphere Integration Developer, and both products share a common user interface, or workbench. |
Install additional WebSphere Integration Developer features into an existing installation of WebSphere Integration Developer Version 6.1, or remove already-installed features from the WebSphere Integration Developer package. | Modify the installed WebSphere Integration Developer
package:
|
Additional WebSphere Integration Developer features are installed and are made available from the WebSphere Integration Developer workbench, for example, IBM WebSphere Adapters. Features which are deselected are removed. |
Install Updates to WebSphere Integration Developer | Use the Update Packages wizard to update the WebSphere
Integration Developer package:
|
Recommended fixes are downloaded and applied to the WebSphere Integration Developer package. |
Use WebSphere Integration Developer Version 6.1 in a different supported language. | Install the national language versions of the packages,
and modify the language setting for the package group:
|
Additional national language support is installed. This language setting applies to WebSphere Integration Developer and all packages installed in the same package group. |
Uninstall WebSphere Integration Developer | Use the Uninstall Packages wizard to uninstall the WebSphere
Integration Developer package:
|
WebSphere Integration Developer is uninstalled. Installation Manager and other products that were installed into the same package group remain installed. |
Install a set of Eclipse features and plug-ins into an existing installation of WebSphere Integration Developer Version 6.1 (for example, using Eclipse Update Manager) | Install Eclipse features and plug-ins into an existing
WebSphere Integration Developer installation:
|
Eclipse plug-ins are installed into the same package group as WebSphere Integration Developer and share the user interface or workbench with all products installed in the same package group. |
This section details hardware, software, and user privilege requirements that must be met in order to successfully install and run your software.
For the most up-to-date, detailed system requirements, refer to http://www.ibm.com/support/docview.wss?rs=2308&uid=swg27010621.
Previous versions of WebSphere Integration Developer cannot be upgraded to version 6.1. For example, WebSphere Integration Developer 6.0.2 cannot be upgraded to WebSphere Integration Developer 6.1. Different versions of WebSphere Integration Developer can co-exist on your workstation, but they must not be installed in the same directory.
The following hardware must be installed before you install WebSphere Integration Developer:
The following software must be installed before you install WebSphere Integration Developer:
In order to view certain product overview information,
links to tutorials, samples and migration information, a compatible browser
must be installed. Follow the steps below to install a compatible version
of Mozilla that can be used with WebSphere Integration Developer. These
changes will not replace your existing browser.
If you are using SUSE LINUX Enterprise Server, the following environment variable settings are required:
These can be set at the system level, user level, or within a script to launch the product.
To set these environment variables at the user level, add the above lines to your .profile file. In order for this to take effect you will need to logout and login again.
If this does not work or you are using another Linux distribution, use the following steps to install a compatible version of Mozilla that can be used with WebSphere Integration Developer; these changes will not replace your existing browser.
cd /opt/mozilla-1.7.12-gtk2+xft/plugins tar xvfz install_flash_player_9_linux.tar.gz mv install_flash_player_9_linux/flashplayer.xpt . mv install_flash_player_9_linux/libflashplayer.so .Optional:
rm -rf install_flash_player_9_linux
cd /opt/mozilla-1.7.12-gtk2+xft ./mozilla
export MOZILLA_FIVE_HOME=/opt/mozilla-1.7.12-gtk2+xft export LD_LIBRARY_PATH=$LD_LIBRARY:/opt/mozilla-1.7.12-gtk2+xft
For more technical information on compatible browser versions, see http://www.eclipse.org/swt/faq.php#whatisbrowser
You must have a user ID that meets the following requirements before you can install WebSphere Integration Developer.
Read all the topics in this section before you begin to install any of the product features. Effective planning and an understanding of the key aspects of the installation process can help ensure a successful installation.
There are a number of scenarios that you can follow when installing WebSphere Integration Developer.
The following are some of the factors that might determine your installation scenario:
These are the typical installation scenarios you might follow:
Note also that you can install updates at the same time that you install the base product package.
In this installation scenario, you have the DVD that contains the product package files, and typically you are installing WebSphere Integration Developer on your own workstation. Refer to Installing WebSphere Integration Developer from DVD: task overview for an overview of the steps.
In this scenario, you have downloaded the installation files from IBM Passport Advantage and you will install WebSphere Integration Developer on your own workstation. Refer to Installing WebSphere Integration Developer from an installation image on your workstation: task overview for an overview of the steps.
In this scenario, you will place the electronic installation image on a shared drive so that users in your enterprise can access the installation files for WebSphere Integration Developer from a single location. Refer to Installing WebSphere Integration Developer from an installation image on a shared drive: task overview for an overview of the steps.
You can customize your software product by selecting which features of WebSphere Integration Developer to install.
When you install the WebSphere Integration Developer product package using IBM Installation Manager, the installation wizard displays the features available in the product package. From the features list, you can select which features to install. A default set of features is selected for you (including any required features). Installation Manager automatically enforces any dependencies between features and prevents you from clearing any required features.
The following table shows the features of WebSphere Integration Developer that you can choose to install. Default selections of features to install may vary. If a feature has already been installed, it will not be selected by default and will not be installed again.
Feature | Description | Selected for installation by default |
---|---|---|
WebSphere Adapters | Adapters access programs and data on Enterprise Information Systems (EISs). | Yes
Available when WebSphere Integration Developer package is selected for installation. |
Portal tools | Provides tools to create, customize, test, debug, and deploy portal applications. The Portal development tools support IBM WebSphere Portal versions 5.1 and 6.0. | No
Available when WebSphere Integration Developer package is selected for installation. |
WebSphere Process Server profile | A profile is used to define a separate runtime environment, with separate command files, configuration files, and log files. The WebSphere Process Server profile enables you to run SCA applications, BPEL business processes, human tasks, transition tables, business rules, selectors, and other resources. You can also run mediation flows that are contained in mediation modules. If you intend to eventually deploy an integration module with one or more of these resources to a WebSphere Process Server production server, then you should install the WebSphere Process Server profile. | Yes
Available when WebSphere Process Test Environment package is selected for installation. |
WebSphere Enterprise Server Bus profile | A profile is used to define a separate runtime environment, with separate command files, configuration files, and log files. The WebSphere Enterprise Service Bus profile enables you to run mediation flows contained in mediation modules. However, you cannot run BPEL business processes, human tasks, business rules, selectors, and other resources. If you intend to eventually deploy your mediation module to a WebSphere Enterprise Service Bus production server, then you should install the WebSphere Enterprise Service Bus profile. | No
Available when WebSphere Process Test Environment package is selected for installation. |
In WebSphere Integration Developer 6.1, both administrative security and application security are enabled by default.
Server security, including administrative security and application security, is automatically enabled for those test environment servers that you choose to install with WebSphere Integration Developer 6.1. The default user ID and password for server security are admin and admin. However, it is strongly recommended that you change the default user ID and password to better secure your test environment servers and business integration applications.
Note that if you change the default user ID and password or disable or enable server security in a server administrative console, you must ensure that these changes are also specified for the same server in the server configuration editor or the Window -> Preferences -> Server -> Security preferences page of WebSphere Integration Developer.
Information about changing the default user ID and password, and about disabling or enabling server security, is found in the Security documentation in the WebSphere Integration Developer help: Help -> Help Contents -> WebSphere Integration Developer -> Managing security.
If you plan to install multiple IBM Eclipse-based products on the same workstation, review the information in this section.
Some products are designed to coexist and share function when they are installed in the same package group. A package group is a location where you can install one or more software products or packages to share a common user interface or workbench. When you install each package, you select whether you want to install the package to an existing package group, or whether you want to create a new one. IBM Installation Manager will block products that are not designed to share or do not meet version tolerance and other requirements. If you want to install more than one product at a time, the products must be able to share a package group.
Any number of eligible products can be installed to a package group. When a product is installed, its function is shared with all of the other products in the package group. If you install a development product and a testing product into one package group, when you start either of the products, you have both the development and testing functionality available to you in your user interface. If you add a product with modeling tools, all of the products in the package group will have the development, testing, and modeling functionality available.
If you want WebSphere Integration Developer 6.1 to coexist with a Rational software product (for example, Rational Application Developer for WebSphere Software), the Rational software product must be at version 7.0.0.5 or higher. When you have an earlier version of the Rational software product you must correct this incompatibility by updating the version to 7.0.0.5 or higher, or choose a new package group. When you want to add a Rational software product to the same package group as WebSphere Integration Developer 6.1, you must install it directly at the required 7.0.0.5 (or higher) level by searching for available updates during the Rational 7.0 installation (using Check for Other Versions and Extensions), or by pointing to the 7.0.0.5 update repository location along with the base Rational 7.0 repository location.
IBM Installation Manager retrieves product packages from specified repository locations.
If the WebSphere Integration Developer launchpad is used to start Installation Manager, the default repository information is passed to Installation Manager. If the Installation Manager is started directly, for example from the Start menu, you must specify an installation repositories that contain the product packages that you want to install. See Setting repository preferences in Installation Manager.
By default, IBM Installation Manager uses an embedded URL in each software development product to connect to a repository server over the Internet. Installation Manager then searches for the product packages as well as new features.
When you start the installation of Installation Manager from the WebSphere Integration Developer launchpad program, the location of the repository that contains the product package you are installing is automatically defined in IBM Installation Manager when it starts. However, if you start Installation Manager directly (for example, installing Installation Manager from a repository located on a Web server) then you must specify the repository preference (the URL for the directory that contains the product package) in Installation Manager before you can install the product package. Specify these repository locations on the Repositories page of the Preferences window.
By default, Installation Manager uses an embedded URL in each software development product to connect to a repository server through the Internet and search for installable packages and new features. Your organization may require you to redirect the repository to use intranet sites.
To add, edit, or remove a repository location in Installation Manager:
When you install the WebSphere Integration Developer package using IBM Installation Manager, you must choose a shared resource directory (if WebSphere Integration Developer is the first product to be installed using Installation Manager) and a package group.
During the installation process, you must specify a package group for the WebSphere Integration Developer package. A package group represents a directory in which packages share a common user interface or workbench with other packages in the same group. When you install the WebSphere Integration Developer package using Installation Manager, you can create a new package group or install the packages into an existing package group. (Some packages might not be able to share a package group, in which case the option to use an existing package group will be disabled.)
Note that when you install multiple packages at the same time, all the packages are installed into the same package group.
A package group is assigned a name automatically; however, you choose the installation directory for the package group.
After you create the package group by successfully installing a product package, you cannot change the installation directory. The installation directory contains files and resources specific to the WebSphere Integration Developer package installed into that package group. Eclipse plug-ins in the product package that can potentially be used by other package groups are placed in the shared resources directory.
The shared resources directory is the directory where Eclipse plug-ins are located so that they can be used by one or more product package groups.
There are a few tasks which should be completed before beginning the installation process.
Before you install the product, complete these steps:
There are four installation scenarios. Overviews for each of these scenarios are provided in this section.
The following sections provide an overview of the installation scenarios that are described in the section Installation scenarios. You can access detailed instructions from links in the main steps.
In this installation scenario, you have the DVD that contains the installation files, and typically you are installing WebSphere Integration Developer on your own workstation.
The following are the general steps for installing from a DVD:
To install any of the optional Lotus Forms software included with WebSphere Integration Developer 6.1, refer to Chapter 15. Installing optional software and documentation for instructions.
The following are the general steps for installing WebSphere Integration Developer from an electronic installation image:
To install any of the optional Lotus Forms software included with WebSphere Integration Developer 6.1, refer to Chapter 15. Installing optional software and documentation for instructions.
If IBM Installation Manager is not detected on your workstation, then it is installed at the same time as the WebSphere Integration Developer package.
In this scenario, you will place the electronic installation image on a shared drive so that users in your enterprise can access the installation files for WebSphere Integration Developer from a single location.
The following steps are performed by the person who places the installation image on a shared drive.
To install WebSphere Integration Developer from the installation files on the shared drive:
The product launchpad program provides you with a single location to view release information and start the installation process.
Use the product launchpad program to start the installation of WebSphere Integration Developer in the following cases:
By starting the installation process from the launchpad program, IBM Installation Manager is automatically installed if it is not already on your computer, and it is automatically configured with the location of the repository that contains the WebSphere Integration Developer package. If you install Installation Manager by itself and then use it to install WebSphere Integration Developer, then you must set the repository locations for WebSphere Integration Developer manually. See Setting repository preferences in Installation Manager for details about how to set repository preferences in Installation Manager.
To install from the launchpad:
Follow the on-screen instructions in the Install Packages wizard to complete the installation. For complete details, see Chapter 7. Installing WebSphere Integration Developer using the IBM Installation Manager graphical interface.
Complete the preinstallation tasks described in Chapter 4. Preinstallation tasks, if you have not done so already.
If you are installing from a DVD and autorun is enabled on your workstation, then the WebSphere Integration Developer launchpad starts automatically when you insert the installation disc into your DVD drive. If you are installing from an electronic installation image, or if autorun is not configured on your workstation, then you must start the launchpad program manually.
To start the launchpad program:
The following steps describe installing the WebSphere Integration Developer package with the Installation Manager GUI.
When the extracted installation image is on your workstation or when you have the WebSphere Integration Developer installation DVD, follow the steps in Setting repository preferences in Installation Manager to specify the repository location of the installation images for WebSphere Integration Developer, and for the WebSphere Process Server and WebSphere Enterprise Service Bus test environments by using the following information:
Once the repository location has been defined, complete the following steps in Installation Manager:
If you selected more than one package to install, there might be a license agreement for each package. On the left side of the License page, click each package version to display its license agreement. The package versions that you selected to install (for example, the base package and an update) are listed under the package name.
The default path is:
You can use install log files to examine the results of an installation session.
For detailed analysis, you can look at the logs generated in the
Installation Manager data area. These logs are available at
C:\Documents and
Settings\All Users\Application Data\IBM\Installation Manager\logs and
/var/ibm/InstallationManager/logs.
You can install the WebSphere Integration Developer product package by running Installation Manager in silent installation mode. When you run Installation Manager in silent mode, the user interface is not available; instead, Installation Manager uses a response file to input the commands that are required to install the product package. You can also install Installation Manager silently using the Installation Manager installer. You can then use the installer to silently install product packages.
Running Installation Manager in silent mode enables you to use a batch process to install, update, modify and uninstall product packages through scripts.
Note that you must install Installation Manager before you can silently install the WebSphere Integration Developer package. Refer to Working with IBM Installation Manager for details on installing Installation Manager.
There are two main tasks required for silent installation:
A sample response file is provided for you to use (see Reference: Sample response file).
Use the Installation Manager installer to install Installation Manager, then use Installation Manager to install product packages in silent installation mode from a command line.
Refer to the Installation Manager Web site for additional documentation on how to run it in silent mode. For example, silently installing from a repository that requires authentication (user ID and password).
The following table describes the arguments used with the silent installation command:
Argument | Description |
---|---|
-vm |
Specifies the Java launcher. In silent mode, always use java.exe on Windows, and java on other platforms. |
-nosplash |
Specifies that the splash screen should be suppressed. |
--launcher.suppressErrors |
Specifies that the JVM error dialog should be suppressed. |
-silent |
Specifies that the Installation Manager installer or Installation Manager should be run in silent mode. |
-input |
Specifies an XML response file as the input to Installation Manager installer or the Installation Manager. A response file contains commands that installer or Installation Manager runs. |
-log |
(Optional) Specifies a log file that records the result of the silent installation. The log file is an XML file. |
Both the Installation Manager installer and the Installation Manager have an initialization or .ini file silent-install.ini that includes default values for the arguments in the table.
The Installation Manager installer is used to install the Installation Manager. Follow these steps to install the Installation Manager silently.
To install Installation Manager silently, extract the installer and switch to the eclipse subdirectory in the extracted files, then use the following commands:
After Installation Manager is installed, you can use it to install other products or you can use the Installation Manager installer to install the products.
To run Installation Manager in silent mode, run the following command from the eclipse subdirectory in the directory where you installed Installation Manager:
If you want to silently install products using the WebSphere Integration Developer installation image, from the eclipse subdirectory in the directory where you installed Installation Manager, enter the following command:
When the Installation Manager installer, or Installation Manager runs in silent installation mode; it reads the response file and writes a log file to the directory you specified. While you must have a response file when running in silent installation mode, log files are optional. The result of this execution should be a status of 0 on success and non-zero number on failure.
You can silently search for and install updates for all available products.
To search for and silently install all available products:
All available products known to Installation Manager are installed.
You can silently search for and install updates for all currently installed products.
To search for and silently install updates for all available products:
All available product updates known to Installation Manager are installed.
You can create a response file by recording your actions as you install the WebSphere Integration Developer product package using Installation Manager, or when you install the Installation Manager installer. When you record a response file, all of the selections that you make in the Installation Manager GUI are stored in an XML file. When you run Installation Manager in silent mode, Installation Manager uses the XML response file to locate the repository that contains the package, select the features to install, and so on.
To record a response file for installation (or uninstallation):
The syntax for using the skipInstall argument is: IBMIM -record <response file path and name> -skipInstall <a writable directory for agent data location>. For example IBMIM -record c:\mylog\responsefile.xml -skipInstall c:\temp\recordData
An XML response file is created and resides in the location specified in the command.
You can use the Installation Manager installer to record the installation of Installation Manager and other products.
To record the installation of Installation Manager, follow these steps:
To start recording a product install with the Installation Manager installer, follow these steps:
If you want to use the silent installation capabilities of Installation Manager, you need to create a response file that contains all of the commands that Installation Manager must run. The recommended way to do this is to create a response file by recording your actions as you install the WebSphere Integration Developer package. However, you can create or edit a response file manually.
There are two categories of commands for the response file:
While you typically specify preferences using the Preferences window, you can also specify preferences (identified as keys) in a response file for use during a silent installation.
When you define preferences in a response file, your XML code will look similar to the following example:
<preference name = "the key of the preference" value = "the value of the preference to be set"> </preference>
Use the following table to identify keys and their associated values for silent installation preferences:
You can use an XML-based response file to specify predefined information such as silent installation preferences, repository locations, installation profiles, and so on. Response files are beneficial for teams and companies that want to install installation packages silently and to standardize the locations and preferences for installation packages.
A sample response file is included as
\image_directory\disk1\util\responsefile_win.txt and
/image_directory/disk1/util/responsefile_linux.txt in the extracted installation image, and as
\<WID_DVD>\util\responsefile_win.txt and
/<WID_DVD>/util/responsefile_linux.txt on the DVD.
You can use this reference table to learn more about response file commands for use during a silent installation.
You can use silent install log files to examine the results of a silent installation session.
The silent installation functionality creates an XML-based log file that records the result of the silent install execution (as long as a log file path is specified using -log <your log file path>.xml). If your silent installation session is successful, the log file will contain just the root element of <result> </result>. However, if errors occur during the installation, the silent install log file will contain error elements with messages such as:
<result> <error> Cannot find profile: profile id</error> <error> some other errors</error> </result> |
For detailed analysis, you can look at the logs generated in
the Installation Manager data area. These logs are available at
C:\Documents and
Settings\All Users\Application Data\IBM\Installation Manager\logs and
/var/ibm/InstallationManager/logs.
By using a preference command, you can optionally set the data area to your
preferred location, as shown in the response file topic.
This section deals with some common tasks relating to IBM Installation Manager. For more information, see the Installation Manager online help.
If you start the installation of your product from the launchpad program, then the installation of IBM Installation Manager is performed automatically if it is not already installed on your workstation. (For more information on this process, refer to Chapter 6. Installing WebSphere Integration Developer from the product launchpad program.) In other cases, you must manually start the installation of Installation Manager.
To start the installation of Installation Manager manually:
If you start the installation of your product from the launchpad program, then the installation of IBM Installation Manager is performed automatically if it is not already installed on your workstation. For more information on this process, refer to Chapter 6. Installing WebSphere Integration Developer from the product launchpad program.
To install Installation Manager manually:
If you start the installation of your product from the launchpad program, then the installation of IBM Installation Manager is performed automatically if it is not already installed on your workstation. This automatic installation starts Installation Manager with a configured repository preference and selected WebSphere Integration Developer packages. If you start Installation Manager directly, then you must set a repository preference and choose product packages manually. For more information, see Chapter 3. Planning to install.
To start Installation Manager manually:
If you start the installation of your product from the launchpad program, then the installation of IBM Installation Manager is performed automatically if it is not already installed on your workstation. This automatic installation starts Installation Manager with a configured repository preference and selected WebSphere Integration Developer packages. If you start Installation Manager directly, then you must set a repository preference and choose product packages manually. For more information, see Chapter 3. Planning to install.
To start Installation Manager manually:
To uninstall Installation Manager:
IBM Installation Manager must be uninstalled using the package management tool that is included with your Linux version.
To uninstall Installation Manager manually on Linux:
IBM Installation Manager can be silently installed and uninstalled.
To install Installation Manager silently, extract the installer and switch to the InstallerImage_platform subdirectory, then use the following commands:
After installation, you can use Installation Manager or the Installation Manager installer to silently install packages.
To silently uninstall Installation Manager on Windows:
To silently uninstall Installation Manager on other platforms:
For best results, before you work with your product, increase the number of file handles available for WebSphere Integration Developer, because it uses more than the default limit of 1024 file handles per process. A system administrator might need to make this change.
Exercise caution when using the following these steps to increase your file descriptors on Linux. Failure to follow the instructions correctly might result in a computer that will not start correctly. For best results, have your system administrator perform this procedure.
To increase your file descriptors:
The following is a sample limits.conf file would look that restricts all users and then sets different limits for others afterwards. This sample assumes you set descriptors to 8192 in step 4 earlier.
Note that the * in the example above sets the limits for all users first. These limits are lower than the limits that follow. The root user has a higher number of allowable descriptors open, while user1 is in between the two. Make sure you read and understand the documentation contained within the limits.conf file before making your modifications.
For more information on the ulimit command, refer to the man page for ulimit.
You can start WebSphere Integration Developer from the desktop environment or a command-line interface.
To start WebSphere Integration Developer from the desktop environment:
Click Start -> Programs -> package
group name -> IBM WebSphere Integration Developer
6.1 -> WebSphere Integration Developer 6.1. For example, click Start -> Programs -> IBM WebSphere Integration Developer -> IBM WebSphere Integration Developer 6.1 -> WebSphere
Integration Developer 6.1
If the installation
location or shared resources directory for WebSphere Integration Developer
is in a directory in the path C:\Program Files\, then
you must run WebSphere Integration Developer as the administrator. To run
as administrator, right-click the program shortcut and click Run
as administrator.
On Windows Vista, the Program Files directory is virtualized in order to allow users who are not running as the administrator to have write access to this protected directory. However, the virtualization workaround is not compatible with WebSphere Integration Developer.
If you selected an installation location or shared resources directory in the path C:\Program Files\ on Windows Vista and you do not want to require running WebSphere Integration Developer as administrator, then complete one of the following steps:
Select the product shortcut on the main menu under package group name -> WebSphere
Integration Developer 6.1. For example, click IBM WebSphere Integration Developer -> WebSphere
Integration Developer 6.1
To start WebSphere Integration Developer from a command-line:
From the package group installation
directory, run the wid.exe command. By default, the package
group installation directory is C:\Program Files\IBM\WID61 for
Windows XP and Windows Server, and C:\Program Files_IBM\WID61 for
Windows Vista installations.
From the package group installation directory,
run the ./wid.bin command. By default, the package group
installation directory is /opt/IBM/WID61.
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 ensure that the plug-in registry is regenerated to reflect any changes from the applied fixes. This only needs to be done once after applying any Interim Fix, as running with -clean takes considerable time in regenerating the plug-in registry.
The Modify Packages wizard in the IBM Installation Manager enables you to change the language and feature selections of an installed product package.
To modify an installed product package:
You can install updates for packages that were installed using IBM Installation Manager.
By default, Internet access is required unless your repository preferences points to your local update site.
Each installed package has the location embedded for its default IBM update repository. For Installation Manager to search the IBM update repository locations for the installed packages, the preference Search service repositories during installation and updates on the Repositories preference page must be selected. This preference is selected by default.
See the Installation Manager help for more information.
To find and install product package updates:
The Uninstall Packages option in the Installation Manager enables you to uninstall packages from a single installation location. You can also uninstall all the installed packages from every installation location.
To uninstall the packages, you must log in to the system using the same user account that you used to install the product packages. A package cannot be uninstalled when another package has a dependency on it, unless the dependent package is also selected to be uninstalled.
To uninstall the packages:
Using the Roll back Packages wizard, you can remove an update to a package and revert to a previous version.
During the rollback process, Installation Manager must access files from the earlier version of the package. By default, these files are stored on your system when you install a package. If the files are not available on your workstation, you must include the location of the repository from which you installed the previous version of the product in your Installation Manager preferences (File > Preferences > Repository). If you installed the product from DVD or other media, they must be available when you use the rollback feature.
Use the rollback feature if you have applied an update to a product package, and decide later that you want to remove the update and revert to the earlier version of the product. When you use the rollback feature, the Installation Manager uninstalls the updated resources, and reinstalls the resources from the previous version. You can only roll back one version level at a time.
See the help in the Installation Manager for more information on using the Rollback wizard.
To roll back an updated package, complete the following steps:
Additional software is made available with WebSphere Integration Developer 6.1 and can optionally be installed.
The following optional software is included with WebSphere Integration Developer:
To begin the installation of each product, select the product on the WebSphere Integration Developer 6.1 Launchpad:
If you have the electronic installation image of WebSphere Integration Developer 6.1 extracted to \image_directory\, the Lotus Forms installation wizards need to be directed as follows:
where image_directory contains the extracted installation image for WebSphere Integration Developer 6.1.
If you have installation media for the Lotus Forms products, insert the CD into the CD drive, and direct the installation wizard to the root of the CD.
If you are installing into an existing IBM WebSphere Integration Developer package, and you do not accept the default installation directory presented by the Lotus Forms installation wizard, ensure that you select a valid installation directory where the WebSphere Integration Developer package is installed.
Note that the installation directory for a package is distinct
from the directory where shared resources are installed. For example, shared
resources are installed in
C:\Program Files\IBM\SDP70Shared\ and
/IBM/SDP70Shared/ by
default.
If you are installing Lotus Forms Designer 3.0, note the following items:
If you are installing Lotus Forms Server - API 3.0, note the following items:
If you installed both the IBM WebSphere Process Server profile and the IBM WebSphere Enterprise Service Bus profile for the integrated test environment, select wps for Profile:
You can install the product documentation for WebSphere Process Server and WebSphere Enterprise Service Bus.
You must have started WebSphere Integration Developer and be connected to the Internet to complete these steps.
Once you restart WebSphere Integration Developer 6.1, you will see the installed documentation integrated with the WebSphere Integration Developer documentation in Help -> Help Contents. You will also benefit from certain links within the WebSphere Integration Developer help which provide you with additional information from a runtime perspective.
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, 2007. 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.
IBM, IBM Logo, WebSphere, Rational, DB2, Universal Database DB2, Tivoli, Lotus, Passport Advantage, developerWorks, Redbooks, CICS, z/OS, and IMS are trademarks or registered trademarks of International Business Machines Corporation in the United States or other countries or both.
UNIX is a registered trademark of The Open Group in the United States, other countries, or both.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Microsoft and Windows are trademarks or registered trademarks of Microsoft Corporation in the United States, other countries, or both.
Linux is a trademark of Linus Torvalds in the United States, other countries, or both.
Adobe is either a registered trademark or trademark of Adobe Systems Incorporated in the United States, other countries, or both.
Other company, product and service names because be trademarks or service marks of others.
Permissions for the use of publications is granted subject to the following terms and conditions.
Personal Use: You may reproduce these publications for your personal, non commercial use provided that all proprietary notices are preserved. You may not distribute, display or make derivative work of these publications, or any portion thereof, without the express consent of IBM.
Commercial Use: You may reproduce, distribute and display these publications solely within your enterprise provided that all proprietary notices are preserved. You may not make derivative works of these publications, or reproduce, distribute or display these publications or any portion thereof outside your enterprise, without the express consent of IBM.
Except as expressly granted in this permission, no other permissions, licenses or rights are granted, either express or implied, to the publications or any information, data, software or other intellectual property contained therein.
IBM reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use of the publications is detrimental to its interest or, as determined by IBM, the above instructions are not being properly followed.
You may not download, export or re-export this information except in full compliance with all applicable laws and regulations, including all United States export laws and regulations.
IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. THE PUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
(C) Copyright IBM Corporation 2005, 2007. All Rights Reserved.