Get familiar with the typical project steps before integrating cloud services with the platform. We will first look over the typical project arrangement and then dive deeper into the design, development, and testing with debugging phases.
In this document:
The integration process directs the ISV staff through all Integration Procedures. The process proposes collaboration of different SI or ISV roles on different integration phases. That is why we start with a definition of roles that can be involved into the integration process. We do not consider it as a full list; you can extend it with other roles.
Will |
Description |
---|---|
Will, as a product manager, is interested in creating a successful sales model for an application. The guidelines must help him understand the business models (including sales models) provided by the platform, identify the sales model for his application, then create the resource model, define integration touchpoints for users, and finally formulate project design requirements for the solution architect. |
Roger |
Description |
---|---|
Roger, as a solution architect, should analyze the project requirements and specify project details sufficient to start developing metadata and executables of the integration package. The guidelines must help him understand resource management in the platform, identify the detailed resource model for his application, define integration endpoint API, map integration touchpoints to user scenarios, identify UI views, and create wireframes. At the end of this process, Alex must formulate development requirements for the developer of the integration package. |
Kevin |
Description |
---|---|
Kevin, as a developer, must develop the integration package in compliance with the development requirements he receives from the program manager. After he completes the package development, he deploys the integrated application on the hosting system, delivers application services to a test customer, and verifies typical management operations with the application resources. He must be able to effectively use the platform and APS tools that help develop, test, and debug integration packages. |
Optimally, you should meet the following prerequisites:
Prerequisite |
Questions for self-evaluation |
Explanation |
---|---|---|
Your team is going to integrate an existing cloud application with an available native API that can provide services to customers through the Internet. |
Which way will your application grant permission to a hosting OSS system to manage application resources remotely? |
The answer depends on the native application interface. Also take into account the platform infrastructure your application will integrate with. |
Your staff has sufficient knowledge and skills in the platform to deploy, sell, provision, and manage application services. |
* Which OSS/BSS features can leverage the benefits of your application services?
* Explain resources, service templates, and subscriptions as components involved in
service provisioning.
* Draw the simplest APS resource model.
* Which component of the hosting platform lets you present application services as a product for sale?
* Which sales models can you use to sell your application services?
|
|
You have the necessary APS development tools and sandbox with an OSS or an OSS and BSS platform to test your solutions. |
Which APS development tools do you use in your local development environment? |
Make sure you gain knowledge and skills in the following integration components and processes. This will help you feel more confident when you start designing and developing your integration project.
Knowledge and skills |
Questions for self-evaluation |
Document |
---|---|---|
Backend API |
* How is a request from the UI routed to the application?
* What is an APS application?
* Why do you need an APS application connector and an APS application instance?
|
|
Resource model and APS package |
* Explain CRUD operations.
* Explain the APS package structure.
|
|
APS type structure |
Explain properties, relations, and operations declared in APS types. |
|
Metadata structure |
* How do you declare a navigation tree?
* How do you declare application services?
|
|
Markup types and APS versions |
Which control panel can use markup 2? |
|
Navigation elements |
* Which elements can a navigation tree contain?
* Which navigation element displays the UI on a screen?
* How do you embed a navigation tree into a control panel?
|
|
Typical structure of a view source file |
* What is the difference between the typical view structure in a CP compared with UX1?
* Why do you need the model and store controls?
|