The following notes provide information on third party software:
For the following databases, Micro Focus supplies a switch module that gives Micro Focus Server access to the database's XA switch structure:
For other databases, refer to the database vendor's documentation for details of their XA switch module's requirements.
For more information on switch modules, see the section Resource Managers in the Configuration chapter of your Configuration and Administration Guide in the Micro Focus Server Help. For other databases, you should refer to the database vendor's documentation for details of their XA switch module's requirements.
Database access is supported using the OpenESQL preprocessor with applications compiled as .NET managed code to access 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). COBSQL and DB2 ECM SQL preprocessors are supported for migration purposes only. For details, see the topic Database Support for COBOL under the .NET Framework in your Micro Focus Help within Visual Studio.
OpenESQL has been tested against the following ADO.NET data providers:
Dynamic SQL using the SQL Descriptor Area (SQLDA) is not currently supported for either OpenESQL applications compiled with the SQL(DBMAN=ODBC) directive, or DB2 applications compiled with the DB2 directive.
The JDK required for generating Java beans depends on the JDK with which your Java client is compiled, as follows:
Java Client | Java Bean |
---|---|
JDK 1.4.2 (IBM) | JDK 1.4.2 (IBM) |
JDK 1.4.2 (Sun) | JDK 1.4.2 (Sun) |
JDK 1.5 (Sun) | JDK 1.4.2 (Sun) |
JDK 1.5 (Sun) | JDK 1.5 (Sun) |
The JDK required for generating EJBs depends on your J2EE application server. See the J2EE support below.
After installing the JDK, you need to set up your Java environment. See the section Setting Up the Environment for Java and COBOL in your Java and COBOL book in the Help for your COBOL development system.
JBoss 3.2.7 | JDK 1.4.2 (Sun) | J2EE1.3 |
JBoss 4.0 | JDK 1.5 (Sun) | J2EE1.4 |
Oracle 10.1.2 | JDK 1.4.2 (Sun) | J2EE1.3 |
Oracle 10.1.3 | JDK 1.5 (Sun) | J2EE1.4 |
WebLogic 8.1 | JDK 1.4.2 (Sun) | J2EE1.3 |
WebLogic 9.0 | JDK 1.5 (Sun) | J2EE1.4 |
WebSphere 5.x | JDK 1.4.2 (IBM) | J2EE1.3 |
WebSphere 6.x | JDK 1.4.2 (IBM) | J2EE1.4 |
-540412
The alternatives are to use stateless beans or to tune WebSphere to prevent passivation of stateful beans. To do the latter, change the timeout value under IBM Extensions. Click the EJB in the Application Assembly Tool (AAT), then in the bottom right pane click the IBM Extensions tab. The default is set to 600 seconds. Change this to 0 seconds to ensure that the stateful bean does not get passivated.
-530027
If you still get the same message, set the ServerHost configuration property to the machine name instead of localhost. You can do this using the WebSphere administration console. You need to restart WebSphere server after setting the property.
Alternatively you can set this property in the deployment descriptor, ra.xml in the resource adapter's archive file: mfcobol*.rar. For the location of the resource adapters see the section Resource Adapters in the chapter Deploying Interfaces in the Configuration and Administration Guide for Micro Focus Server. Again, you need to restart WebSphere server after setting the property.
-540148