Release notes for WebSphere Business Integration Server Express and Express Plus, Version 4.4, for Linux

(c) Copyright International Business Machines Corporation 2005. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents

About this release Known problems and workarounds
Fix and update history Documentation
Installation requirements IBM Software Support
Limitations

About this release

This release adds support for InterChange Server Express on the following operating systems:

The following new functions are available with this release:

The following new adapters are included with WebSphere Business Integration Server Express and WebSphere Business Integration Server Express Plus:

The Adapter for eMatrix is now included with the Adapter Capacity Pack for WebSphere Business Integration Server Express Plus.

Fix and update history

Between releases 4.3.1 and 4.4, the following problems, based on customer-reported cases, were fixed:

Component Tracking number Description
Server WebSphere InterChange Server Fix Packs 422.3, 422.4, and 422.5 have been merged in to this release.
Installer (Adapter Capacity Pack) 44001 After a remote or local capacity pack installation of the Adapter for Metasolv on a Windows 2000 machine, when you launch the adapter, it terminates with an error: The input line is too long. This is caused by command line-length problems on Windows 2000. The same problem occurs with the adapter for Oracle Applications when you install the capacity pack remotely.
Installer 46851 Unresolved text from resource bundles may appear in the window during file transfer. In particular, the following might display:
$L(com.ibm.wbi.install.common.i18n.WBIProductResources, businessIntegrationServerExpressPlusProduct.
displayName)
The correct text is WebSphere Business Integration Server Express Plus V4.3.1.
System Monitor 42481 System Monitor supports running the Web Application Server and client in the same locale. If the server and client are in different locales, text displays in both languages. If it is not possible to run the server in the same locale as the client, set the locale on the JVM to be the same as the client locale.
System Monitor 42705 While exporting Web services to the Activity Editor, the check box tree in the export wizard dialog box does not function correctly. If you select the leaf node, its parent node may not be selected. Even though the parent node is not selected, the exporting functionality is not affected.
System Monitor 43360 If you create a view with more than 20 monitors from the Create and Configure Views page, you might encounter an exception when you select the view.
Web-based Failed Event Manager 43509 Role names must be lowercase for WebSphere Application Server.
DB2 Enterprise 35380 DB2 Enterprise does not restart the database manager when Windows restarts. Because the database manager is not running, two problems can occur if Windows restarts during the installation of WebSphere Business Integration Server Express or Express Plus:
  • The repository creation can fail. When this occurs, the Installer log includes the following message line: No start database manager command was issued.
  • The startup of InterChange Server Express can fail, because without the database manager running, InterChange Server Express cannot connect to SMB_DB. When this occurs, the InterchangeSystem log file messages include the following line: No start database manager command was issued.

Workaround: This workaround is for both problems:

  1. Open the DB2 Control Center.
  2. Expand the All Cataloged Systems folder, then expand the folder for your host, and then expand the Instances folder.
  3. In the Instances folder, right-click the DB2 icon, and click Start.
    The following DB2 message displays: DB2START processing was successful.

After you have performed these steps, you can create a repository and successfully start InterChange Server Express.

DB2 Enterprise and DB2 Express uninstallers 35380 If either DB2 Enterprise or DB2 Express and WebSphere Business Integration Server Express (or Express Plus) has been installed and uninstalled previously, the repository creation fails during reinstallation of WebSphere Business Integration Server Express or Express Plus. This occurs because the uninstallation process for DB2 Enterprise and DB2 Express does not remove aliases for databases from the directory C:\DB2\aliases_directory.

Therefore, the alias for the InterChange Server Express repository called SMB_DB, which is created during the original installation of WebSphere Business Integration Server Express or Express Plus, remains after the uninstallation of DB2. Although the existence of this alias does not affect the reinstallation of DB2 Enterprise or DB2 Express, when WebSphere Business Integration Server Express or Express Plus is reinstalled, the repository creation fails because the system finds the old SMB_DB alias.

Workaround: Manually delete the SMB_DB database before uninstalling and reinstalling DB2 Enterprise or DB2 Express. Deleting the actual database eliminates its alias.

