Data Change Notification (DCN) includes the ability to define cache partitions,
update MBO data within those partitions, and subscribe users to those partitions.
The EIS defined cache partition is a collection of
data from multiple MBOs and provides an alternative subscribe/unsubscribe model compared
to the per-MBO synchronization parameter model (client defined partition). A user can be
assigned to more than one EIS cache partition and an EIS cache partition can be assigned
to more than one user.
The basic flow for defining and subscribing to an EIS cache partition is:
- The MBO developer models the MBOs.
- The MBO developer assigns the MBOs that are part of the EIS cache
partition to a cache group that uses the EIS
Managed policy.
(Optional) The MBO developer sets the
Notify EIS to fetch operation option. The
notification endpoint is set on the EIS cache group before deployment, and
cannot be added to the EIS cache group (or otherwise managed) in
SAP Control Center if it is not specified before
deployment.
- The MBO developer deploys the project to SAP Mobile Server.
- Using SAP Control Center, the
SAP Mobile Server Administrator manages the cache group to
which the EIS cache partition belongs, including:
- Defining the DCN and Notification listeners on which
SAP Mobile Server communicates with the EIS.
- Managing the Web service endpoint for operation upload
notification. This endpoint is used to notify the EIS that replay
messages are ready for upload, not for pushing replay messages to the
EIS, and is available to map to a server endpoint only if the
Notify EIS to fetch operation option was set
during MBO development.
- Viewing cache group information.
- Setting subscription purge threshold and unsubscribed partition purge
threshold for the “Synchronization Cache Cleanup” scheduled task, which
purges expired entries from the cache.
- The EIS Administrator includes JSON messages within the DCN with payload to
manage the partition, including updating data within the partition and user
subscription.
An example business case that benefits from an EIS managed cache partition is a
daily delivery service:
- Each evening the MBOs are updated by the EIS through DCN with the next day's
deliveries and services to be provided. Several MBOs contain the RouteID
attribute which identifies various aspects of the customer: location, services
or products required, customer notes, and so on.
- MBO information also includes the user (partition) assigned to each route.
- In the morning, each user synchronizes and retrieves their schedules based on
the data to which they subscribe.
- Throughout the day each user enters information on the device regarding each
customer visited.
- At the end of the day, the team member updates the EIS through
SAP Mobile Server and logs out. For example, if the
Notify EIS to fetch operation option was selected for
the EIS managed cache group, operation replay records are sent to
SAP Mobile Server, SAP Mobile Platform Runtime queues
them internally and notifies the EIS through the Web service endpoint for
operation upload notification, and the EIS retrieves them.