Unlike previous versions of ActiveControl, the new SAP-UI5 based ActiveControl has a web front-end which requires a docker image to be hosted by the customer. This is in addition to the existing Domain Controller backend requirement.
Figure: ActiveControl Docker Image.
The ActiveControl docker image can either be hosted on a standalone Linux server (eg on AWS, Azure, on-premise server) or to SAP Business Technology Platform (BTP). A BTP deployment requires Cloud Foundry (not Neo) based environment.
As our customers have different deployment requirements (eg 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.
| SAP BTP | Standalone Server | |
|---|---|---|
| BTI Dashboard | Possible | Possible |
| Fiori Launchpad | Possible | Not available in AC9.10 |
Table: Deployment Options for the ActiveControl Web Platform.
Each of the Web Platform deployment options, as well as other information and considerations are described in later Installing ActiveControl section of this Administration Guide.
The Basis Technologies recommendation to our customers would be to deploy the ActiveControl Web Platform on SAP BTP where possible, given this is SAP’s strategic direction, and other parts of SAP are already becoming well-established there. Additionally, using SAP BTP means that capabilities such as SSO and Mobile access will likely also already be available.
For the vast majority of customers, Basis Technologies believe that the out-of-the-box BTI Dashboard will also suffice. We anticipate that only a few of our very largest enterprise customers would want/need to customise the layout enough to warrant via Fiori launchpad.
Post your comment on this topic.