Adapters and data handlers Tracking number Description
All Adapters 43586 The AgentTraceLevel property for a connector running over the JMS delivery transport and using a local connector configuration (specified through the -c command line option) can only be dynamically updated once through System Manager during the connector's lifetime. Subsequent attempts to dynamically update this property will fail.
Adapter for e-Mail 25099 The UseDefault property is not supported for this adapter. This is causing problems when an XML business object is sent to the connector, and the connector does not generate proper XML (it does not generate the "<?xml version" tags).
Adapter for e-Mail 29753 Authentication is needed for SMTP server while sending mail.
Adapter for e-Mail 30751 The SMTP port for the connector needs modification.
Adapter for e-Mail 36801 Support for RFC 822 standard Internet (e-mail) addresses has been added.
Adapter for iSeries 58761 Requests with changes in the business object are not delivered as responses at the other end.
Adapter for iSeries 59167 A program was called twice in some CALLRPG requests.
Adapter for iSeries 60331 The adapter-specific UseDefaults property in the adapter template should be made Boolean and should be selected from a list having values "true/false".
Adapter for JDBC 28594 DeltaUpdate verb support should be added in the ODA.
Adapter for JDBC 29080 The adapter calls are not obeying the timeout.
Adapter for JDBC 29375 Sequences for DB2(R) should be supported.
Adapter for JDBC 29822 The connector generates an unsupported ObjectEventID format.
Adapter for JDBC 31569 The adapter should return output parameters even when the result set is "true" and empty.
Adapter for JDBC 32392 When the database fails, the polling connection is not refreshed in the Event Monitor.
Adapter for JDBC 32473 The ODA should expose nicknames.
Adapter for JDBC 34612 The number of commits in the connector should be reduced.
Adapter for JDBC 35078 The adapter does not shut down when polling fails, if the SPBeforePoll call is enabled.
Adapter for JDBC 35258 The ability to print stack traces for exceptions caught at major events in the adapter has been added.
Adapter for JDBC 60212

If a parent object with a key attribute having UID=AUTO in the application-specific information and with a child object that has an attribute referring to the parent key as a foreign key, the child object's foreign key is not populated with the new identity column value from the parent during a create operation.

Adapters for JDBC and Oracle Applications 28588 Traceable SQL messages are built only if tracing is enabled.
Adapters for JDBC and Oracle Applications 28591 Improvements have been made to the tracing mechanism.
Adapters for JDBC and Oracle Applications 28868 Stored procedures should be supported for the DeltaUpdate verb.
Adapters for JDBC and Oracle Applications 30436 A null pointer exception occurs when the event or archive time is blank.
Adapters for JDBC and Oracle Applications 30774 Performance improvements are needed for the adapter.
Adapters for JDBC and Oracle Applications

31759

Unsubscribed events now generate a message of the proper severity to send e-mail notification. This now occurs when a subscribing collaboration is stopped.
Adapters for JDBC and Oracle Applications 32390 There is a problem with SQL scripts in the dependencies subdirectory.
Adapters for JDBC and Oracle Applications 32484 The connector must change the way it treats date fields.
Adapters for JDBC and Oracle Applications 32508/14585 The JDBC connector uses the default value for polling if the object key uses a name-value pair.
Adapters for JDBC and Oracle Applications 35078 The adapter should return APPRESPONSE TIMEOUT if the SPBeforePoll call fails.
Adapters for JDBC and Oracle Applications 35455

For the Delete verb, if the parent business object is a wrapper business object, multiple-cardinality children of the wrapper business object are not deleted.

Adapters for JDBC and Oracle Applications 35954

When using Copy Attributes to propogate values through a hierarchy of business objects, such values were not being propagated for N-cardinality child business objects.

Adapters for JDBC and Oracle Applications 36188 The connector property RetryCountAndInterval does not work for child business object data.
Adapters for JDBC and Oracle Applications 43390 Support is needed for the retrieval of large CLOB objects as parameters of stored procedures.
Adapters for JDBC and Oracle Applications 58660 The adapter returns an error message if the output parameter of a stored procedure is RS (ResultSet).
Adapters for JDBC and Oracle Applications 59112 The adapter fails to open a new database connection after a ping query fails.
Adapters for JDBC and Oracle Applications 59609 The adapter failed to execute the stored procedure associated with AfterRetrieveByContentSP.
Adapters for JDBC and Oracle Applications 59817 The dummy business object created when the result set is null or empty in a retrieveSP for container was not being returned.
Adapter for JMS 35855 During event notification, WebSphereMQ fails to copy the MessageID generated by a different JMS provider to the CorrelationID field of a WebSphere MQ message.
Adapter for JMS 60609 Added support for BIDI enablement.
Adapters for JMS and WebSphere MQ 33728 When unique conversion properties are not configured in the configuration meta-object, the adapter incorrectly maps events to business objects.
Adapters for JMS and WebSphere MQ 36128 The adapter does not initialize when the InputQueue connector property is not configured.
Adapters for JMS and WebSphere MQ 36438 Starting with release 2.5.x of the adapter, conversion property names in the static and dynamic meta-object are case-sensitive.
Adapters for JMS and WebSphere MQ 37094 When multiple input queues are configured for the adapter, the conversion property retrieval mechanism fails while processing in-progress messages.
Adapter for JText  27291 A new-line character in JText log messages causes problems when the messages are viewed through the Log Viewer.
Adapter for JText  35432 When the SortFilesOnTimestamp property is used and a large number of input files are present, JText takes a long time to process them.
Adapter for JText  37132 When the output directory is specified as remote for service calls with the property FTPKeepConnectionOpen set to "true," an exception occurs.
Adapter for JText 43454 When the adapter is polled with the EventExt attribute of the JText configuration meta-object MO_JTextConnector_Default set to blank, the polling fails and the adapter terminates.
Adapter for JText 44014 The adapter does not start as a service through the Windows Control Panel.
Adapter for JText 46046 When a large business object (approximately 5 MB) is sent during either event processing or service calls, it results in an OutOfMemory error.
Adapter for JText 46499 JText does not archive more than one file that matches the file mask in a Partitioned Data Set (PDS) system.
Adapter for JText 46569 When the FTPArchiveDir and FTPRenameExt properties are specified for an MVS Sequential Data Set (SDS), the connector fails to archive files.
Adapter for JText 46570 During event processing, when an input file with the same name is polled again on an MVS system, the file is not archived successfully.
Adapter for mySAP 33314 During request processing, the ObjectEventId is dropped in the response object. This has been corrected. In the Extension Module, the value of ObjectEventId is preserved for request processing.
Adapter for mySAP 34205

