***
*** (C) Copyright International Business Machines Corp. 2002.
*** All Rights Reserved
*** Licensed Materials - Property Of IBM
***
*** Welcome to WebSphere Data Interchange Version 3.2
***
***
***

For information on how to set up WebSphere MQ for WebSphere Data Interchange
see the wdi_mq_setup.txt file in the samples directory.

On Windows platforms the WebSphere MQ Services Trigger Monitor does not
fully support PROCESS definitions that contain file paths having embedded
blank characters e.g. "C:\Program files\".  Instead run the WebSphere MQ
trigger monitor program runmqtrm as described in wdi_mq_setup.txt. 


*** Install instructions for WebSphere Data Interchange V3.2

1)  Perform subsequent steps as a user with DB2 administrator authority.

2)  After the InstallShield installation, the directory structure within the
    installation directory is as follows:

       bin
       bind
       ddl
       ixf
       include
       lib
       runtime
       runtime/adf
       runtime/aex
       runtime/dicmd
       runtime/dicts
       runtime/dtds
       runtime/edi
       runtime/eex
       runtime/fak
       runtime/prt
       runtime/qry
       runtime/rcv
       runtime/rpt
       runtime/trk
       runtime/wrk
       runtime/xex
       runtime/xml
       samples

    * Additional directories may be created for use by InstallShield. 
      These are used for things like keeping uninstall information, and
      the Java Virtual Machine binaries.


3)  Change directory to the ddl directory

4) Issue the command:

       db2 create db ediec32e

    This process will create the database. When this process has completed
    successfully the database has been built. Once the database has been
    created, issue the command:

       altrec32

    This process will alter some of the default parameters related to log file
    size and number of primary and secondary logs.

5) Change to the DB2 directory which contains the bind files for the DB2 
   utilities.  
    - If installing on Windows, this typically has a name like 
      C:\Program Files\SQLLIB\bnd.  
    - If installing on AIX, this typically has a name like 
      /u/<db2 instance>/sqllib/bnd, where <db2 instance> is the id of the 
      instance owner.  
    (See DB/2 Quick Beginnings "Binding Database Utilities") 

6)  Issue the following commands:

       db2 connect to ediec32e
       db2 bind @db2ubind.lst messages bind.msg grant public
       db2 bind @db2cli.lst messages clibind.msg grant public
       db2 connect reset

    Note for AIX installations: You may need to specify a different file for 
    the messages for example /tmp/bind.msg, if you do not have write authority
    to the current directory.

7)  Change the current directory back to the ddl directory.

8)  Issue the command:

       db2 -tf ediec32.ddl -l ec32.log

    This process creates the WebSphere Data Interchange V3.2
    tables, indices, views, etc.

9)  The next step will issue GRANT statements necessary for DI Client access
    to the newly created tables. The default is to issue GRANTs to public. 
    You may wish to change public to specific userids or a group of authorized
    users.

10) Issue the commands:

       db2 -tf grntec32.ddl -l grntec32.log

11) Change directory to the ixf directory

12) Issue the following command:

       loadec32

    This process will load initial data into the DB2 tables. The loading may
    generate warnings, but you can just ignore them.

13) Change directory to the bind directory

14) The next step will issue GRANT statements necessary for WebSphere Data 
    Interchange Server access to the newly created tables. The default within 
    bindgrnt.fil is to issue GRANTs to public. You may wish to change public 
    to specific userids or a group of authorized users.

15) Issue the command:

       db2 -tf bindgrnt.fil -l bind.log

    This process will BIND the WebSphere Data Interchange V3.2
    DB2 packages and GRANT execute authority to public.

16) The installation for the WebSphere Data Interchange V3.2
    is complete. 


Notes on setting the PATH:
    For Windows installations, the bin directory for WDI 3.2 is added to the
    end of your current path.  If you have another version of WDI installed
    on your system, you need to change your path to make sure that the 
    WDI 3.2 bin directory comes before any other versions of WDI in your PATH.
    If other versions of WDI executables are found in your path, you may 
    receive database errors such as a -818, since the executables from other 
    versions are not bound to the EDIEC32E database.

    For AIX installations, there is a script in the samples directory 
    that can be used to set up the WDI environment variables.  To use
    this script, enter the command:
       . setdienv.sh

    This command can also be run from within your .profile when you login.
    By using the "." followed by a blank, this will set the variables in the
    current environment.  Otherwise, the environment variables are only
    set for the duration of the script.
    
*** Install verification steps

 1) Change directory to the samples directory

 2) Enter the command:

        wditest

    This will start a batch file (Windows) or shell script (AIX) to
    set up environment variables and run a translation using the
    sample map and data provided.  The environment is restored at the
    end of the test.

    If the installation is successful, you should see the following output:
  
       DI Translator Started, build date: (WDI build date)
       DI Translator processed your request.
       DI Translator shutdown
		
    If error(s) are written to the console or to the prtfile (in the
    samples directory), check the messages and take appropriate 
    corrective action.  


*** Setting up a TCP/IP alias for remote access to AIX databases

    For improved performance when accessing an AIX database from the WDI Client,
    use of a TCP/IP alias is suggested.  This also prevents certain performance
    related database errors.  To set up a TCP/IP alias for a database
    do the following steps using an id with db2 sysadm authority:

    You will need to substitute your local values for the following:

	<service>    is the service name in /etc/services for the DB2 port
        <hostname>   is the host name for the machine
        <hostnode>   is the tcpip node name you want to define
	<dbname>     is the database name
        <dbalias>    is the database alias

    Issue these commands one time for the machine to create the TCP/IP node:  

	db2set DB2COMM=tcpip
	db2 update dbm cfg using svcename <service>	
	db2 catalog tcpip node <hostnode> remote <hostname> server <service>	

    Then for each database, you will define an alias by issuing the
    following command:

        db2 catalog database <dbname> as <dbalias> at node <hostnode> 	
									
    For example, if your system had the following local values:

	db2tcp01     is the service name in /etc/services for the DB2 port 
        wdihost      is the host name for the machine
        wditcp       is the tcpip node name you want to define
	EDIEC32E     is the database name
        WDITCP32     is the database alias you want to use

    You would issue the following commands:

	db2set DB2COMM=tcpip
	db2 update dbm cfg using svcename db2tcp01
	db2 catalog tcpip node wditcp remote wdihost server db2tcp01
        db2 catalog database EDIEC32E as WDITCP32 at node wditcp 

    When remote DB2 clients connect to the EDIEC32E database, they can
    use the WDITCP32 alias for the database name.

    If you want to define additional TCP/IP aliases for that system, 
    you only need to issue the "db2 catalog database" command for the
    other databases.  You do not need to define the node again.

    For more information, refer to your DB2 documentation.

    
*** Uninstall instructions for WebSphere Data Interchange V3.2

To uninstall on AIX:

 1) Change directory to the _uninst directory

 2) Issue the command:

       uninstall.bin

To uninstall on Windows:

 1) Use the Windows "Add/Remove Programs" dialog on the control panel
    to uninstall the program.

*** Acknowledgements ***

This product includes software developed by the 
Apache Software Foundation (http://www.apache.org/).  
Copyright (c) 1999-2000 The Apache Software Foundation. All rights reserved.
This software is distributed under Apache Software License, Version 1.1.  
A copy of this license (LICENSE.TXT) is included in the same directory as 
this file.

This product also includes International Components for Unicode.
Copyright (c) 1995-2001 International Business Machines Corporation and others
All rights reserved.  This is distributed under the X License (XLicense.html),
which is included in the same directory as this file.

*** END OF DOCUMENT WebSphere Data Interchange V3.2
