3-2 Administrators Guide for Oracle Imaging and Process Management
3.2 Post-Installation Configuration
If this is an initial installation of Oracle IPM and Oracle UCM in the same Oracle WebLogic Server domain, you must do the following before logging in to Oracle
IPM:
1.
Log in to Oracle Content Server
2.
Accept the Oracle Content Server configuration
3.
Restart Oracle Content Server. Once Oracle Content Server is configured and ready, the first user who logs in to
Oracle IPM is granted security rights to complete the following post-installation configuration steps:
■
connecting to an Oracle Content Server repository
■
configuring Oracle Content Server Storage Provider for production use. See Section 3.3.1, Storage Management
for more information.
■
on Linux systems, configuring the GDFontPath MBeans
■
setting environment variables for Oracle Outside In
■
connecting to a workflow server These steps and the full installation procedure are documented in the Oracle Fusion
Middleware Installation Guide for Oracle Enterprise Content Management Suite.
3.3 Configuration of Repository Options
Oracle IPM uses the functionality of the Oracle Content Server to store and retrieve documents. Documents are stored and secured based on criteria specified in the
application into which they were uploaded. You must create a connection for Oracle IPM to recognize the repository you are using. For more information about creating a
connection, see
Section 7, Managing Connections. Configuring repository options, such as defining the maximum number of search
results returned or if the full-text of a document can be indexed, must be done through the Oracle Content Server repository. It is recommended that you make all necessary
repository configuration prior to defining any application, input, search, or connection objects in Oracle IPM. For more information, see the Oracle Fusion Middleware System
Administrators Guide for Oracle Content Server.
3.3.1 Storage Management
Oracle Content Server uses file store providers to determine where and on what type of media content is stored. Note that the default storage provider configured when
Oracle Content Server is installed is not intended for a production environment and is not adequate for large numbers of ingested documents. The default can be used for
demonstration systems of less than 10,000 documents, but production systems require more advanced configurations. File store providers are configured in Oracle Content
Server independent of Oracle IPM. For more information, see
Section 3.3.4, Oracle Content Server File Store Provider Rules
and the Oracle Fusion Middleware System Administrators Guide for Oracle Content Server.
When integrated with Oracle URM, Oracle Content Server has the option to move documents from one media to another based on time, and documents can be deleted
based on lifecycle. If Oracle IPM is not integrated with Oracle URM and you need to move content to a different file store or delete documents and all revisions, you must
Changing Configuration Settings 3-3
do so explicitly using the Oracle Content Server Archiver or the Oracle Content Server Repository Manager tool.
For more information about configuration options provided by Oracle IPM on the Storage Policy page, see
Section A.28, Application Storage Policy Page. For more
information on retention management using Oracle URM, see Oracle Fusion Middleware Setup Guide for Universal Records Management.
3.3.2 Repository Capacity