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.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
- 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
|
CICS RAs and ECI
|
| JBoss EAP 7.0
|
1.8 (Oracle), 1.8 (OpenJDK)
|
7
|
X
|
X
|
| IBM WebSphere 8.5.5
(UNIX:
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
Enterprise Developer, 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
Back to Top
Java EE 7, including support for EJB 3.2 and Java Connector Architecture 1.7, is supported for the deployment of EJBs generated using the Interface Mapping Toolkit.
The following Java application servers are supported using the following JDKs:
| Application Servers
|
JDK (vendor)
|
Java EE
|
COBOL RA
|
CICS RAs and ECI
|
| JBoss EAP 7.1.4
|
1.8 (Oracle)
1.8 (AdoptOpenJDK)
|
7
|
X
|
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
- 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
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:
- Oracle Pro*COBOL Version 12.2 and 18c database preprocessors
- Sybase Open Client Embedded SQL/COBOL Version 11.1 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.
- Testing
- For this version, COBSQL was tested with Oracle Pro*COBOL version 12.2 and 18c.
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 10.5 or later
- IBM DB2 Connect Version 10.5 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
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 2012 or later, any edition
- Microsoft .NET Framework 4.0
- Microsoft OLE DB Provider for DB2 version 5.0 or later
Notes:
- Microsoft OLE DB Provider for DB2 version 6.0 does not currently work with HCOSS. If you require further information, contact
Micro Focus
SupportLine.
- Be sure to configure the OLE DB Provider to connect to the mainframe. See your Microsoft documentation for details.
- Mainframe DB2
Notes:
- 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 SQL Server 2012 or later, along with its recommended Microsoft ODBC driver version.
- Development SQL Server Machine
- SQL Server 2012 or later
Note: This can be the same machine as the development machine, but is not required to be.
- Deployment Machine
-
- Install
Enterprise Server or
Enterprise Test Server
- Install SQL Server 2012 or later, along with its recommended Microsoft ODBC driver version.
If you want to bind your application from the deployment machine, install the following additional software:
- Microsoft .NET 4 framework, or later
- SQL Server 2012 or later System CLR Types
- SQL Server 2012 or later Shared Management Objects
- Deployment SQL Server Machine
- SQL Server 2012 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 2012, 2014, 2016, and 2017.
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.2
- 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, SQL Server, and PostgreSQL switch modules are provided and 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 10.5
DB2 LUW 11.1
|
db2jcc4.jar (and
db2jcc_license_cu.jar)
|
| Oracle 12.2
|
ojdbc7.zip1
|
| Microsoft SQL Server 2012
Microsoft SQL Server 2014
Microsoft SQL Server 2016
Microsoft SQL Server 2017
|
sqljdbc4.jar2
|
| EDB PostgreSQL 10.5
|
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 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
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
For COBOL JVM code and Java Interoperability, Java 8 (32 or 64-bit versions), and Java 11 (64-bit version only) are supported.
Java 8 (64-bit) is required to run the Eclipse IDE. The minimum recommended version is
AdoptOpenJDK's OpenJDK 8 (u202) with Hotspot, which the Windows product installs automatically. 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.
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.