Get journals 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 the list of available journals for a specific data connection inside a project.

HTML

GET https://hostname/v1/integration/continuous/projects/{projectId}/connections/{connectionId}/journals

A Journal is the source-side log/journal identifier used by CDC:

  • On IBM i, a journal determines which objects can be captured and from where changes are read.
  • Journals are used when configuring LogReaders (a log reader points to a journal).

Typical usage

  • UI/agent step to populate a journal dropdown before creating a LogReader.
  • Validation step to ensure a user-selected journal exists

Required permissions

replication-pipeline::view

Request

Path parameters

Key Required Type Description
projectId Yes string

Project identifier
connectionId Yes string

Connection identifier

Response

If journals are available, the method returns 200 with an array. If no journals are available or none are returned by the source metadata service, the method returns 200 with an empty array. If the project does not exist or is not accessible, the method returns 404.

Response body properties

Property Required Type Description
name No string  

Response examples

Example status code responses for this method are shown here.

Examples
"name": "JRN001"
 
"name": "JRN002"
 
"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}/journals",
"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}/journals",
"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}/journals",
"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}/journals",
"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}/journals",
"properties": {
  "errorCode":"DI-ADAPTER-JRN-0002"
}