Prerequisite configuration
The following machine specifications are required for a Windows-based machine to host WebSphere Integration Developer v7.0:
Most current processor (at least 1GHz or more, which is the norm these days)
Recommended memory of 3 GB
Windows XP or Windows Vista Operating System
Atleast 7.5 GB free hard drive space for the installation
Apart from the Internet Explorer browser, Firefox could also be an option
Adobe Flash Player 9
User must have administrator privileges
Installing WID on Windows
Even if you have an existing
compatible Eclipse platform environment, installing WebSphere
Integration Developer into it is not supported! However, WID can
co-exist with other/previous versions of WID.
Though there are
several installation topologies and scenarios that are possible, we use a standalone version of WID with the necessary unit test environment (UTE) with embedded test environment servers. The next section will cover more details on installation.
IBM Installation Manager
IBM Installation Manager
is a unified tool that we will use to install the WebSphere Integration
Developer packages on our workstation. It will also be used to update
and modify other packages and fixes over time. It keeps track of what we
install, software components that have already been installed, and
components that are available for installation. It searches for updates
and installs the latest version of the WebSphere Integration Developer
product packages. You should use the Installation Manager to modify,
uninstall, and roll back product packages. The following mind map shows
the capabilities of the IBM Installation Manager:
Starting the Installation
Based upon your license with
IBM, you may have DVDs for the WID installation or download it from
Passport Advantage. If you download from Passport Advantage, you need to
get all five image parts of WebSphere Integration Developer V 7.0
Multiplatform Multilingual. Please ensure that these binaries are
available on the installation machine. The following mind map gives an
overview of the sequence of installation steps that we will walk
through:
After verifying the
prerequisites and copying the install images to your server, we begin
the third step, as described in the preceding mind map. In this step, we
use the Installation Manager to install WID V 7.0. The Installation
Manager in turn has a three-step process:
The first step opens a wizard to install IBM WebSphere Integration Developer tooling.
The second step does a silent installation of the WebSphere Application Server in the test environment.
The last step installs WPS over the WebSphere Application Server.
Having unzipped all of the installed images ZIP files (that would add up to five), into the same directory location (for example, D:\WID_Install), launch the installation launchpad program found under disk1/launchpad.exe.
Here are the steps to install IBM WebSphere Integration Developer V 7.0:
Select Install IBM WebSphere Integration Developer V 7.0, as shown in the following screenshot:
The IBM Installation Manager wizard will be launched. Select the components you want to install. In this case, it will install IBM WebSphere Integration Developer Version 7.0.0.0 so click on the Next button as shown in the following screenshot:
On the license agreement page you need to accept the terms of use in order for the Next button to appear. Once you accept, click on the Next button.
If this is a clean machine and this the first time you are installing, the IBM Installation Manager screen will appear. It is recommended to change locations as shown in the following screenshot:
One of the most critical and
common advice is to have no spaces in the directory locations where
various components would be installed under. Also you get a warning
about the 259 character limit for Windows path lengths. If the directory
path is too long you may see the error message The URL length is greater than the Windows limit of 259 characters.
Another piece of advice is
that you can specify the shared resources directory only the first time
you install a package. All subsequent Installation Manager installations
will use this directory. Hence it is critical to allot sufficient space
and to select this location carefully.
Similarly, on the next page select the location of the WID install directory ( for example, D:\IBM\WID7) and click on the Next button.
On language selection, by default, English is selected. You may choose another language as needed and then click on the Next button.
On
select features, you may add features as needed. We have kept the default selections as shown in the following
screenshot and then click on the Next button.
Review the summary of your selections and click on the Install button.
Once the installation completes successfully close the Installation Manager and return to the launch pad.
This completes the first step
of the Installation Manager as you have installed only the tooling
successfully. You still need to install the UTE, even though the UTE is
not required we do recommend it.
Setting up UTE
After installing WID, you
will have the option to install an integrated test environment for both
the WebSphere Process Server (WPS), and/or the WebSphere Enterprise
Service Bus (WESB) profiles, as explained in the next section.
A profile
is used to define a separate runtime environment, with separate command
files, configuration files, and log files.
Typically, you can define three different types of environments:
With profiles you can have
more than one runtime environment on your system, without having to
install multiple copies of the WID. You can create, augment, or modify
profiles using the Profile Management Tool that will be available once you install WID.
WPS and WESB Integrated test environment
If you choose a WPS
profile, you will be able to deploy, debug, and test Service Component
Architecture (SCA)-based SOA applications that contain BPEL-based
business processes, human tasks, state machines, business rules,
selectors, Java components, and so on. You can also add WESB mediation
flows to a module and test them.
You can consider the WPS
profile as a superset that can run all types of components and should be
used in instances when you have solutions that contain a mix of
WPS-based and WESB-based modules. The WESB profile is a subset of the
WPS profile. Hence you cannot run BPEL business processes, human tasks,
business rules, state machines selectors, and so on using a WESB
profile. There is no harm in choosing to create both these profiles
during the installation setup and have them available in the WID
environment.
The steps to install a WPS-integrated test environment for version 7.0 are as follows:
On the launch pad click on step 2-Install WebSphere Application Server.
This will give you a warning to close the Installation Manager before
proceeding. It is critical to ensure that the Installation Manager is
closed, or else your WebSphere Application Server will fail. Click on
the OK button on the warning box to begin the installation.
You will see an installation progress begin at the bottom of the launch pad. Please be patient as this may take a few minutes.
Once the installation is complete you will be given an Installation successful dialog box. Click on the OK button on the dialog box.
On the launch pad now click on step 3-Install the WebSphere test environment. This will launch the Installation Manager.
On Install packages
screen select the packages you want to install. By default, the WPS and
its underlying dependencies SCA and WAS feature packs are selected, as
shown in the following image. Click on the Next button.
The
installation wizard's steps are the same as the WID installation we
covered above. On the feature installation page you are given the option
to install a WPS or WESB or both standalone development profiles. We go with the default WPS standalone
development profile selection, as shown in the following screenshot. On
the next page, you will need to define the admin user credentials for
the WPS profile and provide a username and password (admin / admin is
the default username and password. You are free to change this what you
prefer).
Once you complete installing the test environment, you may close the launch pad screen. This completes your WID installation.
Verifying the installation
Since we chose to install
IBM Installation Manager during the WID setup, it will be available post
installation to update and modify other packages and fixes over time.
You can view the Installation status at any time by going to IBM Installation Manager | File | Installation History
and looking at the summary of the installation details. Also all the
installation log files for the installation are available under the
following location, C:\Documents and Settings\All Users\Application Data\IBM\Installation Manager\logs.
Using IBM Installation
Manager you can import these log files and go though the installation
logs that were done over a period of time. You can do this by starting IBM Installation Manager | View Log | Import log file (icon on top-right) and selecting the log file of interest to view/examine the detailed results of an installation session.
Post installation activities
We strongly recommend that you use the IBM Installation Manager post installation to find any updates and to apply them.
Internet access is
required to install the updates with IBM Installation Manager. As these
packages may be large in size (often several hundred MB) it would be
helpful to have more bandwidth available for the process.
Using the Update
icon in the IBM Installation Manager main screen, if updates are found
(iFix or FixPak, Feature Packs, or Updates), the appropriate updates are
selected and installed. Installation status and logs can be found, as
described in the previous section.
Uninstalling WID
Installation Manager can
also be used to uninstall products and packages. Make sure the package
being uninstalled is not dependent on another package.
