System Architecture

Components

Service form

User Web

End users browse and request services in Zervicepoint's User Web (a IIS based website).

Admin Web

Administrators maintain the portal in Zervicepoint's Admin Web (AW).

Client Web Service

Zervicepoint Client Web service (CWS), a Web service that responds to Ajax queries from the devices. CWS executes inventoried PowerShell or .NET data sources and delivers the response from the target systems to the request or approval forms (on the device).

Provisioning System

Zervicepoint Provisioning System, a Windows service that inventories functions from PowerShell and .NET modules installed on the Zervicepoint Provisioning Server so they can be used as Workflow Activities in a Workflow. The service then executes the PowerShell or .NET activities when they are a part of a Workflow. The response from the workflow activity is delivered back to the Workflow and can be used as input to the next steps in the Workflow. The communication between Provisioning System and the Workflow Engine is done through secure web service calls (HTTPS) via the Process System Web.

Provisioning Inventory System

Zervicepoint Provisioning Inventory System, a Windows service that inventories functions from PowerShell or .NET modules installed on the Zervicepoint Provisioning Server so they can be used as data sources in Zervicepoint Forms.

Provisioning Service

Zervicepoint Provisioning System, a Windows Service that executes PowerShell modules when they are a part of a Workflow. The response is delivered back to the Workflow and can be used as input to the next steps in the Workflow.

Workflow Engine

The Workflow Engine in Zervicepoint consists of the Zervicepoint Process System service, Zervicepoint Process System Web and Microsoft Workflow Manager. The workflows that are designed in Zervicepoint Admin Web are compiled to Microsoft Workflow Foundation.

Service Bus

Microsoft Service Bus, Message Queue used by the Workflow Engine.

Database

Microsoft SQL Server, stores information used by Zervicepoint. Data is logically separated between Zervicepoint stores*.
Zervicepoint is multitenant, a Zervicepoint store is the name of a customer instance, each instance has a unique url and set of certificates.