Get log readers for a connection - Precisely Data Integrity Suite

Data Integrity Suite APIs
Product
Data_Integrity
Spatial_Analytics
Data_Enrichment
geo_addressing_1
Services
Spatial Analytics
Data Enrichment
Geo Addressing
ft:title
Data Integrity Suite APIs
ft:locale
en-US
PublicationType
pt_developer
copyrightfirst
2023
copyrightlast
2026

Retrieves LogReader configurations associated with a specific data connection inside a project.

HTML

GET https://hostname/v1/integration/continuous/projects/{projectId}/connections/{connectionId}/logreaders
A LogReader (also referred to as a Change Selector in some CDC workflows) is responsible for:
  • Reading database logs and journals.
  • Producing changes for downstream replication.
  • Managing journal or receiver position and CDC offsets.

Typical usage

  • UI or agent workflow showing the change capture components configured for a connection.
  • Verification before triggering log reader by start or stop calls.

Required permission

replication-pipeline::view

Request

Path parameters

Key Required Type Description
projectId Yes string

Identifier for the project.
connectionId Yes string

Identifier for the connection.

Response

If log readers are configured for the connection, the method returns the 200 response code with a response array of properties for each log reader. If no log readers are configured for the connection, the method returns the 200 response code with an empty array. If the project does not exist or it is not accessible, the method returns the 404 response code.

Response body properties

Property Required Type Description
name No string The name of the log reader.
journal No string The name of the journal associated with the tables in the schema.
dataConnectionId No string The identifier for the data connection.
parameters No object Column values.

Response examples

Example status code responses for this method are shown here.

Examples
{
  "name":"logreader-name",
  "journal":"journal-name",
  "dataConnectionId":"conn-src-uuid",
  "parameters": {
    "TRACING_SQL_ALL_OTHER_QUERIES":"N",
    "DEL_JRN_RCV":"1",
    "REP_CLEAR_PF_MEMBER":"1",
    "COMMIT_WAIT_TIME":"2"
   }
}

"type":"https://datatracker.ietf.org/doc/html/rfc9110#section-15.5.1",
"title":"Bad Request",
"status":"400",
"detail":"Validation error occurred",
"instance":"/v1/integration/continuous/projects/{projectId}/connections/{connectionId}/logreaders",
"properties": {
  "errorCode":"DI-ADAPTER-VAL-0000"
}
 
"type":"https://datatracker.ietf.org/doc/html/rfc9110#section-15.5.2",
"title":"Unauthorized",
"status":"401",
"detail":"Authorization failed - missing or invalid credentials",
"instance":"/v1/integration/continuous/projects/{projectId}/connections/{connectionId}/logreaders",
"properties": {
  "errorCode":"DI-ADAPTER-AUT-0001"
}
 
"type":"https://datatracker.ietf.org/doc/html/rfc9110#section-15.5.4",
"title":"Forbidden",
"status":"403",
"detail":"Authorization failed - insufficient permissions",
"instance":"/v1/integration/continuous/projects/{projectId}/connections/{connectionId}/logreaders",
"properties": {
  "errorCode":"DI-ADAPTER-AUT-0002"
}
 
"type":"https://datatracker.ietf.org/doc/html/rfc9110#section-15.5.5",
"title":"Not Found",
"status":"404",
"detail":"Not Found - Resource does not exist",
"instance":"/v1/integration/continuous/projects/{projectId}/connections/{connectionId}/logreaders",
"properties": {
  "errorCode":"DI-ADAPTER-PRJ-0005"
}
 
"type":"https://datatracker.ietf.org/doc/html/rfc9110#section-15.6",
"title":"Internal Server Error",
"status":"500",
"detail":"An unexpected error occurred",
"instance":"/v1/integration/continuous/projects/{projectId}/connections/{connectionId}/logreaders",
"properties": {
  "errorCode":"DI-ADAPTER-LGR-0003"
}