BMC Remedy

BMC Remedy is an IT service management platform that integrates with the BMC Remedy AR System to synchronize incidents and assets. You can bring incident and asset data from BMC Remedy into Brinqa to gain a unified view of your IT operations, thus strengthening your cybersecurity posture.

This document details the information you must provide for the connector to authenticate with BMC Remedy and how to obtain that information from BMC. See create a data integration for step-by-step instructions on setting up the integration.

Required connection settings

When setting up a data integration, select BMC Remedy from the Connector dropdown. If you cannot find the connector in the dropdown, make sure that you have installed it first. You must provide the following information to authenticate BMC Remedy with Brinqa:

• Server: The BMC Remedy server hostname or IP address.

• Port: The AR System server port. The default port is 3700.

• User Name: The AR System login username. The user must have proper access to query, create, and delete form entries.

• Password: The AR System login password.

The connector authenticates using a direct server connection via the BMC AR System Java SDK (com.bmc.arsys.api). It creates an ARServerUser session with the provided credentials, which is used for all subsequent operations. This is not a REST API — the connector communicates with the AR System server over its native protocol.

Additional settings

The BMC Remedy connector contains additional options for specific configuration:

• Page size: The maximum number of records to get per request. The default setting is 100. It is not recommended to go over 500.
• Parallel requests: The maximum number of parallel requests. The default setting is 4.

Types of data to retrieve

The BMC Remedy connector can retrieve the following types of data from the BMC Remedy AR System:

Table 1: Data retrieved from BMC Remedy

Connector Object	Required	Maps to Data Model
Asset	Yes	Host
Incident	Yes	Not mapped

info

The BMC Remedy connector does not currently support operation options for the types of data it retrieves.

For detailed steps on how to view the data retrieved from BMC Remedy in the Brinqa Platform, see How to view your data.

Attribute mappings

Expand the sections below to view the mappings between the source and the Brinqa data model attributes.

note

The BMC Remedy connector uses dynamic attribute discovery. Beyond the fixed UID and NAME attributes listed below, all remaining attributes are automatically discovered from the BMC Remedy form at runtime. Each dynamically generated attribute follows the naming convention {field_name}_{field_id}, where the BMC field name is lowercased with spaces and hyphens replaced by underscores, and the BMC numeric field ID is appended (e.g., status_7, short_description_8, submitter_2).

Asset

Table 2: Asset attribute mappings

Source Field Name	SDM Attribute
InstanceId	NAME
InstanceId	UID

Additional attributes are dynamically discovered from the BMC.CORE:BMC_BaseElement form.

Incident

Table 3: Incident attribute mappings

Source Field Name	SDM Attribute
Incident Number	NAME
Incident Number	UID

Additional attributes are dynamically discovered from the HPD:IncidentInterface form.

APIs

The BMC Remedy connector uses the BMC AR System Java SDK. Specifically, it uses the following SDK methods:

Table 4: BMC Remedy SDK methods

Connector Object	SDK Method
Asset	ARServerUser.getListEntryObjects() on BMC.CORE:BMC_BaseElement
Incident	ARServerUser.getListEntryObjects() on HPD:IncidentInterface

Changelog

The BMC Remedy connector has undergone the following changes:

Table 5: BMC Remedy connector changelog

Version	Description	Date Published
3.0.1	Fixed attribute names that used raw numeric field IDs, which violated the platform's minimum length requirement. Attribute names now use a descriptive format combining the field name and ID.	April 29th, 2026
3.0.0	Initial Integration+ release.	April 29th, 2026