Changes

UBIK Push Web Service

54 bytes added, 16:44, 12 March 2015
A normal data web service (Content Service) delivers data when it is asked for it (for example by calling GetNextContentLevel). In contrast the '''Push Service''' is responsible for '''pushing''' data to every client.
The Push Service push service acts as a central data hub and has a set of methods to get the update information, containing the data that must be pushed to the client defined by its [[#Push Criteria|criteria]], by the sequence and by the last known status.
The Push Service push service is aware of known devices and users and delivers the situation relevant update information. The service is capable of persisting the update data in the {{UBIK}} system as the Push Service push service must deliver the correct data for every client.
== Push Triggers ==
The Push Service service supports following update triggers:
* Force update of single Content
* Force update of children of Content
== Push Criteria ==
The Push Service service supports following criteria:
* Sequential
* Device dependent
== Configuration ==
=== Service ===
The {{UBIK}} Push Service is available since Version 2.3.1. As the Push Service uses the same configuration as the {{UBIK}} Content service it is recommended to configure the Push Service push service in the same folder as ''UBIKContent.svc''.
The File ''UBIKPush.svc'' contains the basic definition of the service:
=== Endpoint ===
The Endpoint of the Push Service push service must be configured in the ''service'' section of the ''Web.Config'' file:
<source lang="xml">
<configuration>
== Web Service Interface ==
In this section you can find some of the The most important Web Service web service members. You can find are listed here, where more detailed detailed information about the and a comprehensive list of all the members and about the data types are located in the {{UBIK Class }} class documentation.  The WebService provides a method to add content to be pushed to the clients:
=== AddUpdateInformation ===
The web service provides a method to add content to be pushed to the clients:
<source lang="csharp">
/// <summary>
</source >
=== DebugInfo ===The Push Web Service push web service provides access to its current status via a debug - info method. You can use Use this to get info retrieve information about the current status of the Web Serviceweb service.This method can also be executed called via a Webbrowswer as well:web browswer by browsing the according URL.
<source lang="csharp">
/// <summary>
</source>
=== Reset ===There is a possibility to To trigger a reinitialization (reset) of the Push Web Service push web service from outside. This extern, call this method can be executed via a Webbrowswer as wellweb browser
<source lang="csharp">
/// <summary>
== Future Prospective ==
Up to now (Version 2.3.1) Currently there is no UI implementation for the Push Web Servicepush web service. To guarantee an optimal integration of the Push Service push service to the {{UBIK }} Kernel a socket implementation of the Push Service push service is provided via the Environmentenvironment. This socket class uses the web service methods to add data to the PushServicepush service. The Configura-tion configuration of the WebService web service must be done as it is done for the [[HowTo:Configure_LAS|LAS/GAS]].An instance of this Socket socket class is provided via the Ubik Environment{{UBIK}} environment.
[[Category:Publishing]]
[[Category:Web Service]]
{{Version|2.3.1}}
10,686
edits