Platform services

Platform services are those services that are deployed into a single Kubernetes namespace and are used by Activiti Enterprise to manage applications and services across the entire deployment, irrespective of how many individual applications are deployed.

Modeling service

The modeling service contains the backend functionality required for the Alfresco Modeling Application to run. It requires an instance of Postgres deployed with it for storing project and model definitions that the deployment service uses to deploy projects. This instance of Postgres is deployed at a platform level and is independent of the one used by the application services. It is also independent of the Postgres instance used by the deployment service.

The modeling service also contains simulation services so that decision table and script functionality can be tested during the modeling experience.

The REST APIs that the modeling service exposes deal with projects, models and releases.

The following is a high level diagram of the modeling service:

Modeling service diagram

Deployment service

The deployment service is used to create deployment descriptors and to deploy released projects.

  • Using the deployment service to create a deployment descriptor uses the API to create a descriptor for a released project that can be download as a Helm chart and then subsequently deployed via Helm. A deployment descriptor can also still be deployed into the Activiti Enterprise cluster.

  • Using the deployment service to deploy a released project creates a deployment descriptor but also deploys the application into the Activiti Enterprise cluster in its own namespace.

The following diagram shows the steps that the deployment service takes to create a deployment descriptor and deploy a released project:

Deployment service diagram

Once a payload has been submitted to the deployment service through the API or using the Administrator Application a sequence of events happen:

  • The first thing is validation to ensure the payload contains no errors and that there are no conflicts with any other application names already deployed into the cluster.

  • Once validation has passed a series of data enrichment is applied to the payload specifying default values.

  • After data enrichment is complete the payload is saved to the deployment service database as a descriptor. By default this is a PostgreSQL database instance called aps2-postgresql-ads.

  • Base images already exist in the Docker registry for the all application services and are re-used at deployment time. For the runtime bundle, form service and DMN service, a base image is used that references a persistent volume that contains the static project definition files. The persistent volume is created and mounted in the new namespace

        **Note**: At this point a deployment descriptor can be downloaded.
  • The final stage to deploy uses the Kubernetes API to deploy the images into their own namespace. This also includes a persistent volume that is mounted in the new namespace.

        **Note**: It is still possible to deploy a deployment descriptor using the deployment service as well as download it and deploy it manually via Helm. 

Alfresco Content Services

An instance of Alfresco Content Services (ACS) is deployed as part of Alfresco Activiti Enterprise to store information about in progress tasks and processes in a content repository. ACS is not required to use Activiti Enterprise and the data for tasks and processes is still stored in databases.

Identity Service

Alfresco Activiti Enterprise uses the Identity Service for authentication and user and role management throughout the product. Authentication can be configured to external identity provider instances such as LDAP and SAML.

The Alfresco Administrator Application allows administrators to manage common user-related functions without needing to access the Identity Service.

© 2023 Alfresco Software, Inc. All Rights Reserved.