Installer creates a number of directories, files, and environment variables depending on the selections you made while running Installer.
After the installation is complete, you can view the file system and its contents. Table 5 lists some of the directories you might need to know about. The folders and files created vary depending on the choices made during the installation and on the operating system.
Directory name | Contents |
---|---|
_jvm |
This directory contains the Java Runtime files.
Note:
If you are upgrading from a previous version of WBIA,
the existing directory name is retained from that release. |
_uninst_adapter |
This directory contains files that are required
to uninstall an adapter. For example, the directory named _uninst_JDBC contains files that are required to uninstall the WebSphere Business
Integration Adapter for JDBC.
For more information on uninstalling WebSphere Business Integration Adapters products, see Uninstalling WebSphere Business Integration Adapters products. Note:
If you are upgrading from a previous version of WBIA,
the existing directory name is retained from that release. |
_uninstZip |
This directory contains log files about tool plug-ins. |
bin |
This directory contains the executable files and shell scripts that the business integration adapters use. |
connectors |
This directory contains files specific to each adapter in the system. It also contains adapter-specific files that you may need to install in the application that the adapter supports. |
docs |
This directory contains the license file for the Java Runtime Environment. |
installLogs |
This directory contains log files about the installation of WebSphere Business Integration Adapters products. |
lib |
This directory contains shared libraries and .jar files for the system. |
license_adapter |
This directory contains the license files for an adapter. For example, the directory named _license_JDBC contains the license files for the WebSphere Business Integration Adapter for JDBC. |
logs |
This directory is provided to contain log and trace files. |
connector\messages |
This directory contains message text files used by the connectors to generate log and trace messages. |
oda\messages |
This directory contains message text files used by the ODAs. |
ODA |
This directory contains the .jar and .bat files for each Object Discovery Agent. |
repository |
This directory contains the connector definition files. |
templates |
This directory contains sample script files for
creating and clearing WebSphere MQ queues.
If your integration broker is one of the supported message brokers or WebSphere Application Server, see your broker implementation guide for more information on using these scripts. If your integration broker is WebSphere InterChange Server, see the installation guide for InterChange Server on the appropriate platform. |
jdk |
If you apply fix pack 2.6.0.3, this directory contains IBM Java Development Kit 1.4.2 sr1. |
If you chose one of the supported message brokers or WebSphere Application Server as your broker on a Windows system, Installer takes the actions described in Table 6 to create and update environment variables on the computer. These actions are not taken if you chose WebSphere InterChange Server as your integration broker, because the environment variables required for that broker are created during installation of the broker itself.
Environment variable name | Installer action |
---|---|
MQ_LIB |
Set by ICS, this creates this environment variable to contain the path to the Java\lib directory within the WebSphere MQ installation, as specified when using Installer. |
MQ_LIB_RUNTIME | Contains the location of the MQ Java library, avoiding conflict withe the MQ_LIB environment variable that is set by ICS. |
PATH | Adds the following entries:
ProductDir\jre\bin\classic;
|
WAS_CLIENT_HOME | The adapter framework sets this variable to the WAS client install location directory. If a WAS is not configured as the integration broker, this variable is set to null. |
WBIA_RUNTIME | Creates this environment variable to contain the path to the installation of the adapter framework. |