Task Parameters

<< Click to Display Table of Contents >>

Raynet One Data Hub > 2026.2 > Connectors > Alphabetic Connector List > BMC Discovery > Connector Parameters 

Task Parameters

Search Query

This parameter defines the TPL (Tideway Pattern Language) query to execute against the BMC Discovery search endpoint. The query determines which data is retrieved from the BMC Discovery instance.

 

Technical Name

SEARCH_QUERY

Category

Functional

Type

String (multi-line)

Default Value

n/a

Example Values

search Host where os_type = "Windows"

 

Page Size

This parameter controls the number of items retrieved per API request. The connector automatically issues additional requests to collect all results when the total number of matching records exceeds this value.

 

Technical Name

PAGE_SIZE

Category

Technical

Type

Integer

Default Value

1000

Example Values

1000

 

It is recommended to adjust this value only if there are performance issues or API limitations in your environment. A larger page size reduces the number of requests but increases the memory and processing time required per request.

 

Request Timeout

This parameter sets the maximum number of seconds to wait for a response from the BMC Discovery API before the request is considered failed.

 

Technical Name

TIMEOUT

Category

Technical

Type

Integer

Default Value

60

Example Values

60

 

Maximum Retries

This parameter defines the maximum number of times a failed API request is retried before the connector reports an error. Failed requests are retried with exponential backoff based on the configured retry delay.

 

Technical Name

MAX_RETRIES

Category

Technical

Type

Integer

Default Value

3

Example Values

3

 

Retry Delay

This parameter sets the base delay in seconds between retry attempts. Each subsequent retry applies exponential backoff, multiplying the base delay by a factor of two for each attempt.

 

Technical Name

RETRY_DELAY

Category

Technical

Type

Integer

Default Value

5

Example Values

5

 

finger1

Be aware:

The actual wait time between retries grows with each attempt: first retry waits the configured base delay, second retry waits twice the base delay, and so on. Adjust this value if the BMC Discovery instance requires additional recovery time after a failed request.