This chapter lists the pre-installation requirements you need to consider before installing Oracle Configuration Manager. This chapter contains the following sections:
Before installing Oracle Configuration Manager, ensure that the following pre-installation requirements are met:
Decide whether you need to use a shared home. Oracle Configuration Manager should only be installed as a shared home if the Oracle Home where it is being installed has been installed as a shared home. See Appendix A, "Shared Homes" for more information regarding shared homes.
Shared homes are only used when configuration files must be placed in a separate location from the common executables.
You can use either JDK or JRE for the runtime environment. If you decide to use JDK, you must ensure that the required JDK version (1.2.2 or later on UNIX, and 1.3.1 or later on Windows) is present in the <ocm_install_root> directory of the system on which Oracle Configuration Manager is being installed or the JAVA_HOME environment variable is pointing to an appropriate JDK directory.
If you decide to use the Oracle Support Hub, you can use either JDK or JRE but they must be at version 1.4 or higher.
If you use a proxy server that requires NTLM authorization scheme then the version of Java must be 1.6 or higher.
On Windows environments, ensure that the version of Windows Script Host (WSH), is 5.6 or higher. Windows Script Host is part of the Visual Basic Script functionality. To check the version, run the cscript command and verify the output.
C:> cscript Microsoft (R) Windows Script Host Version 5.7 Copyright (C) Microsoft Corporation. All rights reserved.
For Connected configurations, specify credentials using one of the following methods.
You must have your My Oracle Support User Name (e-mail address) and Password available because they are required when configuring Oracle Configuration Manager executing the setupCCR command without arguments. If you only provide an e-mail address and no password during set up, Oracle Configuration Manager will be registered in unauthenticated mode. Note that unauthenticated mode is not recommended.
or
You must have your Customer Support Identifier (CSI) and your My Oracle Support User Name available.
If you are using the Oracle Support Hub, have the Oracle Support Hub URL available.
Should a proxy server be required, have the proxy server, port, and password information available if they are required to connect to the Internet.
For 32-bit UNIX platforms, 32-bit libraries must be available.
This section provides additional information in consideration for the various targets. The targets include:
Oracle Business Intelligence Enterprise Edition Installation
Oracle Hyperion Enterprise Performance Management System Installation
In an Oracle E-Business Suite Release 11i installation, you must install and configure the Oracle Configuration Manager in the iAS Oracle home and in the database Oracle home. After installing Oracle Configuration Manager, instrument the database and Oracle E-Business Schema for configuration collections as described in Section 3.9.2, "Instrumenting the Database for Configuration Collection".
Important:
For R12 Oracle E-Business Suite customers who want to use / configure Oracle Configuration Manager releases 10.2.6 and earlier, comply with the following:Do not manually download and install Oracle Configuration Manager in a Release 12 environment. Rather, to install Oracle Configuration Manager in an Oracle E-Business Suite Release 12 installation, you must use Rapid Wizard and / or AutoConfig to install and configure Oracle Configuration Manager. This process, along with known issues and other considerations for E-Business Suite users, is described in the My Oracle Support Note 406369.1.
For R12 Oracle E-Business Suite customers who want to use or configure Oracle Configuration Manager releases 10.2.7 and later, to take advantage of the support for native integration, review My Oracle Support Note 727157.1.
In an Oracle Retail 13.0 product line installation, you must install and configure the Oracle Configuration Manager in the installation directory corresponding to the application.
The following Oracle Retail product application zip files include the Oracle Configuration Manager installer zip file.
Oracle Retail Merchandising System (Forms application zip)
Oracle Retail Price Management (Java application zip)
Oracle Retail Invoice Matching (Java application zip)
Oracle Retail Allocation (Java application zip)
Oracle Retail Integration Bus (RIB Kernel distribution)
Oracle Retail Store Inventory Management (Java application zip)
Oracle Retail Central Office
Oracle Retail Back Office
Oracle Retail Labels and Tags
Oracle Retail Predictive Application Server
Oracle Retail Advanced Inventory Planning (Java application zip)
Oracle Retail Workspace (ORW application zip)
Refer to My Oracle Support note 559539.1 for more information of how to perform this installation.
In an Oracle Business Intelligence Enterprise Edition (BI EE) installation, you must install and configure the Oracle Configuration Manager in the installation directory of the Business Intelligence product (SAROOTDIR) and in the database home.
Configuration collection covers the Analytics Server, Presentation Server, Analytics Web Plugin, Scheduler, Cluster Controller and DAC components of the BI stack. The current Oracle Configuration Manager release has been certified for 7.8.4 and 10.1.3.2 releases of Business Intelligence.
After installing Oracle Configuration Manager, instrument the database and Oracle Business Intelligence Enterprise Edition Schema for configuration collections as described in Section 3.9.2, "Instrumenting the Database for Configuration Collection".
In a Siebel Customer Relationship Management (CRM) installation, you must install and configure the Oracle Configuration Manager in the Siebel homes for CRM. For example:
On Windows, if your Siebel home directory is c:\sia81, then your Oracle Configuration Manager installation would be in the c:\sia81\ccr directory.
On UNIX systems, if your Siebel home directory is /app/sia81, then your Oracle Configuration Manager installation would be in the /app/sia81/ccr directory.
The current Oracle Configuration Manager release has been certified for 7.7, 7.8, 8.0 and 8.1 releases of CRM.
After installing Oracle Configuration Manager, instrument the database and Oracle Business Intelligence Enterprise Edition Schema for configuration collections as described in Section 3.9.2, "Instrumenting the Database for Configuration Collection".
In a JD Edwards EnterpriseOne Tools Release 8.97or 8.98 installation, the Oracle Configuration Manager installation is only supported through the JD Edwards Server Manager console, not through the Oracle Configuration Manager command line installation described in this document.
Note:
Oracle Configuration Manager does not currently support the JD Edwards iSeries platform.For more information about installing and administering Oracle Configuration Manager on JD Edwards EnterpriseOne, refer to the JD Edwards EnterpriseOne Tools Release Server Manager Guides, located on My Oracle Support site: https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=747330.1
Oracle Hyperion Enterprise Performance Management System release 11.1.2.0 is the earliest supported release that can be used with Oracle Configuration Manager.
There are no special steps required for the installation and configuration of Oracle Configuration Manager in the PeopleSoft home.
Oracle Configuration Manager works in tandem with PeopleSoft Environment Management Framework (EMF) for collecting configuration data from the PeopleSoft environment. The PSEMAgent must be running on the instance for gathering configuration data. PSEMAgent, after crawling, drops the environment data in XML format (.psft extension) to the PS_HOME/ccr/state folder.
To learn more about configuring EMF, refer to:
Enterprise PeopleTools 8.50 PeopleBooks: PeopleSoft Change Assistant, Configuring and Running Environment Management Components
Oracle Configuration Manager can be installed and configured by the oracle user as long as the base directory is owned by the root user or the oracle user.
If Oracle Configuration Manager has not been installed in the ASM home and Oracle Grid Infrastructure home ($ORACLE_HOME), do the following:
Log in as the root user and unzip the Oracle Configuration Manager kit into the ASM home or the Oracle Grid Infrastructure home
Change the owner of the $ORACLE_HOME/ccr directory and its files to the oracle user:
chown -R oracle:<group> $ORACLE_HOME/ccr
where <group> is the user group for the oracle user
Log in as the oracle user
Setup Oracle Configuration Manager in the $ORACLE_HOME by executing:
$ORACLE_HOME/ccr/bin/setupCCR
The OCM Collector should be installed and configured in the fmw_home/utils directory, and the appropriate environment variables must be set for BEA_HOME and WL_HOME. See Table 5-1, "Environment Variables Used in Oracle Configuration Manager" in the Verifying Environment Variables section for details.
The OCM Collector should be deployed in both the grid home as well as the Oracle Database home:
Grid home default location: /u01/app/11.2.0/grid
Oracle Database home: /u01/app/oracle/product/11.2.0/dbhome_1
To ensure the OCM Collector is installed and cofigured, verify the ccr/bin/configCCR utility exists in the Oracle product home. See the configCCR section for details.
The Oracle database instances require a one-time only instrumentation. Perform the instrumentation after the OCM Collector has been updated to the latest release.
To perform database instrumentation, run:
ccr/admin/scripts/installCCRSQL.sh collectconfig -s <sid> -r <sysdba-account-pwd>
where:
<sid> is a database instance
<sysdba-account-pwd> is the password for an account that holds SYSDBA privilege
For an Oracle RAC database, the instrumentation only needs to be performed on one instance.
Note:
Instrumentation must be performed on each database for configuration collections to be performed.The upload of configuration information for Engineered Systems (such as, Exadata Database Machine, Exalogic) is supported through Oracle Configuration Manager (OCM) or the Enterprise Manager Harvester. If you use Enterprise Manager Cloud Control 12c to manage your Engineered Systems, then the Enterprise Manager Harvester will upload all the configuration to CCR. See Appendix B, "Collecting OCM Data in Enterprise Manager and Ops Center Environments," for information to configure the Enterprise Manager Harvester.
If you are not using Enterprise Manager Cloud Control 12c's Harvester for managing your Engineered Systems, you must configure the OCM Collector in the compute nodes. The OCM Collector should be configured in the software product home in the same manner as it would be configured in a non-Engineered Systems configuration. For example, for an Oracle RAC Database instance running on an Exadata Database Machine, OCM Collector should be configured in all the instances of the compute nodes. The database should also be instrumented for configuration collection. See Post-Installation Database Configuration for more information.
Configurations Supported through OCM and Enterprise Manager Harvester
Both Enterprise Manager Harvester and OCM will upload the following software and Engineered Systems configurations:
For Oracle software configurations:
Enterprise Manager Harvester and OCM will upload all currently supported Oracle software products running in Engineered Systems.
For Engineered System configurations:
Enterprise Manager Harvester and OCM will detect and upload configurations about Exadata Database Machine and Exalogic systems. For example, your Exadata Database Machine system will look like this in My Oracle Support:
<screen shot>
Note:
Only Software products running on SPARC SuperCluster (SSC) are supported through OCM and Enterprise Manager Harvester. Enterprise Manager Harvester and OCM do not support the detection and upload of the configuration about the (SSC) system at this time.For an Engineered System, it is strongly recommended that you use the most recent version of OCM, and associating the relevant OCM instance with the Engineered System's Hardware Customer Support Identifier (CSI). Once associated, you can log Service Requests (SRs) for both hardware and software products installed on your Engineered System. For more information, refer to Logging an Engineered System Service Request using Oracle Configuration Manager (OCM) (Document 1450983.1), available in My Oracle Support:
https://support.oracle.com
If you are not using Oracle Platinum Services or Enterprise Manager Cloud Control 12c's Harvester for managing your Engineered Systems, you must configure the OCM Collector in the compute nodes. Refer to Oracle Configuration Manager (OCM) for Engineered Systems (Document 1446458.1) in My Oracle Support for information on deploying the OCM Collector to the compute nodes.
Note:
Always use the hardware CSI to upload your Engineered Systems configurations.Platinum Services for Engineered Systems
In addition to other hardware products, Oracle Platinum Services have been offered to Engineered Systems with Certified Platinum Configurations. For more information about the the support policies and configurations, see the following documents:
Oracle Platinum Services Policies: http://www.oracle.com/us/support/library/platinum-services-policies-1652886.pdf
Certified Platinum Configurations: http://www.oracle.com/us/support/library/certified-platinum-configs-1652888.pdf
For more information about Oracle Engineered Systems products, see:
http://www.oracle.com/us/products/engineered-systems/index.html