Additional Software Requirements on Windows

To ensure full functionality for some Enterprise Developer features, you might be required to obtain and install additional third-party software in addition to the prerequisite software installed automatically by the Enterprise Developer 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.39 1.7 Servlets 2.5
JBoss 7.1.1 1.7 Servlets 2.5
WebLogic 12.1.1 1.7 Servlets 2.5
WebSphere 8.5 1.7 Servlets 2.5

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

Java EE 5 and Java EE 6 are supported for the deployment of EJBs generated using the Interface Mapping Toolkit, as follows:

  • Java EE 5 includes support for EJB 3.0 and Java Connector Architecture 1.5
  • Java EE 6 includes support for EJB 3.1 and Java Connector Architecture 1.6

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

Application Servers JDK (vendor) Java EE COBOL RA CICS RA
JBoss 5.1.0 1.5/1.6 (Oracle) 5 X
JBoss 6.1.0 1.6 (Oracle) 6 X
JBoss 7.1.1 1.6, 1.7 (Oracle) 6 X X
JBoss EAP 6.4 (AS 7.5) 1.6, 1.7 (Oracle) 6 X X
Oracle WebLogic 10.3.5 1.6 (Oracle) 5 X
Oracle WebLogic 12.1.1 1.6/1.7 (Oracle) 6 X
IBM WebSphere 7.0 1.5 (IBM) 5 X
IBM WebSphere 8.0 1.6 (IBM) 6 X
IBM WebSphere 8.5 1.6/1.7 (IBM) 6 X X

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.

AppMaster Builder Distributed Generation Server

Back to Top

Restriction: This feature applies only when the AppMaster Builder AddPack has been installed, and applies only to Windows platforms.

IBM WebSphere MQ version 7 and later.

CICS Web Services

Back to Top

To use CICS Web Services, you must first install the IBM CCSID conversion tables. See Install and Configure CCSID Conversion Tables for details.

Code Analysis

Back to Top

Apache Ant is required to perform code analysis from the Enterprise Developer command line. You can download Apache Ant from Apache's Web site.

Consolidated Trace Facility

Back to Top

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)

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 Windows X X
XA Switch Module
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.
Certification of RDBMS Precompilers for Native COBOL
Certification of RDBMS precompilers with Micro Focus products is the responsibility of the RDBMS vendor, rather than Micro Focus. Certification information can be found within the relevant Oracle documentation. If you have an Oracle MetaLink account, document # 43208.1 provides details of all language compilers certified by Oracle for use with their precompilers.
Preprocessors
COBSQL supports the following database preprocessors:
  • Sybase Open Client Embedded SQL/COBOL Version 11.1 or later
  • Oracle Pro*COBOL Version 11.2, 12.1, and 12.2
  • Informix Embedded SQL/COBOL Version 7.3 or later
Compiling
On x86 and x86-64 platforms, when compiling with COBSQL for use with Oracle, do not use the COBSQL directive option NOMAKESYN, since this directive results in COMP host variables, and on Intel platforms these are incompatible with the native byte order expected by Oracle.
Testing
For this version, COBSQL was tested with Oracle 11.2, 12.1, and 12.2.

Database Access - HCO for DB2 LUW

Back to Top

Before developing or deploying an HCO for DB2 LUW application, be sure to install and configure all applicable third-party software.

Note: HCO for DB2 LUW is supported for native COBOL only.
Availability
Feature/Platform Native COBOL 32-bit Native COBOL 64-bit PL/I 32-bit PL/I 64-bit
x86-64 running Windows X X X X
XA Switch Module
The DB2 XA switch module is provided and is available on the same platforms as are indicated in the Availability section above.
Certification of RDBMS Precompilers for Native COBOL
Certification of RDBMS precompilers with Micro Focus products is the responsibility of the RDBMS vendor, rather than Micro Focus. You can find IBM document certification information for DB2/COBOL applications within the IBM Information Center for DB2, in the topic Support for database application development in COBOL.
Preprocessor
HCO for DB2 LUW supports the following database preprocessors:
  • IBM DB2 LUW Version 9.7 or later
  • IBM DB2 Connect Version 9.7 or later
Host Compatibility Option (HCO)
Host Compatibility Option requires that you have one of the following software products installed and configured:
  • IBM DB2 Connect - Personal, Enterprise, Application Server or Unlimited Edition
  • IBM DB2 LUW - Workgroup or Enterprise Server Editions including Advanced versions
  • IBM DB2 LUW - Express or Express-C Edition
  • IBM Data Server Client (assumes installation of a remote DB2 LUW Server product)
Testing
For this version, HCO for DB2 LUW was tested with versions 9.7, 10.1, 10.5, and 11.1.

Database Access - HCO for SQL Server (HCOSS)

Back to Top

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

Availability
Feature/Platform 32-bit 64-bit
x86-64 running Windows X X
Database Migration
  • SQL Server 2008 R2 or later, any edition
  • Microsoft .NET Framework 4.0
  • Microsoft OLE DB Provider for DB2 version 5.0 or later
    Note: Be sure to configure the OLE DB Provider to connect to the mainframe. See your Microsoft documentation for details.
  • Mainframe DB2
