Getting Started with WebSphere Application Server

176 Getting Started with WebSphere Application Server Community Edition
Note:
For more information about the deploy command, refer to the product documentation at
http://publib.boulder.ibm.com/wasce/V2.1.1/en/deploy.html.
9.8 Configuring multiple server instances
The Community Edition server provides the capability of running multiple server instances
on one server installation. The advantage of having multiple server instances is that you
can better use the computing capability of your system. These instances share the
following directories under :
• bin
• lib
• schema
• repository
Each Community Edition instance has its own var and deploy directories, so you have
to create var and deploy directories for each non-default instance. To avoid port conflict,
you can override the portOffset attribute in configsubstitutions.properties.
Note:
For more information about the steps to create and run multiple server instances, see the
product documentation:
http://publib.boulder.ibm.com/wasce/V2.1.1/en/configuring-multiple-server-instances.html
9.9 Configuring multiple repositories
You can deploy a single repository on a single server instance, or deploy multiple
repositories on multiple instances. You can also share a repository among multiple server
instances, or deploy multiple repositories on a single server instance.
The advantage of having multiple repositories is that you can deploy your applications or
plugins to different repositories. Therefore, you can replace, migrate or remove applications
or plugins without affecting unrelated repositories, especially the Community Edition default
repository.
Note:
For more information about creating multiple repositories on a single server instance, and
creating multiple repositories on multiple server instances, see the product
documentation: