Modes of Deployment
NetKernel may be deployed in a number of different
configurations.
Standalone mode is preferred as it provides all of
the NetKernel benefits and capabilities.
However, another mode may provide critical integration
or architectural benefits.
The options are listed here with their benefits and downsides
to help you
determine the best mode for your situation.
| mode |
benefits |
downsides |
|
Standalone
|
- run services on any available transports
- hot and cold restart available
- no additional infrastructure needed
|
|
|
Servlet
|
- seamless integration with existing J2EE infrastructure
|
- Requires additional resources and infrastructure
- Restart and dynamic deployment functionality not available
|
|
CommandLine
|
- easily invoked from shell scripts
|
- high startup and shutdown costs
|
|
Co-Processor
|
- utilise NetKernel technologies from existing applications
|
- NetKernel's classloader modularisation requires existing applications
to use an alternate classloader to gain access to NetKernel data types.
|
Preface
Configuration
Deployment
