35.1 File Formats Wizard Might Display Error First Time After Upgrade

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:

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:

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.

35.5 Patch 12369706 for Oracle Information Rights Management

The 11.1.1.5.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.

35.6 Using Node Manager with Oracle ECM

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 AdminServer, IPM_server1, and 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 true.

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.

35.6.1 Configuring a Machine

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.

To configure a machine through the Fusion Middleware Configuration Wizard:

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:

Name

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 localhost.

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 1 to 65535. The default value is 5556.

35.6.2 Assigning Servers to a Machine

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.

To assign servers to a machine through the Fusion Middleware Configuration Wizard:

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.

35.6.3 Enabling the Use of Startup Scripts Before Starting Node Manager

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.