Comms Purge

Job type: JavaClosed A widely used object-oriented programming language that is designed for use in the distributed environment of the internet. It is the most popular programming language for Android smartphone applications

Archive: None

For more information on this job, see the Job Details in the Administration ConsoleClosed An operations web console that allows batch jobs to be scheduled, run manually and monitored. The console also provides for viewing and modification of business and user applicable system configuration.: In the console, navigate to System Maintenance > Jobs. In the Job List, click the name of job to open its Job Details screen.

The Comms Purge job is responsible for removing customerClosed In the context of the Cloud Monetisation Platform, an individual or organisation who has signed an agreement to take goods and services from a service provider. A customer receives a bill associated with one or more subscriptions, and can be a single end user or a large company with many subscriptions assigned to one agreement. communication information stored in CMPClosed Converged Monetisation Platform. The MDS Global product that supports customer care and billing for digital service providers..

The job derives a calculated purge date based on how long data should be retained before it can be purged. Only communications related data that were generated on or before the calculated purge date will be considered by the job.

Selection criteria

The job accepts a single parameter - Months to Retain. This represents the number of months worth of data to retain. The job subtracts this parameter from the current date to calculate a purge date. The months to retain can be entered manually when the job is run. If no value is provided then the value configured for the module property comms.purge.default.noofmonths will be used.

Any transaction data prior to the retention period will be permanently removed.

A value of zero (0) is not allowed as a parameter.

A creationDate attribute enables partitions to be created to support the Comms Purge job. Partitions are created daily; any partitions with a creation date prior to the calculated purge date are removed.

Tables Impacted:

  • Comms Request Header

  • Comms Request Target Detail

  • Comms Request Target Distribution

  • Comms Request Error

  • Comms Request Field Detail

  • Comms Request Not Sent

Running the purge job

In the Administration Console, you can create a schedule for the purge job or run it as needed.

To run a job:

  1. Navigate to Daily Operations > Jobs.
  2. In the Job List, select the checkbox for the job that you want run.
  3. Click Run Now.