Section - 3 : Configuring Oracle WebCenter Content
If you are using Oracle WebCenter Content as your content management system, this section provides information on what you need to set up in WebCenter Content to index data coming from your document source, such as Documaker. Although this topic discusses WebCenter Content configuration, it is not a substitute for the WebCenter Content documentation or familiarity with the WebCenter Content configuration requirements, procedures and user interfaces.
The information in this topic explains the minimum required WebCenter Content setup through one set of interfaces and provides some example information so a knowledgeable WebCenter Content administrator has a few reference points to understand the requirements in this document.
Oracle WebCenter Content is listed in the product suite under Fusion Applications, Oracle WebCenter Content, Document Management. On the Downloads site it is under OTN, Middleware, WebCenter Suite, WebCenter Content.
A minimal WebCenter Content system for use with Documaker Connector starts with installation of the Oracle Content Server. Documaker Connector was developed using Oracle Content Server 10gR3, but has been tested with later versions, including 11g.
The metadata and documents you create and capture in Documaker and pass through Documaker Connector must have homes in your WebCenter Content system. That is, you must set up your WebCenter Content system with the information fields needed to hold your incoming metadata. You must also make sure there is plenty of space to store the documents you are sending in via Documaker Connector.
WebCenter Content allows metadata fields to be required or optional. For WebCenter Content fields you map to incoming data, Documaker Connector checks the fields provided in the database records to make sure the required fields are present. If a required field definition is missing from the table, Documaker Connector logs this information and stops.
By default, the names of the columns in the incoming table from Documaker are used to match the data to WebCenter Content property (field) names. Not all the table columns need be mapped to information fields in WebCenter Content. Many of the table columns are used internally by Documaker and the Documaker Source modules to manage the table itself, remove old records which have been processed, and to keep track of incoming documents before they are processed into WebCenter Content.
Within WebCenter Content, use the Configuration Manager to set up the WebCenter Content information fields for the incoming table columns you want to capture. In the example below, information fields have been established for these example custom fields coming in from Documaker:
| AGENCYID | BATCHID | CUSTID |
| EFFDATE | EXPDATE | INDEX01, ... INDEX12 |
| INSADD1 | INSADD2 | INSCITY |
| INSDOB | INSFNAME | INSLNAME |
| INSPHONE | INSSTATE | INSZIP |
| JOBID | KEY1 | KEY2 |
| KEYID | POLNUM | RUNDATE |
| TRANCODE | TRANID |
Of the column shown in the table of Example Database Table Definition topic, in Configuring Documaker section, these columns are mapped by their default names to the indicated WebCenter Content metadata fields:
- JOBID
- TRANID
- BATCHID
BATCHID, for example, is highlighted in the following Configuration Manager window. The remainder of the custom fields must be handled by adding more columns to the minimum set of columns shown in Minimum DAL Output Database Table. You can find an example of the DDL that does this in Sample Applications and Files. In this example, all the fields shown previously are mapped by default using the same name for both the database table column and the WebCenter Content information field:
