OBI 11g - Linux Start Up Best Practice

The whole idea of starting and stopping processes for OBI is nothing new.  Windows gets buy with a very simple system that most are familiar, but Linux can often pose as a challenge.  Since, I prefer to recommend Linux (*Nix) over Windows when it comes to OBI, especially with OBI 11g it is worth a quick post on automating the start-up of OBI 11g on a Linux box (modify this logic slightly in the next OBI 11g patch when UNIX is supported).

Getting down to it, as a best practice, I recommend starting all java and system components on boot of the server.  For a while there were arguments on whether to do this or not, but ultimately it boils down to maintaining as much of a hands-off approach as possible.  In the Linux world to launch the four (out-of-box) services that would be required to run OBI 11g, a user would basically need to log into the Linux OBI 11g server (or terminal in) to launch a terminal window for at a minimum of three of those components (WLS, WLS Node Manager, and OPMN). The fourth, the OBI Managed Server (handles the Java pieces), could be started from the WLS Admin Console which provides some benefit but it could also be started from a command line.  It should also go without saying, but I’ll state it any way, that the database containing the RCU created MDS and BIPLATFORM schemas should be up, pingable, and in good health before this script is launched.

Here is some basic script below to start your OBI 11g Linux environment on boot.  This is just the init.d script that you should copy, save to a linux text editor with a file name such as “OBI11gStartStop” (no extension) and load to the /etc/init.d/ directory, and load like any other init file. This blog post assumes that you have some familiarity with commands such as chkconfig as well as working with Linux directories and permission sets.

view sourceprint?

01.#!/bin/sh

02.# chkconfig: 345 99 8

03.# description: OBIEE11g and WLS auto start-stop script

04.#

05.# File is saved as /etc/init.d/obiee11gWLS

06.#

07.# Run-level Startup script for OBIEE

08. 

09.# set required paths

10.#export ORACLE_BASE=/u01/app/oracle

11.ORACLE_OWNR=obi11g

12.ORACLE_FMW=/u01/FMW

13.#export PATH=$PATH:$ORACLE_FMW

14. 

15.case "$1" in

16.'start')

17.echo -e "Starting Weblogic Server...."

18.su - $ORACLE_OWNR -c"$ORACLE_FMW/user_projects/domains/bifoundation_domain/startWebLogic.sh > /tmp/WLSStart.log 2>&1 &"

19.sleep 30

20.echo -e "Starting Node Manager..."

21.su - $ORACLE_OWNR -c "$ORACLE_FMW/wlserver_10.3/server/bin/startNodeManager.sh > /tmp/WLSNodeMgrStart.log 2>&1 &"

22.sleep 90

23.echo -e "Starting Managed Server: bi_server1..."

24.su - $ORACLE_OWNR -c"$ORACLE_FMW/user_projects/domains/bifoundation_domain/bin/startManagedWebLogic.sh bi_server1 http://OBI11G:7001 > /tmp/WLSMgdSvr.log 2>&1 &"

25.sleep 90

26.echo -e "Starting OPMN Components...."

27.su - $ORACLE_OWNR -c "$ORACLE_FMW/instances/instance1/bin/opmnctl startall"

28.sleep 120

29.;;

30.'stop')

31.echo -e "Stopping OPMN Components...."

32.su - $ORACLE_OWNR -c "$ORACLE_FMW/instances/instance1/bin/opmnctl stopall"

33.sleep 60

34.echo -e "Stopping Managed Server: bi_server1..."

35.su - $ORACLE_OWNR -c"$ORACLE_FMW/user_projects/domains/bifoundation_domain/bin/stopManagedWebLogic.sh bi_server1 http://OBI11G:7001 > /dev/null 2>&1 &"

36.sleep 30

37.echo -e "Stopping Weblogic Server...."

38.su - $ORACLE_OWNR -c"$ORACLE_FMW/user_projects/domains/bifoundation_domain/bin/stopWebLogic.sh > /dev/null 2>&1 &"

39.sleep 15

40.;;

41.restart)

42.$0 stop

43.$0 start

44.;;

45.*)

46.echo "Usage: 'basename $0' start|stop|restart|status"

47.exit 1

48.esac

49. 

50.exit 0

51. 

52.######################################