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.
# chkconfig: 345 99 8
# description: OBIEE11g and WLS auto start-stop script
# File is saved as /etc/init.d/obiee11gWLS
# Run-level Startup script for OBIEE
# set required paths
case “$1” in
echo -e “Starting Weblogic Server….”
su – $ORACLE_OWNR -c “$ORACLE_FMW/user_projects/domains/bifoundation_domain/startWebLogic.sh > /tmp/WLSStart.log 2>&1 &”
echo -e “Starting Node Manager…”
su – $ORACLE_OWNR -c “$ORACLE_FMW/wlserver_10.3/server/bin/startNodeManager.sh > /tmp/WLSNodeMgrStart.log 2>&1 &”
echo -e “Starting Managed Server: bi_server1…”
su – $ORACLE_OWNR -c “$ORACLE_FMW/user_projects/domains/bifoundation_domain/bin/startManagedWebLogic.sh bi_server1 http://OBI11G:7001 > /tmp/WLSMgdSvr.log 2>&1 &”
echo -e “Starting OPMN Components….”
su – $ORACLE_OWNR -c “$ORACLE_FMW/instances/instance1/bin/opmnctl startall”
echo -e “Stopping OPMN Components….”
su – $ORACLE_OWNR -c “$ORACLE_FMW/instances/instance1/bin/opmnctl stopall”
echo -e “Stopping Managed Server: bi_server1…”
su – $ORACLE_OWNR -c “$ORACLE_FMW/user_projects/domains/bifoundation_domain/bin/stopManagedWebLogic.sh bi_server1 http://OBI11G:7001 > /dev/null 2>&1 &”
echo -e “Stopping Weblogic Server….”
su – $ORACLE_OWNR -c “$ORACLE_FMW/user_projects/domains/bifoundation_domain/bin/stopWebLogic.sh > /dev/null 2>&1 &”
echo “Usage: ‘basename $0’ start|stop|restart|status”
Subscribe to Our Blog
Never miss a post! Stay up to date with the latest database, application and analytics tips and news. Delivered in a handy bi-weekly update straight to your inbox. You can unsubscribe at any time.
Most people will encounter this error when their application tries to connect to an Oracle database service, but it can also be raised by one database instance trying to connect to another database service via a database link.
EPM applications help measure the business performance. This post will help you choose the best EPM solutions for your organization’s needs and objectives.