The Admin>System page allows you to monitor and control CIC Engine activity in real time. Monitoring and controlling the kind of activity displayed on this page allows you to address possible issues. Consider the following examples:
- You expect a time period of heavy Purchase Order traffic (for example, Black Friday) and want to ensure a fast turnaround for these particular document types. Increasing the number of active processes allowed for that document type allows greater concurrent processing. Increasing priority ensures CIC will pick up these document types before others.
- You generate outbound EDI documents, which requires a database SELECT operation that runs often. If two of these processes run concurrently, it is possible that the database won't be updated fast enough to be reflected correctly for both processes resulting in duplicate records being selected. In this case, limiting CIC Engine to a single active process for this type of outbound EDI document can prevent this situation from occurring.
Viewing and Managing System Information
The top section displays the status of the system and system-level information about active processes (those currently running) and queued processes (those waiting to run).
In addition, you can use the System Status panel to pause and resume CIC Engine operation.
Pausing and Resuming System Processing
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. This is useful, for example, for last-minute project changes, where, instead of making the adjustment while transactions are flowing you can suspend the system while you test and deploy your changes, minimizing reprocessing efforts.
Note: 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.
To pause or resume processing for the entire system, use the toggle in the System Status box.
Pausing the system suspends processing on all transactions, inbound and outbound, and those items are queued until you resume. This can take up to several hours, depending on the current load.
Once the system is completely stopped, the status is shown as Paused and the number of Active Processes displayed is 0.
Viewing and Managing Event Information
The Events List displays system events and related attributes. From here you can manage the number of processes assigned to an Event, their priority, and maximum size. The checkbox to the left of each Event enables the pause/resume toggle.
Note: Event-level management capabilities described below are licensable separately from the base CIC platform. Contact your Cleo sales team for more information.
The Events section has these columns:
|Event||The fully-qualified name of the queue.|
|Status||Possible values are Idle, Active, and Paused.|
|Active Processes||The number of processes/jobs currently running. This value corresponds with the Active Processes section, which displays those processes.|
|Max Active||The number of maximum processes that can be assigned to the queue. This maximum value cannot exceed the number of Active Processes based on your Server license.|
|Queued Processes||The number of processes that are currently queued (and waiting).|
|Priority||The priority of the queue relative to other queues; the lower the number, the higher the priority. Important and time-essential processes should have a value of 1 in order to process before other queues with lower priority.|
Displays icons representing available actions for the event.
Possible actions are Pause and Resume.
Pausing and Resuming Event Processing
To pause processing for a single event, click the icon in the Action column for the event. This will toggle processing on or off.
To pause and resume processing for multiple events, select the events in the list and then click the Pause or Resume button.
Prioritizing Event Queues
You can prioritize business-critical and time-sensitive processes and prevent processes from competing for resources to help ensure processes are completed in the correct sequence.
Use the drop-down menus in the Priority column to set priorities for events. Lower values indicate higher priority. Higher-priority processes are performed before lower-priority processes.