Communication between applications

You need to carry out the following steps for each Rule Engine implementation.

Note   Note:From this chapter onwards, this manual explains what you need to do for a single implementation of Rule Engine. Obviously, you need to repeat the steps for each implementation.

Specify the Processing-Context-Ins

Identify the applications that produce information for input to Rule Engine.

For each of these applications, list:

  • How to identify each of the technical fields associated with the Input-Events sent
    (identification of the technical data in the flow)
  • The processing options to be executed
  • The external calls and exits that need to be developed

Where two or more applications produce events with identical physical characteristics (identity of technical fields, processing options, exits activated), you can associate them with a single Processing Context-In.

You need, therefore, one Processing-Context-In for each group of applications that generate distinct physical characteristics.

The result of the above exercise is the set of Processing-Context-Ins which you must reference in Rule Engine and whose characteristics you must define in AI Enabler.

Specify the Processing-Context-Outs

Identify the applications that receive the data output from Rule Engine.

These applications also have their requirements as regards the physical properties of the output from Rule Engine and the mandatory checks to be carried out on this data.

For each of these applications, list the following:

  • The structure to be expected in the incoming data
  • The type of checks to be carried out on the data
  • The processing options to be executed
  • The exits to be developed
  • The exchange zones that are to receive the data

Each set of data sharing an identical set of the characteristics listed above corresponds to one logical Processing-Context-Outs, together with its processing options.

The result of the above exercise is the set of Processing-Context-Outs you must reference in Rule Engine and whose characteristics you must define in AI Enabler.

Specify the sessions

Knowledge of the way in which the applications are used and receive their inputs, together with the frequency with which they produce the relevant data, allows you to define the schedule for running Rule Engine, that is, daily, weekly, monthly, quarterly, annually and so on.

Finally, the sets of Processing Context-Ins, Processing Context-Outs, exits and external calls to be activated, together with the associated execution schedules, allow you to define the various Rule Engine sessions.

Related Links