When the SAP server shuts down abruptly, request events are no longer lost during request processing.

Adapter for mySAP 34614

The value of ObjectEventId is preserved for request processing.

Adapter for mySAP 35192

Performance was degrading when the Request directory filled up with many status files for ALE request processing.

Adapter for mySAP 35387

The setting of the space characters that pad the fields in a segment when sending it to SAP must be corrected.

Adapter for mySAP 35673

When using IDOC files from SAP R/3 4.7 systems, the application-specific information generated in the business objects was incorrect.

Adapter for mySAP 36006

The adapter was not using the configured connector property value for AleEventDir for creating the Request folder. The Request folder holds the status message files for ALE request processing using TID management.

Adapter for mySAP 37005

Child business objects must be processed correctly when the ABAP BAPI_Handler is used.

Adapter for mySAP 37323

Events sent when the connector is paused no longer go to the archive table with the status of 3. They remain in the event table ready to be polled with a status of Q. This change requires importing transports from the following files: 4_Delivery.zip and 4_Utilities.zip.

Adapter for mySAP 37455

When processing IDOCs with an empty text segment, the adapter no longer fails with an MQ error.

Adapter for mySAP 42920

A Search By Description BAPI/RFC down the RFC node was not generating its corresponding business object correctly.

Adapter for mySAP 44080

When the adapter is paused some events disappeared. With this fix, all events are accounted for in the event queue.

Adapter for mySAP 44697

Support for MS932 Japanese characters is now supported. The configuration property PartnerCharset must be used to specify the PartnerCharset encoding.

Adapter for mySAP 45003

When the connector is paused, events were sent to the error queue. With this fix, the events remain in the event queue to be reprocessed again when the connector resumes.

Adapter for mySAP 58492

The restart/retry feature was not restarting the connector correctly.

Adapter for mySAP 58858

The adapter no longer throws NullPointerException in cases of wrong control record data (SAP ALE).

Adapter for mySAP 58954

If a business object is not supported, the adapter should not terminate. Instead, an error should be logged and the adapter kept live.

Adapter for mySAP 59037

When the Dummy_key attribute does not exist in the business object, the adapter failed. With this fix, the adapter processes the event successfully without dummy_key mapping.

Adapter for mySAP 59080 RfcServer no longer terminates when an invalid response message is received from WebSphere Message Broker.
Adapter for mySAP 60038

The event linkage mechanism works on the SAP 4.7 system with this fix. This change requires importing transports into the 47_EventTriggering.zip file.

Adapter for mySAP 60078

The adapter no longer hangs after sending a business object with CR LF characters.

Adapter for mySAP 60220

The ODA was failing to create business objects that contain the same structure in the import and export fields. With this fix, the structures are uniquely renamed and the object is created successfully.

Adapter for Web Services 28828 The connector fails when instantiating the protocol configuration meta-object that contains required attributes.
Adapter for Web Services 30117 While the adapter for Web Services is terminating gracefully, if a poll cycle is initiated, or if the adapter is manually terminated, it exits immediately without releasing resources.
Adapter for Web Services 30302 The application-specific information property ws_prop_name is not used for propagating user-defined protocol properties.
Adapter for Web Services 30580 The Web Services Description Language (WSDL) ODA disconnects when it encounters a circular schema reference.
Adapter for Web Services 30816 The HTTP handler should read no more than content-length sized payload from the response.
Adapter for Web Services 36663 The SOAP data handler does not populate the business object corresponding to an element having only attributes and no child elements.
Adapter for Web Services 37217 The SOAP data handler does not populate business objects with elements having attributes and no children.
Adapter for Web Services 47158

The adapter appends a new line to the beginning of the content returned from a call to a child data handler. The SOAP DataHandler meta-object now supports new property UseNewLine with possible values of true or false. The value of true adds a new line at the beginning of a result obtained from a call to a child data handler. A value of falseappends the content to the element opening tag. The default value is true for backward compatibility. For example:

