This chapter describes installation and configuration issues associated with Oracle Enterprise Content Management Suite (Oracle ECM). It includes the following topics:
Section 48.1, "File Formats Wizard Might Display Error First Time After Upgrade"
Section 48.2, "Configuring the Java Object Cache for AXF in Distributed Oracle I/PM Managed Servers"
For more information about Oracle ECM installation and configuration, see Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite or Oracle Fusion Middleware Quick Installation Guide for Oracle Enterprise Content Management Suite.
In certain circumstances, the first time that you update the File Formats Wizard in Oracle Content Server after an upgrade, you might see an error. This error is harmless, and it will not occur on subsequent updates.
The File Formats Wizard is available in Oracle Content Server when Oracle Inbound Refinery is configured to work with Oracle Universal Content Management. For more information, see Section 6.2, "Installing and Configuring Oracle IBR on Oracle UCM," in Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite.
For Oracle Application Extension Framework (AXF) in Oracle I/PM Managed Servers that run in a cluster, you need to configure a Java Object Cache (JOC) to be distributed to all of the Managed Servers. To configure the JOC, use these instructions instead of the instructions in Section 7.5.1, "Configuring the Java Object Cache for AXF in Distributed Oracle I/PM Managed Servers," of Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite.
You can use HA Power Tools from the Oracle WebLogic Server Administration Console to configure the JOC for all of the Oracle I/PM Managed Servers that run in distributed mode.
Note:
After configuring the Java Object Cache, restart all affected Managed Servers for the configurations to take effect. For more information, see "Restarting a Managed Server" in Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite.In the following instructions, MW_HOME represents the path to a Middleware home, where Oracle Fusion Middleware is installed, and DomainHome represents the path to the Oracle home for an Oracle WebLogic Server domain.
To configure the Java Object Cache for a cluster of distributed Managed Servers:
Enable HA Power Tools in the Oracle WebLogic Server Administration Console:
Copy the following two WAR files from the MW_HOME/oracle_common/hapowertools directory to the DomainHome/console-ext directory:
powertools-core.war
powertools-configurejoc.war
For example:
cd MW_HOME
cp oracle_common/hapowertools/powertools-co* user_projects/domains/base_domain/console-ext/
Restart the Oracle WebLogic Server Administration Server.
For more information, see "Starting the Administration Server" and "Restarting a Managed Server" in Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite.
Access the Oracle WebLogic Server Administration Console (at http://adminServerHost:adminServerPort/console), and click the name of your domain in the left navigation tree.
The HA Power Tools tab appears on the Settings page for the domain.
Configure the distributed cache:
On the Settings page for your domain in the Administration Console, click the HA Power Tools tab.
On the Configure JOC tab, select Configure JOC for Clusters.
In the Cluster Name field, choose a cluster name from the list.
In the Discover Port field, enter the discover port number for the cluster.
In the Hosts field, enter the names of all the Managed Server hosts, separated by commas.
Click the Configure JOC button.
Restart the cluster of Managed Servers.
Verify the JOC distributed cache mode:
From the Middleware home on the host for one of the Managed Servers, run the CacheWatcher utility, as in the following example:
java -classpath oracle_common/modules/oracle.javacache_11.1.1/cache.jar:oracle_common/modules/oracle.odl_11.1.1/ojdl.jar oracle.ias.cache.CacheUtil watch -config=user_projects/domains/base_domain/config/fmwconfig/servers/IPM_server2/javacache.xml
In this example, the class paths for the two JAR files are relative to the current directory (MW_HOME).
The javacache.xml file is the file used by one of the Oracle I/PM servers that is participating in the JOC distributed cache.
Enter the lc command to list the cache information:
INFO: JOC is initialized from oracle.ias.cache.CacheUtil.main, . . .
cache> lc
In the output from the lc command, check that the Distributor Table shows an entry for each member of the distributed cache.
Enter the exit command to stop the CacheWatcher utility.
For more information, see "Using HA Power Tools" and "Running CacheWatcher" in Oracle Fusion Middleware High Availability Guide.
If you upgrade Oracle Universal Content Management (Oracle UCM) 10g to Oracle Enterprise Content Management Suite 11g (11.1.1.4.0) with the Upgrade Assistant, the intradoc.cfg file has an extra variable that causes the following exception to be thrown when you start the Oracle UCM Managed Server:
intradoc.common.ServiceException
To prevent the exception, you can comment out the extra variable after the upgrade:
Open the DomainHome/ucm/cs/bin/intradoc.cfg file in a text editor.
Add a comment character (#) to the beginning of this line:
JAVA_CLASSPATH_defaultjdbc=$SHAREDDIR/classes/ojdbcn.jar
Save the file, and start the Oracle UCM Managed Server.
For information about using the Upgrade Assistant to upgrade Oracle UCM 10g to Oracle Enterprise Content Management Suite 11g, see the Oracle Fusion Middleware Upgrade Guide for Oracle Enterprise Content Management Suite.
Before you upgrade an Oracle Universal Content Management (Oracle UCM) instance to Oracle Enterprise Content Management Suite 11g (11.1.1.4.0), you need upgrade the FileStoreProvider component of Oracle Content Server in the Oracle UCM instance.
If Oracle Content Server does not have FileStoreProvider installed and enabled, you need to install and enable it and then upgrade it.
To upgrade the file store provider:
Under Administration in Oracle Content Server, choose Providers.
Select DefaultFileStore, and choose Upgrade.
Restart Oracle Content Server.