integrator subdirectories

Subdirectory Contents
Alerts Sample alerts file.
AppDefaults X resource definitions. These control visual aspects of the GUIs, such as color, fonts, and icons. They are not user-configurable.
archiving Contains create_template.sql and insert_template.sql.
bin Root level binaries, program scripts, and Raima (database) binaries.
box Contains the configured BOX files.
bitmaps Program icon bitmaps. This is not user-configurable.
CAA Contains the files for CAA-ION, CAA-Direct, and CAA-WS.
clgui Java-based components. Contains the hci wrapper scripts. The subdirectories are all Java components such as the Java Runtime Environment and library classes.
client Client configuration directory; contains client.ini and cached SSL credentials.
contrib Unsupported scripts that are used by implementors on site.
dicom Contains the dicom configuration file.
docs Contains information that is related to the system Java UPoC API.
eoalias Engine output configuration files. When primary-level files are unalterable, Root-level files that are created with EO Configurator are available to all sites.
formats Format files for DBSCHEMA, deprecated, EDIFACT, HL7, HPRIM, LDL, NCPDP, NCPDPFAB, NCPDPSCRIPT, X12, and XML.
helloworld The sample site included with the installation.
JavaDriverSamples Contains the Java driver sample sites.
java_uccs Recommended for keeping root-level Java UPoC *.class files.
lib Library files for public domain tools, perl libraries, and for ODBC middleware clients.
pdls Common PDL (Programmable Driver Language) programs.
perldocs (Windows only): Win32 Perl extension documentation.
productinfo Default root setting. Contains software version and licensing information. The default root is used when the setroot command is run without any arguments.
sbin Root level binaries and program scripts that can be used before HCIROOT is set. This contains mainly hcisetenv, which is used by setroot.
security Security server configuration directory; contains security.ini. This folder exists only when security server is installed.
server Host server configuration directory; contains server.ini.
shared_files Contains files managed by File Transfer. When using File Transfer, users of client-only installations who are remotely connecting to the host server can manipulate files on the remote machine. This can be performed by copying files to a fixed directory on the server.
sitename Site information that includes configuration files, database, and Tcl procedures.
siteProto Site prototype that contains the default directory structure for site creation.
startup (Windows only): Contains the script for starting hciclguiservice.
Tables Non-site-specific lookup tables. These can be copied over to $HCISITEDIR/Tables for customization.
tcl Tcl extension language; distributed programming package; extended Tcl, Tk files, and scripts; and a library of Tcl autoload procedures. Tcl shared libraries are located in /tcl /lib on UNIX platforms and in bin on Windows.
tclprocs Contains provided Tcl procedures. This contains a code set template Tcl procedure file that gives an example of code to use to query a lookup table for a key.
templates Contains the NetConfig template files.
uninstall_integration_services Contains the uninstaller files.
usercmds User-created commands.
vers Version and licensing information.
version When a user adds a configuration into Version Control, a version folder is created in the current site to store the configuration. The root-level version folder is used for the BOX Manager tool.
web Files that are related to the HTTP server plug-in. This includes perl scripts. These can be plugged into a web server. Then, a web server interface into the system is created by permitting it to route web requests by File or TCP/IP threads. CL_HTTPServer.ini is included as a configuration file for this interface. This also contains sample HTML files.
xslt XSLT configuration files. This includes the XSLT validation files for HL7 CDA 2.0 and HITSP_C32 (2.5 version). These files are found in the root level XSLT folder ($HCIROOT/xslt). They can be used by hcixslttest or the engine without any changes. They can also be copied and modified to the site level ($HCISITEDIR/xslt or $HCIMASTERSITEDIR/xslt) for special use.