OBIEE 11g Configuration and Log Files Location and Scripts Locations

In this post, we are going to see where the log files in OBIEE 11g reside.

In OBIEE 11g, we have got Enterprise Manager Console, where we can check log files but we can still see these files in OBIEE install directory.

1. NQSConfig.INI and logconfig.xml

\OBI11G\instances\instance1\config\OracleBIServerComponent\coreapplication_obis1

2. instanceconfig.xml

\instances\instance1\config\OracleBIPresentationServicesComponent\coreapplication_obips1

3. ClusterConfig.xml
ccslogging.xml

\instances\instance1\config\OracleBIApplication\coreapplication

4. instanceconfig.xml (Second instanceconfig.xml dedicated file for BI Scheduler)
\instances\instance1\config\OracleBISchedulerComponent\coreapplication_obisch1

5. config.xml and logging_config.xml
\instances\instance1\config\OracleBIJavaHostComponent\coreapplication_obijh1

6. bridgeconfig.properties (For BI Persentation services Plug-in)

\OBI11G\user_projects\domains\bifoundation_domain\config\fmwconfig\biinstances\coreapplication

7. opmn.xml (OPMN Config file)
/OBI11G/instance/instance1/config/OPMN/opmn/opmn.xml
(It contains the PATH and LD_LIBRARY_PATH values for the system components and the port number for OPMN and optional SSL configuration.)

8. boot.properties
/OBI11G/user_projects/domains/bifoundation_domain/servers/[managed_server]/security

Script Files

1. startNodeManager.sh
(Must be started to allow Managed Server to be started from Weblogic console)
/OBI11G/wlserver_10.3/server/bin/startNodeManager.sh

2. opmnctl(Command line tool to start BI services)

/OBI11G/instance/instance1/bin
— OPMN can be used to automatically start BI on a Linux system. To do that following commands must be included in opmn startup script:

/OBI11G/instance/instance1/bin ./opmnctl startall

3. startWebLogic.sh(Script to start Weblogic server)

/OBI11G/user_projects/domains/bifoundation_domain/bin.

./startManagedWebLogic.sh
/OBI11G/user_projects/domains/bifoundation_domain/bin

To start Managed Server – But this typically can be started from Webogic Console after weblogic server is in running mode.

./startManagedWebLogic.sh bi_server1 http://administration_server_host_name:7001

Log Files:

1. Admin Server (Or weblogic server issues)
\user_projects\domains\bifoundation_domain\servers\AdminServer\logs

2. Managed Server
\user_projects\domains\bifoundation_domain\servers\bi_server1\logs\

3. BI Server
\OBI11G\instance\instance1\diagnostics\logs\OracleBIServerComponent\coreapplication_obis1

4. BI Persentation Server:
\OBI11G\instance\instance1\diagnostics\logs\OracleBIPresentationServicesComponent\coreapplication_obips1

WebLogic Server Log Locations in OBIEE 11g

BI Managed Server:

OBIEE_HOME\user_projects\domains\bifoundation_domain\servers\bi_server1\logs

bi_server1.log – For any issues related to bi_server1

Admin Server:

OBIEE_HOME\user_projects\domains\bifoundation_domain\servers\AdminServer\logs

AdminServer.log – For any issues related to AdminServer

Starting and Stopping OBIEE

Note that in your environment, some paths and locations of files may be different because your system may have been configured differently from the examples in the following sections.

Starting OBIEE

1. Sign onto the Linux server using the non-privileged username (for example, Imran).
2. Start the node manager.
1. cd /u01/app/oracle/product/fmw/wlserver_10.3/server/bin
2. nohup ./startNodeManager.sh &
3. Start OHS (skip this step for non-SSO systems).
1. cd /u01/app/oracle/product/fmw/Oracle_WT1/instances/instance2/bin
2. ./opmnctl startall
3. Verify startup using command ./opmnctl status
4. Start the WebLogic administration server.
1. cd /u01/app/oracle/product/fmw/user_projects/domains/bifoundation_domain/bin
2. nohup ./startWebLogic.sh &
5. Start OBIEE server using WebLogic Server Admin Console.
1. Login into the WebLogic Server Admin Console using the WebLogic administrator username.
2. In the Domain Structure pane on the left, expand Environment.
3. Under Environment, select Servers.
4. In the Summary of Servers pane, select the Control tab.
5. Click the checkbox next to bi_server1, and click the Start button.
6. Watch bi_server1 until it starts (usually around 2-3 minutes).
6. Start opmnctl processes.
1. cd /u01/app/oracle/product/fmw/instances/instance1/bin
2. ./opmnctl startall
3. Verify startup using command ./opmnctl status. Repeat until all processes show status of Alive.
4. If any process fails to start, try command ./opmnctl restartproc

Stopping OBIEE

1. Sign onto the Linux server using the non-privileged username (for example, oemora).
2. Stop opmnctl processes.
1. cd /u01/app/oracle/product/fmw/instances/instance1/bin
2. ./opmnctl stopall
3. Stop OBIEE server using WebLogic Server Admin Console.
1. Login into the WebLogic Server Admin Console using the WebLogic administrator username.
2. In the Domain Structure pane on the left, expand Environment.
3. Under Environment, select Servers.
4. In the Summary of Servers pane, select the Control tab.
5. Click the checkbox next to bi_server1, and click the Shutdown button.
6. Watch bi_server1 until it shuts down (usually less than a minute).
4. Stop the WebLogic administration server.
1. cd /u01/app/oracle/product/fmw/user_projects/domains/bifoundation_domain/bin
2. ./stopWebLogic.sh
5. Stop OHS (skip this step for non-SSO systems).
1. cd /u01/app/oracle/product/fmw/Oracle_WT1/instances/instance2/bin
2. ./opmnctl stopall

Good Luck...