webMethods JDBC Adapter 6.0.3 December 2003 _________________________________________________________________ Welcome to the webMethods solution for database integration. You use the webMethods JDBC Adapter with the webMethods Integration Server and the webMethods Developer, which are components of the webMethods Integration Platform. This file provides important information for using the webMethods JDBC Adapter 6.0.3. For information about new functionality in this version of the JDBC Adapter, see the Release Notes located in the \packages\WmJDBCAdapter\pub directory. For information about the webMethods Integration Platform, see the webMethods Integration Platform Release Notes. You can also view these documents from the webMethods Advantage Web site. Contents: 1.0 Getting Started 2.0 Documentation 3.0 Known Problems and Limitations 4.0 Usage Notes 5.0 Globalization 5.1 Database Configuration 5.2 Known Globalization Limitations 5.2.1 General 5.2.2 Microsoft SQL Server 2000 Driver for JDBC Version 2.2.0019 Problems and Limitations 5.2.3 Oracle JDBC Driver Problems and Limitations 6.0 Deprecated Components 7.0 Fixes and Enhancements 7.1 Fixes in JDBC Adapter 6.0.3 8.0 Copyright Information 9.0 Contacting Us 1.0 Getting Started The webMethods JDBC Adapter Installation Guide version 6.0.3 provides detailed instructions for installing the webMethods JDBC Adapter. The User's Guide provides details about creating and managing JDBC Adapter connections, adapter services, and adapter notifications. 2.0 Documentation The webMethods JDBC Adapter Installation Guide is a PDF file on the webMethods download site. The webMethods JDBC Adapter User's Guide is a PDF file in the directory where you installed the webMethods Integration Platform, under the following directory: IntegrationServer\packages\WmJDBCAdapter\doc To view the documentation, you must have Adobe Acrobat Reader 4.0 or later. You can download and install Acrobat Reader from: http://www.adobe.com/support/downloads/main.html Online help is also available for each JDBC Adapter screen in the webMethods Integration Server Administrator and webMethods Developer. You can access the help using the Help link at the top right corner of the screen. 3.0 Known Problems and Limitations Appendix C in the webMethods JDBC Adapter User's Guide version 6.0.3 lists problems and limitations specific to the JDBC Adapter's supported JDBC drivers and databases. 1-N4CMB To avoid a file conflict when using Informix, you must disable the WmTomcat package in the Integration Server. Be aware that this also disables support for JSPs. 1-MC7TL You cannot enable CJDBC 3.2 driver connections using JVM 1.4.1_01, 1.4.1_03, or 1.4.1_05. 1-MMJO8 The SelectSQL service displays the value of the Hour field as one more than the actual value in the database. If the DATETIME column data type in the database is created with YEAR or MONTH as the upper range (and the HOUR field or lower is selected as lower range), the Select service displays the HOUR field correctly; otherwise, the HOUR field will be one more than the actual value. 1-NNI6R For automatic notifications, if you set the JDBC data type for a TIMESTAMP column to java.sql.Timestamp, the notification internally converts it to java.util.Date. This causes the timestamp value to lose its fractional seconds component. 1-NSJHI When using the BatchInsert or BatchUpdate service with Sybase, you could receive the following error message if the service attempts to return a large number of records: "JZ0BE:BatchUPdateException:Error occurred while executing batch statement:Too many parameters--symbol table overflow". To resolve this problem, apply a jConnect 5.5 emergency bug fix (EBF 11473), which is available at: http://downloads.sybase.com/swd/swx/sdfile.stm. 1-GNUOD The JDBC Adapter does not support the datalink DB2 data type when using the adapter with DB2 for AS/400 or DB2 for OS/390. 4.0 Usage Notes None. 5.0 Globalization webMethods JDBC Adapter 6.0.3 conforms to the international standards of webMethods and includes support for operation in any country, locale, or language. Support for character encodings and proper formatting, display, and validation of data (such as number and date formats) has been provided throughout the product. webMethods JDBC Adapter 6.0.3 is fully compliant with the requirements of the Unicode Standard, version 2.1.8 (see http://www.unicode.org). If you expect to display non-English data in your webMethods tools, you need to ensure that an appropriate font is installed in your operating environment. You should test to see whether hollow boxes or black squares appear where you would expect to see non-English data. If you see problems, modify your JRE font.properties file to reference the font on your system. Information about modifying the font.properties file can be found on Sun's Java Web site (for the JRE provided with this release, see: http://java.sun.com/j2se/1.3/docs/guide/intl/fontprop.html) Or refer to the document located at: http://www.unicode.org/help/display_problems.html. 5.1 Database Configuration The configuration of your database character encoding affects which characters can be stored in it. Characters that are not included in the character encoding you chose when installing your database will be lost when stored by the adapter in that database. Select the most appropriate Unicode encoding for your database character set. Some databases use a different SQL type for Unicode text. For example, Microsoft SQL Server uses the nchar, nvarchar, and ntext types to store Unicode. For these databases, you might need to alter your schema in order to use Unicode. Consult your database vendor's documentation for information about setting the character encoding of your database and environment. 5.2 Known Globalization Limitations This section lists the adapter's known globalization limitations. 5.2.1 General 5.2.2 Microsoft SQL Server 2000 Driver for JDBC Version 2.2.0019 1-GMSI1 There is a known issue in the JVM regarding the conversion of the Euro (U+20AC) character in Microsoft Codepage 936. The JVM returns an empty string instead of the Euro. This issue has been reported to Sun Microsystems. 1-A09M1 The Password field does not recognize double-byte characters when creating a JDBC Adapter connection to a Microsoft SQL Server 2000 instance. 5.2.3 Oracle JDBC Driver 1-82V28 When performing a SELECT on CHAR columns that contain multi-byte data in some national characters sets such as JA16SJIS, extra spaces are returned in the resulting String. The UTF8 and AL32UTF8 Oracle character sets do not have this problem in the JDBC thin driver. 1-88KFD The adapter does not support setting the locale or character encoding per adapter connection. Character encoding is handled by the JDBC driver internally. The locale may affect certain field types. You should use care when mapping Strings to or from date, time, and numeric database fields, to ensure that values are properly interpreted. The following limitations are related to configuring a service or notification in one locale and then editing that service or notification in a different locale. Metadata that is configured in one locale may not be valid with another locale editor. If you encounter this problem, you must reload the service or notification and then reconfigure the corresponding field because the data with other locale will not be valid with the editor's current locale. 1-NL4E9 \ 1-NNIST For all adapter service and adapter notification templates that contain Table tabs, the Table Name disappears after . 1-NL8MR In the StoredProcedure service template and the StoredProcedureNotification template, the Enable Procedure Name Lookup field on the Call tab can be set to TRUE or FALSE. If you set the field to TRUE in the JDBC Adapter 6.0.3 Japanese Language Pack with the Integration Server 601 Janguage Pack a Japanese platform, and then port the service or notification to an English platform, the TRUE value will become FALSE. 6.0 Deprecated Components Version 6.0.3 drops support for the JTOpen v3.3 driver for the AS/400 and replaces it with support for JTOpen v4.1. 7.0 Fixes and Enhancements 7.1 Fixes in JDBC Adapter 6.0.3 1-LRXIN (AJDBC_6-0-2_Fix1) Basic Notifications no longer throw an error after being upgraded from version 6.0 to 6.0.2. 1-M0DE2 (AJDBC_6-0-2_Fix2) The SelectSQL service threw a NullPointerException when it contained count(*) in the expression column. This fix addresses that problem. 1-MO5T7 (AJDBC_6-0-2_Fix3) This fix enables the JDBC Adapter to work with additional database resources. 1-MMJMK (Added feature) The error message for passing a string containing integer data now provides more useful information. 1-NQE0K On an Oracle database, if an Ordered Notification was configured using one schema and its associated connection was configured using a different schema, when you disabled polling for the notification, the buffer table and sequence were dropped correctly, but the trigger was not dropped. This fix addresses that problem by removing the schema prefix in the drop statement. 1-NPSV5 If you used the JDBC Adapter with an Oracle database using the OCI driver and the database went down, the adapter did not reconnect to the Oracle database and you repeatedly received an error message. This fix addresses that problem. 8.0 Copyright Information webMethods Administrator, webMethods Broker, webMethods Developer, webMethods Installer, webMethods Integration Server, webMethods Mainframe, webMethods Manager, webMethods Modeler, webMethods Monitor, webMethods Trading Networks, webMethods Workflow, and the webMethods logo are trademarks of webMethods, Inc. "webMethods" is a registered trademark of webMethods, Inc. All other marks are the property of their respective owners. Copyright (c) 1996-2003 by webMethods, Inc. All rights reserved, including the right of reproduction in whole or in part in any form. 9.0 Contacting Us Authorized technical support contacts can reach webMethods Technical Services for support via: Advantage: http://advantage.webMethods.com E-mail: support@webMethods.com US Phone: 1-888-222-8215 Europe/EMEA Phone: +800-963-84-637 or +31-207783640 Asia/Pacific Phone: +612-8913-1198 or +656-389-3222 Self-service support is also available in the Advantage Knowledge Base and in Advantage Customer Forums at http://advantage.webMethods.com.