- UseNewLine is set to true
<ParentElement>
content obtained from a child datahandler</ParentElement>
- UseNewLine is set to false
<ParentElement>content obtained from a child datahandler</ParentElement>
Adapter for Web Services 59943

The SOAP/JMS protocol handler does not fail a request that has no response within configured ResponsetWaitTimeout value.

Adapter for Web Services 60193

The SOAP/HTTP(S) handler ignores the synchronous response payload if the HTTP header Content-Length is not specified.

Adapter for WebSphere Commerce NA Support for version 5.6 of WebSphere Commerce Business Edition was added.
Adapter for WebSphere Commerce JR20054/CR36128 A problem in the adapter was fixed that caused the adapter to fail during initialization when the connector-specific property InputQueue was not configured.
Adapter for WebSphere Commerce JR20054/CR36438 A problem in the adapter was fixed that enforced case-sensitivity of meta-object application-specific information and attribute names.
Adapter for WebSphere Commerce JR20054/CR33728 A problem in the adapter was fixed that allowed incorrect caching of conversion properties when non-unique InputFormat/InputQueue values were configured in the static meta-object attributes.
Adapter for WebSphere Commerce JR20054/CR37094 A problem in the adapter was fixed that caused the adapter to incorrectly map the conversion properties to event messages when in-doubt events were processed with multiple input queues configured for the adapter.
Adapter for WebSphere MQ 34969 During synchronous event processing, the adapter does not send data handler errors to the report message.
Adapter for WebSphere Commerce 44680 The adapter was unable to restart while using the RestartRetry configuration.
Adapter for WebSphere Commerce 59006 Support for custom security exits was added.
Adapter for XML 6526
  • The asynchronous protocol handler checks and truncates the MIME type if needed before attempting the conversion to an HTTP message from a business object.
  • The asynchronous protocol handler includes additional timeout/retry functionality.
  • The asynchronous protocol handler includes the option to perform base64 encoding.
Adapter for XML 32205 When a request is sent to the connector (which is using a synchronous HTTP protocol handler), if the destination site is busy, then the adapter waits indefinitely, causing the collaboration thread to wait indefinitely. When the number of waiting threads increases to the number in the concurrent events property in the collaboration, no more events are processed. InterChange Server must be rebooted.
Adapter for XML 59588 When the business object contains Japanese characters, the characters are corrupted when the business object is received on the Web server.
XML data handler 31537 The data handler is not backward-compatible with some business object definitions.
XML data handler 32710 The xml:lang attribute in the business object is not populated.
XML data handler 35141 The data handler returns an error during XML-to-business-object translation when the document type declaration or processing instructions are missing.
XML data handler 35148 The data handler does not support documents in UTF-16.
XML data handler 42671 The data handler incorrectly translates XML documents containing a set of brackets ("[ ]") as element data.
XML data handler 44470 The XML ODA does not handle schemas that import other schemas into a different namespace and have complex types or elements with the same name. The ODA prints "Error in call core.setAgentProperties: schema for type QuoteSubLine not found: during business object generation when this error occurs.

Installation requirements

Whether you are installing the software from the CD or downloading it from Passport Advantage and installing it from a local directory, refer to WebSphere Business Integration Server Express Installation Guide for Linux.

Limitations

The WebSphere Business Integration Connect - Express product will not be available with WebSphere Business Integration Server Express Plus, version 4.4, until the following dates:

If you receive WebSphere Business Integration Server Express Plus, version 4.4, media before these dates, you may:

Known problems and workarounds

The following problems have been found in this release:

Component Tracking number Description
Server 45170/45175 The composite identity relationship (an identity relationship used to relate both parent business object and child business object) feature does not function in this WebSphere Business Integration Server, version 4.4.
Server 45460 If WebSphere InterChange Server Express or adapters or both are shut down and restarted many times (possibly thousands of times over a long period) without restarting the Naming Server, the Naming Server does not release memory.

Workaround: If this problem occurs, shut down WebSphere InterChange Server Express and the adapters, shut down the Naming Server, then restart the server and the adapters.

Installer 43593 The title text may be truncated on the message dialog boxes due to its length; however, the intended content of the message displays.
Installer 45860 If you upgrade WebSphere Business Integration Server Express from Fix Pack 4.3.1.1 to version 4.4, the 4.3.1.1 uninstallation program remains on the machine in the install_location\_uninst directory.

Workaround: Do not run the uninstallation program contained in the install_location\_uninst directory to upgrade to version 4.4 because it affects the installation. You can remove the directory manually. However, leaving the directory in place does not affect the functionality of the product.

