The framework provides the ability to bring new enterprises on board the existing configuration. It also helps you separate the existing organizations from newer organizations, and reduces the incidence of various organizations interfering with each other.
As part of enterprise onboarding, you can separate configurable resources such as templates, user exits, and so on, based on an enterprise. You can also add new enterprises without impacting the existing enterprise resources. The resources configured at the enterprise level are identified using a unique Resource Identifier, which can be used to locate the resources belonging to the corresponding enterprise.
As part of the enterprise onboarding feature, the provides an enterprise with the capability to inherit the configuration from some other enterprise, for example, enterprise B can choose to inherit the configuration from an existing enterprise A, instead of defining an entirely new set of configurations.
In a multi-enterprise setup, managing various levels of extensions and configurations can be cumbersome. For example, as part of enterprise onboarding, if you want to expose an additional attribute, you must modify the default template to include the additional attribute. This could have an impact on the other on-boarded enterprises. To resolve this complexity, the provides the ability to develop and package enterprise-specific resources such as database extensions, templates, UI resources, and so on as an extensions service package. This package contains all the components to on board an enterprise.
Flexible Sterling Order Management System Software deployment architecture
The flexible order management deployment architecture of Sterling Order Management System Software provides the ability to support multiple enterprises (tenants) on a single deployment of the application and to segregate data and configurations accordingly. This allows you to leverage your investments in application servers and hardware.
A flexible order management deployment consists of multiple enterprises that have unique business needs, such as different process flows, enterprise specific extensions, and rules. Data is partitioned into Transaction and Configuration shards so that each customer works with a customized virtual application instance.