Directory name | Description of contents |
---|---|
license | Product license files |
javadoc | Product Java™ documentation |
lib | Product runtime libraries |
plugins |
|
samples | Product samples |
template | Template for Foreign Exchange |
jre | Install Anywhere bundled JVM |
Uninstall | Product uninstallation files |
migration | Migration-related files |
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:
BTT
In the same way, add another classpath variable named, for example, BTT_EXTERNAL to point to the external dependencies. To make the external classpath variable work, all the required external JARs must be in the directory to which this variable points. The overall classpath variables make it easier for you to select the Bank Transformation Toolkit JAR files for your Java project.
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).
The remainder of this procedure and all the other procedures assume that you are using the recommended approach.
To make the functional units available to your project, you can either add the compiled JARs to the project's classpath or you can import the JARs into the workspace. You can choose the second option if you want to embed the JARs and resources into your application when, for example, it is self-contained and independently deployed.
For either option, you only add or import the JARs and their corequisites needed for the application to optimize the deployment and distribution of the application. Consult Functional units, packages, and dependencies to obtain these corequisites.
Once you have installed the Bank Transformation Toolkit in IBM Rational Application Developer, you can start developing Bank Transformation Toolkit-based solutions.