HP Neoview Release 2.5 Software - Manual (Page 17)

2 Transporter Configuration
This chapter addresses the following topics:
• “Client Directory Structure” (page 17)
• “The Transporter API” (page 17)
Client Directory Structure
Installation creates the environment variable NVTHOME for the default location of the Transporter
base directory. The directory specification follows the conventions of your loader platform.
For example,
• Windows — c:\Program Files\NVTransporter
• Unix®-type platform— HOME/nvtransporter
These subdirectories are created in the NVTHOME directory:
Contents Directory
License file, Transporter executable scripts, and Readme /
Libraries, static and dynamic and Java class library /lib
Transporter API libraries, message catalog files for all supported platforms. (See
“Client Components” (page 16) for the list of supported platforms.)
/platform
Header files /inc
Transporter Control File Generator template and framework configuration
(properties) files /conf
Message catalogs or locale specific properties files /mesg
Application message log directory /log
Client extensions to Transporter — operation extension /extensions
Sample Transporter control files, scripts, and Transporter tools /samples
Contributed useful files, scripts, and/or programs that may not be supported by
HP. /contrib
Utilities — Control File Editor, Control File Generator /utils
Transporter uninstaller jar file /Uninstall_NVTransporter
Security Parameters Saved
As part of Transporter client installation, the security parameters are saved in NVTHOME/conf/
security
directory. For more information about Transporter security, see “Security” (page 25) .
The Transporter API
If you are using an HP-UX_IA64, Linux_X86, AIX, or Solaris platform, and you are also using
an ETL (extract, transform, load) tool, you need the Transporter APIs. ETL tools integrate with
the Transporter Client through the Transporter APIs. The libjnvt.so library contains
functionality to invoke the Neoview Transporter Client through these APIs.
An ETL tool may invoke the Transporter client in one of two ways - either launch or attach to
the Transporter client in the same process or launch the Transporter client as an external process.
If the Transporter installer detects that your platform is one of the supported platforms,
Transporter automatically installs a platform-specific library. Java JDK 1.5 or later is required;
HP recommends JDK 1.6.
Client Directory Structure 17