Infrastructure Maintenance Workflows and CIC

This information describes the tools and capabilities available to the user while conducting local or cloud-hosted system maintenance. This maintenance pertains to a local system environment (or a cloud-hosted Customer-owned environment), not the monthly CIC maintenance period/release. 

The purpose of this article is to help users understand what happens when you pause system processing.  

In CIC Cockpit, the Admin > System page allows you to monitor and control CIC Engine activity in real-time, and also can be used to pause and resume processing.

The System Administration article describes the complete management of CIC Engine activity in real-time.

Pause and Resume System Processing in CIC (Admin>System)

Pausing and resuming system processing allows systems to be taken offline without having to reprocess payloads. When the system is paused, payloads are held until the system is resumed. When you click the Pause button, CIC processes any payloads that are in a queue before the system is considered to be in a "paused" state. 

Pausing a process 

• This stops new Business Processes from executing, once in-flight work is completed. This includes pausing all database-related processing. This suspension functionality applies to the CIC (Transformation) Engine only.
• For data movement-only processing, CIC has built-in retry mechanisms that will continue attempting delivery until successful. Thus, no manual reprocessing should be required, even if the source or target system is temporarily unavailable during maintenance.

During suspension

• Protocol endpoints (AS2, SFTP, etc.) continue to receive and process files. If processing requires the Transformation Engine, those files will queue in the backlog until processing resumes.
• API requests targeting API Provider endpoints will receive an HTTP 503 “Service Unavailable” response while processing is suspended.

After resuming

• We recommend routing any scheduled database processes to a single-threaded queue using the SendEventNotification Business Process task (see below), or ensuring the Schedule Queue is configured with only one Active Process. This helps avoid race conditions and prevents duplicate processing when the tenant resumes activity.

  ---

SendEventNotification BP Task

This task sends an Event to the Event Notification Manager.