When deploying your application, one consideration is how to deploy the JVM COBOL run-time system required by the JVM COBOL code in your application.
You have two choices, as demonstrated in the diagram below. You can:
- Deploy the run-time system separately, as a shared module or object in your application server.
- Package the run-time system in a deployed archive file, such as an enterprise archive file (.ear) or web archive file (.war).
Both choices have their advantages:
| Deploying as a shared module
|
Deploying as part of an archive file
|
- Uses less memory, because the run-time file (mfcobolrts.jar) is shared by all applications.
- Tracing can be performed centrally.
- For application servers that provide versioning, you can deploy multiple versions of the run-time system.
|
- Administrative rights are not required to configure the application server.
- For application servers that do not provide versioning, you can deploy different applications that use different run-time systems.
- Remote deployment is easier as all required resources are self-contained.
|