BIAPPS on PaaS – Sizing for Middleware and Database

Version 7

    By the BIAPPS Dev/PM Team

     

    The Oracle white paper, OBIA 11g: Oracle BI Applications  Installation on Cloud Services, Doc ID 2136376.1, describes how you can install Business Intelligence applications (BIAPPS) on Platform as a Service (PaaS) services. This article explains how you can arrive at the required sizing for the various PaaS components.

     

    First, let’s understand the architecture and what resides on each of the PaaS components.

     

    image001.gif

     

    Figure1:  BIAPPS PAAS Components and Architecture

     

    The database is stored in Oracle Database Cloud Service (DBCS, also referred to as DBaaS). It typically has at least four schemas:

     

    1. Oracle Data Integrator (ODI) Repository  (Typically takes 30GB-50GB Space)
    2. Oracle Business Intelligence Applications Configuration Manager (BIACM) Repository
    3. SDS Repository (one schema for each Source). The volume  will vary based on Data volumes in the Source and the number of Source Systems.
    4. Data warehouse to store the warehouse tables. Sizing should consider the temp tables, indexes, tables, etc.

     

    A typical BIAPPS database is likely to be around 500GB. Factoring in 20% growth per year, the 5 year space requirement will be approximately 1TB.

     

    A DBaaS instance would need space for software, data, redo, backups and boot components. When using local backup, the space requirement is roughly 1.7 times the data size.  Considering all that, and assuming that you would want to go with the Local Backup storage option, a typical DBaaS Instance would allow you to have a max database size of around 4.6TB. (~4TB for Data, ~8TB for backup and the rest for binaries, redo, boot, etc). If you are likely to have a larger database, you should consider Exadata CS instead for the database. A quarter rack Exadata with local storage will have usable space of around 16.8TB. A full rack will provide 67TB of usable space.

     

    The white paper recommends the following shapes for DBaaS for BIAPPS:

     

    • Small: OC5 (4 OCPUs, 30GB RAM)
    • Medium: OC6 (8 OCPUs, 60GB RAM)
    • Large: OC7 (16 OCPUs, 120GB RAM)

     

    Customers requiring higher memory can use the following high memory equivalent shapes:

    • Medium: OC4M - 8 OCPU, 120 GB RAM
    • Large: OC5M - 16 OCPU, 240 GB RAM

     

    Compute

     

    The compute instance is used to host the BIAPPS Middleware that includes Weblogic Server, Config Manager, Load Plan Generator, ODI Agent, FSM (Functional Setup Manager). Following table shows the memory requirements of the important BIAPPS Server/components that will reside on the Compute instance:

     

                                                                                                

    Paas Component

    Server

    Apps

    Minimum Required Memory

    Compute

    WLS  AdminServer

    Console,  EM

    1Gb

    Compute

    BI          Managed Server*

    BIACM,          LPG

    3Gb

    Compute

    ODI          Managed Server

    ODI

    4GB

     

    *If using BI Publisher or OBIEE on the Compute machine, then the BI Managed Server memory needs to be set to 9GB.

     

    In addition to the above, it is recommended that client components like ODI Studio reside on the Compute and the developers open the Studio on the compute machine via vnc. Technically, you can install ODI Studio on an on prem machine and connect to the ODI repository. However the performance is likely to be very    slow in such a setup and hence not recommended. Each instance of ODI Studio can    take upto 2GB RAM. And if you have multiple developers and/or users opening up other clients (Like SQL Developer), those would take up memory as well.

     

    The  compute machine is also used to store the BIAPPS binaries/installers, files like Source Files etc that would reside on the file system.

     

    Based  on the above, the recommendation for the Compute is as below. This should  accommodate the requirements for BIAPPS Middleware as well as allow 2-3 developers to open ODI studio on the compute box. If you plan to have more ODI developers, then consider a machine with higher RAM/CPU or consider getting an additional compute box.

     

    • Compute: OC4 (2 OCPUs, 15GB RAM)

     

    Oracle Storage Cloud Service

     

    Within the context of BIAPPS, Oracle Storage Cloud Service is primarily used for Database backups. The size should be at least equivalent to the Data files size of the db when using it to backup the  database. Storage Cloud Service can also be used to backup the files on the file system for the compute instance.

     

    On Prem Machine

     

    In addition to the above, an on prem machine is required to host the following:

     

    1. BICS Data Sync:  Used to replicate the data from On Prem Sources to the SDS
    2. Weblogic Server: Required for BICS RDC
    3. OBIEE Admin tool:  To modify the RPD for lift and shift

     

    Summary

     

    The following table summarizes the shapes and sizes for each of the BIAPPS on PAAS components.

     

                                                                                                                                                                              

    Component

    Average  Warehouse Size
    (Up to 1TB database size)

    Mid-Size  Warehouse

    (Up to 4Tb database size)

    Large Warehouse

    (Over 4TB database)

    Compute

    [See note, below]

    OC4  (2 OCPUs, 15GB RAM)

    *Sized for only 2-3 Developers. Increase size for more usage

    1TB  Storage

    OC4  (2 OCPUs, 15GB RAM)

    *Sized for only 2-3 Developers. Increase size for additional for more usage

    2TB  Storage

    OC4          (2 OCPUs, 15GB RAM)

    *Sized for only 2-3 Developers. Size up additional for more usage

    2TB  Storage

    DBCS

    [See note, below]

    OC5 (4 OCPUs, 30GB RAM)

    Or

    OC3M (4 OCPU, 60 GB RAM)

    Size: 500GB 1st Year,

    Increase  to 1TB over 5 years

    OC6  (8 OCPUs, 60GB RAM)

    Or

    OC4M  (8 OCPU, 120 GB RAM0

    Size: 1TB 1st year

    Increase  to 4TB over 5 Years

    NA  (Use Exadata CS instead)

    Exadata CS

    NA

    NA

    Quarter Rack 16.8TB

    Can go up to Full Rack 67TB

    *Max size can go up to 164 TB if using cloud storage only

    Oracle  Storage Cloud Service

    1TB non-metered for Compute Backup

    1TB non-metered for DB Backup

    2TB  non-metered for Compute Backup

    4TB non-metered for DB Backup

    2TB  non-metered for Compute Backup

    Appropriate  Space non-metered for DB backup equivalent to DB size

    BICS

    Yes

    Yes

    Yes

    On Prem Machine

    Yes to host

    • Data Sync Client
    • Weblogic Server for BICS RDC
    • OBIEE Admin Tool to modify the BIAPPS RPD

    Yes to host

    • Data Sync Client
    • Weblogic Server for BICS RDC
    • OBIEE Admin Tool to modify the BIAPPS RPD

    Yes to host

    • Data Sync Client
    • Weblogic Server for BICS RDC
    • OBIEE Admin Tool to modify the BIAPPS RPD

     

    Note: If you plan to have Dev/Test/Prod environments, then each of them would need to be sized as per above, depending on the planned usage.

     

    *Customers need to pay attention to their Ordering Document (OD) when they pick the Compute Shape. If their OD says General Purpose, then they should only select General Purpose and not a High Memory Shape.  The customer will incur overages if they choose a shape that is not present on the OD.

    Additional Reading

     

     

    Disclaimer:  The information presented in this article is based on our testing and assessment. The details may change depending upon your set-up and requirements. Please consider  testing before finalizing the sizing details.