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 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.6 (Oracle)
|
5
|
X
|
|
| JBoss 6.1.0
|
1.6 (Oracle)
|
6
|
X
|
|
| JBoss 7.1.1
|
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
|
COBOL on
Microsoft Azure
Back to Top
Microsoft Azure requires additional software. See the Microsoft
Microsoft Azure web site for a full list of the required software, but the following is a summary of the main prerequisites:
- Windows 7 Service Pack 1, Windows 8, Windows 8.1, Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server 2012 R2. (Windows 7 Home Basic is not supported.)
- Microsoft Azure Tools version 2.6 for the version of Visual Studio you have installed - this includes the
Microsoft Azure SDK
- Visual Studio's Visual Web Developer feature
- IIS7 with ASP.NET and WCF HTTP Activation, Static Content, IIS Management Console and HTTP Redirection.
- Microsoft's Web Deployment Tool version 2.1 or later
Java Development Kit (JDK)
Back to Top
- Native COBOL and Java Interoperability
- Oracle's Java Platform, Enterprise Edition (Java EE) 7 or Java 8 is required
to execute COBOL JVM code and for native COBOL and Java interoperability. The setup file installs Java 8 u51 32-bit. 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.
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, 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.
- Testing
- For this version, COBSQL was tested with Oracle 11.1, 11.2, and 12.1.
Database Access - OpenESQL
Back to Top
- Availability
-
| Feature/Platform
|
Native and
.NET
Managed COBOL 32-bit
|
Native and
.NET
Managed COBOL 64-bit
|
PL/I 32-bit
|
PL/I 64-bit
|
| x86-64 running Windows
|
X
|
X
|
X
|
X
|
- XA Switch Modules
- The
ODBC One-phase Commit and the SQL Server XA switch modules are provided and are available on the same platforms as are indicated in the
Availability section above.
To build the SQL Server XA module, you must have the Windows Software Development Kit (SDK) installed for your version of Windows.
- Native COBOL, .NET Managed COBOL, and PL/I
-
- OpenESQL supports access to relational databases using ODBC 3.0-compliant drivers
- OpenESQL supports access to relational databases using compliant .NET framework drivers (COBOL only)
- Refer to your driver vendor's documentation to determine whether your driver is suitable for use with OpenESQL
- .NET Managed COBOL
- 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)
- OleDb
- Managed ODBC .NET providers
- Npgsql PostgreSQL 9.4
- SQL CLR Integration
- The following software is required to use the SQL CLR integration feature, which is specifically for the development and deployment of COBOL stored procedures under Microsoft SQL Server.
Projects based on the SQL Server Database Project template require:
- Either of the following:
- Visual Studio Shell 2015 and Microsoft SQL Server Tools (SSDT SDK)
- Visual Studio 2015
Professional, Enterprise or Community Edition
- Any of the following:
- SQL Server 2008 R2 targeting .NET CLR v2.0 frameworks (2.0, 3.0, 3.5)
- SQL Server 2012 targeting .NET CLR v4.0 framework (4.0, 4.5) or .NET CLR v2.0 frameworks (2.0, 3.0, 3.5)
- SQL Azure Database targeting .NET CLR v4.0 framework (4.0, 4.5) or .NET CLR v2.0 frameworks (2.0, 3.0, 3.5)
Important: The SQL CLR Database project template available in previous versions of
Enterprise Developer is no longer supported. Projects based on the SQL CLR Database project template are automatically upgraded to use the SQL Server Database project template when opened in
Enterprise Developer
for Visual Studio 2015.
- 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 -
HCO for DB2 LUW
Back to Top
- 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.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 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 DB2 LUW 9.5, 9.7, 10.1, and 10.5.
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 SQL Server Integration Services - available with the Microsoft SQL Server editions listed above
- 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.
- 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
- SQL Server 2012 or later and SqlClient Data Provider in .NET Framework
4.0, or 4.5 (4.x is preferred)
- COBOL Stored Procedures
- See the requirements specified in the
SQL CLR Integration section under
Database Access - OpenESQL in this topic.
- Deploying Native Applications
-
- Development Machine
-
- Enterprise Developer
for Visual Studio 2015
- 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
- Testing
- For this version, HCO for SQL Server was tested with SQL Server 2008 R2, 2012, and 2014.
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.
Enterprise Server for .NET
Back to Top
Note: You also need to enable IIS and some additional Windows features. Read the
Quick Start section in your
Enterprise Server for .NET help for further instructions on how to set up your operating environment.
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
IBM
WebSphere MQ version 7 and later.
Windows Forms
Back to Top
- Microsoft Visual Studio is required for using the Interface Mapping Toolkit (IMTK) to generate Windows Forms and ASP.NET Web site test clients.
- Microsoft Internet Information Service (IIS) is also required for generating Windows Forms test clients.
