OBIEE 11g Start and Stop Steps

####################### Start Files for OBIEE #######################

        START OBIEE 11G

Step 1 of 4: Start Admin Server

Remember to run standard variable scripts first.

[oracle@obiserver bin]$ cd $DOMAIN_HOME/bin
[oracle@obiserver bin]$ pwd
/u01/MiddlewareHome/Oracle_BI1/user_projects/domains/bifoundation_domain/bin
[oracle@obiserver bin]$
[oracle@obiserver bin]$ nohup ./startWebLogic.sh -Dweblogic.management.username=weblogic -Dweblogic.management.password=Oracle_123 &
[oracle@obiserver bin]$ tail -f nohup.out

After issueing the start command we tail the log until we see the message below, indicating that the server has started successfully.
<WebLogicServer> <BEA-000360> <Server started in RUNNING mode>

Step 2 of 4: StartNode Manager

There should be a single Node Manager for the machine.  Start it up with the command below.

[oracle@obiserver bin]$ echo $WL_HOME
/u01/MiddlewareHome/Oracle_BI1/wlserver_10.3
[oracle@obiserver bin]$ cd $WL_HOME/server/bin
/u01/MiddlewareHome/Oracle_BI1/wlserver_10.3/server/bin
[oracle@obiserver bin]$
[oracle@obiserver bin]$ nohup ./startNodeManager.sh > NOD.out &
[oracle@obiserver bin]$ tail -f NOD.out

After issueing the start command we tail the log until we see the message below, indicating that the server has started successfully.
<Info> <Secure socket listener started on port ####>

Step 3 of 4: Start Managed Server

By default there should be one managed server, bi_server1 that we will start up.  At this point you should start  any other Managed Servers in this WebLogic domain.

[oracle@obiserver bin]$ cd $WL_HOME/common/bin
[oracle@obiserver bin]$ pwd
/u01/MiddlewareHome/Oracle_BI1/wlserver_10.3/common/bin
[oracle@obiserver bin]$
[oracle@obiserver bin]$./commEnv.sh
[oracle@obiserver bin]$ cd $DOMAIN_HOME/bin
[oracle@obiserver bin]$ pwd
/u01/MiddlewareHome/Oracle_BI1/user_projects/domains/bifoundation_domain/bin
[oracle@obiserver bin]$
[oracle@obiserver bin]$./setDomainEnv.sh
[oracle@obiserver bin]$ nohup ./startManagedWebLogic.sh bi_server1 t3://obiserver.hinopak.com:7001  > bis1_startup.log &
[oracle@obiserver bin]$ tail -f nohup.out

After issueing the start command we tail the log until we see the message below, indicating that the server has started successfully.
Server started in RUNNING mode

Step 4 of 4: Startup OPMN Components

Oracle Process Manager should be used to shutdown all system components.

[oracle@obiserver bin]$ cd /u01/MiddlewareHome/Oracle_BI1/instances/instance1/bin
[oracle@obiserver bin]$
[oracle@obiserver bin]$./opmnctl startall
[oracle@obiserver bin]$
[oracle@obiserver bin]$./opmnctl status

The opmnctl command stopall should shutdown all running components including opmnctl.  You can verify this by running the status command which should return an error.
You should see ouput such as below.

Processes in Instance: instance1
---------------------------------+--------------------+---------+---------
ias-component                    | process-type       |     pid | status
---------------------------------+--------------------+---------+---------
coreapplication_obiccs1          | OracleBIClusterCo~ |    7227 | Alive
coreapplication_obisch1          | OracleBIScheduler~ |    7226 | Alivecoreapplication_obijh1           | OracleBIJavaHostC~ |    7224 | Alive
coreapplication_obips1           | OracleBIPresentat~ |    7228 | Alive
coreapplication_obis1            | OracleBIServerCom~ |    7225 | Alive

[oracle@obiserver bin]$

####################### Stop Files for OBIEE #######################

STOP OBIEE 11G
Step 1 of 4: Shutdown OPMN Components

Oracle Process Manager should be used to shutdown all system components.


[oracle@obiserver bin]$ cd /u01/MiddlewareHome/Oracle_BI1/instances/instance1/bin
[oracle@obiserver bin]$
[oracle@obiserver bin]$./opmnctl stopall
[oracle@obiserver bin]$
[oracle@obiserver bin]$./opmnctl status
opmnctl status: opmn is not running.
[oracle@obiserver bin]$


Step 2 of 4: Shutdown Managed Server

By default there should be one managed server, bi_server1 that we will shut down.  At the point you should shut down any other Managed Servers in this WebLogic domain.

[oracle@obiserver bin]$ cd $DOMAIN_HOME/bin
[oracle@obiserver bin]$ pwd
/u01/MiddlewareHome/Oracle_BI1/user_projects/domains/bifoundation_domain/bin
[oracle@obiserver bin]$
[oracle@obiserver bin]$./stopManagedWebLogic.sh bi_server1 t3://obiserver.hinopak.com:7001 weblogic Oracle_123

Verify that the Managed Server has shutdown completely with ps -ef | grep bi_server1.


Step 3 of 4: Shutdown Node Manager

There should be a single Node Manager for the machine.  Shut it down with the command below.

[oracle@obiserver bin]$ ps -ef | grep Node | grep nodemanager | grep -v grep | cut -c10-15
[oracle@obiserver bin]$ kill -9 ####


Step 4 of 4: Shutdown Admin Server

There should be a single Node Manager for the machine.  Shut it down with the command below.


[oracle@obiserver bin]$ cd $DOMAIN_HOME/bin
[oracle@obiserver bin]$./stopWebLogic.sh weblogic Oracle_123 t3://obiserver.hinopak.com:7001

Verify that the Managed Server has shutdown completely with ps -ef | grep AdminServer.

Source: Internet/Internal Research