Known Issues for Adapters

The following are known issues for Sun Adapters:

• CR 6676202

  If you import a 5.1.0 project that contains an Oracle Adapter (eWay) along with its associated Environment, the Environment Properties window for the External System does not list the Outbound non-Transaction properties. This occurs because release 5.1.0 did not support non-transactional messaging.

  To work around this issue, create and configure a new Oracle External System in the imported Environment.

• CR 6702711

  The MSMQ Adapter implemented the connection pooling feature, which made changes to the template and added properties to the external system.

  If you import and build MSMQ projects from Java CAPS 5.1.3 and earlier, you need to open the environment properties and Connectivity Map properties in order to build the project.

• CR 6674397

  The database table locks if the application server goes down during the middle of an XA Transaction.

  To work around this issue, restart the database to release the lock.

• CR 6697220

  There is no LDAP support for inbound configuration of HTTP, Siebel, and PeopleSoft Adapters.

• CR 6779560

  The HL7 V3 functionality is disabled from use in HL7 JCA-based EJBs.

• CR 6854684

  The Oracle Adapter must be installed before installing the Oracle Applications Adapter to ensure the correct JAR files are installed. Note that the Oracle Adapter is installed in the standard Java CAPS installation.

• The Adapter Development Kit does not support creating Global RAR (JCA Adapters). (CR 6876283)

• eWays created using the 5.1.x version of the eWay Development Kit need to be recreated in Java CAPS 6.x using the Adapter Development Kit.