This chapter lists the pre-installation requirements you need to consider before installing Oracle Configuration Manager. This chapter contains the following sections:
Before proceeding, you must 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.
OCM supports installation on the following platforms:
Oracle Solaris
SPARC (32-bit and 64-bit)
x86 (32-bit and 64-bit)
Linux
x86 (32-bit and 64-bit)
As of release 10.3.8, OCM has a native 64-bit client for Oracle Linux x86_64. Therefore, the 32-bit libraries are no longer required for Oracle Linux x86_64.
HP-UX
Itanium
IBM AIX5L Based Systems (32-bit and 64-bit)
Microsoft Windows: 2000, XP, Server 2003 (32-bit and 64-bit), 2008, 2012, Vista, NT, other Win 32 platforms
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.
Note:
Installation of Oracle Configuration Manager on a RAW device is not supported. Configuration of the software will result in the following error being returned.Unable to Determine Oracle Configuration Manager content receiver endpoint Oracle Configuration Manager endpoint unknown
Note:
The following platforms are supported for OCM 12.0 (12.0.0.2) and earlier:HP-UX:
PA-RISC (32-bit and 64-bit)
Linux:
Itanium
PowerPC
IBM zSeries Based Linux
If you are already using pre-12.1 OCM for these platforms, then pre-12.1 OCM should be able to send data to Oracle, and you can continue to use all current MOS services.
OCM supports installation on the following software versions:
Database
Oracle Database releases 9.2.0.8 and later
Oracle Real Application Clusters releases 9.0.1 and later
Oracle Exadata 11.2.0.1
ASM 10.2 and later
Ensure that the required JDK version is present in the <ocm_install_root> directory of the system on which OCM is being installed or the JAVA_HOME environment variable is pointing to an appropriate JDK directory. Its recommended to use JDK 1.5 and later; however, the following versions of JDK are minimally supported
JDK or JRE 1.2.2 or later on UNIX platforms (including Linux)
JDK or JRE 1.3.1 or later on Windows
JDK or JRE 1.4 or later if using OCM with an Oracle Support Hub
JDK or JRE 1.6 or later if your proxy server requires NTLM for authentication.
Note:
In preparation for an upcoming security update (around June 2016), our servers will be upgraded with the latest SSL certificate that will be based on the new SHA2 algorithm.For OCM 12.1.2, the collector supports the SHA2 algorithm; so, when the server is updated with the SSL certificate, all collectors earlier than OCM 12.1.2 will fail to connect to the server. To avoid any connection issues, upgrade all of your collectors to OCM 12.1.2 before June 2016.
JDK/JRE 1.4 and earlier does not support SHA2. If your collector is running on JDK 1.4 or earlier, then upgrade to a newer version. You can download the latest version from:
http://java.com
If a supported JDK or JRE is not present in the ORACLE_HOME, but a valid JDK or JRE is present in another directory, you must define the JAVA_HOME environment variable to point to that directory.
Note:
The Java Development Kit (JDK) distributed by the GNU Free Software Foundation is not supported by Oracle Configuration Manager. The GNU version of JDK does not support either required command qualifiers or class loader capabilities.32-bit libraries
Oracle Configuration Manager is a 32-bit application. Ensure that you have installed the 32-bit C run-time libraries so that Oracle Configuration Manager can function normally.
Notes:
For 32-bit UNIX platforms, 32-bit libraries must be available
As of release 10.3.8, OCM has a native 64-bit client for Oracle Linux x86_64. Therefore, the 32-bit libraries are no longer required for Oracle Linux x86_64.
Oracle Application Server releases 9.0.3 and later (note that 1.0.2.2 is only supported in an E-Business Suite configuration)
Oracle WebLogic Server 10.3.2 and later
Oracle Business Intelligence Enterprise Edition/Siebel Analytics versions 7.8.4/10.1.3.2
Oracle Hyperion Enterprise Performance Management System 11.1.2 and later
Oracle Fusion Middleware release 11.1.1.1 and later
Applications
Oracle Enterprise Manager versions 9i, 10g, 11g, and 12c
Oracle E-Business Suite 11.5.4 and later, R12 and later
Peoplesoft People Tools version 8.4.8 and later, 8.5 and later
Siebel CRM versions 7.7, 7.8, 8.0, 8.1.1
JD Edwards Enterprise One 8.97 and later
Oracle Retail version 13.0 and later
Primavera P6 7.0
Primavera CM 13.0
Oracle Collaboration Suite version 10.1.0.2 and later
Oracle Beehive 2.0
Make sure the following network and internet settings are in place before installing OCM:
If you configure OCM in connected mode, you will need to know how OCM will connect to Oracle to upload the collected data. The default option is to have OCM connect directly to the Internet. OCM supports three connection methods:
Direct connection (using port 443).
OCM initiates communication with Oracle using HTTPS. If you have direct connectivity to the internet from your system, no additional configuration is required. OCM contacts https://ccr.oracle.com on port 443.
Connection using a proxy server (either with or without user authentication).
If a proxy server is being used, you must supply the host name (or IP address) and port number of the proxy server. If the proxy server requires authentication, you will also need the connection credentials for the proxy (user name and password).
If you are unsure of these details, the settings used in your web browser may work.
To view these settings in Internet Explorer:
From the Tools menu, select Internet Options, select Connections, select Lan Settings, then select Advanced.
To view these settings in Mozilla Firefox:
From the Tools menu, select Options, select Advanced, select Network, then select Settings.
Connection using a Support Hub. Using this method, the server on which OCM is installed does not need a connection to the Internet, but rather only the ability to reach the internal server on which the Support Hub is deployed. If a Support Hub is being used, you must supply the URL and port of the Support Hub. You will also need the proxy server information if a proxy server is required to access the Support Hub.
Note:
If you configure OCM in disconnected mode, connection information is not required.If installing OCM 10.3 or later: You must have a My Oracle Support ID and either (a) the associated password for that My Oracle Support ID, or (b) a Customer Support Identifier (CSI) registered for that My Oracle Support account.
When configuring Oracle Configuration Manager 10.3 or later, the default setup method requires your My Oracle Support ID and password for the configuration data collected to be accessible or usable by you in My Oracle Support.
Optionally (recommended for My Oracle Support accounts with more than one CSI in their profile), you can specify a My Oracle Support ID and CSI.
If you have any problems with registration, log in to My Oracle Support for assistance:
https://support.oracle.com
Alternatively, there is a dedicated page for the latest OCM documentation located in the My Oracle Support - Collector home page.
OCM uses the features of the Secure Socket Layer (SSL) and HTTPS for all communications.
All communications with Oracle is directed to https://ccr.oracle.com on port 443.
You can use the following methods to test for a viable network connection to Oracle. They are not listed in order of Oracle preference, but in a logical sequence that one can work through to determine the method requiring the least configuration work.
If you have questions concerning your specific network topology, contact your local network administrator.
To test a direct connection:
| Test Procedure | Success Indicator | Comments |
|---|---|---|
telnet ccr.oracle.com:443 |
Trying...
Connected to... |
Test the route to the Oracle servers |
To test connection through a proxy server:
| Test Procedure | Success Indicator | Comments |
|---|---|---|
| Step 1:
|
Trying...
Connected to... |
Use the host name of your proxy server and the port your proxy server listens |
| Step 2:
|
HTTP connection established | Confirmation on connection to the target |
| Note: To avoid a time out, the steps must be executed in rapid sequence. | ||
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. My Oracle Support Note 406369.1 describes this process, along with known issues and other considerations for E-Business Suite users.
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 and 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 configured, 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 Postinstallation 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 currently do not support the detection and upload of the configuration about the (SSC) system.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 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