The Agent in Data Integrity Suite supports multiple services, each serving a specific role in data movement, integration, or platform operations. This table summarizes their functions relevant to the suite.
-
Update DIS CLI: Before updating the operator, make sure you are using the latest version of the DIS CLI.
Run the following command:
./discli updateCli
Updating the CLI ensures compatibility with the latest operator update workflow.
-
Update operator version: After updating the CLI, update the operator service to the latest available version.
Run the following command:
./discli agent applyOperatorVersion --version=<latest-version>
Updating the operator version ensures that all agent services are automatically upgraded. You can find the latest available operator version in the Data Integrity Suite UI.
- Verify agent health: After the operator update completes:
- Verify that the agent health status is OK.
- Check the agent module versions.
If you observe a discrepancy where the Latest Version and Current Version of agent modules differ, restart the operator to initiate the update process.
Run the following command:
./discli agent restart operator
Restarting the operator triggers the update process and updates the remaining agent services.
| Service Name | Description |
|---|---|
| connect-cdc | Data Integration service for running continuous replication projects. |
| connect-hub | Data Integration service for routing requests, commands, and status information among replication components. |
| cloud-applier | Data Integration service that applies changes to cloud data warehouse targets such as BigQuery and Snowflake. |
| sqdata-management | Data Integration service for running mainframe replication projects. Also known as mainframe-replication-manager. |
| message-adapter | Routes internal messages between Precisely Cloud queues and individual Agent service message queues. |
| log-aggregation | Collects and aggregates logs across agent services for diagnostics. |
| operator | Manages lifecycle and coordination of services within the agent. |
| mailbox | Enables bidirectional communication between the local Precisely Agent services and the Precisely Cloud services using AWS SQS messaging. |
| kafka | Provides a local message queue for inter-service communication within the Agent. |
| spark-connector | Runs Data Quality pipeline and assessment jobs using the Apache Spark framework for distributed data processing. |
| custom-jdbc-connector | Performs cataloging of basic metadata for most types of datasources. |
| credentials-management | Provides and manages service certificates to authenticate communication between the Precisely Agent and Precisely Cloud services on AWS. |
| trust-manager | Manages the lifecycle of TLS certificates and cryptographic credentials for internal Agent service communications. |
| acb-connector | Performs cataloging of advanced metadata for supported datasources, for workspaces with the Advanced Connectivity Bundle feature. |
| databricks-connector | Performs cataloging and assessment (including Data Quality) functionality for Agent-based connections to Databricks datasources. |
Agent services for data integration and data quality
This section provides an overview aimed at assisting you in updating the agent that manages Agent services for data integration and data quality. To ensure that your agent services are properly configured and updated for optimal data integration, please follow the guidelines referenced below:
Update the Agent configurations when you see an Update label next to an agent's name; it means there is a new update available for that agent, which is used in data replication processes. To ensure optimal performance, consider updating as soon as possible.
The Spark connector is an essential part of Agent. It allows the Agent to easily connect and work with Spark-based services. To use the Spark connector, simply follow the steps outlined in the user guide to enhance your data handling capabilities.