These guidelines direct you through all development steps on your way of creating an integration APS package.


The document contains a bit more details on the development steps outlined in the Integration Workflow as well as provides links to more detailed descriptions.

On completion of the development process, you will have an APS package ready to test the integration of your cloud application with a test platform. Optionally, your can go through the certification process to get your application certified for the platform.


To leverage the effect of this document, Kevin, as the integration developer, should comply with the following prerequisites:



Knowledge and skills in platform resource management, deployment and provisioning of application services.


Knowledge and skills in platform business models and configuration of the platform products for sale.

Depends on the sales model

Solid knowledge and skills in the programming languages used for backend and frontend integration:
* A language to be used in the backend provisioning logic, for example, Java, Python, or PHP
* JavaScript for UI


Integration Points

The platform provides many touchpoints that APS application can use to integrate with the OSS/BSS platform as well as with other applications. Kevin must receive from Roger a list of integration points selected from the full list of integration touchpoints the OSS/BSS platform supports.

The list of integration touchpoints contains links to the documents explaining implementation steps. They direct Kevin through the process of integrating the application with OSS/BSS and other applications. They also refer to demo projects illustrating typical integration cases.

Package Structure

Kevin must develop the APS application in a separate folder, containing the following typical files and folders at the top level as explained in the Package Structure document:

  • APP-META.xml file contains meta description of the application structure and its main components.

  • ui/ folder contains the HTML, JavaScript, and other auxiliary files to be plugged into the platform control panels.

  • scripts/ folder contains the backend scripts implementing the application provisioning logic.

  • schemas/ folder contains the JSON representation of the application APS types.

  • Folders to store images, licenses, localization data, and other.