Thursday 26 April 2012

Installing a Single, Scaled-out Oracle Business Intelligence Instance on Multiple Computers OR How to scale out another OBIEE system with existing domain

In the series of OBIEE installation here I am going to discuss the Enterprise Management’s Scale-out option installation procedure.
To perform the scale out oracle business instance on multiple computer perform the following step
1)      Install the Standalone Oracle Business Intelligence Instances on one Computer called it as MASTER BI SERVER to know the procedure check the post "Enterprise Install with NEW BI SYSTEM option"
2)    Install the Enterprise install with scale-out option on another computer or we can say the system where we want to scale out the components of MASTER BI SERVER


To do the scale out on new system, need to run the OBIEE installation with enterprise install option. Before Proceeding to scaling the deployment to other servers, Please follow the following steps:

 1.Create a shared directory for the Repository Publishing Directory. The MASTER BI SERVER must have read and write access to this directory. All other Oracle BI Servers must have read access.
2. Use the Repository tab of the Deployment page in Fusion Middleware Control to designate the shared location for the Oracle BI repository

 
 
 













Sharing the Oracle BI Presentation Catalog
1. Create a network share for the Oracle BI Presentation Catalog on MASTER BI SERVER. All Presentation Services components in the cluster must have read and write access to this share.
2. Place the catalog on the network share.
3. Use the Repository tab of the Deployment page in Fusion Middleware Control to change the location of the Oracle BI Presentation Catalog to the shared location















Setting Up the Global Cache
1. Create a shared directory for the global cache MASTER BI SERVER. All Oracle BI Servers must have read and write access to this directory.
2. Use the Performance tab of the Capacity Management page in Fusion Middleware Control to set the Global cache path and Global cache size options.
















Now Run the OBIEE installer on the second machine/Server


Fill the required fields with the below information
The host name and port number for the Administrator Server domain (Created using the Create New BI System option on Server 1)
The user name and password for logging to the Weblogic Administrator Server






























 



 














just click on next and provide the security detail, once complete the installation follow the following steps:

1) Logged in to http://hostname:7001/em and 
2) Navigate over Business Intelligence->coreapplication->capacity Management->Scalability
Configure primary and secondary instance of the Cluster Control and Oracle BI Scheduler so that the primary and secondary instance of each component type are distributed across two different machines/Servers. Use the Availability tab of the Capacity Management page in Fusion Middleware Control to configure the primary and secondary instance of Cluster controller and BI schedules









11 comments:

  1. If you want to scale out this infrastructure, you would typically run the OBIEE 11g installer on a second server, and instead of choosing to do a new install, you’d choose to instead scale out the existing BI domain.

    ReplyDelete
  2. Hi Rhishikesh,

    Thanks for your post. I have a question regarding SSL implementation. We have two physical servers; one system has WebLogic (admin_server) with BI server (bi_server1) and the second one has the presentation server (bi_server2). We would like to implement https for presentation server. Would you please give me a some information for this implementation? I appreciate your help.

    Thanks.

    ReplyDelete
  3. Hi all,

    Would it be possible to automate the creation of another instance (like a silent install) ? Or even more, is it possible to clone an existing instance to replicate it n-times ?

    TIA,
    JohnP

    ReplyDelete
  4. Correction for the 2nd q:
    Is it possible to automate the cloning of an existing instance to easily replicate it n-times ?

    JohnP

    ReplyDelete
  5. JohnP

    I am also looking to automate the Scale-Out.. We need to use SCALE_OUT=true on response file for it to install and i am still looking for automating configuration steps on EM

    Let me know if you found out any

    ~Srix

    ReplyDelete
    Replies
    1. Hi JohnP

      The response file is present at location
      Disk1/stage/Response (on UNIX operating systems) or Disk1\stage\Response(on Windows operating systems)


      To perform the scale out you need to set EXTEND_BISYSTEM=true and If this is set to true then variables "CREATE_BISYSTEM" and "SCALEOUT_BISYSTEM" must be set to false, since the variables are mutually exclusive.

      While launching the OBIEE setup pass this response file with location
      -response /~/response/oracle.classicwls.top.Custom.rsp

      Rhishikesh

      Delete
    2. Can you install another copy of Enterprise Manager client tool on another server in a cluster without
      negatively impacting the OBIEE 11g environment. The 2nd node we are targeting to install the EM client on
      has been reporting node is down but all indications is the node is up and running when we run
      command line tools on problem node/server. Thanks in advance.



      Delete
  6. This comment has been removed by a blog administrator.

    ReplyDelete
  7. I'm trying to scale out the BI system. I have installed OBIEE on 1st node. On 2nd node, instead of selecting "Create New BI system", i selected "Scale out" and provided the details of first node. Installation is complete and in post installation configuration, there is a step called "starting scaled out managed server" .Its hanged there.

    In the 1st node weblogic console, i'm able to see this new managed server bi_server2, but its status is shutdown.

    Can you help me in this.

    ReplyDelete
    Replies
    1. Hello. Can you tell me if you managed to solve this problem and how?. The same thing happens to me. Regards

      Delete