ADK 66604 If an adapter and WebSphere InterChange Server Express are running and the server is shut down and restarted, the adapter attempts to connect to the server based on the RestartRetryCount and RestartRetryInterval properties specified for that adapter. However, if the retry counts are exhausted and the server is not restarted within that time, the adapter does not restart and an exception occurs. This situation occurs only if JMS is the transport. If the server is restarted after this exception occurs, the adapter still cannot connect to the server. The adapter must be stopped and restarted manually to connect to the server.
Launchpad 37017 When running the Launchpad from a CD, the Launchpad splash screen hangs at the initial window. Some CD drives labeled DVD Multi Player & Compact Disk Rewritable High Speed (the drive has to be both of these) may cause the Express Plus CD to hang during installation, and the splash screen will hang indefinitely.

To work around this, if possible, configure the CD drive to remove the high speed capability during installation. If this is not possible, run the installation from the electronic software delivery (ESD) image. You can also try copying the contents of all the CDs to the hard drive.
System Monitor 43759 If you are using Netscape 4.7x with double byte character languages, the characters may not display in Netscape. To configure Netscape to enable the double byte character set characters to display, follow these steps:
  1. From the View menu within Netscape, choose Character Set > Unicode (UTF-8).
  2. From the View menu, choose Character Set > Set Default Character Set.
  3. From the Edit menu, choose Preferences.
  4. In the Preferences window, choose Appearance > Fonts.
  5. In the For the Encoding field, choose Unicode.
  6. In the Variable Width Font field, choose Lucida Sans Unicode.
  7. Select Use my default fonts, overriding document-specified fonts.
  8. Click OK.
Web-based Deployment 45346 When WebSphere Application Server 5.1.1 is used as the application server for Web deployment, the Web Deployment Tool cannot connect to WebSphere Business Integration Server Express using HTTPS. This problem is due to the WebSphere Application Server, version 5.1.1, default system property java.protocol.handler.pkgs, which is set to com.ibm.net.ssl.internal.www.protocol. This property must be set to com.ibm.net.ssl.www.protocol for HTTPS to work correctly. To reset the property, follow these steps:
  1. Go to Start > Programs and find the WebSphere Application Server 5.1.1 shortcuts.
  2. Click Start Application Server
  3. Open the Administrative Console (local)
  4. Log in to the console (use ibm for userid)
  5. Click Servers in the left panel
  6. Click Application Servers
  7. Click ICSMonitor
  8. Click Process Definition
  9. Click on Java Virtual Machine
  10. Scroll to find "Generic JVM arguments and append the following to the end of the existing arguments:

    -Djava.protocol.handler.pkgs=com.ibm.net.ssl.www.protocol
Internationalization 70964 A set of messages can be generated by InterChange Server Express as a diagnostic aid for solution development. These messages are not translated and are available only in English. Some of these messages might display during normal operation of the product.

Adapters Tracking number Description
Adapter for eMatrix 66617 The adapter documentation incorrectly specifies "ArchiveProcessed" property; however, the configuration template correctly specifiies "ArchivedProcessed"
Adapter for iSeries 45275 Three properties (TracefileName,Messagefilename and Tracelevel) in the ODA for iSeries take their default values from XML files that are shipped with Adapter Framework, version 2.6, and are not visible in the Business Object Designer tool.
Adapter for iSeries 45475 The iSeries ODA requires the following workaround for selecting IFS files.

Workaround: Provide the full iSeries IFS file path in the iSeriesFilePath property, for example, /QSYS.LIB/PNPLIB.LIB/SRCPF.FILE/. After the path is set, the ODA lists the files under this folder. Choose the appropriate files for business object generation. For more information, refer to the technote at http://www-1.ibm.com/support/docview.wss?rs=695&context=SSMKUK&dc=DB520&q1=iseries&uid=swg21188205&loc=en_US&cs=utf-8&lang=en

Adapter for JDBC NA WebSphere Business Integration Adapters and InterChange Server Express do not support bidirectional characters as part of business object and business object attribute names.

Workaround: After the business object template is generated based on the database tables with column names containing bidirectional characters, rename all business object names and attribute names that include non-Latin characters to include only Latin characters.

Adapter for JDBC NA In the JDBC ODA, Hebrew table and column names for the DB2 OS/390 IBM Universal JDBC driver restrict how non-Latin characters should be specified as part of an SQL query. In particular, it does not correctly process SQL queries having bidirectional characters as part of table and column names, if the table and column names are not enclosed in parentheses.

Workaround: Because business object templates generated by the JDBC ODA do not enclose table and column names in parentheses in the application-specific information (ASI), if you are using those templates for communication with OS/390 DB2 through the IBM Universal JDBC driver, modify the table and column names in the business object templates as follows:

  • Replace all TN=<table name> appearances in the business object level ASI with TN="<table name>"
  • Replace all CN=<column name> appearances in the business object attribute level ASI with CN="<column name>"
