Journey Manager (JM) The transaction engine for the platform. | System Manager / DevOps | 24.04 This feature was introduced in 24.04
Manager comes with the Data Retention Management v2 service, which extends the Data Retention Management service and provides Transaction Processor service performance improvements. The improvements include reduced memory footprint and more efficient database queries.
The Data Retention Management v2 service is not set as the default service for the Data Retention Management type, so you must make it default before you start using it.
To configure the Data Retention Management v2 service:
For explanation of the parameters, see Data Retention Management Service.
Some of the service's settings duplicate the Global Data Retention Configuration, so you can override them.
Data Retention Management (v2.0.1) applied, 493 total records deleted in ~634 ms
Processing 1 of 2 - Transactions PII Data purged 1 records in ~18 ms:
"AWS Submission Data Storage" removed 1 records in 0 ms
"File Upload Batch Update" updated 0 records in 0 ms
"Submission History Batch Update" updated 0 records in 0 ms
"Async Msg and Body PII" removed 0 records in 0 ms
"Extracts and Search PII" removed 0 records in 3 ms
"File Uploads and Data PII" removed 0 records in 0 ms
"Groovy Service Logs and Data PII" removed 0 records in 1 ms
"Submission History Data PII" removed 0 records in 2 ms
"Job Properties and Search PII" removed 0 records in 2 ms
"Submission Error Logs" removed 0 records in 0 ms
"Submission Properties and Search PII" removed 0 records in 2 ms
"Submission Data PII" removed 0 records in 0 ms
Processing 2 of 2 - Transactions and Related Data purged 492 records in ~615 ms:
"Audit Log(s)" removed 0 records in 0 ms
"Email Queue(s)" removed 456 records in 42 ms
"Error Log(s)" removed 0 records in 18 ms
"Event Log(s)" removed 2 records in 14 ms
"Groovy Service Log(s)" removed 0 records in 13 ms
"Scheduled Job History(s)" removed 33 records in 15 ms
"Security Manager Log(s)" removed 0 records in 13 ms
"Submission(s)" removed 1 records in 453 ms
"Transaction History(s)" removed 0 records in 13 ms
"User Authorized Event(s)" removed 0 records in 14 ms
"Composer Package Queue(s)" removed 0 records in 15 ms
"Import Action(s)" removed 0 records in 2 ms
"Job(s)" removed 0 records in 1 ms
"Job Group(s)" removed 0 records in 1 ms
"Request Log(s)" removed 0 records in 0 ms
"Submission Group(s)" removed 0 records in 1 ms
Then you can search for particular retention event in the event logs using the following criteria: Submission Data Pii
as a message. This is illustrated below.
You can further narrow the search down by using an event ID, for example, 748285
, as shown below:
Next, learn how to view all core global services.