Search Engine: Elastic

Article ID: 119959, created on Feb 3, 2014, last review on Oct 23, 2015

  • Applies to:
  • Operations Automation
  • APS 2.x


What is this endpoint server? How it should be used? Do all APS2 applications need to package and install provisioning scripts on provider's premises?


Endpoint host may indeed be thought of as an analogue of provisioning gateway host (in a sense that it hosts application backend code and executes it). The main difference between them is that endpoint host is not managed by Odin Automation. Configuring the host is fully up to the provider.

APS application endpoint is management code exposing APS application API in REST format. It must process REST requests received from the APS controller. It interacts with the application through the application native API to process these requests. An application and its APS endpoint can exist (1) as two separate installations, (2) be combined within the provider cloud infrastructure as a single installation or (3) only on application vender cloud.

  1. There is an endpoint on provider's premises that communicates with APS controller, processes the data and prepares requests to be sent to application vendor cloud in the format it understands.

  2. If nothing is stored/created in the cloud all operations can be done on provider's endpoint (example package

  3. APS controller contacts the cloud directly.

There are some difficulties to this scenario:

  • APS controller is not accessible from the Internet due to security reasons so it will be needed to either set up the proxy or create a vpn connection, the procedure should be described in deployment guide.

  • Since there is no intermediate code enpoint in application vendor's cloud has to be able to process REST requests/responses

  • You must support the scenario when providers connecting to your cloud have different versions of your application (schema, navigation, UI), so that the provider with version application-1.1 is able to perform operations specified in his package as well as a provider with application-1.8, application back-end must be backwards compatible.

Read more on endpoint security here.

70bf700e0cdb9d7211df2595ef7276ab 717db81efe94e616312b74fb03a5d474 caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae

Email subscription for changes to this article
Save as PDF