Adapter for JDBC NA Due to limitations of the DB2 OS/400 IBM Universal JDBC driver, table column names that include bidirectional characters are excluded from the generated business object template. Consequently, only columns containing Latin names are considered during business object template generation. If a table has no Latin columns, no business object template is generated.
Adapter for JDBC 43503 When you use the ODA to generate a business object from a DB2 database server running on Linux, Business Object Designer hangs. This occurs because the DB2 JDBC Applet Server does not start.

Workaround: Log in to the DB2 server and run the following command: db2jstrt LISTENPORT.

Adapters for JDBC and Oracle Applications 41966 The JDBC ODA cannot generate a business object from the nickname of a stored procedure when using the Oracle thin driver, because the driver does not support analysis of Synonyms to StoredProcedures.

Workaround: Either use the actual stored procedure name to generate the business object using the ODA, or construct the business object manually.

Adapters for JDBC and Oracle Applications 41967 Adapter Framework cannot process more than 20,000 property values when displaying the ODA configuration properties or when prompting for business object definition-specific properties. Ensure that no more than 10,000 values are returned in the drop-down list, or the ODA hangs.
Adapters for JDBC and Oracle Applications 43246 The start script for the Oracle Applications ODA includes the xworacle.jar file in the DRIVERPATH, which does not list all tables in the Oracle database as expected.

Workaround: To list all the tables in the database, use the native JDBC driver-classes12.zip file provided by Oracle.

Adapters for JDBC and Oracle Applications 43888 The JDBC ODA shows stored procedure node names with a ";1" suffix when analyzing an SQL Server database. This is a problem with the SQL Server database for which there are no fixes.

Workaround: Manually remove the ";1" in the application-specific information generated for the stored procedure attributes in the generated business object.

Adapters for JMS and WebSphere MQ 45751 Message key 21021 is missing from WebSphere MQ message file. This is a generic error message: "Failed to complete processing. See previous error message(s) for details".
Adapter for JText NA

This release includes the following limitations in the adapter:

  • JText has two processing modes: text (normal mode) and binary. The binary mode requires an appropriate data handler to be plugged in.
  • JText cannot rename a data set that uses MVS naming conventions.
  • Archiving logic in MVS is different from that in UNIX(R) and Windows(R) environments because of MVS limitations.
  • JText can poll remote files based on a timestamp from an FTP site only if the FTP server supports the modification date and time (mdtm) command. Enabling this feature can reduce performance, especially if there are a large number of event files in the event directory.
  • When the LargeObject meta-object attribute in the JText adapter is set to true, the adapter follows a different archiving methodology. In this methodology, if an event file has multiple business objects, archiving is done only after all the business objects for that event file are processed. Also, the original file is not archived in case the business object processing for all the business objects for that event file results in a failure or an unsubscribed status. The original file is archived only when the business object processing for the event file results in a mixed status, for example, a combination of successes and failures.
  • Bidirectional support for the FTPFileEventMask property does not exist in this release, due to the following restrictions:
    • Only the VM operating system allows the definition of file names that include bidirectional characters.
    • FTP support in the JText connector does not allow communication with VM FTP.
Adapter for JText 33378 When large numbers of request calls are made, JText writes out only n-1 files when n calls are made.
Adapter for JText 34834 Secure FTP support is required by JText. The password field, which is visible to the JText system administrator, is not visible to anyone with Secure FTP.
Adapter for JText 35571 A provision to specify EOF as a value to the EndBODelimiter in the binary processing mode is required.

Workaround: For all files with no other EndBODelimiter than the EOF itself, use a Hex editor to include a couple of bytes (for example, FF02) as the delimiter, and specify the bytes as the EndBODelimiter.

Adapter for JText 58964 For FTP servers that have non-Latin characters in their file paths, JText uses the following encoding conventions:
  • ISO-8859-8 if the locale is Hebrew
  • ISO-8859-6 if the locale is Arabic
  • ISO-8859-1 for all other cases
Adapter for Lotus Domino 31633 In a UNIX environment, a connector_manager_adapter script is generated by the Installer. The script references adapterEnv.sh, which was introduced with version 2.4.0 of Adapter Framework. If you are running an older version of Adapter Framework, adapterEnv is not available. To run this version of the adapter with an older version of the Framework, change the reference from adapterEnv.sh to CWSharedEnv.sh in the connector_manager_adapter script.
Adapter for mySAP 70689 The adapter for mySAP throws an OutOfmemory exception when processing large IDOCs.

Workaround: See the technote Memory utilization for the IBM WebSphere Business Integration Adapter for mySAP.com v6.0.0 (ALE module).

Adapter for Oracle Applications 41977 When using the DataDirect SQL driver, the Oracle Applications ODA does not generate appropriate application-specific information for stored procedures that return result sets. The driver does not support analysis of the return type when the stored procedure returns a result set. For example, the stored procedure returns @RETURNVALUE, which the ODA cannot use to generate an attribute.

Workaround: Manually add the attribute in the business object definition.

Adapter for Oracle Applications (Adapter Framework) 66615 The adapter for Oracle fails on a retrieve or retrieveall operation with the following error when using the verb level application-specific information: "java.sql.SQLException: ORA-00933: SQL command not properly ended". This problem is caused by an Adapter Framework problem and occurs only when using JMS as the DeliveryTransport.

Workaround: Set the DeliveryTransport standard property to IDL.

Adapter for Web Services NA In the XML ODA, bidirectional characters are not supported as part of business object and business object attribute names.

Workaround: After a business object template based on the XML/XSD files with attribute/element names containing bidirectional characters is generated, rename all business object names and attribute names that include non-Latin characters, so that they contain only Latin characters.

Adapter for Web Services 23993

When the WSDL ODA encounters multiple inline schemas that import each other without providing schema locations, it logs warnings or errors; however, the business objects are generated properly.

Workaround: Separate each schema into an individual file and update the imports/includes to contain the appropriate file locations. Import these individual schema files into the WSDL document using an import statement with the appropriate file locations.

Adapter for Web Services 24662

When WebSphere MQ 5.3 CSD03 is used as the JMS provider, the adapter JMS listener cannot read message bodies after moving the message from the input queue to the in-progress queue. This is a problem with the WebSphere MQ application.

Adapter for Web Services 59428 The Web Services Description Language (WSDL) ODA cannot access WSDL files through URLs that contain non-English characters when destination URLs are specified in the non-encoded form. However, the WSDL ODA can successfully process files with the local paths containing international characters.

Workaround: Use an encoded URL, or save the WSDL file to the local storage and use the local path instead of the HTTP URL.

Adapter for Web Services 59584 The adapter cannot send HTTP(S) requests to URLs that contain non-English characters when destinations URLs are specified in the non-encoded form.

Workaround: Use encoded URLs.

Adapter for Web Services 59634 The adapter cannot generate a response to synchronous listener requests that use non-TLOs (top-level business objects).
Adapter for WebSphere Commerce 42516 When WebSphere Commerce, Business Edition, version 5.5 with Fix Pack 4 (or an earlier version) is used on the commerce server, the store user cannot be created properly with the adapter for WebSphere Commerce. The store user cannot log onto the store because of improper authority. A Websphere Commerce efix is required to fix this problem. The efix is JR20090 on WebSphere Commerce 5.5 with Fix Pack 4.
Adapter for WebSphere MQ 34688 WebSphere MQ version 5.3 at CSD06 or lower does not support bidirectional data in the JMSCorrelationID field; therefore, to fully utilize the bidirectional capabilities of the adapter, you must use WebSphere MQ version 5.3 at CSD07.
Adapter for WebSphere MQ 58988 The adapter hangs when deployed on a Linux(TM) multiprocessor system. This problem is caused by a known Linux JDK 1.4.2 problem that causes a hang during garbage collection. (The PMR number opened for this JDK issue is 27182.001.866.)

Workaround: Modify the adapter start script to set the JVMArgs variable with the option "-Xgcthreads1" as shown in the following example:
JVMArgs="-Xgcthreads1 %JVMArgs%"

Documentation

Product documentation is not included as part of the product package, either by CD or electronic product distribution. The documentation for this product can be found in the IBM WebSphere Business Integration Server Express InfoCenter.

Adapter user guides NA

In this release, some adapter guides, as listed below, have not been revised with the product names and platform-support and feature restriction information that is specific to the WebSphere Business Integration Server Express and Express Plus releases. Instead, the latest versions of the guides from the IBM WebSphere Business Integration Adapters product release have been provided. This applies to the following guides:

Adapter for eMatrix User Guide
Adapter for Healthcare Data Protocols User Guide
Adapter for HTTP User Guide
Adapter for iSeries User Guide
Adapter for JMS User Guide
Adapter for Lotus Domino User Guide
Adapter for mySAP.com (for SAP R/3 V. 3.x) User Guide
Adapter for Oracle Applications User Guide
Adapter for SWIFT User Guide
Adapter for TCP/IP User Guide
Adapter for Web Services User Guide
Adapter for WebSphere Commerce User Guide
Adapter for WebSphere MQ User Guide

These guides contain up-to-date information for the adapter features as delivered in the the IBM WebSphere Business Integration Adapters product release. You may notice differences between the names used for certain tools referenced in these guides and the names used for tools delivered for the IBM WebSphere Business Integration Server Express and Express Plus product. Additionally, the following feature references that may appear in these guides are not valid for the WebSphere Business Integration Server Express and Express Plus releases:

  • References to integration brokers other than InterChange Server Express
  • References to MQ as a delivery transport mechanism
  • References to implementation of the connector agent using MQ Internet Pass-through, which enables implementation of the connector agent with InterChange Server Express installed on the other side of an Internet firewall
  • References to connector agent parallelism
  • References to ITLM signature support

