How can I be alerted when related Sterling Connect:Enterprise batches arrive?

To be alerted when related batches arrive in a Sterling Connect:Enterprise® mailbox, use a workflow SLC.

Associate a duration SLC schedule with the workflow SLC with a minimum duration of 00:00:00 and an appropriate maximum duration. This duration might be the expected time between the arrival of the first and last of the related batches.
Within the workflow SLC, define one milestone per batch to be received. The milestones you define must specify parameters that uniquely identify each batch.
Each milestone must specify values for duration. Specify minimum and maximum values that match the values in the duration schedule.

In the following example, four batches, named File1, File2, File3, and File4 are expected to be received by a managed Sterling Connect:Enterprise server named kukla35 within 5 minutes of one another. This data is to be sent by a user named Raj. You want to know when they all arrived, or that they did not arrive within the allotted time.

Create a duration SLC schedule to be referenced by the workflow SLC.
Because we expect all four batches to arrive within 5 minutes of one another, this duration schedule specifies a dMin of 0 hours, 0 minutes, and 0 seconds, and a dMax of 0 hours, 5 minutes, and 0 seconds.
Create the Workflow SLC.
On the General pane, the Enabled and Generate Notification if event has not occurred check boxes are selected.

The check box for Suppress Milestone Messages is selected. This check box is selected because we want events generated only for the workflow, not for its milestones.

The Start Monitor Window Tolerance is set to 1 hour. Also, the End Monitor Window Tolerance is set to 1 hour. This causes an event to be generated if all batches are not received within 1 hour and 5 minutes after the first batch arrives. The event states that the workflow did not complete within the monitoring window.
Select the duration schedule created in a previous step.
The concurrence count must be set to the number of related groups of batches expected to arrive per hour. We expect at most one per hour, so set concurrence count to 1.
Add the first milestone to the workflow SLC, the one corresponding to the first batch.
Here are the parameters for the milestone, named File1:

Key Operator Value

Server Wild Card kukla35

Process name Wild Card File1

Submitter Wild Card Raj

The server the batches are to arrive on is specified, as is the name of the batch and the sender of the data. Remember for Sterling Connect:Enterprise, Process name equates to batch ID, and submitter equates to the origin of the data.
Set the schedule for the milestone.
The minimum and maximum durations correspond to the durations for the workflow SLC schedule. In this example, the Minimum Duration (Dmin) is set to 000:00:00 and the Maximum Duration (Dmax) is set to 000:05:00.
Duplicate this milestone three times by using the Duplicate button. Duplicate the milestone once for each additional related batch, setting the process name to the new related batch name. The following table illustrates the Milestones pane settings for this example:

# Name Dmin Dmax

1 File1 000:00:00 000:05:00

2 File2 000:00:00 000:05:00

3 File3 000:00:00 000:05:00

4 File4 000:00:00 000:05:00

Key	Operator	Value
Server	Wild Card	kukla35
Process name	Wild Card	File1
Submitter	Wild Card	Raj

#	Name	Dmin	Dmax
1	File1	000:00:00	000:05:00
2	File2	000:00:00	000:05:00
3	File3	000:00:00	000:05:00
4	File4	000:00:00	000:05:00

IBM® Sterling Control Center Monitor comes with built-in rules that watch for corresponding SLC events that potentially could be generated as a result of this workflow SLC. They are:

Proc duration short - CSLC041E - alert2
Proc duration okay - CSLC042I - alert0
Proc duration not ended - CSLC043E - alert2
Proc duration exceeded - CSLC044E - alert1
Proc duration way over - CSLC045E - alert1

You might want to add your own rules and actions that are similar to the existing, built-in rules, which reference these message IDs. Do so by duplicating them, giving them new names, and specifying additional parameters, such as the name of the workflow SLC, and specifying your own actions.

For example, the Parameters pane could contain the following criteria:

Key	Operator	Value
Message Id	Matches	CSLC041E
SLC Name	Matches	Watch for 4 batches

Be sure, after constructing the new rules, to assign them a higher priority than existing rules that specify the same SLC event message ID. More specific rules should always be higher in priority than their more general counterparts.

That is all that needs be done. This workflow SLC is triggered whenever a batch arrives with an ID of File1, File2, File3, or File4 that was sent by Raj to kukla35. An SLC event will be generated when the last of the four batches arrives, or after 5 minutes, and after an hour and 5 minutes if they do not all arrive.