Skip to main content

Axios Assyst (Ticket)

Connector name

pxassyst

Connector type

Executable with script

Type (UI field value)

Axios Assyst (Ticket)

Target system versions supported / tested

Bravura Security Fabric uses the pxassyst interface program to trigger creations and updates on Axios Assyst systems when certain events occur on the Bravura Security Fabric server.

Connector status / support

Customer-Verified

Clients may contact Bravura Security support for assistance with this connector. Troubleshooting and testing must be completed in the client's test environment as Bravura Security does not maintain internal test environments for the associated target system.

Installation / setup

Interface programs are installed in the interface directory.

Modify the sample pxassyst.cfg script included in the samples directory and copy it to the \<instance>\script\ directory.

The following sections show you how to configure the event actions interface for Bravura Security Fabric 7.0 or higher by:

  • Preparing the target

  • Setting the target system address in Bravura Security Fabric (version 7.0 and higher)

  • Writing a configuration file for event actions

Preparation

In order to interface with Assyst Help Desk 5.5, 6.5, 7.0, you must first:

  1. Install and configure the Assyst 5.5, 6.5, or 7.0 AssystApps and Command Line Loader on the Bravura Security Fabric server.

  2. Ensure that the Assyst installation directory is configured in your system’s path environment variable (usually C:\Program Files\Assyst Enterprise).

    You may need to restart your computer in order for your web server (IIS) to be made aware of the path.

Targeting an Assyst Help Desk server

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 (Manage the System > Resources > Target systems) for each Assyst Help Desk server to support the event actions interface.

  • Type is Axios Assyst (Ticket) , listed under IT Service Management Systems .

  • Address uses the following options:

    Database name The name of the Axios Assyst database

    Database type The type of database on the Axios Assyst server.

    Server The hostname or IP address of the Axios Assyst server.

    The address is entered in KVGroup syntax:

    {database=<database name>;databasetype=<type>;server=<server 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 Axios Assyst, you must write a configuration file. Modify the pxassyst.cfg 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 Targeting a Assyst Help Desk server . In both cases, pxassyst looks for the default script with the matching name.

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

  • pxassyst.exe -cfg myfile.cfg

    or

  • MYASSYST -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 Assyst Help Desk script.

Table 1. Variables for Assyst Help Desk

Key

Flag in acli.exe

Description of the value

databasetype

-v

The database type (for example, SQLServer).

server

-h

The database server (for example, <host name>\\<server name>).

database

-d

The database name (for example, assyst).

adminid

-u

The database user ID (for example, sa).

adminpwd

-p

The password for the database user ID.



In this section: