Additional Software Requirements

To ensure full functionality for some COBOL Server features, you might be required to obtain and install additional third-party software in addition to the prerequisite software installed automatically by the COBOL Server setup file. The following information specifies the third-party software required for each feature.

Application Server support for JVM COBOL

Back to Top

The following application servers are supported using the following JDKs:

Application Servers JDK version Containers support version
Tomcat 7.0.x 1.7 Servlets 2.5
JBoss EAP 6.4 1.7, 1.8 Servlets 2.5
WebLogic 12.1.1 1.7 Servlets 2.5
WebLogic 12.1.1 on AIX 6.1 1.7 Release 1 Servlets 2.5
WebLogic 12.2.1 1.8 Servlets 2.5
WebSphere 8.5 1.7 Servlets 2.5
WebSphere 8.5 on AIX 6.1 1.7 Release 1 Servlets 2.5
WebSphere 9.0 1.8 Servlets 2.5

Please consult your Application Server documentation to determine which JDK you should use. The JDK is used to:

  • Start the Application Server
  • Compile EJBs and Servlets generated by the Interface Mapping Toolkit or the imtkmake command

After installing the JDK, you need to set up your Java environment.

Support for the following Java application servers using the following JDKs is planned for future release:

Application Servers JDK (vendor) Java EE COBOL RA
JBoss EAP 7.0 (AS 7.5) 1.8 (Oracle), 1.8 (OpenJDK) 7 X
IBM WebSphere 8.5.5

(all platforms)

1.7, 1.8 (IBM) 6 X
Tomcat 8.5.x* 1.7, 1.8 (Oracle), 1.8 (OpenJDK)
*Apache Tomcat is an HTTP server and servlet container supporting Java Servlet and JavaServer Pages (JSP). Micro Focus Tomcat non-transactional support includes servlet generation with J2SE Beans; no transactional support is provided. Tomcat does not support the use of Enterprise Java Beans (EJBs) or resource adapters (RAs).
Note: If you experience any incompatibility issues when using these third-party products with COBOL Server, please report them to SupportLine. Until full support is available, a timely effort to resolve incompatibility issues will be made; however, Micro Focus does not guarantee full compatibility until we have fully tested our software updates against these products.
Note:
  • On AIX and zLinux, you need to have IBM's JDK. The earliest supported release of IBM's JDK 1.7 is 7.0 Service Refresh 8. If you install IBM's JDK 8, on AIX you must install its latest fix - JDK 8 SR5 FP16. You can get IBM's AIX JDK from IBM's Web site.
  • On HP-UX, you need to have HP-UX JDK. The earliest supported release of HP-UX JDL 1.7 is Java 7.0.11. You can get the HP-UX Java JDK from HP's Web site.
  • On Solaris platforms (both SPARC and Intel) only the 64-bit version of Java 8 is supported.
  • On all other platforms, you need Oracle's JDK. The earliest supported release of Oracle's JDK 1.7 is 1.7.027. You can download Oracle's JDK from Oracle's Web site.

Application Server JCA support for Enterprise Server

Back to Top

Restriction: This feature applies only when the Enterprise Server feature is enabled.

Java EE 7, including support for EJB 3.2 and Java Connector Architecture 1.7, is supported for the deployment of EJBs.

The following Java application servers are supported using the following JDKs:

Application Servers JDK (vendor) Java EE COBOL RA
JBoss EAP 7.1.x (where x>=4 for JCA), and 7.2x 1.8 (Oracle)

1.8 (AdoptOpenJDK)1

7 X
Oracle WebLogic 12.2.1 1.8 (Oracle) 7 X
IBM WebSphere 9.0 and Liberty 19.0.0.x (where x>=12 for JVM COBOL) 1.8 (IBM) 7 X
Tomcat 9.0.x2 1.8 (AdoptOpenJDK)
1JBoss EAP 7.1.4 and later restricts support of AdoptOpenJDK to Red Hat Enterprise Linux platforms. For more information, see the Red Hat Web site for supported configurations.

2Apache Tomcat is an HTTP server and servlet container supporting Java Servlet and JavaServer Pages (JSP). Micro Focus Tomcat non-transactional support includes servlet generation with J2SE Beans; no transactional support is provided. Tomcat does not support the use of Enterprise Java Beans (EJBs) or resource adapters (RAs).

