WBT Manager™ Installation Procedure for Oracle®
May 18, 2005
WBT Manager has been tested with the following versions of Oracle client software. Click the desired version for details.
Oracle 10:
Oracle 10 client software
has not yet been tested with WBT Manager. It is recommended that you use one of
the configurations listed above for earlier Oracle versions to access Oracle 10
databases.
Installation procedures
I. Database setup.
1. Use Oracle management tools to create a database and instance for WBT Manager.
2. Create a user to own the WBT Manager database objects. This user must have permissions to create tables, indexes, constraints, and public synonyms. User must also be able to grant access to owned objects. This procedure will use "wbtmanadmin".
3. Create a user or group of users to be used by the WBT Manager modules to access the database. The supplied script for granting table access uses "wbtmanuser" as will the remainder of this procedure.
4. Create an Oracle service name and connect it to the database.
5. Create an ODBC DSN using the Oracle ODBC Driver and connect it to the database. Verify that the connection works properly.
5. Using the RUNSQL.EXE program found in the WBT Manager installation set (\utilities\database\runsql.exe) connect to the database as "wbtmanadmin" and execute the sql scripts found in \utilities\database\scripts to create and initialize the WBT Manager Tables. The scripts are (in order of execution):
oracle.sql - contains table, index, and constraint definitions.
initdb.sql - contains initial data for the tables.
report_views_oracle.sql - creates views for certain standard reports.
orasyn.sql - creates public synonyms for each WBT Manager table.
grantdb.sql - grants access to all WBT Manager tables to user "wbtmanuser". Copy and edit this script for other user ids.
There are two additional scripts which may be of interest:
cleandb.sql - drops all WBT Manager Tables.
orasynd.sql - drops all WBT Manager public synonyms.The WBT Manager Database is now ready for use.
II. Install WBT Manager Web Server Module
1. Install Oracle client software on the Web Server. See the "Oracle configuration notes" below for the required components and versions.
2. Configure the Oracle client software to connect to the database created above. Test the connection with TNSPING.
3. If not already installed, install version 3 of the Microsoft XML Parser (Windows XP and systems with IE6 installed do not require this step).
There is a copy of the installation file msxml3sp1.exe for version 3 sp1 in \utilites\msxml on the WBT Manager CD, or the most current version can be downloaded from http://www.microsoft.com/xml . Execute msxml3sp1.exe to install the parser.
NT and Windows 98 users may need to install Windows Installer 1.2 before the MSXML installation can succeed. There are copies of the installation sets in \utilities\windows_installer\ver12_9x_me and \utilities\windows_installer\ver12_nt4.
4. If not already installed, install the latest version of Microsoft Data Access Components.
There is a copy of the installation file mdac_typ.exe in \utilites\database\mda2 on the WBT Manager CD, or the most current version can be downloaded from http://www.microsoft.com/data. This file contains the required version of the Microsoft ODBC for Oracle driver and also corrects a few problems with data access on IIS4. Execute mdac_typ.exe to install the upgrade. If you select "custom installation" you must include "ODBC Components", "OLE DB Components", "ODBC Driver for Oracle Databases", "OLE DB Provider for Oracle Databases", and "Microsoft ActiveX Data Objects".
5. Insert the WBT Manager CD or launch wbtman_setup.exe from the installation set. Select "Install WBT Manager Web Server Module" from the menu and follow the installation instructions with the following exception:
When prompted for the "Database Type", select "Oracle Database" and click "Next".
Enter the Oracle network service name connected to the database and click "Next".
Enter the user id ("wbtmanuser") and password for the web module to use to connect to the database and click "Next".Complete the installation as directed by the instructions.
A student and an administrator are predefined for demonstration and test purposes. The student ID/Password is "demo"/"demo". The administrator ID/Password is "admin"/"admin".
III. Install WBT Manager Administrator Module
On each workstation which is to run the WBT Manager System Administrator module repeat the following:
1. Install Oracle client software on the workstation. Please see note on stability at the top of this document. See the "Oracle configuration notes" below for the required components and versions.
2. Configure the Oracle network client to connect to the WBT Manager database. Test the connection with TNSPING.
3. Create a DSN with the Oracle ODBC driver and connect it to the database. Set the name as desired (this procedure will use "WBT Manager Oracle DB"), do not enter a user name, and enter the connection name from step 2 above as the server. Check the connection using ODBC Test (executing "select * from students" should return at least one row). Resolve any problems before proceeding.
6. Insert the WBT Manager CD or launch wbtman_setup.exe from the installation set. Select "Install WBT Manager System Administrator Module" from the menu and follow the installation instructions with the following exception:
When prompted for the "Data Source", select "Pre-existing data source" and click "Next". Select the data source defined in step 3 above ("WBT Manager Oracle DB") and click "Next". Enter the user id ("wbtmanuser") and password for the administrator module to use to connect to the database and click "Next".
The WBT Manager System Administrator Module is now ready for use. On initial startup connecting to a new database you will be prompted to enter your license key before you can log onto WBT Manager. The initial administrator account ID is "admin" and it's password is "admin". You should change this password to secure the system.
Oracle configuration notes
Please read these notes carefully and pay attention to the red "cautionary" notes.
See the section below for the version of Oracle you are using.
Oracle 8.1.5:
Application
Driver & version
Net-8 8.1.5.0.0
(required by all applications)System Administrator Module
Oracle 8i ODBC Driver 8.1.5.5.0
Web-Server Application
Student Import Tools
Site Configuration UtilityMicrosoft ODBC for Oracle 2.575.1022.00 or later*
Oracle 8.1.7:
Application
Driver & version
Net-8 8.1.7.0.0
(required by all applications)System Administrator Module
Oracle 8i ODBC Driver 8.1.7.8.10
WARNING: earlier versions of this driver will
result in errors during database access.Web-Server Application
Student Import Tools
Site Configuration UtilityMicrosoft ODBC for Oracle 2.575.1022.00 or later*
Oracle 9.0.1:
Application
Driver & version
Oracle client 9.0.1.1.1
(required by all applications)System Administrator Module
Oracle 9 ODBC Driver 9.0.1.8.0
WARNING: Using the System Administrator application or Course Import application from versions prior to patch180_5 (1.8.0.3) will result in unexpected loss of course structure information from the database. Identify and upgrade all WBT Manager version 1.8 copies of wbtman.exe and impexp.exe from administrator systems before attempting to use this driver.Web-Server Application Oracle OleDB provider 9.0.1.0.1
Configuration: Modify the "connectionstring" keywork in the "[database]" group in appsettings.ini to use OLEDB instead of an ODBC DSN. The following is an example (it should be on a single line in appsettings.ini):
connectionstring=Provider=OraOLEDB.Oracle;
Data Source= <oracleservicename>;
UserId=%%uid%%;Password=%%pwd%%Student Import Tools
Site Configuration UtilityOracle OleDB provider 9.0.1.0.1
Oracle 9 ODBC Driver 9.0.1.8.0Note: Log onto the utilities using an Oracle ODBC DSN. Internally the utilities will detect this and reconnect using the OraOLEDB provider.
Oracle 9.2.0:
Application
Driver & version
Oracle client 9.2.0.1.0
(required by all applications)System Administrator Module
Oracle 9 ODBC Driver 9.2.0.6.3
WARNING: Using the System Administrator application or Course Import application from versions prior to patch180_5 (1.8.0.3) will result in unexpected loss of course structure information from the database. Identify and upgrade all WBT Manager version 1.8 copies of wbtman.exe and impexp.exe from administrator systems before attempting to use this driver.
WARNING2: Oracle ODBC Driver 9.2.0.6.5 does not work properly with WBT Manager.Web-Server Application Oracle OleDB provider 9.2.0.4.0
Configuration: Modify the "connectionstring" keywork in the "[database]" group in appsettings.ini to use OLEDB instead of an ODBC DSN. The following is an example (it should be on a single line in appsettings.ini):
connectionstring=Provider=OraOLEDB.Oracle;
Data Source= <oracleservicename>;
UserId=%%uid%%;Password=%%pwd%%Student Import Tools
Site Configuration UtilityOracle OleDB provider 9.2.0.4.0
Oracle 9 ODBC Driver 9.2.0.6.3Note: Log onto the utilities using an Oracle ODBC DSN. Internally the utilities will detect this and reconnect using the OraOLEDB provider.
*Microsoft® driver is required on the web server because Oracle driver does not support dynamic datasets as required by ADO recordsets. Other 3rd party Oracle drivers may also be effective.
NOTE:On some Windows 98 systems we have found the Oracle 8i network software to be very unstable. Typical symptom is that the System Administrator Module fails with an application error on startup. If you encounter this problem you should use the Oracle 7.3 network software to connect to the 8i database. The following versions have been found to be stable.
RSF 7.3.3.00
SQLNet 2.3.3.0.0
Oracle ODBC Driver
2.00.0301