OBIEE 12c Differences Between config.sh (Enterprise vs Single Server)?

chillychin

Im finally close to getting a working sample of OBIEE running and believe I am on one of the last steps - running through the configuration utility.

From what I have been reading up on, it sounds like there are actually TWO configuration utilities.

There is one located at

<obiee_home>/bi/bin

And another one located here

<obiee_home>/oracle_common/common/bin

I tried running both just to see what the different options are, and from what I can tell, and from most of the articles I have found online it sounds like the config.sh file located in <obiee_home>/bi/bin seems to be the most common installation.

I hear mention that the config.sh located in <obiee_home>/oracle_common/common/bin is for "enterprise deployments" or cluster deployments.

I was wondering, are there any other differences between these two config.sh?

Is there an advantage to using either one aside from ease of use?

Gianni Ceresa

Hi,

I would say the most used is ORACLE_HOME/bi/bin/config.sh .

Most people use this one.

Even for a OBIEE cluster you use this one on the main server and then pack the config and move to the next server (where you didn't run config.sh) and unpack it and use that to add it to the cluster.

I guess the one in /oracle_common/common/bin/ is a more generic config script for Weblogic, you can use it for generic domain creation, while the one in bi/bin is really focused on the OBIEE domain configuration. (for example as done here https://blogs.oracle.com/blogbypuneeth/entry/steps_to_create_a_domain )

Gianni Ceresa

In addition Enterprise vs Single Server can be a bit confusing as in 11g there was the simple install and enterprise install where simple install was mainly for testing and OBIEE was deployed on the Weblogic admin server skipping the managed server (= less resources needed) while the enterprise install was the class setup with admin server and managed server where OBIEE was deployed.

Here it seems to be something different (not sure how "formal" are these names), the doc for scaling out says to run /bi/bin/config.sh and then a set of other scripts to easily configure and run the additional nodes of the cluster.

chillychin

Many thanks!