Installing DB2 Run Time Client Windows =========================================================== Contents 1 About this document 1.1 Who should read this document 2 Pre-installation procedures 3 Installation procedures 4 Post-installation procedures --------------------------------------------------------------- 1 About this document This document contains the instructions to install the DB2 Run Time Client (RTLITE) on Windows platform. 1.1 Who should read this document This document is intended for users of IBM Cloudscape who require ODBC Support and need only minimal functionality from the DB2 Run Time Client. --------------------------------------------------------------- 2 Pre-installation procedures (1) If you have any DB2 client or server products installed on your machine from any other source, uninstall it by following the instructions provided by that source. (2) If you have the DB2 Run Time Client already installed on your machine by following the instructions given in this file, run en_US_setup.exe (used to install the DB2 Run Time Client) to uninstall the DB2 Run Time Client or uninstall the DB2 Run Time client from the Control Panel. --------------------------------------------------------------- 3 Installation procedures Do the following to install the DB2 Run Time Client: (1) Download the DB2 Run Time Client as follows: - Go to "https://www6.software.ibm.com/dl/rtcl/rtcl-p" - Register yourself if you have not registered yet. - Sign in with the userid and the password that you have registered with. - On the next page, answer all the questions and click on "View License". - After viewing the license, click on "Accept License". - On the next page, go to the section for "Installers for individual national languages" and download en_US_setup.exe. (2) Run en_US_setup.exe. (3) Follow the steps given in installation wizard. (4) The setup.exe installs the DB2 Run Time Client in default directory "C:\Program Files\IBM\SQLLIB". You can choose any other directory to install Run Time Client while going through installation wizard. The installation directory will be referred to as ${db281} in the rest of this document. --------------------------------------------------------------- 4 Post-installation procedures Post-installation procedures are steps to ensure that the DB2 Run Time Client can connect to the Cloudscape Server. Note: ---- You need to have IBM Cloudscape installed on your machine to do the post-installation procedures. The directory in which you have installed IBM Cloudscape will be referred to as the ${cloudscape} directory in the rest of this document. Do the following to check if the DB2 Run Time Client can communicate with the Cloudscape Server: (1) Go to the directory ${db281}\bin and run the command "db2cmd". This will open another window. In new window, run the command "db2". The db2 command starts the command line processor (CLP). The CLP is used to execute database utilities, SQL statements and online help. (2) Open another dos window, and start the Cloudscape Network server as follows: - Go to the directory where you have installed Cloudscape. >cd ${cloudscape} - Setup the CLASSPATH to point to the following Cloudscape jar files in directory ${cloudscape}\lib: derby.jar derbynet.jar derbytools.jar - Setup the PATH to point to whichever jdk you are using. - Start the Network Server by issuing the following command: >java org.apache.derby.drda.NetworkServerControl start (3) Open another dos window, and start the Cloudscape command line processor as follows: - Go to the directory where you have installed Cloudscape. >cd ${cloudscape} - Setup the CLASSPATH to point to the following Cloudscape jar files in directory ${cloudscape}\lib: derby.jar derbytools.jar db2jcc.jar db2jcc_license_c.jar - Setup the PATH to point to whichever jdk you are using. - Run the following command to start Cloudscape command line processor: >java org.apache.derby.tools.ij - Now you will get the prompt "ij>". Give the following command at the prompt "ij>" ij>connect 'jdbc:derby:net://localhost:1527/DataBaseName;create=true:user=usr;password=pwd;'; where DataBaseName is the name of the database to be choosen by the user. Example: -------- The following command creates database with name "my_test_db": ij>connect 'jdbc:derby:net://localhost:1527/my_test_db;create=true:user=usr;password=pwd;'; (4) Now go back to the window in which you ran the db2 command (see step 1). At the prompt "db2 =>", issue the following commands to check if the DB2 Run Time Client can communicate with the Cloudscape Server: Note: The following commands uses database name "my_test_db", and node name "cns". If you are using any other names for database and node, the commands should be changed accordingly. db2 => catalog tcpip node cns remote localhost server 1527 DB20000I The CATALOG TCPIP NODE command completed successfully. DB21056W Directory changes may not be effective until the directory cache is refreshed. db2 => catalog db my_test_db at node cns authentication server DB20000I The CATALOG DATABASE command completed successfully. DB21056W Directory changes may not be effective until the directory cache is refreshed. db2 => connect to my_test_db user usr using pwd Database Connection Information Database server = Apache Derby CSS10000 SQL authorization ID = USR Local database alias = MY_TEST_DB db2 => select * from sys.systables TABLEID TABLENAME TABLETYPE SCHEMAID LOCKGRANULARITY ------------------------------------ ---------------- --------- ------------------------------------ ------------------- 80000010-00d0-fd77-3ed8-000a0a0b1900 SYSCONGLOMERATES S 8000000d-00d0-fd77-3ed8-000a0a0b1900 R 80000018-00d0-fd77-3ed8-000a0a0b1900 SYSTABLES S 8000000d-00d0-fd77-3ed8-000a0a0b1900 R 8000001e-00d0-fd77-3ed8-000a0a0b1900 SYSCOLUMNS S 8000000d-00d0-fd77-3ed8-000a0a0b1900 R 80000022-00d0-fd77-3ed8-000a0a0b1900 SYSSCHEMAS S 8000000d-00d0-fd77-3ed8-000a0a0b1900 R 8000002f-00d0-fd77-3ed8-000a0a0b1900 SYSCONSTRAINTS S 8000000d-00d0-fd77-3ed8-000a0a0b1900 R 80000039-00d0-fd77-3ed8-000a0a0b1900 SYSKEYS S 8000000d-00d0-fd77-3ed8-000a0a0b1900 R 8000003e-00d0-fd77-3ed8-000a0a0b1900 SYSDEPENDS S 8000000d-00d0-fd77-3ed8-000a0a0b1900 R c013800d-00d7-ddbd-08ce-000a0a411400 SYSALIASES S 8000000d-00d0-fd77-3ed8-000a0a0b1900 R 8000004d-00d0-fd77-3ed8-000a0a0b1900 SYSVIEWS S 8000000d-00d0-fd77-3ed8-000a0a0b1900 R 80000056-00d0-fd77-3ed8-000a0a0b1900 SYSCHECKS S 8000000d-00d0-fd77-3ed8-000a0a0b1900 R 8000005b-00d0-fd77-3ed8-000a0a0b1900 SYSFOREIGNKEYS S 8000000d-00d0-fd77-3ed8-000a0a0b1900 R 80000000-00d1-15f7-ab70-000a0a0b1500 SYSSTATEMENTS S 8000000d-00d0-fd77-3ed8-000a0a0b1900 R 80000000-00d3-e222-873f-000a0a0b1900 SYSFILES S 8000000d-00d0-fd77-3ed8-000a0a0b1900 R c013800d-00d7-c025-4809-000a0a411200 SYSTRIGGERS S 8000000d-00d0-fd77-3ed8-000a0a0b1900 R f81e0010-00e3-6612-5a96-009e3a3b5e00 SYSSTATISTICS S 8000000d-00d0-fd77-3ed8-000a0a0b1900 R c013800d-00f8-5b70-bea3-00000019ed88 SYSDUMMY1 S c013800d-00f8-5b53-28a9-00000019ed88 R 16 record(s) selected. db2 => disconnect my_test_db DB20000I The SQL DISCONNECT command completed successfully. db2 => uncatalog db my_test_db DB20000I The UNCATALOG DATABASE command completed successfully. DB21056W Directory changes may not be effective until the directory cache is refreshed. db2 => uncatalog node cns DB20000I The UNCATALOG NODE command completed successfully. DB21056W Directory changes may not be effective until the directory cache is refreshed. (5) Go back to the window with the prompt "ij>" (see step 3) and issue the following commands: ij>disconnect; ij>exit; (6) Go back to the window in which you started the Cloudscape Network Server (check step 2) and issue the following command to shut down the Network Server: >java org.apache.derby.drda.NetworkServerControl shutdown