Multiple Context-Root Deployment

In a multiple context-root deployment, each node on the application server can have separate data for each enterprise or groups of enterprises. As the following illustration shows, this separation of enterprises means that there is a EAR for each enterprise (or for a group of enterprises) as well as a customer-specified URL that points to enterprise-specific login screens.

In this scenario, each enterprise has its own context root, or EAR. Enterprise A's data resides in E1, while Enterprise B's data resides in E2. Each enterprise can upgrade independently and can completely separate data from each other because the databases connect only to their respective EARs.

Following are the advantages and limitations of this multiple context-root deployment:

Advantages

Limitations

In this deployment, you cannot leverage the same Configuration data across the deployment while still keeping Transaction data separate among enterprises. These kinds of benefits are available in a multischema deployment.