Single-Instance Single-Schema Deployment

Sterling Warehouse Management System offers multi-tenancy support for single-instance deployments that contain:

In this configuration, all extensions can be defined by enterprise. These include code extensions, user exit implementations, events, templates, menus, and extensions to the user interface. Each enterprise can have its own sourcing rules, pipelines, tasks, and so on. In addition, this type of deployment offers isolation of configuration; that is, if one enterprise's configuration changes, the others are not affected. In a single instance, all the data is centrally located, so you can upgrade the entire instance together and consolidate database maintenance tasks.

The following illustration shows an example of single-instance, single-schema deployment:

As this illustration shows, in a single-instance deployment, Configuration and Transaction data reside within the same schema. This schema is shared by three enterprises: E1, E2, and E3. It has a cluster of nodes in an application server and one EAR.

Following are the advantages and limitations of this single-schema deployment.

Advantages

Limitations