Subscription Event Mapping 

Use

 

Events that a repository manager sends and that pertain to subscriptions can be filtered using subscription event mapping.

Instead of sending all notifications, the subscription service only sends notifications defined in the implementation (Mapping Class parameter).

Depending on configuration, subscription event mapping forms a targeted subscription-internal event from a particular repository manager event.

Features

The following parameters can be modified in subscription event mapping:

Subscription Event Mapping Parameters

Parameter	Required	Description
Name	Yes	Name of subscription event mapping service.
Link Handling (“user decision” reserved for future use)	Yes	Defines how subscriptions to links are handled. use link: Subscription to the link itself. use link target: Subscription to the target of the link. follow link target: Subscription follows the target of the link dynamically. The user decision entry is reserved for later development.
Mapping Class	Yes	The Java class that maps the low-level events sent by the repository framework to "semantic" events that trigger notifications for subscriptions. The default value is: com.sapportals.wcm.repository.service.subscription.wcm.SubscriptionEventMapStandard The value of the extended Java class that includes the report for the changed properties of the resource is: com.sapportals.wcm.repository.service.subscription.wcm.SubscriptionEventMapStandard2
Repositories	Yes	List of repositories that use the subscription service.

 

Activities

Each newly created repository manager for which you want to use subscriptions has to be entered into subscription event mapping.

You can find the configuration of the subscription event mapping under Content Management → Repository Services → Subscription Event Mapping →Subscription Event Mapping.

 

Each repository manager can only use one subscription event mapping service. This means that only one subscription service can be assigned to a repository manager.