Application Server JCA Support for Enterprise Server

Starting with Enterprise Developer version 2.2 Update 2, HotFix 9, Micro Focus ECI programs that use mfccl.jar raise an error exception, EXCIRespException, if exciResp1 and exciResp2 are not both equal to zero. To ensure your ECI program captures all errors, you must catch this exception in your code. Please add the following code snippet, which enables your program to compile and execute properly:

try {
                …
        } catch(ExciRespException e) {
               String rcMsg = e.getRcMsg();
        }

If an error occurs, rcMsg captures the appropriate error message.

EJBs generated for WebLogic 10.3.5 do not support local interfaces. This is because this version of WebLogic does not make business local interfaces available on the global JNDI tree.

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 ...

You need to specify a container-managed authentication alias for the data source or connection factory, or configure the application to use component-managed authentication. For more details on these warnings, see the IBM Support Web site.

When using XA transactions with EJB 3.0 on Websphere 7 with the EJB 3 Feature Pack, if there are two resource managers and one of them is ES and the other is using JDBC, if the JDBC update fails, the Transaction Manager in Websphere does not receive the failure message and hence does not send a rollback to the other resource manager or managers (Enterprise Server included). Instead, it sends a commit which is incorrect. This issue is being investigated.