The destination folder ITP/Server will have the following layout:
ITP Server\apis\COM
contains all files relating to the COM library client to access ITP/Server
ITP Server\apis\COM\Examples\C++Builder
contains the sources for and a compiled version of the ITP/Server Test Tool that uses the COM library and has been developed in Borland C++Builder.
ITP Server\apis\COM\Examples\Scripts
contains sample scripts (VBScript, Java Script and Lotus Script) that use the COM library to submit jobs to ITP/Server.
ITP Server\apis\COM\Examples\Visual Basic
contains sources for a Visual Basic sample program that uses the COM library to submit jobs to ITP/Server.
ITP Server\apis\directorywatch
contains the executable for the Directory Watch interface. Refer to chapter Installing the Directory Watch interface for more information.
ITP Server\apis\Java
contains the ITP/Server Java client library in a .jar file and the corresponding documentation. Documentation is also available in a .jar file.
ITP Server\apis\Java\Doc
contains the documentation for the Java client in HTML format.
ITP Server\apis\MQSeries
contains the executable for the MQSeries interface. Refer to chapter Installing the MQSeries interface for more information.
ITP Server\apis\OnLine
contains the ITP/OnLine Server Java and COM client libraries.
ITP Server\apis\OnLine\Example XML files
contains sample versions of the XML files that are used in the communication with ITP/OnLine Server.
ITP Server\apis\Tcp ip
contains a dll file and a corresponding command-line program for job submission via TCP/IP.
ITP Server\apis\Tcp ip\Borland
contains the Borland C++Builder .lib file for the TCP/IP dll.
ITP Server\apis\Tcp ip\Sample Client
contains the sources for the TCP/IP command-line job submission program.
ITP Server\apis\Web Services
contains the files required for the installation of the ASP.NET implementation of the ITP/Server Web Services interface.
ITP Server\apis\Web Services\Bin
contains binary components required for the installation of the ASP.NET implementation of the ITP/Server Web Services interface.
ITP Server\apis\Web Services\Sample client
contains a synchronous and an asynchronous client application for submitting jobs to the ITP/Server Web Services interface. It also contains the sources for these applications.
ITP Server\apis\Web Services J2EE
contains the files required for the installation of the J2EE implementation of the ITP/Server Web Services interface.
ITP Server\BACKUP
contains files that are necessary for uninstalling ITP/Server (components).
ITP Server\Bin
contains the ITP/Server executables and their support files.
ITP Server\Bin\DocToPDF
contains the files that are needed to use the command DocToPDF. Only installed when a special agreement is accepted during the installation.
ITP Server\DPMonitor
contains the software for the ITP/Server Monitor.
ITP Server\Examples
contains examples on how to use the custom JSP tags for ITP/Server.
ITP Server\Manuals
contains the manuals and the Help sources.
ITP Server\Resources
contains the message files and other files necessary for the user interface.
ITP Server\Tools
contains a synchronous and an asynchronous client application for submitting jobs to the ITP/Server Web Services interface. It also contains the sources for these applications.
ITPWORK
The folder ITPWORK should be accessible for all Document Processors. Most of the subdirectories in ITPWORK can be kept read-only for the Document Processors. The only exceptions are the Temp, Log and Sessions directories. The folder ITPWORK contains several subfolders:
ITPWORK\Config
contains the configuration files for ITP/Server. At installation time, basic versions of the configuration files dp.ini,dm.ini and itp.cfg will be generated.
ITPWORK\Data
contains the data files and a local connection dll for the examples.
ITPWORK\DID
contains the DID that is used in the example.
ITPWORK\Log
is the default log directory. After installation, this location can be changed with the ITP/Server Administrator for each server machine that participates in the ITP/Server setup. For performance reasons we advise to choose local directories.
ITPWORK\Moddocs
contains the example ITP Model documents that were used to create the example ITP Models that are distributed with ITP/Server. The Model documents can be adapted and recompiled with ITP/Workstation.
ITPWORK\Moddocs\Includes
contains the example include documents that belong to the example ITP Model documents. This folder also contains a file with example styles for Text Blocks.
ITPWORK\Models
contains the ITP Models that can be used by services. At installation it contains 5 example ITP Models.
ITPWORK\Models\Includes
is the folder where ITP/Server will search for pre-include documents (if any) during compilation.
ITP Work\Models\PostIncludes
is the folder where ITP/Server will search for post-include documents (if any) during model execution.
ITPWORK\Scripts
contains the scripts that implement the services. At installation, some scripts are installed.
ITPWORK\Scripts\System
contains the scripts for internal services. These scripts are installed read-only and should not be modified. These scripts will be replaced during an upgrade of ITP/Server.
ITPWORK\Scripts\System Library
contains utility scripts which can be used in custom ITP/Server scripts. These scripts will be replaced during an upgrade of ITP/Server.
ITPWORK\Scripts\User Library
contains scripts that are user exit points. These scripts are for internal functions provided by ITP/Server, and will not be replaced during an upgrade of ITP/Server.
ITPWORK\Temp
is the default temporary directory. After installation, this location can be changed with the ITP/Server Administrator for each server machine that participates in the ITP/Server setup. For performance reasons we advise to choose local directories.
ITPWORK\Sessions
will only be created if you use this installation as an ITP/OnLine Server. It stores session information of each OnLine job and will be created at the moment the first OnLine job gets started. The location of this directory cannot be changed in the ITP/Server Administrator, as the session directory must remain accessible to all participating servers.