This topic describes how to install WebSphere® Multichannel Bank Transformation Toolkit on a development workstation.
To set up the development workstation, do the following steps:
The Installation Wizard detects if any version of Bank Transformation Toolkit is already installed on your system. WebSphere Multichannel Bank Transformation Toolkit V7.1 can coexist with Branch Transformation Toolkit V4.3, 5.0, 5.1 and 5.2. However, WebSphere Multichannel Bank Transformation Toolkit V7.1 cannot coexist with WebSphere Multichannel Branch Transformation Toolkit V5.2.0.1 and 5.2.0.2, and WebSphere Multichannel Bank Transformation Toolkit V7.0 and 6.1.1, and 6.1.2. If you already have version 7.0.0 installed, the Installation Wizard displays an error message, which indicates that V7.0 is already installed. You must uninstall V7.0 before you installed V7.1.
The Installation Wizard also checks whether IBM Rational Application Developer is installed. If IBM Rational Application Developer is installed, the Installation Wizard installs the toolkit components designed for IBM Rational Application Developer.
Directory name | Description of contents |
---|---|
license | Product license files |
javadoc | Product Java documentation |
lib | Product runtime libraries |
plugins | Tooling:
|
Runtime:
|
|
samples | Product samples |
jre | Install Anywhere bundled JVM |
Uninstall | Product uninstallation files |
migration | Migration-related files |
reference | Open source components |
rcptools | Rich client platform tooling |
A recommended approach is to add an overall classpath variable named BTT to point to the root directory of the Bank Transformation Toolkit installation. To do this, do the following steps:
Another approach is to define a classpath variable for each functional unit available in the product. Each classpath variable points to the concrete JAR associated with the functional unit (see the tables in Functional units, packages, and dependencies).
To add another classpath variable, repeat steps 9a - 9f. You might want to add a classpath variable named BTT_EXTERNAL to point to the external dependencies. To enable the external classpath variable, all the required external JAR files must be in the directory to which this variable points. The overall classpath variables makes it easier for you to select the WebSphere Multichannel Bank Transformation Toolkit JAR files for your Java project.
The remainder of this procedure and all the other procedures assumes that you are using the recommended approach.
WebSphere Multichannel Bank Transformation Toolkit uses functional units to provide a coherent structure of JAR files for you to build an application. The JAR files in the functional units contain the required set of classes for an execution environment.
To enable the functional units to become available to your project, add either the compiled JAR files to the project classpath or import the JAR files into the workspace. You might want to import the JAR files into the workspace if you want to embed the JAR files and resources into your application when, for example, it is self-contained and independently deployed.
For either option, you only add or import the JAR files and the corequisite functional units that are required to optimize the deployment and distribution of the application. For more information on JAR files and their corequisite functional units, see the Functional units, packages, and dependencies topic.
After you have installed WebSphere Multichannel Bank Transformation Toolkit in IBM Rational Application Developer, you can develop solutions that are based on WebSphere Multichannel Bank Transformation Toolkit.