About this task
There are three ways to specify the way to read dse.ini
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.
- 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.
- 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.
- 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.
- Package the dse.ini and all the external files into the root of
a JAR file, such as dseserver.jar, or dseclient.jar.
- Define the variable dseIniPath with /dse.ini.
- Define the entities value with fromJAR:
<kColl id="paths">
<field id="entities" value="fromJAR">
</kColl>
- Add the JAR file into the JAR dependencies of CHA server or CHA
facade module.