Migrating to the new Web Platform UI

Deploying the new Web Platform UI.

The new ActiveControl Web Platform UI requires a docker image to be hosted by the customer. This is in addition to the existing Domain Controller backend requirement.

The ActiveControl docker image can either be hosted on a standalone Linux Server (e.g. on AWS, Azure etc, cloud or on-premise server) or on SAP Business Technology Platform (BTP). A BTP deployment requires Cloud Foundry (not Neo) based environment.

As customers have different deployment requirements (e.g. some are already using SAP BTP, some are not) and different levels of integration with Fiori Launchpad, the ActiveControl Web Platform can be deployed using various alternative deployment options, as described below.

Table: Deployment Options for the ActiveControl Web Platform.

Basis Technologies’ recommendation to customers would be to deploy ActiveControl Web Platform on SAP BTP where possible, given SAP’s strategic direction as components of SAP’s standard offerings (e.g. SAP CPI) are already running on SAP BTP. In addition, it means that functionality such as Single Sign-On (SSO) and Mobile access will likely already be available within your organisation. For the vast majority of customers, the BTI Dashboard will also suffice. Basis Technologies anticipate only larger enterprise customers wanting to customise via Fiori launchpad.

More information on the deployment options for the ActiveControl Web Platform, as well as links to the deployment steps, can be found in the ActiveControl 9.20 Administration Guide.

Availability of legacy UIs

Basis Technologies will be deprecating the legacy BSP-based Web UI and Windows GUI from ActiveControl 9.20. This means that both of the legacy UIs that existing customers are familiar with will not be available with the AC9.20 release, or thereafter.

Table: Timeline for deprecation of the legacy Windows GUI and BSP-based Web UI.