Examples of Generating and Processing Notifications

Use

Notifications are generated when the trigger conditions of a tag subscription have been met. PCo sends the notification to the destination systems that are assigned in the notification.

The following examples of generating and processing notifications are described:

Prerequisites

For a subscription through Business Suite applications, PCo first creates a notifications for the transferred application handle. For this, the Business Suite application needs to select an existing notification template of the associated PCo agent instance when subscribing to tags (see Notification Template). You need to create the notification template in the PCo Management Console for the PCo agent instance first. The notification template contains the following information:

Field/Setting in the Notification Template

Meaning

Trigger Type and Trigger Expression

Trigger Type Always is the preferred Trigger Type for Business Suite integration scenarios. The other trigger types can be used for Business Suite integration scenarios insufficiently only.

Subscription Lifetime (Seconds)

The default value for the lifetime is an hour (3600 seconds). See also: Notification Template: Remote Subscription Tab

Settings for reliable connections and reliable message delivery

  • You can set the number of attempts to restore the connection if the PCo connection to the external data source is lost.

  • You can state the lifetime of notification messages that could not be delivered. The default value for the lifetime is one day.

See also: Notification: Reliable Connection Tab

PCo destination systems to which the notification is transferred

On the Destinations tab of the notification template you assign the PCo destination system for your Business Suite system, which is to receive and process the notification message. You define the connection data for the Business Suite system when defining the relevant PCo destination system in PCo (see Destination System: RFC Client Settings Tab).