Open topic with navigation

TIBCO BusinessEvents® Enterprise Edition 6.3.1

# Setting up TIBCO BusinessEvents Engine as a Windows NT Service

You can configure the TIBCO BusinessEvents engine, Rule Management Server (RMS), or Views to start as a Windows NT service.

Note: TIBCO Hawk must be installed on the same machine for installing the BusinessEvents engines as a Windows NT service.

To set up the engines, follow these steps:

Procedure
1. Open the required TRA file for editing:
   BE_HOME/bin/be-engine.tra for the TIBCO BusinessEvents engine
   BE_HOME/rms/bin/be-rms.tra for RMS
   BE_HOME/views/bin/be-views.tra for Views
2. Add the following environment paths under the common environment variables:

       tibco.env.HAWK_HOME=<absolute path where TIBCO Hawk is installed>

3. Edit the arguments for the application property to provide the absolute path to the EAR file:

       tibco.env.APP_ARGS=<absolute path of the EAR file>

   The value of the `tibco.env.APP_ARGS` property depends on the type of engine:

   Absolute path of `BEprojectName.ear` file for the TIBCO BusinessEvents engine
   BE_HOME/rms/bin/RMS.ear for Rule Management Server (RMS)
   Absolute path of `ViewsProjectName.ear` file for Views

   Optionally you can provide name to the engine using the`-n` option of the `tibco.env.APP_ARGS` property. For example, for TIBCO BusinessEvents engine for FraudDetection project

       tibco.env.APP_ARGS=C\:/tibco/be/6.0/examples/standard/FraudDetection/fd.ear -n fddef

4. Edit the TIBCO standard classpath property to include classpath for RV and HAWK. Append `%PSP%%HAWK_HOME%/lib%PSP%%RV_HOME%/lib` to the existing value of the `tibco.env.STD_EXT_CP` property.
5. Add the following properties to define the Windows NT service configurations:

       ntservice.name=<short name for Windows NT service>
       ntservice.displayname=<full description of the service>
       ntservice.starttype=<type of start, whether automatic or manual>
       ntservice.binary.path.absolute=<absolute path of engine executable>
       ntservice.interactive=false

   The `ntservice.binary.path.absolute` property identifies the absolute path of the respective executable:

   BE_HOME/bin/be-engine.exe for the TIBCO BusinessEvents engine
   BE_HOME/rms/bin/be-rms.exe for RMS
   BE_HOME/views/bin/be-views.exe for Views

   For example, for TIBCO BusinessEvents engine the Windows NT service configurations are:

       ntservice.name=TIBBEFD
       ntservice.displayname=TIBCO BusinessEvents FD Default
       ntservice.starttype=automatic
       ntservice.binary.path.absolute=C\:/tibco/be/6.0/bin/be-engine.exe
       ntservice.interactive=false

6. Add the following properties to provide CDD file to the engine:

       tibco.clientVar.CDD=<absolute path of the CDD file>

   The value of the `tibco.clientVar.CDD` property depends on the type of engine:

   Absolute path of `BEprojectName.cdd` file for the TIBCO BusinessEvents engine
   BE_HOME/rms/bin/RMS.cdd for RMS
   Absolute path of `ViewsProjectName.cdd` file for Views

   For example, for TIBCO BusinessEvents engine for the FraudDetection project

       tibco.clientVar.CDD=C\:/tibco/be/6.0/examples/standard/FraudDetection/FraudDetection/fd.cdd

7. Set the processing unit ID (PUID) for the engine to the PUID that is set up in the CDD file.

       tibco.clientVar.PUID=<processing unit ID mentioned in the CDD file>

   For example, the PUID in the `fd.cdd` file is set as `default` for the BusinessEvents engine, then the value of PUID in the TRA file is also `default`.

       tibco.clientVar.PUID=default

8. (Optional) Specify the path of the log file in the `Engine.Log.Dir` property. For example:

       Engine.Log.Dir C:/temp/logs

9. Save and close the TRA file.
10. Open the command prompt and browse to the `bin` directory of the respective engine.
11. In command prompt run the commands to install or uninstall the Windows NT service.

    For example, to install the TIBCO BusinessEvents engine as Windows NT service:

        BE_HOME/bin>be-engine.exe -install

    For example, to uninstall the TIBCO BusinessEvents engine as Windows NT service:

        BE_HOME/bin>be-engine -uninstall

Result

To verify, if the service is set up correctly, browse to the `bin` directory of the respective engine in the command prompt and run the engine without any argument. If the service does not start check logs for the cause.

Note: For any change to the TRA file, run -uninstall and -install commands again for the changes to take effect.

Did you find this helpful?

YesNo
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO BusinessEvents® Enterprise Edition

Copyright © 2004-2024. Cloud Software Group, Inc. All Rights Reserved.