Table Of Contents

Previous topic

Resource Model

Next topic

APS Resource Management

Integration Model

When integrating a cloud application with the platform, consider the following parts involved in it:

  • Cloud Applications, for example, Office 365 or Backup Agent, provide their native API for resource (service) management and consumption.

  • APS applications are deployed APS packages that integrate OSS with cloud applications.

  • OSS is the core system that provides control panels for managing the integrated applications.

../../../_images/oa-app-integration.png

Note

This model does not include any commercial part that we will add later. Even if this is not the model you need in production, you can still use it to understand deployment and provisioning processes as well as to use a sandbox based on such a model to test your applications.

The integration process for a cloud application consists of the following stages.

  1. Using PCP, the provider staff deploy the application integration package. This stage consists of two steps:

    • Installation of the APS package that integrates the application with OSS through backend and frontend integration components.

      Result: the platform is able to manage the application on backend and the application UI is embedded to CP or UX1.

    • Configuration of a service template presenting a set of application resources the provider can deliver to customers.

      Result: a service template the provider can use to subscribe customers to the application services.

  2. Using PCP, the provider staff subscribe a customer to the service template.

    Result: subscriptions are created for the application resources with limits on resource consumption.

  3. In the user panel, the subscriber (customer) staff configure available services (meaning resources) and initiate the resource provisioning process. Depending on a resource’s nature, it belongs to the whole customer, for example, mail service, or is assigned to a service user, for example, an email account.

    Result: provisioned resources, for example, virtual servers or email accounts are available for their consumers.

  4. Once service users get resources, they can configure them through the user panel and consume the service by direct access to the cloud application.

    Result: finally, users can manage and consume assigned resources.