Documentation

This section briefly illustrates the basic elements of THRON ecosystem, so that developers and integrators can quickly identify information they need in order to build custom projects or simply learn about THRON architecture.

For any further in-depth analyisis of THRON ecosystem and APIs, please refer to our thecnical documentation which includes manuals and libraries available for download. THRON will provide support and backward compatibility only for documented services. Any undocumented service may change and is not supported; therefore THRON strongly advises you against using them.

Platform Components

THRON platform is made of several main components interacting with each other.

xsso is the Single Sign-On component of the entire platform. It provides a set of interfaces authentication via web services and methods forretrieving of user-defined configuration settings.

xcontent is the component for content-related information management: content metadata, comments, tags, content proprieties, ratings, visualizations and relations with other contents. For example it provides a set of web services to manage contents within folders, to moderate comments added by other users or to update content's description in different languages.

xpackager is the component for managing user's working area (i.e., the area where contents are stored before publication) and content's packaging and transcoding process. Moreover, this component provides a set of services to manage content preview before their publication over CDN.

xadmin is the component that allows content publication process management, thanks to its interaction with xpackager and xcontents. Moreover, it provides a set of services for user roles and playlist management.

xintelligence is the component that allows content intelligence tools management, allowing the user to define new classifications and tags and to link them to entities (contacts and contents).

xdevice is the component that allows you to hook devices used for accessing your contents, and to link them to your contacts.

xcontact is the component used for managing your contact list.

xreccomendation is the component used to manage content reccomendation.

Classes

THRON platform provides a complete API system for developers, including: identity and content provisioning, content management and publishing. These APIs are implemented as classes that allow communication with all previously described components.

Classes can be either "models" or "services". Models describe how the information is represented into THRON platform. Services declare which models and interfaces must be used to exchange information between client and server entities.

We adopt the following formalism:

• service classes have the "J" character as prefix (J<service name>);
• all the elements with "M" prefix refer to model classes used by any web service as either message request or response to given messages (M<class name>).

The xml or json structure for request /response messages fully reflects the structure of the model classes hereby defined.

Download Manuals

In this section you can download THRON manuals in PDF format.

Component manuals are organized into packages, according to a persistence criteria: all the service models representing transient information are grouped into SERVICES package; on the other hand, business object models representing persistent information are collected into MODEL package. In turn, SERVICES package has two sub-packages: REST and MODEL. The first one contains the list of web services, while the other details the models to use for representing the corresponding transient information.

Given a specific task to implement (in terms of interaction with THRON platform), the following steps allow to identify the right web service into manuals:

1. Identify the proper component for the action you need to perform;
2. Find the right package according to previous description;
3. Find the right service among REST sub-package implementing the method you need in order to perform your specific task (e.g., content upload or content research);
4. For the given service, identify possible constraints or specific usage;
5. Check the right parameters and models to fill the body of your request.

For a better understanding of this process, we invite you to test our interactive APIs and learn how to use web services.