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.6 / 1.7 Servlets 2.5
JBoss 7.1.1 1.6 / 1.7 Servlets 2.5
WebLogic 12.1.1 1.6 / 1.7 Servlets 2.5
WebSphere 8.5 1.6 / 1.7 Servlets 2.5

You need Oracle's JDK. The earliest supported release of Oracle's JDK 1.6 is 1.6.027. You can download Oracle's JDK from Oracle's Web site

Application server support for interaction with 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
JBoss 5 1.5/1.6 (Oracle) 5
JBoss 6 1.6 (Oracle) 6
Oracle WebLogic 10 1.5 (Oracle) 5
Oracle WebLogic 12 1.6/1.7 (Oracle) 6
IBM WebSphere 7.0 1.5 (IBM) 5
IBM WebSphere 8.0 1.6 (IBM) 6
IBM WebSphere 8.5 1.6/1.7 (IBM) 6

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.

Java Development Kit (JDK)

Back to Top

Native COBOL and Java Interoperability
Oracle's Java Platform, Enterprise Edition (Java EE) 6 or Java 7 is required to run the Eclipse IDE, to execute COBOL JVM code and for native COBOL and Java interoperability. The earliest supported release of Java 6 is 1.6 Update 27. You can download Oracle's Java EE from Oracle's Web site and install it anywhere on your machine.
Compiling Java
Either the IBM or the Oracle Java Development Kit (JDK), version 1.5 or later, is required for compiling Java.
Interface Mapping Toolkit (IMTK)
Restriction: This feature applies only when the Enterprise Server feature is enabled.
The JDK is required for generating Java interfaces from the Interface Mapping Toolkit or the imtkmake command.
Java Beans
Your Java client needs to be compiled with JDK 1.6 or greater.
EJBs
Use the same JDK vendor and version that is used by the application server.

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

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.

Database Access

Back to Top

Before you can use Enterprise Developer to develop and deploy SQL applications that use COBSQL, HCO for DB2 LUW, HCO for SQL Server (HCOSS), SQL Option for DB2, or OpenESQL, ensure any third-party software prerequisites are installed and the environment is set properly.

Database Access - COBSQL (Pro*COBOL)

Back to Top

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 (http://metalink.oracle.com), 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.1 (11gR1) or later
  • 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.

Database Access - OpenESQL

Back to Top

Availability
Feature/Platform Native COBOL 32-bit Native COBOL 64-bit PL/I 32-bit
x86-64 running Windows 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. The SQL Server XA switch module is also provided.

To build the SQL Server XA module, you must have the Windows Software Development Kit (SDK) installed for your version of Windows.

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 Managed COBOL
OpenESQL supports access to relational databases using JDBC 4.0-compliant JDBC drivers. 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 Object. 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 Simple-JNDI topic in this documentation set for instructions on downloading, installing, and using the open source JNDI server Simple-JNDI for this purpose.

Database Access - HCO for SQL Server (HCOSS)

Back to Top

Microsoft SQL Server
SQL Server 2008 R2 or later, Developer or Enterprise Editions, including Microsoft SQL Server Management Studio.
Database Migration
  • Microsoft .NET Framework 4.0
  • Microsoft OLE DB Provider for DB2, available in the SQL Server 2008 R2 or later Feature Pack
    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.
Deploying Native Applications
Development Machine
  • Enterprise Developer for Eclipse
  • 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 Server or Enterprise Test Server installed
  • 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 software in addition:
  • 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

Database Access - HCO for DB2 LUW

Back to Top

Availability
Feature/Platform Native COBOL 32-bit Native COBOL 64-bit PL/I 32-bit
x86-64 running Windows 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.5 or later
  • IBM DB2 Connect Version 9.5 or later
Host Compatibility Option (HCO)
Host Compatibility Option requires that you have one of the following software products installed and configured:
  • IBM Database Connect
  • IBM DB2 LUW Personal Edition or DB2 Express-C
  • DB2 LUW Workgroup or Enterprise Edition

You must also install the DB2 Application Development Client (formerly called DB2 SDK) or you will not be able to compile any DB2 programs.

Database Access - SQL Option for DB2

Back to Top

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.

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

IBM WebSphere MQ version 7 and later.