November 2007
WebSphere Data Interchange Client v3.3 FIX PACK 3 README.TXT
Included in this section are:
1. List of problems fixed added in Fix Pack 3
2. Server Dependencies
---------------------------------------------------------------
1. Problems fixed in Fix Pack 3 include:
P8011804
DTD CONVERT PROGRAM HELP TEXT EMPTY
P8011851 - PK50701
DATABASE ERROR IMPORTING XSD FILE CONTAINING XML SCHEMA
------------------------------------------------------------------------
2. Server Dependencies
There are no server dependencies with this fix pack.
*************************************************************************
*End of WebSphere Data Interchange Client v3.3 FIX PACK 3 README.TXT**
*************************************************************************
July 2007
WebSphere Data Interchange Client v3.3 FIX PACK 2 README.TXT
Included in this section are:
1. List of problems fixed added in Fix Pack 2
2. Server Dependencies
---------------------------------------------------------------
1. Problems fixed in Fix Pack 2 include:
P8011564
UPDATE CLIENT BUSINESS IDS HELP TEXT
P8011615 - PK35573
SET COMPILE REQUIRED FLAG TO 'NO' WHEN IMPORTING MAP CONTROL STRING
P8011778 - IC51859
ALLOW BLANK VALUE IN CODE LISTS TO BE IMPORTED
P8011807
CLIENT - VARIOUS HELP PROBLEMS, INCLUDING DATA REFERENCES
P8011813
UPDATE THE SERVICE PROFILE HELP
P8011817
MULTIPLE HELP UPDATES
P8011818
VARIOUS HELP UPDATES
P8011819
ADD HELP FOR DATA TRANSFORM MAP DETAILS
P8011832
COPYING RECEIVE USAGES WHEN CHANGING VERSION/RELEASE/AGENCY VALUES
P8011840 - PK46590
ABEND WHEN OPENING VERY LARGE XML SCHEMA
------------------------------------------------------------------------
2. Server Dependencies
There are no server dependencies with this fix pack.
*************************************************************************
*End of WebSphere Data Interchange Client v3.3 FIX PACK 2 README.TXT**
*************************************************************************
April 2007
WebSphere Data Interchange Client v3.3 FIX PACK 1 README.TXT
Included in this section are:
1. List of problems fixed added in Fix Pack 1
2. Server Dependencies
---------------------------------------------------------------
1. Problems fixed in Fix Pack 1 include:
P8011182
SEND/RECEIVE MAP REPORT NOT PRINTING REPEATED SEGMENTS
P8011768
ABEND - COMPILE VALIDATION MAP - ERRMSG SUBSTITUTION
P8011721
FA DATE/TIME FIELDS REVERSED IN DOCUMENT STORE - ENVELOPED
TRANSACTIONS - TRANSACTION INFORMATION TAB
P8011761
CLIENT - VARIOUS HELP PROBLEMS
P8011766
CLIENT - VARIOUS HELP PROBLEMS
P8011777
SQl0969N ERROR OPENING XML/DATA FORMAT DOCUMENTS IN DOCUMENT
STORE
P8011783
XML IMAGE IN DOCUMENT STORE MAY APPEAR OUT OF ORDER
P8011788
ABEND - SAVING DATA FORMAT THAT CONTAINS A RECORD WITH
DUPLICATE FIELDS
P8011790
RECEIVE MAP QUALIFY BY VALUE ON LOOP NOT WORKING
P8011791
ERROR 15458 WHEN DRAG/DROP FIELD TO QUALIFIED ELEMENT IN MAPS
P8011797
997 FA PENDING REPORT BLANK
P8011801
TA1 PENDING FA REPORT INCORRECT
P8011803
HELP FOR TP COMPANY INFO TAB - FIELDS INCORRECT
P8011805
HELP TEXT IN BOLD
P8011810
HELPTEXT 'PAGE CANNOT BE DISPLAYED' - XML LIST IN DOCUMENT STORE
P8011811
HELPTEXT 'PAGE CANNOT BE DISPLAYED' - DF LIST IN DOCUMENT STORE
------------------------------------------------------------------------
2. Server Dependencies
There are no server dependencies with this fix pack.
*************************************************************************
*End of WebSphere Data Interchange Client v3.3 FIX PACK 1 README.TXT**
*************************************************************************
WebSphere Data Interchange Client v3.3 README.TXT
Included in this file are:
1. Installation instructions for WebSphere Data Interchange Client 3.3
2. Installing and Using WDI Client from a Server
3. Creating and Using a Shared CONFIG Database
4. EDI Standards Installation
5. Known problem areas
6. ODBC considerations
7. Document Store considerations
8. Multi-user database considerations
9. Middleware, Upload/Download considerations
10. Creating Multiple PC database configurations
11. Fixes included in this version
-------------------------------------------------------------------
1. Installation instructions for installing WebSphere Data Interchange Client
Start the installation by placing the install CD in the CD-ROM drive.
The install should start automatically, in the event that it does not then
Use Windows Explorer to view the WDI Client directory. Execute WDIClient33.exe
to begin the install. Follow the install wizard instructions to complete
the installation.
If you are converting from a previous version of the Client to
WebSphere Data Interchange Client 3.3, make sure you install to a different
directory. Otherwise, WDI Client 3.3 will overlay the existing WDI Client
version(s). Before installing WDI Client, perform a release migration to
extract data from local databases and/or customization time data from
Server databases. To perform a release migration, perform the following
actions:
1. In WDI Client 3.2 from the View menu on the Menu bar, select the option
“Release Migration”. This option will only appear if all list windows
are closed. When “Release Migration” is selected, a wizard will appear
which will guide you through the release migration process. Include
configuration data if you have Queries, Systems or Customizations that
you want to retain. You may select multiple Systems to export if desired.
Do not export data from a Server database. Data on a Server database will
be migrated by WebSphere Data Interchange 3.2 to 3.3 migration process.
Exporting is tracked using an Status Window, with messages indicating
progress being written to the Execution Status Window as the exporting
progresses.
For WDI 3.2 Windows and AIX customers that created their server database
after CSD16 was installed, see section 6, "Known problems areas",
item c) for a workaround to possible release migration export errors.
2. Install WDI Client 3.3.
3. Open WDI Client 3.3.
4. Using WDI Client 3.3, if you exported configuration data in WDIClient 3.2,
perform a release migration in WDI Client 3.3 to import the configuration
data you exported from your previous version.
5. Using WDI Client 3.3, open the Systems List window. Update any existing
Systems to utilize the correct ODBC Data Source Name (DSN). Add any new
Systems that need to be added. You may wish to set the System background
frame color at this time.
6. Using WDI Client 3.3, use release migration to import each System that
was exported from previous versions.
Migration is complete after this last step. Note that the WebSphere Data
Interchange server migration must be performed before everything is in place
and ready to use. Also note that release migration export from a shared
database, such as a WebSphere Data Interchange Host DB2 database needs to be
performed only once. The release migration import also needs to be performed
only once. Only Systems not shared with other users will need to be migrated
by individual users.
See the WebSphere Data Interchange Users Guide for complete
installation instructions.
Run the application by clicking on the WDI V3.3 Client icon in the IBM
WebSphere Data Interchange V3.3 Client program group.
-------------------------------------------------------------------
2. Installing and Using WDI Client from a Server:
WDI Client can be installed and run to a shared disk on a LAN. Doing this
eases maintenance considerations by allowing a single user to handle maintenance
for all users.
For complete instructions please go to this link on the website:
http://www-1.ibm.com/support/docview.wss?rs=799&context=SSFKTZ&q1
=client+lan+install&uid=swg27007052&loc=en_US&cs=utf-8&lang=en
-------------------------------------------------------------------
3. Creating and Using a Shared CONFIG Database
WDI Client can be run with a shared CONFIG database. This allows multiple
users of WDI Client to share queries and can ease maintenance
considerations.
Please go to this link on the website for the document with complete
instructions:
http://www-1.ibm.com/support/docview.wss?rs=799&context=SSFKTZ&q1
=shared+config&uid=swg27007051&loc=en_US&cs=utf-8&lang=en
-------------------------------------------------------------------
4. EDI Standards Installation
Reference the WebSphere Data Interchange Users Guide, Version 3, Release 3
for instructions on importing the EDI Standards. All files can be found
for downloading on the WebSphere Data Interchange web site:
(www.ibm.com/websphere/datainterchange)
The files are intended to be imported into WDI Client 3.3. The name of the
export/import file (.eif) is the version and release of the EDI standard.
The envelope standards are also available for downloading from the
web site. Once the envelope standards are imported into a
WebSphere Data Interchange System, they must be compiled before
they can be used by Websphere Data Interchange Host.
Web Site address: www.ibm.com/websphere/datainterchange - Support
-------------------------------------------------------------------
5. Known problem areas
a) If an installation is running in client/server mode using
DB/2 as the Host database, some functions are not supported.
Some functions on WDI Client require database support of CASCADE
UPDATE, DB2 does not support this function. Therefore, the RENAME
function is not supported for most complex objects, including Trading
Partner profiles, maps, data formats and EDI standards. RENAME is not
supported for any database that does not support CASCADE UPDATE,
including DB2. Some simple objects will support rename because there
are no referential integrity rules associated with them.
b) Collation tables in the PC Database
Some databases provide a table that dictates a collation sequence
for update and sorting purposes. These tables may not only be used
to determine the order characters will sort in, but also to determine
what character values are equal to one another. For instance, the
default collation table used by Sybase SQL Anywhere specifies that
a character hex 'D5' is equivalent to a character hex '31'. This
causes problems when both of these characters are used as a 'key'
value. A 'duplicate record' message will occur, even though there
appears to be no duplicate keys.
This problem is not likely to occur when using standard characters.
If collation becomes a problem, refer to the documentation for the
database product you are using. Either avoid using characters that
cause these problems, or try to determine how to update the collation
table used by the database product.
c) Customers Migrating from WDI 3.2 MP to 3.3:
The following error may occur during WDI Client Release Migration
export processing for a system where the WDI 3.2 server database was
created after CSD16 was installed.
11041 - A database error occurred while attempting to open table
"EDIENU32.EDIPSCR". ODBC return code is: -1. Description:
SQL0206N "TRACKNM" is not valid in the context where it is used.
SQLSTATE=42703. Internal Codes: State:S0022,Native:-206,
Origin:[IBM][CLI Driver][DB2/NT]
The error is due to the EDIPSCR table missing several new columns,
e.g. "TRACKNM". The fix is to run the CSD16.ddl from the WDI 3.2
ddl directory and re-run the export. Note: "TRACKNM" is only the
first of several columns that are missing.
-------------------------------------------------------------------
6. ODBC Considerations
6.1 What is ODBC?
Open DataBase Connectivity (ODBC) is an industry standard for
the application-to-relational database interface. It allows
the customer to use the database of their choice with an
off-the-shelf application like WDI Client 3.3. For example, if
you would rather that WDI Client 3.3 store its data on your LAN
database server, you can do that. It does not matter which
database is running on your server (DB2 Version 2, SQL Server,
etc.) as long as that database is ODBC compliant, and they provide
you with an ODBC driver that you can load onto the computers that
are running WDI Client 3.3. Most relational databases that you can
purchase today provide this capability.
6.2 What does it mean to be ODBC Compliant?
The topic of ODBC compliance is a complex one. There is more than
one version of the ODBC standard and there are various levels of
compliance (core, minimum and extended). Finally, there are some
small ambiguities in the standard. As a result, it is not possible
to guarantee that any database that claims ODBC compliance will
work with WDI Client 3.3. For information on databases that we know
won't work with WDI Client 3.3, call technical support.
6.3 How is ODBC used in configuring your WDI Client implementation?
ODBC is also fundamental to the Client/Server configuration of
WDI Client. ODBC is used to access the z/OS DB2 database of
WebSphere Data Interchange Host 3.3. Therefore your Client/Server
environment must include an ODBC Client driver for z/OS DB2. This
may be implemented as two separate programs: an ODBC RPC
(Remote Procedure Call) client driver on the PC with WDI Client 3.3
and an ODBC driver on either a LAN database server, or on the z/OS system
with DB2. As a result of using ODBC for access to DB2, any Client/Server
environment that supports ODBC clients and z/OS DB2 servers can be used
with WDI Client and Host 3.3. As discussed previously, the topic of
ODBC compliance is complex, so contact technical support for information
on any Client/Server environments that we know won't work with
WebSphere Data Interchange 3.3.
For information on your database servers and/or Client/Server
environments we suggest you contact your I/S professionals. The
people that can help you are most likely associated with your LAN
or Database Administration departments.
6.4 Where do the ODBC drivers need to be?
For DB2 Connect Personal Edition all drivers/software is on the PC.
For Enterprise Edition, DB2 Client, also known as Client Application
Enabler (CAE), is installed on each PC to provide the needed drivers.
6.5 How is an ODBC Data Source Name setup in Windows?
After you have installed the appropriate ODBC drivers on the PCs
that are running WDI Client 3.3, you must configure them using ODBC
Data Source Administrator, which is invoked by selecting "Data Sources
(ODBC)" found under the Administrative Tools. "Administrative Tools"
is found on the Control Panel.
ODBC Data Source Administrator maps Data Source Names (DSNs) to ODBC
drivers. WDI Client has one DSN for configuration information called
"WDIClient33CFG". It also has one DSN for each System that you define.
You decide what these DSNs are. WDI Client is shipped with one System
called "Development". The DSN associated with it is "WDIClient33Dev".
See the documentation or help for the Systems topic for
information on how to define Systems to WDI Client.
To enable Client/Server mode, you must associate your DSNs with
your Client/Server ODBC driver within ODBC Data Source Administrator.
Go into the ODBC Data Source Administrator and press the "Add" button
to create your Client/Server mode DSN. Select your Client/Server
driver from the "Installed ODBC Drivers" list. Next, name your new
Client/Server DSN and provide any required parameters specific to your
driver.
6.6 Can you use DB2 Connect since its a DB2 database instead of using
ODBC?
You can use DB2 Connect because it supports ODBC. Only ODBC is used
by WDI Client to access DB2 databases. Tested and recommended
version of DB2 Connect is V8.2.
-------------------------------------------------------------------
7. Document Store Considerations
The Document Store is maintained by the WebSphere Data Interchange
Server and the data in the Document Store is not available to
WDI Client unless the user is in Client/Server mode.
-------------------------------------------------------------------
8. Multi-user Database Considerations
- All components, including the default databases will be installed
when you first install WDI Client. WDI Client is installed with a
single user database.
If you take steps to reconfigure your database setup for multi-user,
then you should exercise caution whenever you re-install WDI Client.
If you re-install again, you will overwrite your databases and drivers
with the defaults.
- When creating the multi-user environment, make sure that the
drivers go in the proper System directories. The UNINSTALL may
not remove drivers.
- Make sure that the server drivers are from the same version
of the database product from which the database(s) were created.
-------------------------------------------------------------------
9. Middleware, Upload/Download Considerations
Data in Windows and AIX files is typically stored in ASCII
format while data in z/OS host datasets is typically stored in
EBCDIC format. When files are moved from a Windows system to
a z/OS host (or vice versa) the data is normally converted from
ASCII to EBCDIC (or EBCDIC to ASCII). This type of conversion
occurs whenever you upload or download data using a file transfer
program like IND$FILE or FTP.
Conversion problems can occur whenever you move data between a PC
and a host computer. These problems usually occur when the file
transfer software converts a character to a value you don't expect.
It is particularly important that the file transfer software does
not change the value of the hex '01' character since this character
is used as a delimiter in the DataInterchange profiles.
In standalone mode, files are uploaded and downloaded using file
transfer software. During a download to the PC from the host or an
upload from the PC to the host, an EBCDIC/ASCII conversion occurs.
We have seen instances where a character does not convert to the
expected EBCDIC character or the expected ASCII character. For
instance, a character vertical bar (|) on the host converted to a
character double-quote (") on the PC. You must refer to the product
that is used in the download/upload procedure to determine how to
alter the EBCDIC/ASCII conversion. Also, verify that the hex '01'
character is not altered during data transfer.
When using client-server mode, the WDI 3.3 Client processes the data
as Unicode and stores the Unicode values directly into the WDI 3.3
server database. This helps to avoid the ASCII to EBCDIC conversion
issues that may occur with the file transfers and standalone mode.
Note: The tested and recommended version of DB2 Connect is V8.2.
Versions earlier than this may have problems reading and updating
the Unicode DB2 tables in the server database.
-------------------------------------------------------------------
10. Creating Multiple PC database configurations
WDI Client is distributed with a single set of databases. The
databases are WDIClient33CFG.MDB, and WDIClient33Dev.MDB.
They appear in the installation directory after a typical installation.
They contain only default data when installed.
If you would like to create a second database, i.e. have
a DEVELOPMENT System and a TEST System, then follow these instructions:
a) copy the file WDIClient33Dev.MDB to WDIClient33Dev2.MDB.
(note WDIClient33CFG.MDB need not be copied since it contains tables
common to all 'Systems').
b) create the ODBC data definitions for the new database;
to do this:
- invoke the ODBC Data Source Administrator by selecting Data
Sources (ODBC) from Administrative Tools. Administrative Tools
is found on the Control Panel
- click on ADD, select Microsoft Access (*.mdb) drivers, then FINISH
-The ODBC Microsoft Access Setup diaglog is displayed. Fill in this dialog
and press the OK button. For example, to create a new database entry
do the following:
- type in a Data Source Name, e.g. TestSys
- type in a Description, e.g. test System
- click on the Select button (a Select database window appears)
- select a database file - this is the file name of the copied
database, e.g. c:\program files\ibm\WDI Client v3.3\wdiclient33dev2.mdb
- click on OK to save the entry
c) setup the System definition in WDI Client;
- select VIEW from the WDI Client toolbar
- select Administration
- select Systems
- when the list appears, select the New icon on the toolbar
- create a System entry as follow:
- type a System Name - e.g. TEST
- select the Server Platform corresponding to the WebSphere Data
Interchange Server
- select the Data Source Name (this is the same name as created in
(b) above) e.g. TestSys
- If you are accessing a shared database, such as DB2, enter the
Database Qualifer
- select a background frame color to associate with the System
- click on SAVE to save the entry
-------------------------------------------------------------------