Experience Agent for Developers

Not only is the Atlas Experience Agent an automated application runner, it is also a development platform that your application may build upon.

This document provides n overview of the development resources available with links to implementation resources.

Resources

• Application Environment
• Cloud Connect
• Content Management System (CMS) Proxy API’s
• Node API
• Image API

Application Environment

When your application is launched via the Experience Agent, a numebr of environment variables are provided that enable your application to access the Local Experience Agent API's and Remote Experience Manager API's.

Application Environment =>

Cloud Connect

Cloud Connect is an MQTT based distributed messaging system providing real-time control of the Experience Agent. It may also be used by developers to implement custom messaging protocols so that their applications may commnucate on-premesis or in the Cloud

Cloud Connect =>

Content Management System (CMS) Proxy API’s

The CMS Proxy API's provide limited access to a cached local copy of the Experience Manager CMS' Records and Assets. The CMS Proxy API may be relied on as a RESTful cache for your application alleviating the need for the application to implement caching.

CMS Proxy API’s =>

Node API

The Node API provides resources to applications running on Nodes, including an API token endpoint to access the Experience Manager and a limited environment variable endpoint for applications that cannot access the environment.

Node API =>

Image API

The Image API provides on the fly media processing, allowing for format conversion, cropping and resizing of Images provided by the CMS.

Image API =>