An Oracle White Paper January 2012

Governance, Risk and Compliance 8.6.4.1500 with Real Application Clusters

Governance, Risk and Compliance 8.6.4.1500 with Real Application Clusters

Disclaimer
The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracles products remains at the sole discretion of Oracle.

Governance, Risk and Compliance 8.6.4.1500 with Real Application Clusters

Introduction ....................................................................................... 2 Creating a New RAC Environment .................................................... 2 Updating an Existing RAC Environment ............................................ 3

Governance, Risk and Compliance 8.6.4.1500 with Real Application Clusters

Introduction
The database that serves Oracle Governance, Risk and Compliance (GRC) can be one in which Real Application Clusters (RAC) is enabled. To deploy GRC on a RAC instance, you need to add certain steps to the procedures you complete to install GRC, as documented in the Governance, Risk and Compliance Installation Guide for version 8.6.4. Even if you have already deployed GRC on a RAC instance for the initial 8.6.4 release of GRC, you need to complete some additional steps. In this case, skip ahead to Updating an Existing RAC Environment.

Creating a New RAC Environment

Deploy GRC on a RAC instance as you install GRC. First, install an Oracle 11gR2 RAC database with Single Client Access Name (SCAN) mode on two nodes. Next, complete procedures documented in chapter 2 of the Governance, Risk and Compliance Installation Guide for version 8.6.4, up to a section titled EGRCM Configuration. (The Installation Guide is available on Oracle Technology Network.) Where the Installation Guide instructs you to create a GRC schema, do so on the RAC database. Before proceeding to EGRCM Configuration, complete these steps: 1. Set up a jdbc-oci driver, which is used for the connection between GRC and the RAC database. a. For platform-specific libraries, go to http://www.oracle.com/technetwork/database/features/ instant-client/index-097480.html. Select the Instant Client link for the platform on which you are installing, then find the Basic download for 11.2.0.1.0.

b. Download and unzip the package into a single directory, such as instantclient. c. Set the library loading path in your environment to this directory before starting the application. On many Linux platorms, LD_LIBRARY_PATH is the appropriate environment variable.

2. Start the WebLogic Server and GRC. Be sure the library loading path is set before the WebLogic Server is started. 3. Complete the procedures documented in the Installation Guide, beginning at the EGRCM Configuration section of chapter 2. As you do, you will enter values at the Properties tab of a GRC Manage Application Configurations page. Substitute the following values for those documented in the Installation Guide:

Server Name: RAC@<SCAN_NAME>, where <SCAN_NAME> is the IP address/host name of the SCAN address configured for your RAC database. Service Identifier: The RAC service name configured for your RAC database.

4. Shut down GRC and the WebLogic Server.

Governance, Risk and Compliance 8.6.4.1500 with Real Application Clusters

5. Move ojdbc6.jar from the Instant Client package to <MW_HOME>/oracle_common/modules/ oracle.jdbc_11.1.1 as ojdbc6dms.jar. (As noted in the GRC Installation Guide, <MW_HOME> represents the full path to the home directory of your middleware installation the highest-level directory in which Fusion Middleware components exist, including WebLogic.) 6. Start the WebLogic Server and GRC.

Updating an Existing RAC Environment

If you have already deployed GRC on a RAC instance for the initial 8.6.4 release of GRC, complete these steps to update it: 1. Shut down GRC and the WebLogic Server.

2. Move grc/WEB-INF/lib/ojdbc6.jar to <MW_HOME>/oracle_common/modules/oracle.jdbc_11.1.1 as ojdbc6dms.jar. 3. Remove grc/WEB-INF/lib/cachedir. 4. Restart the WebLogic Server and GRC.

Governance, Risk and Compliance 8.6.4.1500 with Real Applicatin Clusters January 2012 Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores, CA 94065 U.S.A. Worldwide Inquiries: Phone: +1.650.506.7000 Fax: +1.650.506.7200

Copyright 2012, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark licensed through X/Open Company, Ltd. 0112