Configure Tomcat to use the isCOBOL EIS framework
$CATALINA_HOME is the Tomcat installation directory. The default location on Windows is:
C:\Program Files\Apache Software Foundation\Tomcat 8.5 |
To configure Tomcat to use the isCOBOL Runtime Framework on Windows you can change the value of the shared.loader property in $CATALINA_HOME/conf/catalina.properties to the following:
shared.loader=/program\ files/veryant/iscobol2021R2/lib/iscobol.jar |
On Unix, set the CLASSPATH in Tomcat's startup environment to include iscobol.jar. For example, on Linux add the following line to /etc/tomcat8/tomcat8.conf or other script called during the Tomcat startup:
CLASSPATH=$ISCOBOL/lib/iscobol.jar:$CLASSPATH; export CLASSPATH |
Make sure that you have a valid license for isCOBOL Evolve in /etc/iscobol.properties (i.e. iscobol.license.<release year>=<license key>) or in the iscobol.properties in the home directory for the user that starts Tomcat.
Disable persistence across restarts
Whenever Apache Tomcat is shut down normally and restarted, or when an application reload is triggered, the standard Manager implementation will attempt to serialize all currently active sessions to a disk file located via the pathname attribute. All such saved sessions will then be deserialized and activated (assuming they have not expired in the mean time) when the application reload is completed. In order to successfully restore the state of session attributes, all such attributes must implement the java.io.Serializable interface. Since not all isCOBOL classes are serializable, we strongly suggest you disable this persistence feature.
To disable this persistence feature, create a Context configuration file for your web application and add the following element there:
Note - The file context.xml in the Tomcat home directory already includes the above entry, but it’s commented. You can easily disable the persistence for all your web applications by removing the comment markers around the entry.
Data access
When relying on file handler that includes native parts (e.g. DCI, c-tree or Vision) we suggest using a File Connector, if available.
However, the c-tree file handler is also certified to work without the need of a File Connector if installed and configured as follows:
• copy iscobol.jar to the webapp’s WEB-INF/lib folder
• copy ctree-rtg.jar to the Tomcat’s lib folder
• set iscobol.file.index=ctreej in the webapp configuration (WEB-INF/classes/iscobol.properties)
• set java.library.path in Tomcat’s configuration to point the folder where the ctree dynamic library is stored (i.e. on Windows use -Djava.library.path=C:\Veryant\isCOBOL_SDK2022R1\bin)
Relative paths
Relative paths used by COBOL programs in EIS environment are relative to the webapp directory except for iscobol.code_prefix paths that are relative to the Tomcat working directory.
Tomcat 10
Applications that run on Tomcat 9 and earlier will not run on Tomcat 10 without changes. Java EE based applications designed for Tomcat 9 and earlier may be placed in the webapps-javaee directory and Tomcat will automatically convert them to Jakarta EE and copy them to the webapps directory.