An InterChange Server (ICS) product CD is supplied for each
platform. Each contains the ICS software for that platform.
When mounted, the CD is usually accessed through the following path
per platform:
AIX: /cdrom
Solaris: /cdrom/WebSphereBI
HP-UX: /cdrom
Linux: /mnt/cdrom
Table 22 shows the contents of the InterChange Server
product CD.
Table 22. Components on the InterChange Server product CD
InterChange Server component
| Directory on product CD
|
InterChange Server software
| WebSphereBI
|
InterChange Server installation software
| WebSphereBI
|
To access software on the InterChange Server product CD:
- Insert the CD in the CD-ROM drive.
- Mount the CD.
You invoke Installer by executing the platform-specific executable
in the WebSphereBI directory. Table 23 lists the executables for each supported UNIX
platform.
Table 23. Platform-specific executables for Installer
UNIX platform
| Installer executable file
|
AIX
| setupAIX.bin
|
Solaris
| setupsolarisSparc.bin
|
HP-UX
| setupHP.bin
|
Linux
| setupLinux.bin
|
- Important:
- Make sure you are logged in as the WebSphere business integration system
administrator before you perform the installation. When you install on
a UNIX computer, the permissions of the folders and files that are created are
set based on the permissions of the user account that performs the
installation.
- Important:
- You must not install WebSphere InterChange Server as root on AIX. The
entry that is added to the Object Data Manager (ODM) when installing as root
prevents you from using SMIT to uninstall other applications, therefore you
should not install InterChange Server as root.
The graphical Installer presents you with a wizard that allows you to make
choices about the installation of the WebSphere InterChange Server
product. Follow the appropriate methods described in the sections below
to invoke Installer.
If you are running the Common Desktop Environment (CDE) and working on the
UNIX computer directly then you can navigate to the WebSphereBI
directory of the product CD and double-click the .bin file
specific to the operating system.
You can also navigate to the WebSphereBI directory of the
product CD and run the .bin file at the command line.
The following example shows how to do so on a Solaris computer:
# ./setupsolarisSparc.bin
If you are using a Windows computer to connect to the UNIX computer through
X emulation software do the following to invoke the installer:
- Determine the IP address of the Windows computer that
you are using to connect to the UNIX computer.
You can issue the ipconfig command at the Windows command line
interface to display the IP address of the Windows computer.
- Set the DISPLAY environment variable on the UNIX computer to
the IP address determined in step 1.
You must be sure to follow the IP address with a colon and the identifier
for the monitor or display on the Windows client computer. If the
Windows client computer only has a single monitor then the display value is
0.0.
The following example shows the DISPLAY environment variable
being set to the single monitor on a Windows computer whose IP address is
9.26.244.30:
DISPLAY=9.26.244.30:0.0
- Export the DISPLAY environment variable by executing the
following command:
export DISPLAY
- Start the X emulation client on the Windows computer and connect to the
UNIX computer.
- Navigate to the WebSphereBI directory of the product CD at the
command line of the X emulation client.
- Run the .bin file specific to the operating
system. For example, if the UNIX computer is running AIX then you would
issue the following command:
# ./setupAIX.bin
The graphical installer starts on the Windows computer that you are using
to connect to the UNIX computer.
When running, the Installer prompts you to make your installation
choices and then performs the installation.
- At the "Language selection" prompt, choose the desired language from
the list and click OK.
Figure 1. Language selection screen

- At the "Welcome" screen click Next.
Figure 2. Welcome screen

- At the "Software License Agreement" screen, click I accept the
terms in the license agreement and then click Next.
Figure 3. Software License Agreement screen

- At the "Installation directory" screen, either type the full path of
the directory into which WebSphere InterChange Server should be installed,
click Browse to select a directory, or accept the default path,
then click Next.
Figure 4. Installation directory screen

- Important:
- You must specify an installation directory that does not have spaces in the
path.
Notes:
- The WebSphere InterChange Server cannot be installed in the same directory
as the WebSphere Business Integration Adapter version 2.6 Adapter
Framework.
- If the WBIA 2.6 Toolset is discovered to exist on the target
machine, then installation of ICS 4.3 will not be allowed to
continue. You must first uninstall the WBIA 2.6 Toolset before
attempting to install ICS 4.3 to the target machine.
- At the "Component selection" screen, select the check boxes
corresponding to the features you want to install and then click
Next.
- Note:
- This sample installation assumes IBM WebSphere InterChange Server
4.3 and all components are installed on the same machine.
Figure 5. Component selection screen

- At the "Database selection" screen, select the database you are
using from the list. If you are using IBM WebSphere MQ 5.3 for
messaging support, ensure that the check box beside Use IBM WebSphere MQ
5.3 for messaging support is checked. Then click
Next. Depending on the choices made, clicking
Next will lead to various screens.
- If you choose a database other than DB2, but a DB2 client is installed on
the host machine the installer will proceed to step 7: the "DB2 Client detected" screen.
- If you choose DB2 as your database then the installer will proceed to step
8: the "DB2 Installed Directory" screen.
- If you choose a database other than DB2 and there is no DB2 client on your
host machine the installer will proceed to step 9: the "InterChange Server Name" screen.
Figure 6. Database selection screen

