Additional Software Requirements

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:

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.

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 Visual COBOL to develop and deploy SQL applications that use COBSQL, DB2 ECM, or OpenESQL, ensure any third-party software prerequisites are installed and the environment is set properly.

Database Access - COBSQL (Pro*COBOL)

Back to Top

Availability

Feature/Platform	32-bit	64-bit
x86-64 running Windows	X	X

XA Switch Module

When the Enterprise Server feature is enabled, 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
x86-64 running Windows	X	X

XA Switch Modules

When the Enterprise Server feature is enabled, 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

• 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 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 2012 Update 1 or later and Microsoft SQL Server Tools (SSDT SDK)
  • Visual Studio 2012 Update 1 or later Professional, Premium, or Ultimate
• 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 Visual COBOL 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 Visual COBOL for Visual Studio 2012.

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 - DB2 ECM

Back to Top

Availability

Feature/Platform	32-bit	64-bit
x86-64 running Windows	X	X

XA Switch Module

When the Enterprise Server feature is enabled, 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

DB2 ECM supports the following database preprocessors:

• IBM DB2 LUW Version 9.5 or later
• IBM DB2 Connect Version 9.5 or later

Testing

For this version, DB2 ECM was tested with DB2 LUW 9.5, 9.7, 10.1, and 10.5.

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.

XML Extensions

Back to Top

• XML Extensions has the same requirements as Visual COBOL. Both 32-bit and 64-bit versions are available. See the XML Extensions for Visual COBOL, available from the Visual COBOL product documentation section of the Micro Focus SupportLine Web site for more details.
• Additionally, XML Extensions may be used in conjunction with Terminal Server.