To ensure full functionality for some
Visual COBOL features, you might be required to obtain and install additional third-party software in addition to the prerequisite software installed automatically by the
Visual COBOL 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.7
|
Servlets 2.5
|
JBoss 7.1.1
|
1.7
|
Servlets 2.5
|
WebLogic 12.1.1
|
1.7
|
Servlets 2.5
|
WebSphere 8.5
|
1.7
|
Servlets 2.5
|
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
Restriction: This feature applies only when the Enterprise Server feature is enabled.
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
|
JBoss 5.1.0
|
1.5/1.6 (Oracle)
|
5
|
X
|
JBoss 6.1.0
|
1.6 (Oracle)
|
6
|
X
|
JBoss 7.1.1
|
1.7 (Oracle)
|
6
|
X
|
JBoss EAP 6.4 (AS 7.5)
|
1.6, 1.7 (Oracle)
|
6
|
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
|
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.
Code Analysis
Back to Top
Apache Ant is required to perform code analysis from the
Visual COBOL command line. You can download Apache Ant from
Apache's Web site.
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 run the Eclipse IDE, 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.
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 - 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
- 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 -
DB2 ECM
Back to Top
Before
developing or
deploying
a DB2 ECM application, be sure to install and configure all applicable third-party software.
Note: DB2 ECM is supported for native COBOL only.
- 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.
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
Managed COBOL 32-bit
|
Native and
JVM
Managed COBOL 64-bit
|
x86-64 running Windows
|
X
|
X
|
- XA Switch Module
- When the Enterprise Server feature is enabled, the
ODBC One-phase Commit switch module is provided and is 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
- JVM Managed 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.5
DB2 LUW 9.7
DB2 LUW 10.1
DB2 LUW 10.5
|
db2jcc4.jar (and
db2jcc_license_cu.jar)
|
Oracle 11.1, 11.2
Oracle 12.1
|
ojdbc6.zip1
ojdbc7.zip1
|
Microsoft SQL Server 2008 R2
Microsoft SQL Server 2012
Microsoft SQL Server 2014
|
sqljdbc4.jar2
|
PostgreSQL 9.4
|
|
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.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.
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.