Third Party Software for Micro Focus Server

The following notes provide information on third party software:

• Database Access Support within Micro Focus Server
• Java Support and Restrictions

Database Access Support within Micro Focus Server

• Micro Focus Server supports the execution of application-managed services running against the databases listed above, in the section Database Access Support for Unmanaged COBOL.
• Micro Focus Server supports the execution of container-managed services running against any XA-compliant database.

  For the following databases, Micro Focus supplies a switch module that gives Micro Focus Server access to the database's XA switch structure:

  • Oracle - Applications precompiled using Pro*COBOL, or Cobsql, using Oracle Pro*COBOL Version 9 or later.
  • IBM DB2 Universal Database - Applications precompiled using the IBM command-line precompiler or compiled using the Micro Focus DB2 Compiler directive.

  For other databases, refer to the database vendor's documentation for details of their XA switch module's requirements.

  If you are defining external XA resource managers for the following, you need to do some additional set up:

  • For Oracle or IBM DB2, you need to have set up the database environment before starting the Directory Server. Please refer to your database vendors' documentation for further details.
  • For both Oracle and IBM DB2, you should ensure that the Oracle resource manager is defined before the DB2 resource manager from within Enterprise Server Administration. If you are defining external XA resource managers for Oracle, in order to execute your user application, you must create a callable shared object containing Oracle DBMS support, rather than creating a new executable run-time system including that support. For background information see the COBSQL chapter in your Database Access Guide, and see also the Micro Focus Knowledge Base article #22062, located at http://supportline.microfocus.com/mf_kb_display.asp?kbnumber=22062. This article also provides a script that will create the callable shared object for you.
  • For Oracle on HP_UX, you need to perform an additional step before starting the Directory Server. Having installed the patch, you need to set an environment variable, LD_PRELOAD, to point to the Oracle client callable shared object. You need to set this within the user environment before starting the Directory Server. For example:

    LD_PRELOAD=$ORACLE_HOME/libdir/libclntsh.sl  
          export LD_PRELOAD     
    

    Where libdir is :

    • lib32 for 32-bit environments
    • lib for 64-bit environments.

  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.

Java Support and Restrictions

• The Java Development Kit (JDK) is required for compiling Java. The JDK is required for generating Java interfaces using the Deploy tool in the Interface Mapping Toolkit or the imtkmake command.

  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)
  JDK 1.5 (IBM)	JDK 1.4.2 (IBM)
  JDK 1.5 (IBM)	JDK 1.5 (IBM)

  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.

• J2EE 1.3 and 1.4 are supported for the deployment of EJBs generated using the Interface Mapping Toolkit, as follows:
  • J2EE 1.3 includes support for EJB 2.0 and Java Connector Architecture 1.0
  • J2EE 1.4 includes support for EJB 2.1 and Java Connector Architecture 1.5
  • Java EE 5 includes support for EJB 3.0 and Java Connector Architecture 1.5
  • The following J2EE application servers, using the following JDKs:

    JBoss 3.2.8	JDK 1.4.2 (Sun)	J2EE1.3
    JBoss 4.0.2	JDK 1.5 (Sun)	J2EE1.4
    Oracle 10.1.2	JDK 1.4.2 (Sun)	J2EE1.3
    Oracle 10.1.3.0	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.1	JDK 1.4.2 (IBM)	J2EE1.3
    WebSphere 6.0	JDK 1.4.2 (IBM)	J2EE1.4
    WebSphere 6.1	JDK 1.5 (IBM)	J2EE1.4
    WebSphere 6.1 with IBM EJB 3 Feature Pack	JDK 1.5 (IBM)	Java EE 5

• BEA WebLogic 8.1 fails to throw an exception on a failure of the commit verb in the local transaction resource adapter. The Micro Focus resource adapter throws an exception indicating the commit failure, but WebLogic ignores this and continues the processing and throws an exception in the user code at a later point.

  -540412

• When you undeploy a resource adapter from WebLogic 8.1 and WebLogic 9.0, you receive a java.lang.NullPointer exception. This does not cause any problems and will be investigated in future.

  -542611

• IBM WebSphere issues various warnings when running some applications. These are WebSphere problems. For example:

  07/12/10 11:35:55:843 JST] 00000056 PrivExAction  W   
  J2CA0144W: Could not find a mappingConfigAlias for the connection ...
  [07/12/10 11:35:55:908 JST] 00000056 PrivExAction  W   
  J2CA0114W: Could not fing a container managed credential alias ...
  

  For details on these warnings, see the IBM Support Web site.

  -547718

• With IBM WebSphere 5.1 on IBM xSeries running SuSE Linux, you get the message 'connection refused’ when running an EJB that calls an enterprise server. Check that the port is correct and that the enterprise server is started (before starting WebSphere).

  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.