OBIEE 11g Technical Footprint

by Marty Mersinger, Solution Engineer This document attempts to provide concise information on hardware size and space requirements related to Oracles 11g BI Suite for planning purposes. Factors; such as, number of users, user types (Ad-Hoc versus Dashboard), number of reports and dashboards for example, are not taken into consideration.

Oracle Portal, Forms, Reports and Discover

a. Disk Space: 15GB b. Available Memory: 4GB c. Temp Space: 150MB d. Swap Space: 512MB

OBIEE 11g with SOA and BAM (needed for

Requirements
Oracles documented requirements are the same for Production as well as Development. With FMW 11g there is no requirement difference based on Instance Usage. A minimally size desktop may have been sufficient for OBI 10g, but due to the integration between OBI and Fusion Middle Ware (FMW) as well as the integration of FMW with database schemas it is not recommended to attempt using 11g with the same minimally sized system. Depending on the components you choose to include in your deployment will decide overall size and space for your system requirements. Listed below are the system requirements by component. These are only minimum requirements and are not an indication that you will obtain maximum performance.

Application Framework): a. CPU: dual-core Pentium 1.5 GHz or greater b. Disk Space: 15G or more c. Available Memory: 4GB or more 1. BAM Client a. Windows XP sp2 or Vista b. IE 7 or 8 c. 1 CPU at 1.2 GHz (complex dashboards require more) d. 512MB RAM e. 5MB free disk space f. 1024x768 Active Studio g. 800x600 Active Viewer h. MS Excel XP, 2003, or 2007 a. Weblogic Admin Server: 750MB b. Weblogic Managed Server running Directory Integration Services: 720MB c. Weblogic Managed Server running Oracle Identity Federation: 650MB d. Oracle Virtual Directory 105 MB e. Oracle Internet Directory: 75 MB f. Oracle Enterprise Manager Agent: 25 MB g. Oracle Process Manager and Notification Server: 5 MB

Oracle Identity Management

Minimum Memory: Physical 2GB, Available 1GB

for all Operating Systems

860 Blue Gentian Road Suite 290 Eagan, MN 55121

Tel 866.953.4757

Email info@biconsultinggroup.com

Web www.BIConsultingGroup.com

Copyright 2009, BI Consulting Group, LLC. All rights reserved. No part of this material may be reproduced, stored in a retrieval system or transmitted by any means, electronic, mechanical, photocopy, recording or otherwise, without written permission from the authors

OBIEE 11g Technical Footprint

Supported Components
This section provides supported versions of WebLogic and Oracle Database in case you may already have these deployed components. If you are installing for the first time, then the OBI 11g installation includes a limited usage license for WebLogic and the most recent Oracle 11g database would be recommended.

Supported WebLogic Server versions:

10.3.1 for Fusion Middleware 11.1.1 10.3.2 for Fusion Middleware 11.1.1.2 10.3.3 for Fusion Middleware 11.1.1.3

Repository Creation Utility (RCU) Supported Platforms RCU is available only on 32-bit x86 Linux and 32-bit Microsoft Windows operating system platforms. You can run RCU from these machines to connect to any certified versions of Oracle, IBM DB2, or Microsoft SQL Server database in order to create the schemas required by Fusion Middleware components. The database server can be running on any platform that is supported by its respective database.
If your database does not use the AL32UTF8 character set, you will see the following warning when running RCU:

Certified Databases

Using Repository Creation Utility (RCU) (11.1.1.1.0) with Database 11g (11.2.0.1) You will receive a warning message The database you are connecting is not a supported version. Enter Database with version equal to or higher than 10.2.0.4.0 in 10g or version equal to higher than 11.1.0.7.0 in 11g. Refer to the certification matrix for supported DB versions which can be safely ignored. Using 11g (11.1.0.7) with Identity Management you must apply the following patches: Linux operating systems: p7614692_111070 p7000281_111070 p8327137_111070 p7598314_111070

The database you are connecting is with non-AL32UTF8 character set. Oracle strongly recommends using AL32UTF8 as the database character set. You can ignore this warning and continue using RCU.
The user creating the RCU schemas must have SYSDBA privileges. If the user is one other than SYS, then you need to grant execute on sys.dbms_lock with grant option. There are additional specific requirements outlined within Oracles documentation by database vendor regarding schemas.

