Skip to main content

Generic ODBC (Ticket)

Connector name

pxodbc and pxodbc-32

Connector type

Executable

Type (UI field value)

  • ODBC Generic (Ticket) for a 64-bit ODBC data source

  • ODBC Generic (32-bit) (Ticket) for a 32-bit ODBC data source

Target system versions supported / tested

Use the pxodbc and pxodbc-32 programs and its associated configuration file (pxodbc.cfg) to integrate with the ODBC-based database backend of a help desk system if no client and event action (px*) program are written for that purpose. The pxodbc and pxodbc-32 programs can be used to trigger automatic updates when certain events occur on the Bravura Security Fabric server.

Connector status / support

Bravura Security-Verified

This connector has been tested and is fully supported by Bravura Security.

Installation / setup

Interface programs are installed in the interface directory. Modify the sample pxodbc.cfg script included in the samples directory and copy it to the \<instance>\script\ directory.

Targeting ODBC-based ticket systems

Bravura Security Fabric provides the option of using the target system name in event action fields in the Manage the system (PSA) module or Configure event (itsm) module, rather than the program name. The security 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.

Add a target for each ODBC database to support the event actions interface:

  • Type is:

    • ODBC Generic (Ticket) for a 64-bit ODBC data source

    • ODBC Generic (32-bit) (Ticket) for a 32-bit ODBC data source

  • Address uses the ODBC data source name that points to the database used for the application:

    {server=<data source name>;}

  • Administrator ID and Password identify the user with permissions to perform all required operations.

Once you write a configuration file, you can use the target ID to configure event actions in the Manage the system (PSA) module or Configure event (ITSM) module.

Configuring event actions

To configure an event action to interface with an ODBC-based database, you must write a configuration file. Modify the sample script included in the samples directory and copy it to the \<instance>\script\ directory. If you cannot find the sample file, try re-running setup to modify your installation. Sample files are automatically installed with complete (typical) installations. You can select them in custom installations.

When you configure an event, you enter the program name or, as of Bravura Security Fabric version 7.0, the target ID you set up in earlier. In both cases, pxcasd looks for the default script with the matching name.

You can write an alternative .cfg file; for example when you have multiple targets of the same type. When you configure an event, you specify the file using the -cfg parameter; for example:

  • pxodbc.exe -cfg myfile.cfg

  • pxodbc-32.exe -cfg myfile.cfg

    or

  • <targetid> -cfg myfile.cfg

Requirements

If you do not use a ticket target to configure events, you must define the variables shown in the table below in every ODBC script.

Table 1. Required variables for ODBC

Variable

Description of the value

server

The Windows DSN for the desired ODBC connection.

adminid

The user ID of a user with permissions to perform all desired operations.

adminpwd

The password for the above user.



In this section: