Using Tables for Content Items, the Search Index, and the File Store

9-16 Oracle Fusion Middleware Developers Guide for Oracle Universal Content Management Use these argument values for the client: ■ -alias SecureClient ■ -file client_cert ■ -keystore server_keystore ■ -storepass idcidc Use these argument values for the server: ■ -alias SecureServer ■ -file server_cert ■ -keystore client_keystore ■ -storepass idcidc Examples of -import commands follow: keytool -import -alias SecureClient -file client_cert -keystore server_keystore -storepass idcidc Owner: CN=SecureClient Issuer: CN=SecureClient Serial number: 3c42e605 Valid from: Mon Jan 14 08:07:01 CST 2002 until: Sun Apr 14 09:07:01 CDT 2002 Certificate fingerprints: MD5: 17:51:83:84:36:D2:23:A2:8D:91:B7:14:84:93:3C:FF SHA1: 61:8F:00:E6:E7:4B:64:53:B4:6B:95:F3:B7:DF:56:D3:4A:09:A8:FF Trust this certificate? [no]: y Certificate was added to keystore keytool -import -alias SecureServer -file server_cert -keystore client_keystore -storepass idcidc Owner: CN=SecureServer Issuer: CN=SecureServer Serial number: 3c42e61e Valid from: Mon Jan 14 08:07:26 CST 2002 until: Sun Apr 14 09:07:26 CDT 2002 Certificate fingerprints: MD5: 43:2F:7D:B6:A7:D3:AE:A7:2E:21:7C:C4:52:49:42:B1 SHA1: ED:B3:BB:62:2E:4F:D3:78:B9:62:3B:52:08:15:8E:B3:5A:31:23:6C Trust this certificate? [no]: y Certificate was added to keystore The certificates of each program have now been imported into the keystore of the other.

9.12 Using Tables for Content Items, the Search Index, and the File Store

The following subsections describe how to search tables for information about content items: ■ Section 9.12.1, Finding Information for Each Content Item ■ Section 9.12.2, Using a Search Index ■ Section 9.12.3, Using the File Store Provider Using Remote Intradoc Client RIDC 9-17

9.12.1 Finding Information for Each Content Item

Content managed by Oracle Content Server is primarily tracked by four tables: ■ Revisions ■ Documents ■ DocMeta ■ RevClasses These tables track the contents metadata, state, and actions as well as information that is associated with each file. Revisions This table tracks core information about each revision of the content: ■ One row per revision ■ Different revisions with the same content that share the same content ID and RevClass ID ■ System metadata for each revision: – Metadata for revisions: content ID, title, author, check-in date, and so on – Metadata for categorization and security: type, security group, doc account ■ State information for various actions: – Indexing – Workflow – Document conversion ■ Numeric IDs and text labels to help track and retrieve a revision: – A unique dID value for each revision the primary key in the table – A unique dRevClassID value for the content – A revision ID to mark the revision number for each revision Documents This table tracks information for files that are associated with each content revision. ■ One row per revision ■ Multiple rows per revision, with one row for each of these files: – Primary – Alternate – Web-viewable ■ File information: original name, location, language, size, and so on DocMeta This table contains extended metadata fields: ■ One row for each revision ■ One column for each metadata field ■ Definition of each field, stored in the DocMetaDefinition table 9-18 Oracle Fusion Middleware Developers Guide for Oracle Universal Content Management RevClasses This table tracks information for each content revision: ■ One row per content item ■ Row locked for content modification ■ Unique dDocName and RevClassId values ■ Current indexed revision ■ Dates and users: – Creation date and creator – Last modified date and user – Owner

9.12.2 Using a Search Index

Oracle Content Server provides various ways to search the repository. Metadata searches can be based on the Revisions, Documents, DocMeta, and RevClasses tables. To efficiently perform text searches, the full-text search feature of Oracle Database can be utilized, and the IdcText table can be created to hold the search index. IdcText This table contains selected columns from the Revisions, Documents, DocMeta, and RevClasses tables as well as columns for other data: ■ It contains a predefined list from the Revisions, RevClasses, and Documents tables. ■ It contains custom metadata that is indicated as searchable from the DocMeta table. ■ The OtsMeta column CLOB field contains an SDATA section and additional indexable fields that are not in the other columns. However, SDATA has significant limitations. The SDATA section has significant limitations. ■ The OtsContent column contains an indexable document. ■ The ResultSetInterface column can be used for sorting or count estimation, or to drill down.

9.12.3 Using the File Store Provider

The File Store Provider can be used to distribute files managed by Oracle Content Server on the file system, a database, other devices, or any combination of these. The files are stored in SecureFiles in Oracle Content Server 11g. For database-backed file storage, the FileStorage and FileCache tables store the information related to each file. Using Remote Intradoc Client RIDC 9-19 FileStorage This table stores file information and some additional information: ■ File stored in a BLOB field SecureFiles in Oracle Content Server 11g The database administrator can turn on additional BLOB optimizations. For example, deduplication, compression, and encryption with SecureFiles. ■ Values for dID and dRenditionID that point to a particular file managed by Oracle Content Server ■ Tracking information in a small number of fields: last modified date and file size FileCache This table stores pointers for files cached on the file system, for certain types of processing extraction, conversion, and so on, and for quick access by the web server. This pointer is also used to perform cleanup. 9-20 Oracle Fusion Middleware Developers Guide for Oracle Universal Content Management 10 Using Content Integration Suite CIS 10-1 10 Using Content Integration Suite CIS This chapter describes how to use the Content Integration Suite CIS, which offers access to Oracle Content Server by exposing its services and data in a unified object model. The Universal Content and Process Management UCPM API is modeled into a set of services APIs, which are API calls that communicate with the target server, and the returned value objects from the server. This chapter includes the following sections: ■ Section 10.1, CIS Architecture