Resolution:
Description:
===========
How to install BusinessEvents(BE) Rule Management Server (RMS) or BE Monitoring Management(MM) or BE Engine as a Windows NT Service.

Environment:
===========
Windows platform.
BusinessEvents version: All

Resolution:
==========
This Solution explains how to configure RMS as a NT service and also applies for the BEMM and BE engine as well.

In the tra file (be-rms.tra, be-mm.tra or project.tra) provide the absolute ear file (RMS.ear, MM.ear or project.ear) location as follows:

Example: BE_HOME = C:\tibco\be\&ltversion>

*******
tibco.env.APP_ARGS=C\:/tibco/be/&ltversion>/rms/bin/RMS.ear
*******

Add the following properties in be-rms.tra
*******
ntservice.name=TIBRMS
ntservice.displayname=TIBCO RMS (RMS)
ntservice.starttype=automatic
ntservice.binary.path.absolute=C\:/tibco/be/&ltversion>/rms/bin/be-rms.exe
ntservice.interactive=false
*******
You can also configure the log directory by adding the following property:

Engine.Log.Dir            C:/temp/rms/logs

In addition to the above settings, for BE version 4.x and greater, add the following properties:

******
tibco.env.RV_HOME=&ltRV HOME location>
tibco.env.HAWK_HOME=&ltHAWK HOME location>
tibco.clientVar.CDD=C\:/tibco/be/&ltversion>/rms/bin/RMS.cdd
tibco.clientVar.PUID=default
******

Modify the following property’s values:
******
com.tibco.be.config.path=&ltabsolute path of RMS.cdd>
tibco.env.STD_EXT_CP - Add &ltRV_HOME>/lib and &ltHAWK_HOME>/lib to existing value of the property
******


PUID value default is required for BEMM and RMS as both the engines are configured to start with the default PUID. Additionally, set RV_HOME & HAWK_HOME respectively in the tra files.

To install the NT service:

Traverse to the RMS bin directory(C:/tibco/be/&ltversion>/rms/bin) using the command prompt and run the following command:

BE_HOME/rms/bin&gtbe-rms.exe --install

To uninstall the NT service:

BE_HOME/rms/bin&gtbe-rms --uninstall

If there is any change to the tra file you will have to run --uninstall and --install again for the new changes to take effect. If the configured NT service does not start, you can search for the cause in the log file under C\windows\system32\logs\BEMM.log.