Additional Software Requirements

Application Server JCA support for Enterprise Server

Java EE 5 and Java EE 6 are supported for the deployment of EJBs 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

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

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.

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.

Testing

For this version, COBSQL was tested with Oracle 11.1, 11.2, and 12.1.

Database Access - HCO for DB2 LUW

Back to Top

Before 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

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.

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.5, 9.7, 10.1, and 10.5.

Database Access - HCO for SQL Server (HCOSS)

Back to Top

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

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, you can install SQL Server Native Client 10.x (or later) for ODBC connectivity on your local machine instead of installing SQL Server. For SQL Server 2014 connectivity, you can install Microsoft ODBC Driver 11.0 for SQL Server. For information on configuring a deployment machine, see the section Deploying Native Applications below.

Application Migration

ADO.NET applications

ADO.NET applications require either of the following combinations:

SQL Server 2008 R2 and SqlClient Data Provider in .NET Framework 3.5
Note: Microsoft recommends .NET Framework 3.5.1
SQL Server 2012 or later and SqlClient Data Provider in .NET Framework 4.x
Note: Microsoft recommends .NET Framework 4.5.2

Deploying Native Applications

Development Machine

Enterprise Developer
If SQL Server 2008 R2 or 2012 is not installed, you must have Microsoft SQL Server 2008 R2 or 2012 Native Client installed. For SQL Server 2014, you must have Microsoft ODBC Driver 11.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 Test Server or Enterprise Test Server
If SQL Server 2008 R2 or 2012 is not installed, you must have Microsoft SQL Server 2008 R2 or 2012 Native Client installed. For SQL Server 2014, you must have Microsoft ODBC Driver 11.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, and 2014.

Database Access - Mainframe Batch Database Tools (MBDT)

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

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 deploying an OpenESQL application, be sure to install and configure all applicable third-party software.

Availability

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

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 Managed 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 PostgreSQL 9.4

JVM Managed 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.5 DB2 LUW 9.7 DB2 LUW 10.1 DB2 LUW 10.5	db2jcc4.jar (and db2jcc_license_cu.jar)
Oracle 11.1, 11.2 Oracle 12.1	ojdbc6.zip¹ ojdbc7.zip¹
Microsoft SQL Server 2008 R2 Microsoft SQL Server 2012 Microsoft SQL Server 2014	sqljdbc4.jar²
PostgreSQL 9.4
¹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 11.1, 11.2 and 12.1
DB2 LUW 9.5, 9.7,10.1,10.5
SQL Server 2008 R2, 2012, 2014
PostgreSQL 9.4

Note: Micro Focus provides compatibility for PostgreSQL but does not directly contribute to or support the PostgreSQL open source project. Any issues relating to PostgreSQL functionality 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.

Data Manager

Back to Top

Restriction: Data Manager is available in Enterprise Test Server Premium only. To obtain a license for Enterprise Test Server Premium, contact Micro Focus SupportLine.

The following third-party software is required:

IBM DB2
Note: Although not explicitly required, we recommend that your Windows machine have a direct connection to the DB2 database through DB2 Connect.
- When using Gateway DB2 Connect Enterprise Edition to directly connect, you must also use IBM DB2 Connect Personal Edition version 6.1 or later
- If not using Gateway DB2 Connect Enterprise Edition, use either IBM DB2 Client Application Enabler for Windows version 6.1 or later, or IBM DB2 Connect Personal Edition version 6.1 or later
Borland Database Engine
Important: Install this software after installing Enterprise Test Server.

Interface Mapping Toolkit (IMTK)

.NET client generation for Service Interfaces requires Visual C++, which is an optional feature of Visual Studio 2015. To ensure that Visual C++ is installed with Visual Studio 2015, you must do a custom installation of Visual Studio 2015, and specifically choose the Visual C++ option.

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.