OBIEE 11g Windows Services

When system is logged off, OBIEE is not accessible from other machines, in order to access OBIEE from other machine, even system is log off, One need to add the OBIEE(Admin and Managed Server Services) to windows, which will run in backgound.

Steps for creating windows services.

1) Modify installSvc.cmd scrip to add log file path.

2) Create Admin Server Service

3) Create Managed Server Service

4) Create Node Manager Service (If not available)

5) Regedit  modifications (If required)

---------------------------------------------------------------------------------------------------------------

For troubleshooting / debugging purposes it is helpful to redirect standard out and error to a text file. Although most information is captured in the AdminServer server log files, you will not see all standard out and error when the server is started via a MS Windows Service (unlike when you start an AdminServer in console mode from the command prompt using startWebLogic.cmd). To redirect standard out to a text file, backup and editinstallSvc.cmd file and change the line at the bottom of the file so it includes the -log parameter. For example:

"%WL_HOME%\server\bin\beasvc" -install
-svcname:"%DOMAIN_NAME%_%SERVER_NAME%"
-javahome:"%JAVA_HOME%" -execdir:"%USERDOMAIN_HOME%"
-extrapath:"%WL_HOME%\server\bin" -password:"%WLS_PW%"
-cmdline:%CMDLINE%
-log:"[middleware_home]\user_projects\domains\bifoundation_domain\servers\AdminServer\AdminServer-stdout.txt"

Note: You may also want to change the service name from beasvc to Oracle so that all of your Oracle services are ordered together in the services screen, for example:

-svcname:"Oracle %DOMAIN_NAME%_%SERVER_NAME

Ex:-     -log:"D:\OBIEE11G\user_projects\domains\bifoundation_domain\servers

\AdminServer\AdminServer_stdout.txt"

 InstallAdmServer_Service

Create a file installAdmServer_Service.cmd. and add the below content as per your environment and double on the file, which creates the windows service.Save in the folder D:\OBIEE11G\wlserver_10.3\server\bin\

Open a text file and input the following lines [edit for your install]:

echo off
SETLOCAL
set DOMAIN_NAME=bifoundation_domain
set USERDOMAIN_HOME=D:\OBIEE11G\user_projects\domains\bifoundation_domain
set SERVER_NAME=AdminServer
set PRODUCTION_MODE=true
call "D:\OBIEE11G\user_projects\domains\bifoundation_domain\bin\setDomainEnv.cmd"
call "D:\OBIEE11G\wlserver_10.3\server\bin\installSvc.cmd"
ENDLOCAL

Managed Server

Create a command script called installManagedSrvr_Service.cmd which has lines like:
Example:-
Host name is the machine name or ip address and port is Adminserver listen port
----------------------------------
SETLOCAL
set DOMAIN_NAME=biserver1
set USERDOMAIN_HOME=D:\OBIEE11G\user_projects\domains\bifoundation_domain
set SERVER_NAME=bi_server1
set PRODUCTION_MODE=true
set ADMIN_URL=http://168.31.123:7001
cd %USERDOMAIN_HOME%
call %USERDOMAIN_HOME%\bin\setDomainEnv.cmd
call "D:\OBIEE11G\wlserver_10.3\server\bin\InstallSvc.cmd"
ENDLOCAL

Next,  run "installAdmServer_Service.cmd" and the service should be installed, it will have a name like "Oracle %DOMAIN_NAME%_%SERVER_NAME%" or beasvc if you left it at the default (e.g. Oracle bifoundation_domain_AdminServer)

Note: you could put all these in one script if you desire.

The Service "Startup Type" will be 'Automatic'. Just like any other MS Windows Service you can change the 'Startup Type' to 'Manual'.

Start the Service. The Service will come back fairly quickly to say it is started. The actual time taken for AdminServer to start and reach a state of 'RUNNING' will be longer - perhaps two or three minutes. The state of the server can be monitored by reviewing the stdout txt file.

Next Run the installManagedSrvr_Service.cmd

Oracle WebLogic NodeManager (D_OBIEE11G_wlserver_10.3)

If Node manager service is not available in services list then create a node manager service using the following procedure.

Edit nodemanager properties file and the set the following two properties

CrashRecoveryEnabled=true
StartScriptEnabled=true.

Navigate the above folder and run the batch file installNodeMgrSvc.cmd,which creates a service in windows

1. Ensure you make the managed Server to a automatic (delayed) or manual startup so this service can be started after the AdminServer is confirmed as started via the standard out file.  Alternatively consider using the delay parameter to force the managed Server to start after the Admin server, as outlined in Setting Up a Windows Service: Main Steps in Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server 11g.
   
   
2. You may choose to start the managed server from the WebLogic Console instead of creating the MS Windows service.
3. First start the Node Manager, Admin Server and the Managed Server in this Order.

If any of the services are not running check the below properties from regedit and log files.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ 

And set if anything is missing (host name, port number….)

CmdLine parameter has been modified to increase the JVM parameters

From

-server –Xms32m –Xmx200m -XX:MaxPermSize=128m -XX:+UseSpinning  -

to

-server -Xms1024m -Xmx1024m -XX:MaxPermSize=512m -XX:+UseSpinning  -

CmdLine parameter has been modified to increase the JVM parameters

From

-server –Xms32m –Xmx200m -XX:MaxPermSize=128m -XX:+UseSpinning  -

to

-server -Xms1024m -Xmx1024m -XX:MaxPermSize=512m -XX:+UseSpinning  -

Log file for the services will be generated in the below path as specified in the installSvc file.

Once all the services are started ,check em,console and analytics login. Try to log off from the machine and access the obiee urls from other machines, obiee should be accessible.