Section - 3 : Installation Directories
By default Document Factory, Docupresentment and Shared Objects are installed in the following directory structure.
documaker
This directory contains the following subdirectories and files:
| Directory |
Description |
| bin |
Contains the DLL, EXE, and shared object files for Documaker server processing. Documaker Studio can be used from this location. |
| database |
Contains the SQL script used during the post-setup process that creates the database tables and sample resources which are used to validate the installation. |
| docfactory |
Contains the DLL, EXE, and Java archive (JAR) files needed for Document Factory processing. The subdirectories are: bin, config, deploy, global, internal-db, lib, logs, and temp.
Note: There is a directory for each worker within the temp directory. You can find the log information for each worker in these directories, including worker activity and errors. |
| docupresentment |
The directory where Docupresentment (IDS) is installed. This directory includes many files and subdirectories to support IDS processing. These include DAP.INI, LONGCONF.XML, DOCSERV.XML, WIPEDIT.INI (configure auto/default fields), and the following log and debugging files: DPRTRC.LOG, WATCHDOG-STDERR.TXT, and WATCHDOG-STDOUT.TXT. |
| filesystem-archive |
This is the default location for archived documents when using the file system storage destination. |
| hotdirectory |
This is the default location for archived documents when using the file system storage destination.
The Receiver monitors this directory for files that it can accept as jobs into the Document Factory. Set up this directory as a networked or shared directory so it can be accessed by applications that submit jobs into the Document Factory.
To change the location of the watched directory, update the Receiver's HotDirectories property within the Documaker Administrator web application after you install it. |
| j2ee |
The parent directory for web applications and J2EEcomponents that support the Document Factory and Documaker Interactive: Correspondence processes. Contains the scripts used to create the required and sample users and groups. |
| jre |
Contains the Java archive (JAR) files and resources needed to run the Document Factory workers. |
| mstrres |
Contains the sample resources, including a master resource library and supporting runtime files used with Document Factory and Documaker Interactive: Correspondence. |
documaker\j2ee
This directory contains the following sub directories and files in the WebLogic directory:
| Directory |
Description |
| bpel |
The web service Java archive (JAR) files for processing Documaker Interactive: Correspondence requests for approval and rejection. It uses Oracle Business Rules to determine the next step in documents submitted within Documaker Interactive: Correspondence.
See the Documaker Enterprise Administration Guide for more information. |
| dashboard |
Contains the enterprise archive (EAR) file for the Document Factory Dashboard web application. |
| documaker_administrator |
Contains the EAR file for the Documaker Administrator web application. |
| idocumaker_correspondence |
Contains the EAR file for the Documaker Interactive: Correspondence web application. Also contains the pass-through web service that can be used to bypass the BPEL approval workflow within Documaker Interactive: Correspondence. |
| scripts |
Contains the command scripts and associated files used to create the required and sample user accounts and establish the WebLogic/ WebSphere domains. |
JAR files are used to distribute Java applications or libraries, in the form of Java class files and associated metadata and resources. JAR files are built on the ZIP file format.
An EAR file is a standard JAR file with an ear extension, with entries representing the modules of the application, and a metadata directory called META-INF which contains one or more deployment descriptors.