Audit Trail and Recovery Notification Handling
Configure the following properties for the processing of audit trail and recovery notifications.
Property | Description | Default Value |
---|---|---|
auditTrailNotificationQueue | Queue on which the Orchestrator dispatches the audit trail notifications. | tibco.aff.orchestrator.audit.trail.notification.queue |
orderEventNotificationQueue | Queue on which the Orchestrator dispatches the recovery notifications. | tibco.aff.orchestrator.order.event.notification.queue |
The orchestrator no longer directly saves audit trails and notifications. Instead, it dispatches these notifications to EMS for archival and processing by the Broker Service.
Audit Trail Updates
-
Dispatching Audit Trail Notifications: The Orchestrator now dispatches audit trail notifications to the Archival Service using the queue specified by the
auditTrailNotificationQueue
property. -
Archival Service Responsibility: The Archival Service receives these notifications and saves them in its database.
Impacts
-
API changes: The following APIs are now managed by the Archival Service:
-
Submit Audit Trail: POST
/order/audit
Note: For Submit Audit Trail request from TIBCO EMS, the date format must be as follows:2023-10-09T15:20:28.773Z
-
Get Audit Trail: GET
/v1/orders/audit
-
-
JMS Listeners: The JMS listeners for custom audit trails have been moved to the Archival Service.
Recovery Notification Updates
-
Dispatching Recovery Notifications: The Orchestrator now dispatches recovery notifications to the Broker Service using the queue specified by the
orderEventNotificationQueue
property. -
Broker Service Responsibility: The Broker service receives these notifications and saves them in its database.
-
No Functional Impact: There is no impact on the existing functionality of the Orchestrator or Broker Service.
This new approach improves the separation of concerns and enhances the efficiency of handling audit trails and notifications by leveraging EMS for better scalability and performance.