Windows operating systems: p8416539_111070_Win32 p8451592_111070_Win32 p8260294_111070_Win32

Using 11g (11.2.0.1) with OID and Oracle Data Vault Must apply patch 8897382 You must also change a line in a command rules script. Details of that change are found in the appendix of this document.

860 Blue Gentian Road Suite 290 Eagan, MN 55121

Tel 866.953.4757

Email info@biconsultinggroup.com

Web www.BIConsultingGroup.com

Copyright 2009, BI Consulting Group, LLC. All rights reserved. No part of this material may be reproduced, stored in a retrieval system or transmitted by any means, electronic, mechanical, photocopy, recording or otherwise, without written permission from the authors

OBIEE 11g Technical Footprint

Recommended Installation Scenarios

There are 3 options when installing Business Intelligence; Simple, Enterprise, and Software-Only. The Simple Install uses default values such as directories and ports on a single computer with minimum steps. The Enterprise Install allows for the creation of a new deployment or to scale out an existing deployment. Thus, it enables you to specify several configuration settings. The Software-Only Install will install the binary files and configuration is done afterwards rather than part of the installation. When installing on AIX or with a 64-bit JVM, then this installation mode is used. The following installation scenarios are recommended along with the installation mode to use. Demonstration and Evaluation Simple Install Single-User Development Simple Install Enterprise Deployment for Hosted Development and Production Enterprise Install Enterprise Deployment for Highest Levels of Availability and Security Software Only Install

Typical Developers Deployment

A typical installation for a single developers system would be similar to that listed in the following table. The numbers shown do not include space for the installation files.

Typical Enterprise Deployment

Typical hardware requirements for the Enterprise Deployment on Linux operating systems are listed in Table 1-1. For detailed requirements, or for requirements for other platforms, see the Oracle Fusion Middleware Installation Guide for that platform. Table 1-1 Typical Hardware Requirements

860 Blue Gentian Road Suite 290 Eagan, MN 55121

Tel 866.953.4757

Email info@biconsultinggroup.com

Web www.BIConsultingGroup.com

Copyright 2009, BI Consulting Group, LLC. All rights reserved. No part of this material may be reproduced, stored in a retrieval system or transmitted by any means, electronic, mechanical, photocopy, recording or otherwise, without written permission from the authors

OBIEE 11g Technical Footprint

860 Blue Gentian Road Suite 290 Eagan, MN 55121

Tel 866.953.4757

Email info@biconsultinggroup.com

Web www.BIConsultingGroup.com

Copyright 2009, BI Consulting Group, LLC. All rights reserved. No part of this material may be reproduced, stored in a retrieval system or transmitted by any means, electronic, mechanical, photocopy, recording or otherwise, without written permission from the authors

OBIEE 11g Technical Footprint

Additional Information
Oracles requirement documents include information on supported packages by Unix platform and version which aretoo numerous to list here. When planning an 11g installation, it is always recommended to review Oracles requirements and certification documents. Additionally, these documents include required environment variables and Open File Limits for Unix/Linux operating systems. http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-requirements-100147.html http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

Appendix
When using OBIEE 11g with OID and Oracle Data Valult you will need to make a change to the command rules file. Details are below: In the ORACLE_HOME/ldap/datasecurity/dbv_oid_command_rules.sql (on UNIX opera&ng systems) or ORACLE_HOME\ldap\datasecurity\dbv_oid_command_rules.sql (on Windows opera&ng systems) file, find the following code: /declare . begin . dvsys.dbms_macadm.CREATE_COMMAND_RULE( command => CONNECT ,rule_set_name => OID App Access ,object_owner => ODS ,object_name => % ,enabled => Y); . commit; . end;/ Change the following line: ,object_owner => ODS to: ,object_owner => %

860 Blue Gentian Road Suite 290 Eagan, MN 55121

Tel 866.953.4757

Email info@biconsultinggroup.com

Web www.BIConsultingGroup.com

Copyright 2009, BI Consulting Group, LLC. All rights reserved. No part of this material may be reproduced, stored in a retrieval system or transmitted by any means, electronic, mechanical, photocopy, recording or otherwise, without written permission from the authors