Note:
  • We support only the mainframe DB2 versions that are currently under IBM support.
  • If you intend to develop applications on your local machine, but deploy applications to a SQL Server database on a remote machine, configure the remote machine using the requirements listed in the Deploying Native Applications > Deployment Machine section below.
Deploying Native Applications
Development Machine
Install one of the following combinations:
  • For SQL Server 2008 R2 and SQL Server 2012 databases, install SQL Server Native Client 10.x or later
  • For SQL Server 2008 R2 and SQL Server 2012 databases, install SQL Server along with the Microsoft ODBC Driver version 11.0.
  • For SQL Server 2014 databases, you must install both SQL Server 2014 and the Microsoft ODBC Driver 11.0 for SQL Server.
  • For SQL Server 2016 databases, you must install both SQL Server 2016 and the Microsoft ODBC Driver 13.0 for SQL Server.
Development SQL Server Machine
SQL Server 2008 R2 or later
Note: This can be the same machine as the development machine, but is not required to be.
Deployment Machine
  • Enterprise Server or Enterprise Test Server
  • For SQL Server 2008 R2 and SQL Server 2012 databases, install SQL Server along with the Microsoft ODBC driver version 11.0.
  • For SQL Server 2014 databases, you must install both SQL Server 2014 and the Microsoft ODBC Driver 11.0 for SQL Server.
  • For SQL Server 2016 databases, you must install both SQL Server 2016 and the Microsoft ODBC Driver 13.0 for SQL Server.
If you want to bind your application from the deployment machine, install the following additional software:
  • Microsoft .NET 3.5 framework, or later
  • SQL Server 2008 R2 or later System CLR Types
  • SQL Server 2008 R2 or later Shared Management Objects
Deployment SQL Server Machine
SQL Server 2008 R2 or later
Note: This can be the same machine as the deployment machine, but is not required to be.
Testing
For this version, HCO for SQL Server was tested with SQL Server 2008 R2, 2012, 2014, and 2016.

Database Access - Mainframe Batch Database Tools (MBDT)

Back to Top

Availability
Feature/Platform 32-bit 64-bit
x86-64 running Windows X X
OpenESQL
The MBDT toolset consists of OpenESQL applications, and are native code using ODBC. Please see the Database Access - OpenESQL section for further details.
Testing
For this version, MBDT was tested with:
  • DB2 LUW 10.5
  • Oracle 12.1
  • SQL Server 2012

Database Access - OpenESQL

Back to Top

Before developing or 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 PL/I 32-bit PL/I 64-bit
x86-64 running Windows X X X X
XA Switch Module
The ODBC One-phase Commit switch module is provided and is available on the same platforms as are indicated in the Availability section above.
Native COBOL and PL/I
  • 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 9.7

DB2 LUW 10.1

DB2 LUW 10.5

DB2 LUW 11.1

db2jcc4.jar (and db2jcc_license_cu.jar)
Oracle 11.2

Oracle 12.1

ojdbc6.zip1

ojdbc7.zip1

Microsoft SQL Server 2008 R2

Microsoft SQL Server 2012

Microsoft SQL Server 2014

Microsoft SQL Server 2016

sqljdbc4.jar2
PostgreSQL 9.6 postgresql-42.0.0.jre7.jar
1Some Oracle JDBC drivers are distributed as .zip rather than .jar files.

2 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 11.2 and 12.1
  • DB2 LUW 9.7, 10.1, 10.5, and 11.1
  • SQL Server 2008 R2, 2012, 2014, and 2016
  • EDB PostgreSQL 9.6
  • 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.

Database Access - SQL Option for DB2

Back to Top

Availability
Feature/Platform 32-bit
x86-64 running Windows X
XA Switch Module
XDB XA switch modules are provided and are available for the Windows x86-64 32-bit platform.

Java Development Kit (JDK)

Back to Top

Native COBOL and Java Interoperability - Oracle's Java Platform, Standard Edition (Java SE) 7 or Java 8 is required to run the Eclipse IDE, to execute COBOL JVM code and for native COBOL and Java interoperability. The setup file installs Java 8 u102 64-bit. You can download Oracle's Java SE from Oracle's Web site and install it anywhere on your machine.

JCL Support - DSNREXX

Back to Top

Note: This is a technology preview feature only. It is being made available to allow you to test and provide feedback on this new capability; however, this feature is not intended for production use and it is not supported as such.
Availability
Feature/Platform 32-bit 64-bit
x86-64 running Windows X X
OpenESQL
DSNREXX is supported in OpenESQL applications, and is native code using ODBC. See the Database Access - OpenESQL section in this topic for additional software requirements, and the DSNREXX Support topics for complete details.
Testing
For this version, DSNREXX was tested with:
  • DB2 LUW 10.5
  • SQL Server 2012

Mainframe Access - Endevor Support

Back to Top

  • To use the Mainframe Access support for Endevor you must be using Endevor R14 or later. CA stabilized the Endevor API at R14, so if you upgrade from R14 to a later version you will not need to update the support module that Mainframe Access uses.

Micro Focus Rumba

Back to Top

  • On Windows 8, in order to install Micro Focus Rumba you must have the Microsoft .NET Framework 3.5 Service Pack 1 installed.

WebSphere MQ

Back to Top

This product supports IBM WebSphere MQ version 7 and later.