IBM WebSphere Multichannel Bank Transformation Toolkit, Version 7.1

Specify the way to read dse.ini

About this task

There are three ways to specify the way to read dse.ini

Procedure

  1. Read dse.ini from URL. You can define the variable dseIniPath with the URL, for example: http://localhost:9080/TestWeb/dse.ini. In this way, the external files are placed in a Web project.
  2. Read dse.ini from hard-drive path. You can define the variable dseIniPath with the hard-drive path, for example, in Window, you can define c:\\dse\\dse.ini, and in UNIX, you can define /etc/dse/dse.ini
  3. Read dse.ini from JAR file. You can define the variable dseIniPath with path string, for example: /dse.ini, or /com/ibm/btt/base/dse/dse.ini. BTT will search the dse.ini configuration file in Java class path to initialize.
    Note: If you use this way to read dse.ini, the entity path cannot be specified with relative path.

What to do next

To initialize other external files such as dsectxt.xml, dsedata.xml, dsetype.xml, dseoper.xml, dsesrvc.xml, and dsefmt.xml, entity path should be correctly specified in dse.ini. This is the key information for BTT Initialization to locate such external files. The definition position in dse.ini is:
<kColl id="paths" dynamic="false">
   <field id="entities" value="./" description="" /> 
</kColl>
There are also three ways to specify the entity path.
  1. Use the relative path. You can define the entities value with a relative path such as / or ./client. This path is relative to the absolute path of dse.ini.
  2. Use the absolute hard-drive path. You can define the entities value with a hard-drive path, such as c:\\client in Windows, and /client in Unix.
  3. Use the Java class path. You can define the entities value with string fromJar. In this way, BTT can search the external files from Java class path.
  1. Package the dse.ini and all the external files into the root of a JAR file, such as dseserver.jar, or dseclient.jar.
  2. Define the variable dseIniPath with /dse.ini.
  3. Define the entities value with fromJAR:
    <kColl id="paths">
           <field id="entities" value="fromJAR">
    </kColl> 
  4. Add the JAR file into the JAR dependencies of CHA server or CHA facade module.
Screen capture showing the JAR file added.


Feedback