Back to documentation index

Introduction

Non-events allow you to monitor the ports in your BizTalk group based on a set of rules that define the expected traffic-behavior within a specified time interval. A Non-event rule set is defined by several rules and is applied to one or more of your applications ports.

Configuration

Any given rule is defined by traffic intervals and time of application

The traffic intervals

The traffic intervals define which intervals that produce different stati on your ports:

• Lower error - The lowest allowed number of messages to pass through the port which does not produce an error on the port
• Lower ok - The lowest allowed number of messages to pass through the port which produces a OK status on the port
• Upper ok -The highest allowed number of messages to pass through the port which produces a OK status on the port
• Upper error - The highest allowed number of messages to pass through the porte which does not produce an error on the port

Time of application

Time of application defines when the rule should be active and apply to the port(s).

• Specific interval - Checks the amount of messages within a specific interval. Such as 08:00 to 16:00. If the traffic does not fall in the expected interval, this port will display an error after 16:00.
• Sliding interval - Checks the amount of messages in the last predefined sliding-period (i.e. 3 hours) within a specific interval (i.e. 08:00 to 16:00). In this case, IPM will begin monitoring at 08 and continually do so until 16:00, checking that the aggregated traffic at the given port the last three hours fall within the predefined traffic levels.
• Valid for days - The day(s) of the week when the rule applies.

Example

The below figure is an example rule set defined by two rules.

The first rule applies on weekdays and states that there should be between 10-20 messages per hour between 08:00 and 16:00. Any traffic data below 5 or above 100 will produce and error, and anything between 5-9 and 30-100 would be marked by a warning status.

The second rule applies every night of the week, and assumes that 25-75 messages will be processed by the system every night between 04:00 and 05:00.

The rule set once defined can be applied to any tracked port in your application by checking it in the port's context menu (as seen in the figure below).