This chapter describes installation and configuration issues associated with Oracle Enterprise Content Management Suite (Oracle ECM). It includes the following topics:
Section 47.1, "File Formats Wizard Might Display Error First Time After Upgrade"
Section 47.2, "Oracle UCM Configuration Automatic on Same Machine and Domain As Oracle I/PM"
Section 47.3, "Verifying the AXF Installation with HelloBpel"
Section 47.4, "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.
When you configure Oracle Universal Content Management (Oracle UCM) on the same machine and in the same Oracle WebLogic Server domain as Oracle Imaging and Process Management (Oracle I/PM), the postinstallation configuration of Oracle UCM is done automatically. In this case, Oracle UCM does not display the Content Server Configuration page when you first log in to Oracle Content Server at
http://managedServerHost:managedServerPort/cs
If you follow the default configuration for the installation of Oracle UCM and Oracle I/PM, both applications are installed on the same machine. In this environment, Oracle I/PM provides a configuration file to Oracle UCM that sets up Oracle UCM for use by Oracle I/PM.
If the Oracle UCM instance is intended to be used as a full Oracle UCM Managed Server in addition to servicing Oracle I/PM, then the Oracle UCM administrator should review the automatic configurations through the administration interfaces in Oracle Content Server. The additional configuration steps described in Chapter 5, "Configuring Oracle Universal Content Management," of Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite should be done on the Oracle UCM Managed Server to fully configure it for production.
The Oracle I/PM administrator should verify that the default Oracle UCM configurations are correct for use by the Oracle I/PM Managed Server. For Oracle I/PM use, many of the Oracle UCM postinstallation configuration steps, such as configuring Oracle Inbound Refinery, are not required.
In Section 7.5.2, "Verifying the AXF Installation with HelloBpel," of Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite, the following values to enter for Step 5 are not correct:
Solution Namespace: HelloBpel
Command Namespace: OPEN_TASKLIST
User Name: jcooper
Here are the correct values to enter for Step 5:
Solution Namespace: HelloBPEL
Command Namespace: StartHelloBPEL
User Name: A valid Oracle I/PM user; for example, weblogic
The preceding Oracle I/PM user needs to be part of a group named California. If this group does not exist, then create it, and add the user to the group.
Included per bug 10076301.
For Oracle Application Extension Framework (AXF) in Oracle I/PM Managed Servers that run in a cluster or other distributed configuration, you need to configure the Java Object Cache (JOC) to be distributed to all of the Managed Servers.
You can use the MW_HOME/oracle_common/bin/configure-joc.py Python script, in the Middleware home, to configure the JOC on all of the Managed Servers in distributed mode. The script runs in the Oracle WebLogic Scripting Tool (WLST) online mode and expects the Administration Server to be up and running.
Note:
After configuring the Java Object Cache, restart all affected Managed Servers for the configurations to take effect.To enable the JOC in distributed mode with the configure-joc.py script:
Connect to the Administration Server with a WLST command; for example:
MW_HOME/oracle_common/common/bin/wlst.sh
$ connect()
Enter the Oracle WebLogic Administration user name and password when prompted.
After connecting to the Administration Server with WLST, use the execfile command to start the script; for example:
wls:/mydomain/serverConfig>execfile('MW_HOME/oracle_common/bin/configure-joc.py')
Configure JOC for all the Managed Servers for a given cluster.
Enter y when the script prompts whether you want to specify a cluster name, and also specify the cluster name and discover port when prompted. This discovers all the Managed Servers for the given cluster and configures the JOC for each Managed Server. The discover port is common for the entire JOC configuration across the cluster. An example follows:
Do you want to specify a cluster name (y/n) <y> y Enter Cluster Name : IPM_Cluster Enter Discover Port : 9988
Here is a sample walkthrough for using configure-joc.py for high availability (HA) environments:
execfile('MW_HOME/oracle_common/bin/configure-joc.py')
.
Enter Hostnames (eg host1,host2) : IPMHOST1, IPMHOST2
.
Do you want to specify a cluster name (y/n) <y> y
.
Enter Cluster Name : IPM_Cluster
.
Enter Discover Port : 9991
.
Enter Distribute Mode (true|false) <true> : true
.
Do you want to exclude any server(s) from JOC configuration (y/n) <n> n
For more information, see "Configuring the Java Object Cache for Oracle WSM" and "Running CacheWatcher to Verify Java Object Cache" in Oracle Fusion Middleware High Availability Guide.
For each Managed Server using the Sun JDK, you need to set the size of the heap allocated for the Java Virtual Machine (VM) to 512 MB rather than 1 GB so that programs configured to use all available space will not fail at initialization. Address space must be reserved for the permanent generation, and the MaxPermSize setting for a Managed Server reduces the space available for the rest of the heap.
The Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite and Oracle Fusion Middleware Quick Installation Guide for Oracle Enterprise Content Management Suite recommend setting the following Java VM memory parameters for the SUN JDK:
-Xms256m -Xmx1024m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=1024m
The MaxPermSize value, however, should be set to 512m. Before you start the Administration Server or any Managed Server for your Oracle WebLogic Server domain, you can set the USER_MEM_ARGS environment variable as follows:
set USER_MEM_ARGS="-Xms256m -Xmx1024m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m"
You can put this command in the startup script for a Managed Server or in a command (.cmd) file.
For more information, see "Increasing the Java VM Heap Size for Managed Servers" in the Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite.