Directory Tree
The Linux installation of TrueAddress (TA) requires the creation of a ‘tatemp’ directory the .zip installation file mentioned above is downloaded to. From the ‘tatemp’ directory, the install script file should be executed (refer to TrueAddress®(TA) OnPrem - Linux Installation Guide for instructions). The actual product should be installed in a directory other than the ‘tatemp’ directory.
When the installation of TA is complete and an operational test is successful, the ‘tatemp’ directory can be deleted from the server.
Shown below is the default ‘TrueAddress’ directory tree that is created when the install script is executed.
|
/.. (Client specified, parent directory) |
|||
|
/Data |
This is the default data directory that contains the data files relating to CASS, SuiteLink, and LACSLink. Data in this directory must be updated regularly by the user to ensure the most current address information is being used by TA (refer to Updating CASS & EWS Dataore information). |
||
|
/dpv |
|||
|
/lacslink |
|||
|
/out |
|||
|
/pob |
|||
|
/rrt |
|||
|
/str |
|||
|
/suitelink |
|||
|
/EWS |
This directory is where the EWS data is stored and updated (refer to Updating CASS & EWS Data for more information). |
||
|
/Forms |
This directory is where the example form files are stored (e.g. HTML forms and PS Form 3553), that can be used by the Client for creating forms of their own. Window Book recommends saving all Client-created form files in this directory. |
||
|
/Input |
This directory is where the example input files are stored. Examples are provided in both .csv and fixed formats. This directory may be used to store Client-related input files, but depending on job workflow, any appropriate location may be used. It is important to note that the job XML configuration file specifies the input file name, including the absolute or relative directory path. |
||
|
/Output |
This is the directory where example jobs’ output day is saved to when TA is run. As with the Input directory, this directory may be used to store Client-created output files, but depending on job workflow, any appropriate location may be used and specified in the job XML file. When the example jobs are run, the Output directory contains examples of output files in all of the possible the output formats. |
||
|
/XML |
This directory is intended to house a Client’s XML files, which are used to configure or build the output files. It contains example XML files for Client use. As with the Input and Output directories, job XML files may be stored anywhere, depending on the Client’s workflow. The file path is specified on the command line when the job is run. |
||
|
*TrueAddress |
|||
|
TrueAddress.xsd |
|||
|
TrueAddress_config.xml |
|||
|
data_dir.xsl |
|||
|
file_mapper.xsl |
|||
|
*get_CASS_data.sh |
|||
|
*get_EWS.sh |
|||
|
job_parms.xsl |
|||
|
libaddress_lookup.so |
|||
|
*run_TrueAddress.sh |
|||
|
version.txt |
|||
Window Book strongly recommends creating a copy of any of the example files before making any modifications to them so that an original always exists.
Continue Installation Steps on Linux