Using The Properties File

Documaker Connector and the standard Oracle interface components use a single common properties file for all configuration settings, described below. Custom source or destination components may be configured differently, but the standard components described in this document all use this file for their settings. If you are developing a custom component, you should also use this means of configuration.

You can enter the name of this properties file on the command line via the -config parameter. The default file name is connector.properties, which must be located in the execution directory if you omit the -config parameter.

This file is referenced in the dm_connector_svc.files by uncommenting it and commenting out the rest. The targeted file for use is based on the source and destination combination.

Files	Description
dmkr-ucm-conn.properties	Use dmkr-ucm-conn.properties if the source is dmkr and destination is ucm
mock-mock-conn.properties	Use mock-mock-conn.properties if the source is mock and destination
mock-file-conn.properties	Use mock-file-conn.properties if the source is mock and destination
batch-ucm-conn.properties	Use batch-ucm-conn.properties if the source is batch and destination is ucm

The configurations are contained in the properties file support:

• General Connector configuration
• Source component configuration
• Destination component configuration

The first topic, General Connector Configuration, provides parameters for the connector application which are independent of the source and destination, including identifying which source and destination components to use. The other topics are properties entirely dependent on the particular components chosen in the first topic. This document describes these components:

Sources	Documaker, using the AOR table Mock, which generates fake documents and metadata BatchLoader, which works with the WebCenter Content Batch Loader utility files
Destinations	Oracle WebCenter Content/Content Server Oracle WebCenter Content Imaging (formerly Imaging and Process Management (IPM)) Mock, which accepts documents and metadata and discards them FTP, which sends documents to a receiving FTP site File, writes documents into folders in a local file system AssureSign, submits documents to the AssureSign e-signature service

Note in the following tables, that some of the property names are quite long. To save space in the tables, some groupings of properties that start with common prefixes are listed without the prefix. The common prefix is given above the group of properties in a separate line in the table labeled Property Name Prefix. These properties are written starting with a period (.), which is also shown as part of the prefix as a reminder that the property name includes the prefix shown above it. A single period is always used between the prefix and the rest of each property name when it is used in the file.

Note:

There are mock source and destination components that provide fake documents and data or let you send them to nowhere as a destination. You can use these together to test the installation of Documaker Connector or individually to test a specific source or destination. For example, you can set up the mock destination to test the Documaker source configuration without really archiving the test documents.