Watch the following video to learn about the key considerations for the design of the IT landscape for SAP Build Work Zone.
Note
While SAP Build Work Zone is considered as software-as-a-service, it follows the architectural best practices and guidelines for SAP Business Technology Platform, and it’s recommended to have at least 2-tier landscape.
Note
Since SAP Build Work Zone and SAP SuccessFactors Work Zone are both SAP BTP services, they follow all design principles, guidelines, and best practices for SAP BTP. In regards IT landscape, it’s recommended to read Account Models with Subaccounts available on the SAP Help Portal: it explains different design patterns and how subaccounts can be organized.
Digging into the last question. SAP Build Work Zone has two components to support working with business applications and information: Digital Workplace Service (DWS) and launchpad.
DWS provides limited capabilities to transport content:
- Menu content, workpages and workspaces can be manually exported and imported between SAP Build Work Zone tenants.
- Settings in Administration Console should be maintained manually in every SAP Build Work Zone tenant.
- UI Integration Cards and Content Packages must be deployed manually in every SAP Build Work Zone tenant.
The launchpad component provides two options:
- Business apps, groups, catalogs, and roles can be exported and imported manually.
- It is also possible to setup integration with SAP Cloud Transport Management service. In this case, the administrator creates a transport request with scoped content (business apps, groups, catalogs, and roles) and then deploys it using SAP Cloud Transport Management service.