Multiple-Instance Deployment

In a multiple instance deployment, you can have two or more instances of databases, application servers, and EARs installed. If database size limitations were an issue in a single-instance deployment, you can keep adding instances in a multiple-instance deployment as the number of your enterprises grows.

A multiple instance deployment can also consist of separate enterprises or groups of enterprises, each with its own context root or EAR, as described in **** MISSING FILE ****.

The following illustration shows an example of a multiple-instance deployment:

Following are the advantages and limitations of this multiple-instance deployment.

Advantages

Limitations

Many multiple-instance deployments enjoy the advantages listed above and are unaffected by the limitations, because they have no need to share data between instances or maintain a central point of control. They benefit from being able to add databases as their enterprises grow.

However, if hardware resource or memory constraints require that you run separate enterprise deployments within each node on the application server, you can achieve this with a multiple context-root deployment.