Skip Headers

Oracle® Configuration Manager Installation and Administration Guide Release 10.3.6 Part Number E24182-01 |
Home | Book List | Contents | Index | Contact Us

Previous | Next
| PDF · Mobi · ePub

# 2 Pre-Installation Requirements

This chapter lists the pre-installation requirements you need to consider before installing Oracle Configuration Manager. This chapter contains the following sections:

- Section 2.1, "General Pre-Installation Requirements"

- Section 2.2, "Considerations for Various Targets"

## 2.1 General Pre-Installation Requirements

Before installing Oracle Configuration Manager, ensure that the following pre-installation requirements are met:

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

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

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

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

5. If you are using the Oracle Support Hub, have the Oracle Support Hub URL available.

6. Should a proxy server be required, have the proxy server, port, and password information available if they are required to connect to the Internet.

7. Oracle Configuration Manager is a 32-bit product, not a 64-bit product. As such, 32-bit libraries on UNIX platforms must be available.

## 2.2 Considerations for Various Targets

This section elaborates on the considerations for the various targets. The targets include:

- Section 2.2.1, "Oracle E-Business Suite Installation Considerations"

- Section 2.2.2, "Oracle Retail Product Line Installation Considerations"

- Section 2.2.3, "Oracle Business Intelligence Enterprise Edition Installation Considerations"

- Section 2.2.4, "Siebel Customer Relationship Management Installation Considerations"

- Section 2.2.5, "JD Edwards EnterpriseOne Installation Considerations"

- Section 2.2.6, "Oracle Hyperion Enterprise Performance Management System Installation Considerations"

### 2.2.1 Oracle E-Business Suite Installation Considerations

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

Note:

You must not install Oracle Configuration Manager in the APPL_TOP or the 8.0.6 Oracle home.

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.

### 2.2.2 Oracle Retail Product Line Installation Considerations

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.

### 2.2.3 Oracle Business Intelligence Enterprise Edition Installation Considerations

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

### 2.2.4 Siebel Customer Relationship Management Installation Considerations

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

### 2.2.5 JD Edwards EnterpriseOne Installation Considerations

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`

### 2.2.6 Oracle Hyperion Enterprise Performance Management System Installation Considerations

Oracle Hyperion Enterprise Performance Management System release 11.1.2.0 is the earliest supported release that can be used with Oracle Configuration Manager.

### 2.2.7 PeopleSoft Installation Considerations

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