Installing the Bank Transformation Toolkit on a development workstation

To set up the development workstation, do the following:
  1. Install IBM® Rational® Application Developer.
  2. Insert the Bank Transformation Toolkit CD into CD-ROM and browse the CD. If you want to install Bank Transformation Toolkit for windows, locate and double-click the setup.exe in the Windows® platform. If you want to install Bank Transformation Toolkit for Linux®, locate and invoke setupLinux.bin in the Linux platform. This starts the Installation Wizard for Bank Transformation Toolkit. The Introduction window opens.
  3. Click Next, and the product license agreement window opens. Check the I accept the terms in the license agreement checkbox and click Next.
  4. The Installation Wizard detects if any version of Bank Transformation Toolkit is already installed on your system. Bank Transformation Toolkit version 6.1.2 can coexist with Branch Transformation Toolkit version 4.3, 5.0, 5.1 or 5.2. However Bank Transformation Toolkit version 6.1.2 cannot coexist with Branch Transformation Toolkit version 5.2.0.1 and 5.2.0.2, Bank Transformation Toolkit version 6.1.0 and version 6.1.1. If you already have version 6.1.2 installed, the Installation Wizard will display an error message showing that you already have version 6.1.2 installed. You need unstall previous version 6.1.2 before you installed new version 6.1.2.
  5. The Installation Wizard also checks the IBM Rational Application Developer you installed. If you have installed IBM Rational Application Developer, the Install Wizard will install toolkit components designed for IBM Rational Application Developer.
  6. You are prompted to choose if you want to install 32-bit or 64-bit BTT. If you want to run BTT in 64-bit AIX® or 64-bit Linux on IBM System z™ runtime environment, select Bank Transformation Toolkit 6.1.2.0 64-bit and click Next. Otherwise, select Bank Transformation Toolkit 6.1.2.0 32-bit and click Next.
  7. You are prompted to choose the destination directory for the installation files. If you want to choose a location other than the default location (C:\IBM\WebSphere\Multichannel Bank Transformation Toolkit 6.1.2.0 for Windows, and /opt/IBM/WebSphere/Multichannel Bank Transformation Toolkit 6.1.2.0 for Linux), click Browse, and select that folder you want to use.
  8. Click Next, and the Pre-Installation Summary window opens. It displays the product name, install folder and the disk space that the installation takes. Click Install.
  9. The Bank Transformation Toolkit installation program creates the following set of directories on the target machine.
    Table 1. Directories created by installation
    Directory name Description of contents
    license Product license files
    javadoc Product Java™ documentation
    lib Product runtime libraries
    plugins
    • Transaction Editor plug-in
    • APAR viewer plug-in
    • Migration tool plug-in
    • Grammar Validator plug-in
    • Formatter Simulator plug-in
    • Application Wizard plug-in
    • XUI Editor plug-in
    • Deployment Descriptor Editor plug-in
    • Outline Viewer plug-in
    • check with JF
    samples Product samples
    template Template for Foreign Exchange
    jre Install Anywhere bundled JVM
    Uninstall Product uninstallation files
    migration Migration-related files
  10. Start IBM Rational Application Developer.
  11. Set some preferences before you import Bank Transformation Toolkit Java source:
    • To work with complex projects, you should use the source folders as source containers instead of creating packages directly inside the project. To do this, you create source folders as children of the project and create your packages inside these source folders. To automate this, go to Window > Preferences. Expand the Java node and select the New Project node. Enable the Folders check box.
    • To develop with the Bank Transformation Toolkit, add the framework functional units (the JAR files containing the classes) to the application classpath. You can use any approach to do this but you must account for the class loader policies.

      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:

      1. Go to Window > Preferences.
      2. Expand the Java node and select Build Path.
      3. Expand the Build Path node and select Classpath Variables.
      4. Click New and in the Name entry field, type the following:
        BTT
      5. In the Path entry field, type the path to where the Bank Transformation Toolkit was installed.
      6. Click OK.

      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.

  12. Create a Java project for application. To create the project:
    1. Select File > New > Project.
    2. Select Java in the left panel and then select Java Project in the right panel. Click Next.
    3. Type the name of the project, such as HomeBanking, and click Finish.
  13. When deploying an application, you must embed Bank Transformation Toolkit functional units, along with the required application resources, inside the J2EE EAR file. The Bank Transformation Toolkit uses functional units to provide a coherent structure of JAR files that you use to build an application. The JARs in the functional units contain the required set of classes for a given execution environment.

    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.