Configuring OCM for WebCenter Content

This article applies to WCC and later.

Oracle Configuration Manager (OCM) is a tool used to upload configuration information to the Management Repository within My Oracle Support. Once configured, OCM collects environmental information from your WebCenter environment and provides the following:

  • Checks if all relevant and recommended patches have been applied. Proactive patch recommendation information is flagged within the My Oracle Support Dashboard.
  • Performs health checks against the environment and gives proactive recommendations to improve system stability and performance.
  • When multiple snapshots of the environment have been uploaded to the Repository, changes can be examined between two snapshots.

Location of OCM

The binaries for OCM are located in <Middleware_Home>/utils/ccr/bin

The out-of-the-box version of OCM with 11g WebCenter is not the latest version. OCM will need to be manually upgraded before configuring. See the ‘Manually Upgrading OCM’ section of this blog.

Testing if OCM is Already Configured

Within <Middleware_Home>/utils/ccr/bin, run emCCR status, similar test results to below confirms your environment is already configured for OCM:

Oracle Configuration Manager – Release: – Production
Copyright (c) 2005, 2011, Oracle and/or its affiliates. All rights reserved.
Start Date 26-Oct-2011 13:23:13
Last Collection Time 07-Sep-2011 16:22:56
Next Collection Time 27-Oct-2011 12:30:00
Collection Frequency Daily at 12:30
Collection Status idle
Log Directory c:\oracle\middle~1\utils\ccr\hosts\\log
Registered At 06-Sep-2011 12:30:43
Automatic Update On
Collector Mode Connected

Connected Mode:

  • Data and configurations are automatically uploaded to Oracle’s repository.
  • OCM updates are automated.

Disconnected Mode:

  • OCM data is not being uploaded to Oracle’s repository.
  • To operate in disconnected mode, it is necessary to perform a manual collection and upload the resulting ocmconfig.jar to My Oracle Support.
  • OCM must be updated manually when a new version is released.

Configuring OCM

  1. Set the value of $ORACLE_HOME in (<Middleware_Home>/user_projects/domains/bin) to <Middleware_Home>/utils
  2. Run setupCCR from <Middleware_Home>/utils/ccr/bin – This will set up OCM in Connected Mode.
    1. This will prompt for your Oracle Support credentials.

To switch to disconnected mode, execute configCCR -d then emCCR collect.

Scheduling OCM Collections

By default, when OCM has been configured for connected mode, collections will be performed daily and uploaded to My Oracle Support.

The following is an example of configuring OCM to perform uploads on the fourth day of the month at 11:30PM:

ORACLE_HOME/ccr/bin/emCCR set collection_interval=”FREQ=MONTHLY;BYMONTHDAY=4;BYHOUR=23;BYMINUTE=30″

Once a configuration has been uploaded, it can be viewed from the Dashboard tab in My Oracle Support.

Manually Upgrading OCM

  1. Download the latest version of OCM. This is found under the Collector tab in My Oracle Support or by downloading the latest OCM bundle.
  2. Run the emCCR update_components command.


./emCCR update_components -distribution=”/home/oracle/patches/OCM/”

Oracle Configuration Manager – Release: – Production
Copyright (c) 2005, 2010, Oracle and/or its affiliates. All rights reserved.
Deploying core – Version
engines.jar is an old package. No update required.
metricdata.jar is an old package. No update required.
Deploying scripts – Version

./emCCR status

Oracle Configuration Manager – Release: – Production
Copyright (c) 2005, 2010, Oracle and/or its affiliates. All rights reserved.
Log Directory /u01/middleware/utils/ccr/hosts/demohost/log
Collector Mode Disconnected
To switch to connected mode, please run <MW_HOME>/utils/ccr/bin/configCCR

Additional Items

  • A collection may also be performed behind the scenes if you run RDA. The RDA output will include a file called “RDA_OCM_payload.jar”.
  • A manual OCM collection can be uploaded to the OCM Repository via the My Oracle Support ‘Create SR’ process. If all you want to do is upload an OCM collection to the Repository, you do not actually have to submit the Service Request. In the Upload Files screen, upload the ocmconfig.jar. Then click the “Save as Draft” button. You can then exit the SR creation process. Even if you delete the draft SR, the uploaded OCM collection will remain in the OCM Repository for future use and reference. It will take a few minutes before the uploaded configuration becomes visible in the Dashboard.

Is your organization looking for ways to proactively manage your WebCenter environment? Is your current environment slow or running on an old patch set with known vulnerabilities? Contact Inspired  ECM today to learn about our health check and managed service offerings.