- If you selected a database other than DB2 as your database but a DB2
client is detected on the target machine, the "DB2 Client detected"
screen appears. If you intend to use DB2 for Relationships or User
Database Connections with WebSphere InterChange Server, click Yes
if not, click No, then click Next. Depending on
the choices made, clicking Next will lead to various
screens.
- If you do intend to use DB2 for Relationships or User Database Connections
with WebSphere InterChange Server, the installer will proceed to step 8: the "DB2 Installed Directory" screen.
- If you do not intend to use the installed DB2 client then the installer
will proceed to step 9: the "InterChange Server Name" screen.
Figure 7. DB2 Client detected screen

- If you selected DB2 as your database, or you intend to use DB2 for
Relationships or User Database Connections with WebSphere InterChange Server,
the "DB2 Installed Directory" screen appears. Type the full path
of the directory in which the db2java.zip file can be found,
click Browse to select a directory, or accept the default path,
then click Next.
Figure 8. DB2 installed directory screen

- At the "InterChange Server Name" screen, type the
name of the InterChange Server instance in the InterChange Server
Name field and then click Next.
Figure 9. InterChange Server Name screen

- Important:
- The server name is case-sensitive, therefore be sure to type it exactly as
you want the server to be named. If you do not type it exactly as you
want it to be named, when you attempt to connect to it using clients such as
the tools and adapters, you might experience errors.
- The WebSphere MQ library must reference the WebSphere MQ Java
Library directory. Hence the "WebSphere MQ Java Library" screen
appears. Type the directory path to the java/lib directory
of the WebSphere MQ installation or click Browse to select the
directory, then click Next.
Figure 10. WebSphere MQ Java Library screen

- The "Summary" screen lists the features selected for installation,
the specified product directory, and the amount of disk space required.
Read the information to verify it and then click Next.
Figure 11. Summary screen

- As the installation process nears the end, Installer presents the
InterChange Server Configuration wizard, which you use to specify some basic
configuration settings. For information on how to use the InterChange
Server Configuration wizard, see Configuring or reconfiguring InterChange Server.
- When you complete the InterChange Server Configuration wizard, Installer
presents a screen indicating that installation succeeded. Click
Finish to exit the Installer.
Figure 12. Finish screen

See Table 24 for a list of the directories and files that were created
during the installation process.
- When the installation is complete, proceed to Configuring the WebSphere MQ Listener.
- Note:
- The JDBC drivers of all three supported databases are referenced in
the CWSharedEnv.sh file in the
ProductDir/bin directory. These drivers are
db2java.zip, xworacle.jar and
xwsqlserver.jar for DB2, Oracle and MS SQL Server,
respectively. If you are installing WebSphere InterChange Server in a
high-availability environment it is recommended that you edit the
CWSharedEnv.sh file. It is important to create a
backup before editing. Remove the references to the redundant
drivers: the two which correspond to the databases that you are not
using.
After InterChange Server is installed, you can view the file structure and
its contents. The directories are located in the ProductDir
directory ($HOME/IBM/WebSphereICS by default). Table 24 lists these directories.
- Note:
- The particular files and directories that appear in ProductDir
depend on the components selected during InterChange Server
installation. Files and directories related to the XML Data Handler,
e-Mail Adapter, and other installed adapters might also appear. The
files and directories in your installation might differ from the ones listed
here.
Table 24. IBM WebSphere InterChange Server directory structure
Directory name
| Contents
|
_jvm
| This directory contains the Java Virtual Machine (JVM) that is used by
Installer.
|
_uninstWICS4.3.0
| This directory contains the uninstaller.bin file that
is used to remove InterChange Server 4.3.0.
|
bin
| This directory contains the executable files, .dll
files, and .sh files that the InterChange Server system
uses.
|
DataHandlers
| This directory contains the .jar files for data
handlers that InterChange Server uses.
|
DevelopmentKits
| This directory contains sample files to assist the developer in creation
of various system components. Samples provided include: Server
Access for EJB, Server Access for J2EE Connector Architecture, and Object
Discovery Agents.
|
DLMs
| This directory contains subdirectories that contain Dynamic Loadable
Modules (DLMs) and other files for InterChange Server maps.
|
jre
| This directory contains the Java runtime.
|
legal
| This directory contains the license files.
|
lib
| This directory contains .jar files for the
system.
|
logs
| This directory contains log files related to the ics_manager
and snmpagent_manager scripts.
|
messages
| This directory contains the generated message files.
|
mqseries
| This directory contains files specific to WebSphere MQ, including certain
executable files.
|
ODA
| This directory contains the Object Discovery Agent .jar
and .sh files for each agent.
|
repository
| This directory contains the business object and collaboration template
text files.
|
snmp
| This directory contains components required for SNMP support, such as the
SNMP agent logging and tracing README files, as well as the
wbi_snmpagent_v2.mib file, and the
wbi_snmpagent.txt file.
|
src
| This directory contains samples of Relationship Service APIs for
cross-referencing.
|
WBFEM
| This directory holds information on Failed Event Management.
|
WBSM
| This directory contains System Monitor files.
|
- Note:
- All product pathnames are relative to the directory where ICS is installed on
your system (ProductDir or
$HOME/IBM/WebSphereICS is the default).
