OBIEE Services as Window Service

OBIEE Services as Window Service

By default the only Fusion Middleware 11g components configured as MS Windows Services by the install process are:

• Weblogic Node Manager
  (configured as a MS Windows Service if Custom Install route is chosen when installing Weblogic)
• FMW 11g Process Manager (OPMN)
  (installed as a MS Windows Service if a System Component Instance is configured)

This document shows how to install the Weblogic AdminServer and BI Managed Server as MS Windows Service for the OBIEE 11g installation.

Note: If you install OBIEE 11g version 11.1.1.5+ with the Simple Install type, then you will only have an AdminServer and not a BI Managed Server; therefore, the Managed Server section would not apply in that specific version and installation type.

Stop all the bi services.

1.Configure the boot.properties to create an encrypted method to automatically pass the admin username and password

%middleware_home%\user_projects\domains\bifoundation_domain\servers\AdminServer\security\boot.properties

eg., %middleware_home% - E:\obiee then boot.properties file exists in the following location

E:\obiee\user_projects\domains\bifoundation_domain\servers\AdminServer\security\boot.properties

Add the following lines:

username=[the Administrator username created during install, e.g weblogic]
password=[the weblogic username password e.g welcome1]

Note: the above credentials are the same as the one provided when the AdminServer is started from Command line. Do not use or leave the brackets [ ] in the file. They are only used to show what should be entered.
As soon as you start the Admin Server the username and password values in this file will be encrypted


Admin Server:
2..Create a command script called installAdminServer_Service.cmd in the following path
E:\OBIEE\wlserver_10.3\server\bin,

Please note that the middleware home values need to be specific to your install

3.Then add the Weblogic_home and setDomainEnv path in InstallSvc.cmd which is under the following path E:\OBIEE\wlserver_10.3\server\bin

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 modefrom the command prompt using startWebLogic.cmd). To redirect standard out to a text file, backup and edit installSvc.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

4.Next,  run as administrator "installAdminServer_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)

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.

Managed Server:

1.Configure the boot.properties to create an encrypted method to automatically pass the admin username and password

%middleware_home%\user_projects\domains\bifoundation_domain\servers\bi_server1\security\boot.properties

eg., %middleware_home% - E:\obiee then boot.properties file exists in the following location

E:\obiee\user_projects\domains\bifoundation_domain\servers\bi_server1\security\boot.properties

Add the following lines:

username=[the Administrator username created during install, e.g weblogic]
password=[the weblogic username password e.g welcome1]

2..Create a command script called installManageSrvr_Service.cmd  in the following path
E:\OBIEE\wlserver_10.3\server\bin,

change the -log parameter in the installSvc.cmd file to the new location. Fore example:

-log:"[middleware_home]\user_projects\domains\bifoundation_domain\servers\bi_server1\bi_server1-stdout.txt"

Then run the installManagedSrvr_Service.cmd as Administrator to create the Managed services.