Additionally, the Linux platform-support statement details in the "New in this release" and adapter-platform sections of the guides listed above are not current. For an adapter in this release that is listed as supporting Linux, the Linux versions supported are as follows:

  • Red Hat Enterprise Linux WS/AS/ES 3.0 Update 2, Intel (IA32)
  • SuSE Linux ES 8.1 SP3, Intel (IA32), and SuSE Linux ES 9.0, Intel (IA32)
Platform-specific information is commonly relevant for the following sections of the guides:
  • Platform support statements
  • Path name and file name references
  • Creation and use of startup scripts
  • Instructions for starting and stopping the connector
  • Instructions for creating a new configuration file
  • Instructions for setting Security properties in Connector Configurator

Information about implementation and administrative tasks relevant to all adapters supported on Windows, Linux, or OS/400 and i5/OS platforms is available in the System Implementation Guide and the System Administration Guide. For more information and for questions about feature limitations of adapters, visit the WebSphere Business Integration Server Express support Web site.

User guides for:
Adapter for eMatrix
Adapter for iSeries
Adapter for JDBC
Adapter for mySAP.com
Adapter for Oracle Applications
Adapter for Web Services
66473 These guides describe ODA initialization properties that are available in Step 2 of the Business Object Wizard. The following ODA initialization properties are listed in the guides, but are not available by default through the Business Object Wizard:
  • TraceFileName
  • TraceLevel
  • MessageFile
For an ODA that has BIA_ or other such prefix for the message files, make sure that the file oda.dd.xml is present in the ODA/adapterNameODA folder. Also, make sure that the entry for messagefile has the corresponding prefix set in the oda.dd.xml file, for example:
<messagefile prefix="BIA_">></messagefile>

This ensures that the ODA starts up fine after loading the proper message file.

IBM software support

Support information about this product can be found on the WebSphere Business Integration Server Express support Web site.

To receive weekly e-mail notifications about fixes and other news about IBM products, follow these steps:

  1. From the Support site, click My support in the upper-right area of the support page.
  2. If you have already registered for "My support," skip to the next step. If you have not registered, click register now on the "My support" sign-in page, using your e-mail address as your IBM ID.
  3. Sign in to "My support."
  4. On the Edit profile tab, click Add Products.
  5. From the Products drop-down list, select Software or any other product category. This action generates a second drop-down list.
  6. From the second drop-down list, select a product segment, for example, Application servers. A third drop-down list is generated.
  7. From the third drop-down list, select a product sub-segment, for example, Distributed Application & Web Servers. A list of applicable products is displayed.
  8. Check the boxes next to the products for which you want to receive updates, for example, IBM HTTP Server and WebSphere Application Server.
  9. Click Add products.

Contacting IBM Software Support

IBM Software Support provides assistance with product defects. Before contacting IBM Software Support, your company must have an active IBM software maintenance contract, and you must be authorized to submit problems to IBM. The type of software maintenance contract that you need depends on the type of product you have:

If you are not sure what type of software maintenance contract you need, call 1-800-IBMSERV (1-800-426-7378) in the United States, or, from other countries, go to the contacts page of the IBM Software Support Handbook on the Web (techsupport.services.ibm.com/guides/contacts.html), and click the name of your geographic region for phone numbers of people who provide support for your location.

Follow the steps in this topic to contact IBM Software Support:

  1. Determine the business impact of your problem.
  2. Describe your problem and gather background information.
  3. Submit your problem to IBM Software Support.

Determine the business impact of your problem

When you report a problem to IBM, you will be asked to supply a severity level. Therefore, you need to understand and assess the business impact of the problem you are reporting. Use the following criteria:

Severity 1 Critical business impact: You are unable to use the program, resulting in a critical impact on operations. This condition requires an immediate solution.
Severity 2 Significant business impact: The program is usable but is severely limited.
Severity 3 Some business impact: The program is usable with less significant features (not critical to operations) unavailable.
Severity 4 Minimal business impact: The problem causes little impact on operations, or a reasonable circumvention to the problem has been implemented.

Describe your problem and gather background information

When explaining a problem to IBM, be as specific as possible. Include all relevant background information so that IBM Software Support specialists can help you solve the problem efficiently. To save time, know the answers to these questions:

Submit your problem to IBM Software Support

You can submit your problem in one of two ways:

If the problem you submit is for a software defect or for missing or inaccurate documentation, IBM Software Support will create an Authorized Program Analysis Report (APAR). The APAR describes the problem in detail. Whenever possible, IBM Software Support will provide a workaround for you to implement until the APAR is resolved and a fix is delivered.

IBM publishes resolved APARs on the IBM product support Web pages daily, so that other users who experience the same problem can benefit from the same resolutions.

Copyright IBM Corp. 2004, 2005