Please consult your Application Server documentation to determine which JDK you should use. The JDK is used to:

  • Start the Application Server
  • Compile EJBs and Servlets generated by the Interface Mapping Toolkit or the imtkmake command

After installing the JDK, you need to set up your Java environment.

The availability of COBOL resource adapters and ECI support for these Application Servers differs between UNIX platforms. The following table indicates where support is available for each platform:

Feature/Platform JBoss EAP 7.1.4 JBoss EAP 7.2 WebSphere 9.0 WebSphere Liberty 19 WebLogic 12.2.1 Tomcat 9.0.x1
AIX 7.1 on RS6000 64-bit 64-bit 64-bit 64-bit 64-bit
HP/UX 11.31 on Intel IA64 64-bit 64-bit 64-bit 64-bit
Red Hat EL 6.2 on IBM390 64-bit 64-bit 64-bit 64-bit 64-bit
Red Hat EL 6.1 on x86-64 64-bit 64-bit 64-bit 64-bit 64-bit 64-bit
Solaris 11.3 on AMD Opteron 64-bit 64-bit 64-bit
Solaris 11.3 on SPARC 64-bit 64-bit 64-bit 64-bit
SUSE SLES 12 SP2 on IBM390 64-bit2 64-bit 64-bit 64-bit 64-bit
SUSE SLES 12 SP2 on AMD x86-64 64-bit2 64-bit 64-bit 64-bit 64-bit
SUSE SLES12 on PowerLinux LE 64-bit
1Apache Tomcat is an HTTP server and servlet container supporting Java Servlet and JavaServer Pages (JSP). Micro Focus Tomcat non-transactional support includes servlet generation with J2SE Beans; no transactional support is provided. Tomcat does not support the use of Enterprise Java Beans (EJBs) or resource adapters (RAs).

2JBoss EAP 7.1.4 and JBoss EAP 7.2 not listed as tested by RedHat on this platform.

Browser

Back to Top

Browser versions which can be used for embedded browser support (such as SWT) and their corresponding Eclipse versions are listed here.
Note: Eclipse 4.5 and newer support Mozilla 1.4 GTK2 - 1.7.x GTK2, XULRunner 1.8.x - 1.9.x, 3.6.x, 10.x, 24.x and 31.x (but not 2.x nor other unlisted versions), WebKitGTK+ 1.2.x and newer (Eclipse 4.5 support for XULRunner 31.x is not available on Linux due to Bug 467646.). For Eclipse 4.6 you must install a 64-bit browser version.

Database Access - COBSQL (Pro*COBOL)

Back to Top

Before deploying a COBSQL application, be sure to install and configure all applicable third-party software.

Note: COBSQL (Pro*COBOL) is supported for native COBOL only.
Availability
Feature/Platform 32-bit 64-bit
x86-64 running Red Hat Linux X X
x86-64 running SUSE Linux X X
IBM System p running AIX X X
IBM System z running Red Hat Linux X X
IBM System z running SUSE Linux X X
Itanium running HP-UX X X
x86-64 running Solaris X X
SPARC running Solaris X X
XA Switch Module
When the Enterprise Server feature is enabled, the Oracle XA switch module is provided for COBSQL (Pro*COBOL), and is available on the same platforms as are indicated in the Availability section above.
Executing
On HP-UX, to execute an application precompiled using Pro*COBOL (or COBSQL) after you have created a callable shared object of Oracle DBMS routines, you need set an environment variable, LD_PRELOAD, to point to the Oracle client callable shared object, for example:
LD_PRELOAD=$ORACLE_HOME/lib/libclntsh.so       
export LD_PRELOAD

A script is available that creates an executable run-time system or a callable shared object containing Oracle support. You can find the script in the Micro Focus Knowledge Base article titled Building and executing Pro*COBOL applications on UNIX.

Testing
For this version, COBSQL was tested with Oracle 18c and 19c.

Database Access - DB2 ECM

Back to Top

Before deploying a DB2 ECM application, be sure to install and configure all applicable third-party software.

