<Insert Picture Here> Configuration Manager Installation Process

Agenda Collector and Configuration Manager Unzipping the distribution file Creation of the CCR directory Running Setup Installation, License, and Configuration Summary Q&A

Collector / Configuration Manager Collector Data Collector - deployed onto customer s systems, Collects configuration information about the system, Uploads the information to Oracle s Customer Configuration Repository Configuration Manager Provides Simplified Configuration Management Faster Problem Resolution Improved System Stability

Oracle Configuration Manager The Four C s Configuration Collector (at Customer) Collector deployed into each Oracle Home Allows configuration information to be collected and uploaded directly from the customer site Collector is auto-updating Uploads initiated by collector over a secure pipe Centralized repository (at Oracle) Contains the customer configuration information Can be leveraged to provide: Health checks Patch advice Inventory and usage Content Server (at Oracle) Acts as publisher of revised configuration collector content for download by the collector. Connection with My Oracle Support(at Oracle) Allow customers to log SRs referencing the uploads configurations Allow customers to view their configuration details

Oracle Configuration Manager What Data is Collected? Captures information about: Host Oracle Software and Patches E-Business Suite Patches Database and ias Patches Third party software inventory Access to this data is limited by: Hardware System Software Oracle Product Information Collected data does not include: Business Transactions Passwords Control Sensitive Information

Configuration Manager: The Big Picture My Oracle Support Support System View Interface Oracle CCR Knowledge Management HTTPS Proxy Server Simple install/ command UI Customer Site

Collector Designed to collect configuration data with no customer intervention, no management cost Simple install 30 seconds Small footprint 15.5MB Download (self contained) Designed as a utility/command-line vs. daemon Collects on a scheduled basis (cron) Self updating (more on this later)

Collector (cont d) Installed in every ORACLE_HOME Launched by lightweight scheduler process Enhanced target discovery (no manual configuration) Target Credential not required! Collects configuration data for elements in the home Uses Grid Target Metadata definitions Uploads configuration data that has only changed Initial Linux host config ==.5MB, subsequent updates 900 bytes Provides a secure pipeline to Oracle

Security How we ensure that All connections go trough https/ssl 128 bit with public/private key exchange All connections go to https://ccr.oracle.com:443 You can instruct OCM to use a proxy if you are not connected to the internet directly You can create firewall rules to allow outgoing traffic to CCR Host More informations: http://download.oracle.com/docs/html/e12881_01/security.htm http://download.oracle.com/docs/html/e12882_01/connectivity.htm

Possible Scenarios : 1 Direct Connection (test box) ccr.oracle.com:443 customer server (test box)

Possible Scenarios : 2 Proxy server connection: proxy server ccr.oracle.com:443 customer server

Possible Scenarios : 3 Firewall/Proxy protected connections: ccr.oracle.com:443 proxy server customer server firewall 2 with rules that allow traffic only to ccr.oracle.com:443 firewall 1 with rules that allow traffic ony to ccr.oracle.com:443

Possible Scenarios : 4 Disconnected Mode (no connection with the Internet): ccr.oracle.com:443 customer server Using a draft SR is possible to upload configurations files as we used to do with RDA

Possible Scenarios : 5 Oracle Support Hub (Former Configuration Manager Repeater): intranet servers are connected only to a system that can connect to the internet customer servers ccr.oracle.com:443 proxy server Oracle Configuration Manager Repeater firewall 2 with rules that allow traffic only to ccr.oracle.com:443 firewall 1 with rules that allow traffic ony to ccr.oracle.com:443

Disconnected Mode Collector can be configured at install or later in disconnected mode No automatic collections No uploads User s job: Manually perform collection of data Take output to a machine that has a connection Upload it to My Oracle Support; will be able to attach it to a SR Once uploaded, the same capabilities are enabled as if the collection was performed in connected mode

Collection and Distribution Utilities Harvester EM Grid control for Configuration Collection Mechanism for collecting System Configuration Data Eliminates the need to install a second collection mechanism on their Servers For addition information see Note 848962.1 Oracle Support Hub Single point for uploading configuration data Makes it easier for the configuration collections to be passed up to CCR Allows many OCM instances to upload data via a single internal point For more information view Note 791357.1 (Companion Distribution Guide) Mass Deployment Tool Single Point distribution tool Allows for the installation of Configuration Manager software to multiple homes from a single point For more information view Note 791357.1 (Companion Distribution Guide) To start using the Oracle Support Hub and the Mass Deployment Tool Download it from the Collectors tab in My Oracle Support

Collector Auto-Update Once installed, customer shouldn t have to pay any attention: Install and Forget, for customer convenience Oracle publishes software updates for the collector on the content server (digitally signed for security) Directive transparently performed at start of every scheduled collection Passes current OCM Collector component inventory Receives list of files to download Content is validated that it is signed by specific certificate Auto-updating can be enabled or disabled through OCM configuration commands

Collector Installation Requires Metalink Id (My Oracle Support login) Password Supports Proxy specification Command line arguments permitted to eliminate prompting Steps: 1. Unzip distribution 2. Run setup command to configure and register 3. Optionally instrument database (including for EM rep or EBS)

Stage the Distribution File Installation Zip File Distribution [named P5567658_1030_LINUX-86.ZIP ] Staged in the Oracle_Home directory called stang05 db_2.

Unzip the Distribution File Unzip the Distribution Creates CCR sub-directory In Oracle_Home

Running Setup Go into the CCR directory Go into the bin directory Run setup CCR

License Agreement ORACLE CONNECTION TOOLS AGREEMENT Introduction ------------ Customer (hereafter "Customer" or "you") agrees to the following conditions regarding the use of Oracle's live connection tools, including Oracle Configuration Manager and Remote Diagnostic Agent, that you have either downloaded from Oracle's technical support web site or which you received from Oracle, and the related services that Oracle provides in connection with those tools (collectively, the "Tools"). The individual entering into this agreement certifies that he/she has authority to enter into this agreement on Customer's behalf. These terms supplement the terms of your licensing or distribution agreement with Oracle and the terms of Oracle's Technical Support Policies. In the event of a conflict between your licensing or distribution agreement or the Technical Support Policies and the following terms, the relevant terms below will control your use of the Tools. Export Compliance ----------------- You agree that you will comply with all United States export laws and that none of the Tools will be exported, directly or indirectly, in violation of such laws. Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores, CA 94065 USA Worldwide Inquiries: Phone (+1) 650.506.7000 *** Do you accept this license agreement? (Y/N) [Y]: Y

Provide your Credentials

Connected / Disconnected Mode Connected Mode Disconnected Mode -d

Instrumenting the Database To configure the database for configuration collection -Go to the Bin directory -Go to /admin/scripts/ installccrsql.sh (UNIX) or installccrsql.exe (Windows) -Now this database will be instrumented correclty and your configuration will show up -Complete instruction can be found in 2.3.2 of the Installation guide -For an Enterprise Repository or an E Business Suite. Then there is additional line of instrumentation that you will need to do very similar to what you just did Which can be found in 2.3.2.1 of the Installation guide -For the Enterprise Manager Grid control you will need to follow 2.3.2.2 of the Install Guide.