Section - 4 : Checking Your Installation
Although there are slight differences by platform, most of the installed files are the same regardless of the target system. The following example is from a Windows-based installation.
Setup wizard files
The Setup wizard places its own support files in the .install4j subdirectory. This directory should not be disturbed, as it contains information used if you decide to remove Documaker Connector. For more information, see Removing Documaker Connector on page 32.
Java run-time files
The Setup wizard places a Java 8 run-time environment (JRE) for the correct platform in the jre subfolder of the installation target directory. The configuration files for Documaker Connector are set up to use this JRE. If you need to use another JRE, you can reconfigure the properties and script files to use another JRE in the same or different location.
Java application and support files
All the Java JAR files for the application and the required support code are installed in the lib subdirectory. These JAR files must be in the Java classpath for the Documaker Connector to run (either from the command line or as a service). All of these files are installed as part of the normal installation process, but the list is provided here for information useful in troubleshooting or customizing the install.
The default logging properties file log4j.xml is installed in the lib folder, with the .jar file listed in this table. Some of the files are 3rd-party libraries which are available via the Internet. For these files, the URL you can use to download the file is provided, in case you need it.
| Name | URL |
|---|---|
| commons-beanutils.jar | http://commons.apache.org/beanutils/ |
| commons-codec-1.6.jar | http://commons.apache.org/codec/ |
| commons-collections-3.2.jar | http://commons.apache.org/collections/ |
| commons-dbcp-1.2.2.jar | http://commons.apache.org/dbcp/ |
| commons-httpclient-3.1.jar | http://hc.apache.org/httpclient-3.x/ |
| commons-lang-2.3.jar | http://commons.apache.org/lang/ |
| commons-logging-1.1.1.jar | http://commons.apache.org/logging/ |
| commons-net-2.2.jar | http://commons.apache.org/net/ |
| commons-pool-1.3.jar | http://commons.apache.org/pool/ |
| DdlUtils-1.0.jar | http://db.apache.org/ddlutils/ |
| jakarta-oro-2.0.8.jar | http://jakarta.apache.org/oro/ |
| log4j-1.2.15.jar | http://logging.apache.org/log4j/1.2/ |
| ojdbc14.jar |
http://www.oracle.com/technetwork/database/ enterprise-edition/jdbc-10201-088211.html or http://www.oracle.com/technetwork/database/ enterprise-edition/jdbc-112010-090769.html |
| oracle-dmkr-conn-assuresigndestination.jar | Oracle proprietary file |
| oracle-dmkr-conn-batchloadersource.jar | Oracle proprietary file |
| oracle-dmkr-conn-documakersource.jar | Oracle proprietary file |
| oracle-dmkr-conn-documentdatasource.jar | Oracle proprietary file |
| oracle-dmkr-connector.jar | Oracle proprietary file |
| oracle-dmkr-connectorapi.jar | Oracle proprietary file |
| oracle-dmkr-conn-filedestination.jar | Oracle proprietary file |
| oracle-dmkr-conn-fileplusdestination.jar | Oracle proprietary file |
| oracle-dmkr-conn-ftpdestination.jar | Oracle proprietary file |
| oracle-dmkr-conn-ipmdestination.jar | Oracle proprietary file |
| oracle-dmkr-conn-mockdestination.jar | Oracle proprietary file |
| oracle-dmkr-conn-mockperiodicprocess.jar | Oracle proprietary file |
| oracle-dmkr-conn-mockreporter.jar | Oracle proprietary file |
| oracle-dmkr-conn-mocksource.jar | Oracle proprietary file |
| oracle-dmkr-conn-pdfburster.jar | Oracle proprietary file |
| oracle-dmkr-conn-ucmdestination.jar | Oracle proprietary file |
| oracle-dmkr-ezridc.jar | Oracle proprietary file |
| oracle-dmkr-scrambler.jar | Oracle proprietary file |
| oracle.ucm.ridc-11.1.1.jar | Get this file from your UCM installation in the directory: <Middleware Home>\<ECM Home>\ucm\Distribution\RIDC |
In addition to the files supplied with the application, you must make sure the appropriate JAR files for your database provider are also included the classpath. These files are not included in the installation of the Documaker Connector — with the exception of the Oracle JDBC JAR file.
Here are some examples of the JAR files required for the JDBC connectivity for various databases:
Configuration and script files and Windows utility programs
At the root of the target installation folder, scripts, and configuration property files for Documaker Connector are placed along with utility programs useful on Microsoft Windows. These files are described here:
| File | Description |
|---|---|
| dm_connector_agent.exe (Windows only) | This program creates the Task Tray Agent and provides convenient control of the Documaker Connector Windows Service |
| dm_connector_svc.exe (Windows only) | This program can be run as a Windows service and configured to run a Java program, like Documaker Connector, as the actual service program. |
| dm_connector_svc.properties Windows only) | The configuration file for dm_connector_svc.exe which causes it to run Documaker Connector as the real service and sets the CLASSPATH for the Documaker Connector program as well as the Documaker Connector properties file. It includes the path to the JVM and the Documaker Connector mode to be run as a service. |
| ecmconnector.bat (Windows only) | Batch script which may be useful to run Documaker Connector in a command prompt window. This file is described more later. |
| uninstall.exe (Windows only) | Lets you uninstall Documaker Connector. |
| source-dest-conn.properties | Series of example files providing a starting point for configuration of Documaker Connector with specific combinations of a source and a destination. The specific files are:
|
| ecmconnector.sh | A UNIX shell script useful to run Documaker Connector. |
| vcredist_x86.exe (Windows only) | Microsoft installer for run-time support for the above applications. Provided in case the target install computer does not have the required support files. |
Setting Up Documaker Connector as a Windows Service
The dm_connector_svc.exe application runs Documaker Connector as a Windows Service. For more information, see Windows Service Application.
The dm_connector_agent.exe program places the Task Tray Agent icon in the Windows task bar:
This icon shows the status of the Documaker Connector Windows service. Right-click on the icon to open the log file and start and stop the Windows service without opening the Services Control Panel.