Per the 4.3 SRND, Archive jobs for archiving activities older than a certain number of days must be configured via the Cisco Interaction Manager Administration Console, if the Active database size exceeds 30 GB. The maximum size of the Active database must not exceed 40 GB, in order to ensure optimal system performance.
- You can archive cases and activities. However, attachments of activities are not archived to a different server - they remain on the File Server.
- Once archived, a case or activity cannot be “unarchived.” If a customer replies to an archived case, a new case gets created.
- Archiving must be properly combined with regular reindexing for maintaining a healthy and optimal EIM/WIM database.
What makes up an Archive Job?
Start at the highest level - the Archive Job. This is configured from the Administration Console > Departments > Service > Archive Jobs. From this UI, you can set:
- Job Name
- Queues to Archive
- Time Frame (How far back to archive)
- Scheduled days to run the job
- Job state (on/off)
The Job can be validated from the eGActiveDB with the below query. Note the JOB_ID - this can be used to correllate Job Runs.
select * from egpl_arch_job
LAST_RUN_STATUS of 0 means that the last job run was successful. The same is true for RUN_STATUS in subsequent tables.
Whenever a Job is run, a new entry is made in the egpl_arch_job_run table. Note the value of JOB_RUN_ID - this represents one single run of the job (i.e., Tuesday night).
select * from egpl_arch_job_run
Within each Job Run is a series of batches, each designated by BATCH_ID and run sequentially by the system.
- Each batch can archive a maximum of 5000 records. This is defined in egpl_archiverconfig.properties (<>:\cisco\eService\config) batch.size.1=5000
- Every batch completes archiving in two steps:
- First, it inserts data from the active database to the archive database.
- After successfully inserting the data in the archive database, it deletes the data from the active database.
- All Batches must complete successfully for a Job Run to be marked complete.
select * from egpl_arch_job_run_batch
Within each Batch are multiple steps, each designated by STEP_ID. All Steps must complete successfully for a Batch to be marked complete.
select * from egpl_arch_batch_step
- Job Run
- Job Run
Purging Archive Job Runs
Purge jobs can systematically manage the size of the eGArchiveDB. Note that deleting a Job Run (either manually or via a purge schedule) will delete all cases, activities, attachments, etc. associated with that Job Run.