Skip to main content

Adding programs to run

Bravura Security Fabric automatically configures certain programs to run when you set up actions as described in Adding email support and Configuring ticket updates . For other interface programs, you must write a configuration script for the program. You can configure multiple programs for the same event.

To set up scripted programs to run when certain events occur on the Bravura Security Fabric server:

  1. Type the name of the programs, or ticket system target IDs, to be invoked when the event occurs.

    You can do this in the appropriate configuration page, or Using the Configure event (ITSM) module .

    When adding program names, you must include the full name; for example pxrem.exe. Do not include path information.

    You can specify a configuration file with the -cfg parameter, described on the current page.

  2. Click Update.

  3. Write a script file that defines the interaction between Bravura Security Fabric and the interface program. You can define a different sequence of actions for every type of event. Default script file names correspond to the interface program name.

Using target IDs

When using ticket system target IDs, you can specify alternate configuration files. For example, assuming you have a Remedy Action Request System 9.0+ (Ticket) target with an ID of ARS7, you can add:

  • pxrem9.exe

    or

  • ARS9

In both cases, the pxrem9 program will use the default script pxrem9.cfg in the script directory.

You can specify an alternative configuration file using the -cfg parameter; for example:

pxrem9.exe -cfg myfile.cfg

or

ARS9 -cfg myfile.cfg

In both cases, the pxrem9 program will use the script myfile.cfg in the script directory.

It is recommended that you use a target system ID in this field. The benefit is that all sensitive information (server address, admin credentials) is automatically passed to the program, rather than stored in the .cfg file in plain text. This enhances security.

You must specify an alternative .cfg file when you have multiple ticket targets of the same type; for example, ARS1 and ARS2. If you wanted to configure event actions only for the ARS1 target, then the program to run would be: ARS1-cfg ARS1_file.cfg.

Warning

The cfg file name must not contain the string -itsm ; for example, myfile.cfg is allowed, but my-itsm.cfg is not.

In this section: