This chapter describes installation and configuration issues associated with Oracle Enterprise Content Management Suite (Oracle ECM). It includes the following topics:
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.
Enable HA Power Tools in the Oracle WebLogic Server Administration Console:
Copy the following two WAR files from the
/oracle_common/hapowertools directory to the
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
/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 (
javacache.xml file is the file used by one of the Oracle I/PM servers that is participating in the JOC distributed cache.
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.
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 (220.127.116.11.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:
To prevent the exception, you can comment out the extra variable after the upgrade:
/ucm/cs/bin/intradoc.cfg file in a text editor.
Add a comment character (#) to the beginning of this line:
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 (18.104.22.168.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.
Under Administration in Oracle Content Server, choose Providers.
Select DefaultFileStore, and choose Upgrade.
Restart Oracle Content Server.
The 22.214.171.124.0 Oracle IRM Server Management Console has an issue that requires a patch to be applied to the installed or updated system. When rights are being selected for a context, the Properties, Edit, and Remove buttons are always disabled and cannot be used. Selecting one or more rights will not enable the buttons. Patch 12369706 fixes this issue.
This patch can be downloaded from My Oracle Support at
Log in to
Click the Patches & Updates tab.
Enter the patch number,
12369706, in the Patch Name or Number field, under Patch Search.
Follow the installation instructions provided with the patch.
For general information about patching, see the Oracle Fusion Middleware Patching Guide.
The Oracle WebLogic Server Node Manager enables you to start and stop Oracle WebLogic Server instances remotely, monitor them, and automatically restart them after an unexpected failure. You can configure Oracle Enterprise Content Management Suite (Oracle ECM) Managed Servers, the Administration Server, and Node Manager to work together in an Oracle WebLogic Server domain. Node Manager is installed on all the machines that host any server instance.
Before you can use Node Manager to start and stop Oracle ECM Managed Servers in a domain, you need to do these configuration tasks:
Configure at least one machine for the domain.
Assign the Administration Server and Managed Servers (such as
UCM_server1) to one or more machines.
Enable Node Manager to use the Oracle ECM startup scripts by setting the
StartScriptEnabled property in the
nodemanager.properties file to
This section describes how to configure a machine in an Oracle WebLogic Server domain, assign the Administration Server and Managed Servers to a machine, and enable Node Manager to use startup scripts before you start it. For information about creating or extending a domain to configure Oracle Enterprise Content Management Suite, see Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite.
The Administration Server uses a machine definition and the Node Manager application to start remote servers. During the initial configuration of Oracle ECM, you can configure machines through the Fusion Middleware Configuration Wizard. After the initial configuration, you can configure machines through the Oracle WebLogic Server Administration Console.
When you get to the Select Optional Configuration screen in the Fusion Middleware Configuration Wizard, be sure to select Managed Servers, Clusters and Machines.
On the Configure Machines screen, click Add.
Specify values for these fields:
Enter a valid machine name, such as Linux-Box. The machine name identifies the machine within the Oracle WebLogic Server domain; it does not have to match the network name for the machine. The name must be unique within the domain.
Node manager listen address
Select a value from the drop-down list for the listen address used by Node Manager to listen for connection requests. By default, the IP addresses defined for the local system and
localhost are shown in the drop-down list. The default value is
If you specify an IP address for a machine that hosts the Administration Server and you need to access Node Manager, you must disable host name verification. For more information, see "Using Host Name Verification" in
Securing Oracle WebLogic Server.
Node manager listen port
Enter a valid value for the listen port used by Node Manager to listen for connection requests. The valid listen port range for Node Manager is from
65535. The default value is
During the initial configuration of Oracle ECM, you can assign the Administration Server and Managed Servers to one or more machines through the Fusion Middleware Configuration Wizard.
After the initial configuration, you can assign Managed Servers to machines through the Oracle WebLogic Server Administration Console.
On the Assign Servers to Machines screen, select one or more servers in the Server area
Click the right arrow button to assign the selected server or servers to a machine.
Click Next when you are done.
Before you start Node Manager the first time, you can run the
setNMProps.sh script to set the
StartScriptEnabled property to
true. This setting is required for Node Manager to start the Managed Servers with startup scripts. You must use the
StartScriptEnabled property to avoid class-loading failures and other problems.
If you enable Node Manager to use startup scripts on a machine that hosts one or more Managed Servers that are assigned to a machine, you can start and stop the Managed Servers remotely using the Administration Console or the command line. Node Manager can also automatically restart a Managed Server after an unexpected failure.
For an Oracle URM Managed Server, before you start Node Manager, be sure to complete the Oracle URM setup checklist, described in Section 9.1, "Completing the Oracle URM Configuration," in Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite.
Navigate to the following directory
MIDDLEWARE_HOME is the directory where Oracle Fusion Middleware is installed.
setNMProps.sh script to set the
StartScriptEnabled property to
true before starting Node Manager:
This is a one-time action. After you run this script, you can skip this step before starting Node Manager again.
Start Node Manager with the
WL_HOME is the directory where Oracle WebLogic Server is installed.
For more information about Node Manager, see Managing Server Startup and Shutdown for Oracle WebLogic Server and Node Manager Administrator's Guide for Oracle WebLogic Server.