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
Application Server JCA support for Enterprise Server
Consolidated Trace Facility
Database Access - COBSQL (Pro*COBOL)
Database Access - DB2 ECM
Database Access - OpenESQL
Deployment - running . NET COBOL applications from a network server
XML Extensions

Application Server support for JVM COBOL

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.2.1	1.8	Servlets 2.5
WebSphere 8.5	1.7	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

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	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.

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

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.4	1.8 (Oracle) 1.8 (AdoptOpenJDK)	7	X
Oracle WebLogic 12.2.1	1.8 (Oracle)	7	X
IBM WebSphere 9.0	1.8 (IBM)	7	X
Tomcat 9.0.x*	1.8 (AdoptOpenJDK)
*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).

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

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

Consolidated Trace Facility

The Microsoft .NET Framework 2.0 or later is required for the CTF Viewer. It is available from the Microsoft .NET downloads area.

Note: The setup file installs .NET Framework v4.5.2.

Database Access - COBSQL (Pro*COBOL)

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 Windows	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.

Testing

For this version, COBSQL was tested with Oracle Pro*COBOL version 12.2 and 18c.

Database Access - DB2 ECM

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 Windows	X	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 and 11.1.

Database Access - OpenESQL

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

Availability

Feature/Platform	Native, ADO.NET Managed, and JVM COBOL 32-bit	Native, ADO.NET Managed, and JVM COBOL 64-bit
x86-64 running Windows	X	X

XA Switch Module

When the Enterprise Server feature is enabled, the ODBC One-phase Commit, SQL Server, and PostgreSQL switch modules are provided and available on the same platforms as are indicated in the Availability section above.

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

.NET COBOL

OpenESQL supports access to relational databases using compliant .NET framework drivers
OpenESQL has been tested against the following ADO.NET data providers:
- Microsoft provider for SQL Server
- Microsoft provider for Oracle
- IBM DB2
- Oracle Data Provider for .NET (ODP.NET) - fully managed and unmanaged providers
- OleDb
- Managed ODBC .NET providers
- Npgsql 3.2.2 for EDB PostgreSQL

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	db2jcc4.jar (and db2jcc_license_cu.jar)
Oracle 12.2	ojdbc7.zip¹
Microsoft SQL Server 2012 Microsoft SQL Server 2014 Microsoft SQL Server 2016 Microsoft SQL Server 2017	sqljdbc4.jar²
EDB PostgreSQL 10.5	postgresql-42.0.0.jre7.jar
¹Some Oracle JDBC drivers are distributed as .zip rather than .jar files. ² On Windows platforms, if you are not using Windows authentication, no additional resources are required. However, if you are using Kerberos authentication with a driver version of 4.0 or later, although integrated authentication is not required, you might need to follow additional configuration steps as described in the driver documentation. No additional resources are required for UNIX platforms.

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:

Oracle 12.2 and 18c
DB2 LUW 10.5 and 11.1
SQL Server 2012, 2014, 2016, and 2017
EDB PostgreSQL 10.5
MySQL 5.7 (5.3 ODBC drivers only)

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

Support for the following is planned for future release:

Azure SQL Database (Managed Instance)
Azure SQL Database (Logical server)
Amazon Aurora PostgreSQL-Compatible Edition

Deployment - running . NET COBOL applications from a network server

For .NET COBOL applications that you run from a network server, the server must have the Microsoft .NET Framework version 4.5.2 or later and the Microsoft Visual C++ 2017 Redistributable Runtime installed.

XML Extensions

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.