To ensure full functionality for some
Enterprise Test Server features, you might be required to obtain and install additional third-party software in addition to the prerequisite software
installed automatically by the
Enterprise Test Server setup file. The following information specifies the third-party software required for each feature.
Application Server JCA support for Enterprise Server
Back to Top
Various Java EE versions 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
- Java EE 7 includes support for EJB 3.2 and Java Connector Architecture 1.7
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 6.4 (AS 7.5)
|
1.6, 1.7, 1.8 (Oracle), 1.8 (OpenJDK)
|
6
|
X
|
X
|
| Oracle WebLogic 10.3.x
|
1.6, 1.7 (Oracle)
|
5
|
X
|
|
| Oracle WebLogic 12.1.x
|
1.6, 1.7, 1.8 (Oracle)
|
6
|
X
|
|
| Oracle WebLogic 12.2.1
|
1.8 (Oracle)
|
7
|
X
|
|
| IBM WebSphere 8.5
|
1.6, 1.7 (IBM)
|
6
|
X
|
X
|
| IBM WebSphere 9.0
|
1.8 (IBM)
|
7
|
X
|
|
| Tomcat 7.0.x *
|
1.6, 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).
|
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
|
CICS RAs and ECI
|
| JBoss EAP 7.0
|
1.8 (Oracle), 1.8 (OpenJDK)
|
7
|
X
|
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
Enterprise Test 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.
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.
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.2, 12.1, and 12.2.
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.7, 10.1, 10.5, and 11.1.
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.
- Availability
-
| Feature/Platform
|
32-bit
|
64-bit
|
| x86-64 running Windows
|
X
|
X
|
- Database Migration
-
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.
- Application Migration
-
- ADO.NET applications
- ADO.NET applications require either of the following combinations:
- 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 Test 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, 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.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, 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 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
|
| EDB 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, 2016, and 2017
- 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.
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.
Deployment - running . NET COBOL applications from a network server
Back to Top
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.
Interface Mapping Toolkit (IMTK)
.NET client generation for Service Interfaces requires Visual C++, which is an optional feature of Visual Studio 2015 and
later. To ensure that Visual C++ is installed with Visual Studio, you must do a custom installation of Visual Studio, and
specifically choose the Visual C++ option.
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.