You can select any deployed module to start automatically when the server starts. If you choose to start an application, all of its EJBs and Web modules are also started, even if they are not explicitly listed.
Table 3-5 describes the system modules that are deployed in a standard EAServer installation. By default, they all start automatically.
Module |
Description |
|---|---|
application-console |
Provides the Management Console user interface |
ejbjar-management |
Provides systems management functionality |
webapp-sybasewst |
Implements the Web Services Toolkit |
webapp-wfs |
Provides FTP service |
webapp-wlb |
Provides HTTP redirects to achieve load balancing for other Web applications |
webapp-wsh |
Enables running shell commands on remote servers |
To specify which system modules to start, under System Start Modules, choose Select, then select or unselect each module. To start all the modules, select All. You can also select None.
You can exclude system modules from starting by selecting All or Select under System Exclude Modules. For example, to start all but one of the modules:
Under System Start Modules, select All.
Under System Exclude Modules, choose Select, then select the module that you do not want to start.
The next time the server starts, all the modules are started except the one selected under System Exclude Modules.
The configuration properties systemStartModules and systemExcludeModules define the system modules to start or exclude, as comma-separated lists.
If you deploy a new module, it displays under User Start Modules and User Exclude Modules. You can select user modules to start automatically, the same as you do for system modules. The configuration properties that define which user modules to start or exclude are startModules and excludeModules.
