Scribd Logo
Upload

Welcome to Scribd!

  • 105 views

    Horizontal Clustering in OBIEE11g

    Uploaded by

    PSIEBEL
    Horizontal clustering in OBIEE involves setting up multiple instances of key components like the BI Server, Presentation Services, and Java Host on separate machines for scalability and high availability. The key steps are: 1) creating shared directories for files like the repository and web catalog, 2) installing additional instances using the Universal Installer, 3) configuring additional system components in the Enterprise Manager, and 4) specifying primary and secondary instances for components like the Cluster Controller and Scheduler. This allows load balancing and failover capabilities across multiple servers.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    Horizontal Clustering in OBIEE11g

    Uploaded by

    PSIEBEL
    105 views13 pages
    Horizontal clustering in OBIEE involves setting up multiple instances of key components like the BI Server, Presentation Services, and Java Host on separate machines for scalability and high availability. The key steps are: 1) creating shared directories for files like the repository and web catalog, 2) installing additional instances using the Universal Installer, 3) configuring additional system components in the Enterprise Manager, and 4) specifying primary and secondary instances for components like the Cluster Controller and Scheduler. This allows load balancing and failover capabilities across multiple servers.

    Original Description:

    Horizontal Clustering in OBIEE11g

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Horizontal clustering in OBIEE involves setting up multiple instances of key components like the BI Server, Presentation Services, and Java Host on separate machines for scalability and high availability. The key steps are: 1) creating shared directories for files like the repository and web catalog, 2) installing additional instances using the Universal Installer, 3) configuring additional system components in the Enterprise Manager, and 4) specifying primary and secondary instances for components like the Cluster Controller and Scheduler. This allows load balancing and failover capabilities across multiple servers.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    105 views13 pages

    Horizontal Clustering in OBIEE11g

    Uploaded by

    PSIEBEL
    Horizontal clustering in OBIEE involves setting up multiple instances of key components like the BI Server, Presentation Services, and Java Host on separate machines for scalability and high availability. The key steps are: 1) creating shared directories for files like the repository and web catalog, 2) installing additional instances using the Universal Installer, 3) configuring additional system components in the Enterprise Manager, and 4) specifying primary and secondary instances for components like the Cluster Controller and Scheduler. This allows load balancing and failover capabilities across multiple servers.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 13

    Horizontal Clustering in OBIEE11g

    Horizontal Clustering: - If we are going to implement horizontal clustering then


    we need multiple boxes for multiple instances of BI Server, Presentation Services etc.

    In this type of clustering generally 3 components are clustered


    1. BI Server
    2. BI Presentation Services
    3. Java Host
    That is, all the components that can act in active-active configuration can be clustered
    in Vertical Clustering. Other components like Scheduler Cluster Controller which
    work in active-passive fashion are generally not clustered vertically.
    We start with logging into the enterprise manager FMW control and navigating to the
    deployment section. Since we are doing vertical clustering,
    Administration and Management:-
    • WLS Admin Server used for controlling WLS platform
    ‣ Startup, shutdown, security, non-OBIEE specific tasks
    • Fusion Middleware Control (EM) used for managing OBIEE
    • OPMN used for starting, stopping system components
    • Node Manager used for
    Starting, stopping, managed servers

    Horizontal Scaleout of System Components


    • Used for adding additional managed servers (Java components) and system
    components to an existing cluster
    • Used for scalability and failover
    • Set up via the Universal Installer > Scale Out BI System option.
    Importance of Horizontal Clustering:-
    Scalability
    Increasing or decreasing the capacity of a system by making effective use of resources
    is known as scalability. A scalable system can handle increasing numbers of requests
    without adversely affecting response time and throughput.

    High Availability

    High availability refers to the ability of users to access a system without loss of
    service. Deploying a high availability system minimizes the time when the system
    is down, or unavailable and maximizes the time when it is running, or available. To
    provide a highly available system, Oracle BI EE requires the following external
    services:
     A fault tolerant HTTP load balancer
     A highly available shared file system
     A highly available database for Oracle BI Scheduler.
    NOTE:-Once the drive is identified (one for RPD and the other for Web Catalog),
    copy the web catalog to the shared drive. In the deployment section of the Enterprise
    Manager, enter the shared directory details of both the RPD and the Web Catalog.
    Upload the repository (RPD) into the shared
    Drive using the enterprise manager.
    Horizontal Clustering Step 1: Create Shared Areas
    • Create folders on network share for RPD, Web Catalog and Global Cache
    • Share needs to be accessible to all hosts
    • Copy the web catalog across manually, the others will be populated automatically

    Access the Fusion Middle ware Control 11g. Select core application under Business
    Intelligence and select Capacity Management. Go to
    Scalability tab and click Lock and Edit Configuration.

    Now the Enterprise Manager will allow editing the values.


    Horizontal Clustering Step 2: Prepare Installation

    • Start the Oracle Universal Installer on the new host, select


    Enterprise Install > Scale Out BI System option
    • Enter connection details to the WLS Admin Server

    Horizontal Clustering On the new server:-

    On the new server copy the setup files


    for OBIEE and then run the Installer. Select Enterprise Install and then select Scale

    Out BI System option.

    Here fill out the host name where the primary setup is installed and the port number
    for the web logic is listening.
    The installer gives and option to place the Domain Home, Applications Home and
    Instance Home.

    Select the option to auto allocate the ports or to give a preference for the port.

    Review the summary and confirm the Installation.


    Horizontal Clustering Step 3: Install and Configure
    • Allow installation to complete, and then post-install configuration steps
    • This should then complete the scale-out of the managed server and java components
    After the confirmation the installer copies the relevant files to the directories.

    Now the scale out process is completed successfully.


    Horizontal Clustering Step 4: Add New System Components
    Add new BI Servers, Presentation Servers and Java Hosts on new host
    Summary of the servers:-
    Instance 2 is added and you can see it under the fusion middle-ware console.
    1. In the left pane of the Console, expand Environment and select Servers.
    2. Select the name of the Configuration tab where you want to view the Summary of
    the servers.

    Summary of Machines:
    This page displays key information about each machine that has been configured in
    the current WebLogic Server domain.
    1. In the left pane of the Console, expand Environment and select Machines.
    .

    Monitor Node Manager Status


    To monitor Node Manager Status:
    1. In the left pane of the Console, expand Environment and select Machines.
    2. Select the name of the machine where you want to view the Node Manager status.
    3. Select Monitoring > Node Manager Status.
    If Node Manager is currently running on the machine, the Node Manager Status
    displays the following information about the Node Manager process:
    o Status - current status of this Node Manager
    o Version - version string returned from the Node Manager
    This page allows you to view current status information for the Node Manager
    instance configured for this machine.

    System Components in Enterprise Manager


    At this point, you’ve got an additional managed server, but you’ve not yet brought any
    additional system components into the cluster. You do this from Enterprise Manager,
    where you can now add additional BI Servers, Presentation Servers, Java Hosts,
    Cluster Controllers or Schedulers to the cluster, by selecting them from the Capacity
    Management > Scalability screen, where you’ll now see a new entry for your
    managed server.
    1. In the left pane of the EM, expand Business Intelligence and select core application.
    2. Select the name of the Capacity Management tab and click on Scalability tab.
    Where you want to view the System Components

    BI Server Repository
    You’ll also need to specify a shared location for your RPD, and for the web catalog.
    You do this again from Enterprise Manager, this time selecting
    the Deployment > Repository screen and typing in the details of the shared locations.
    1. In the left pane of the EM, expand Business Intelligence and select core application.
    2. Select the name of the Deployment tab and click on Repository tab.
    3. Check the Share Repository check box, Share the Shared Repository path also
    Share the catalog path from the Shared catalog folder.
    4. Upload the Repository file give password and apply.
    Performance Options (Global Cache)

    1. In the left pane of the EM, expand Business Intelligence and select core application.
    2. Select the name of the Capacity Management tab and click on Performance tab.
    3. Give the Global cache path and Global cache size
    Using Fusion Middleware Control to Configure Primary and Secondary
    Instances

    You can use Fusion Middleware Control to configure primary and secondary
    instances of the Cluster Controller and Oracle BI Scheduler.
    1. In the left pane of the EM, expand Business Intelligence and select core application.
    2. Select the name of the Capacity Management tab and click on Availability tab.
    3. Click Lock and Edit Configuration to allow changes to be made.
    4. In the Primary/Secondary Configuration section, select the host and Oracle
    instance on which you want to run the primary or secondary Cluster Controller or
    Oracle BI Scheduler.
    5. Click Apply, then click Activate Changes.
    6. Return to the Business Intelligence Overview page and click Restart.

    You might also like