Note: DB2 ECM is supported for native COBOL only.
Availability
Feature/Platform 32-bit 64-bit
x86-64 running Red Hat Linux X X
x86-64 running SUSE Linux X X
IBM System p running AIX X X
IBM System z running Red Hat Linux X X
IBM System z running SUSE Linux X X
Itanium running HP-UX X
x86-64 running Solaris
SPARC running Solaris X X
PowerLinux LE running Red Hat Linux X
PowerLinux LE running SUSE Linux X
XA Switch Module
When the Enterprise Server feature is enabled, the DB2 XA switch module is provided and is available on the same platforms as are indicated in the Availability section above.
Testing
For this version, DB2 ECM was tested with DB2 LUW 10.5, 11.1, and 11.5.

Database Access - OpenESQL

Back to Top

Before deploying an OpenESQL application, be sure to install and configure all applicable third-party software.

Availability
Feature/Platform Native and JVM COBOL 32-bit Native and JVM COBOL 64-bit
x86-64 running Red Hat Linux X X
x86-64 running SUSE Linux X X
x86-64 running Solaris X X
IBM System p running AIX X X
IBM System z running Red Hat Linux X X
IBM System z running SUSE Linux X X
Itanium running HP-UX X X
SPARC running Solaris X X
PowerLinux LE running SUSE Linux X
PowerLinux LE running Red Hat Linux X
XA Switch Module
When the Enterprise Server feature is enabled, the ODBC One-phase Commit switch module is provided and is available on the same platforms as are indicated in the Availability section above.

The PostgreSQL switch module (early adopter program) is available on the following platforms:

  • x86-64 running Red Hat Linux
  • x86-64 running SUSE Linux
Native COBOL
  • OpenESQL supports access to relational databases using ODBC 3.0-compliant drivers
  • Refer to your driver vendor's documentation to determine whether your driver is suitable for use with OpenESQL
JVM COBOL
OpenESQL supports access to relational databases using JDBC 4.0-compliant JDBC drivers. The following table shows the tested DBMSs and their corresponding JDBC driver filenames:
Tested DBMS Versions JDBC 4.0 Compliant Drivers
DB2 LUW 10.5

DB2 LUW 11.1

DB2 LUW 11.5

db2jcc4.jar (and db2jcc_license_cu.jar)
Oracle 18c and 19c ojdbc7.zip*
Microsoft SQL Server 2014

Microsoft SQL Server 2016

Microsoft SQL Server 2017

Microsoft SQL Server 2019

sqljdbc4.jar
EDB PostgreSQL 10.5 and 11.x postgresql-42.0.0.jre7.jar
*Some Oracle JDBC drivers are distributed as .zip rather than .jar files.

To use JDBC DataSource Objects, you must also install and configure a JNDI server.

  • If you are using a Java application server, it includes a JNDI server you can use to configure DataSource objects. This process is described in the Java documentation for the application server.
  • If you are not using a Java application server, or if you require a standalone JNDI server to configure DataSource objects for initial evaluation and development, see the To install and configure Simple-JNDI topic in this documentation set for instructions on downloading, installing, and configuring the open source JNDI server Simple-JNDI for this purpose.
Testing
For this version, OpenESQL was tested with the following:
  • Oracle 18c and 19c
  • DB2 LUW 10.5, 11.1, and 11.5
  • SQL Server 2017 and 2019
  • PowerLinux LE using DB2 LUW 10.5 only
  • EDB PostgreSQL 10.5 and MySQL 5.7 (5.3 ODBC drivers only) on the following platforms:
    • x86-64 running Red Hat Linux
    • x86-64 running SUSE Linux
Note: Micro Focus provides compatibility for PostgreSQL and MySQL but does not directly contribute to or support either open source project. Any issues relating to the functionality of either DBMS should be addressed through an open source support vendor.
Planned
Amazon Aurora PostgreSQL-Compatible Edition running on the following platforms:
  • x86-64 running Red Hat
  • x86-64 running SUSE Linux

Java Development Kit (JDK)

Back to Top

For COBOL JVM code and Java Interoperability, Java 8 (32 or 64-bit versions), and Java 11 (64-bit version only) are supported. Alternatively, you can download AdoptOpenJDK's OpenJDK 8 with Hotspot from AdoptOpenJDK's Web site and unpack the archive anywhere on your machine.
Note: Eclipse does not run using Java 11.

XML Extensions

Back to Top

  • XML Extensions has the same requirements as Visual COBOL. Both 32-bit and 64-bit versions are available. See the XML Extensions for Visual COBOL, available from the Visual COBOL product documentation section of the Micro Focus SupportLine Web site for more details.