Previous topic

Use Service

Next topic

Resource Model Overview

Last updated 13-Feb-2017


In the APS infrastructure, its backend contains the following interacting components and interfaces between them.

  • APS controller (APSC) is the central part that is responsible for the following operations:

    • Control the central storage of all APS resources, types, and packages.

    • Manage the interaction between all other components in the APS infrastructure. This messaging functionality is often referred to as a service bus. Its own base endpoint is https://apsc/aps/2/, where apsc must be changed to the actual domain name of the management node. The short /aps/2/ base URL will be used in almost all examples to represent the APS controller base endpoint.


      When managing APS objects, all communications must go through the APS controller.

  • Each integrated application is represented by its APS application, which contains two active integration components:

    • Similar to APSC, each APS application exposes its base endpoint, e.g. https://endpoint/app1/, and enpoint for each its service, e.g. https://endpoint/app1/service1/, where endpoint must be changed to the actual domain name of the host used to expose application endpoints. The APS application endpoint accepts all REST requests from the APS controller addressed to the application instance, services, and resources.
    • APS application instance is an integration code that can initiate own REST requests addressed to the APS controller endpoint on behalf of the integrated application. Each APS application instance, during its installation, gets a unique certificate and private key generated by the APS controller. When sending a REST request to the APS controller, the APS application instance must confirm its identity by applying its APS certificate to the package.
  • APS user interface represents the one-way communication tool connecting users with other components through the APS controller.