Provisioning Logic

Using the input data, Kevin must develop the executable files that implement the required services. These files must comply with the resource properties, relations, and operations declared in the APS types in the previous step.

Input

• APS resource model

• Information architecture with detailed description of backend provisioning logic

• Declaration of services in metadata

• APS type definition from the previous step

Development Process

Kevin uses his development environment to develop a set of executable files to be deployed as an APS connector (web application) on an endpoint host. The executables must implement all necessary CRUD and custom operations in accordance with the Information architecture and the APS types. For the APS controller, it does not matter which programming language is used to develop the provisioning logic.

For example, if PHP is chosen as the programming language, Kevin can install and use the APS PHP runtime and follow its description and examples to create and compile the APS types (in the previous step) and methods implementing the provisioning logic.

For each particular integration case, follow the Integration Points section.

Outcome

On completion of this step, Kevin must have a folder, typically called scripts/, with all files implementing the provisioning logic.

← APS Types

Presentation Logic →