JVM applications are a collection of classes (.class files), which are usually stored within
.jar files.
When deploying a JVM application, it must be accompanied by one or more Micro Focus
.jar files. Each JVM application must be deployed with
mfcobolrts.jar, the
Micro Focus COBOL managed run-time, and then depending on the content of your COBOL, you may also need to deploy one or more of the following:
- mfidmr.jar if the application uses JSON PARSE syntax.
- mfsqljvm.jar if the application uses SQL syntax.
- mfle3790.jar if the application uses any LE Callable Services APIs.
Further requirements depend on the environment in which the application is being deployed.
- JVM COBOL applications that do not use an application server
- Compile your JVM COBOL application to
.class files. Optionally, package these as a
.jar file (using the
jar command). Deploy all required files alongside
COBOL Server (requires a license).
- JVM COBOL applications that run on an application server
- You can deploy JVM COBOL applications to an application server such as JBoss, WebSphere or Tomcat.
The applications could include only JVM COBOL code or could be a mixture of JVM COBOL and Java Code. They could use EJBs,
or use Web services such as managed REST or WSDL.
In order to deploy, you need to:
- Package the application as either a
.jar,
.ear, or a
.war file.
- Deploy the file to the application server according to the server's requirements.
- Deploy the other required files mentioned in the section above. You can do this either separately or include them in the application's
.ear or
.war file. See
Java Calling JVM COBOL.
You do not need to deploy
COBOL Server in this scenario.