When you install IDM Desktop 3.0.0 or IDM Web Services 3.0.0 with support for Oracle-based IDM Document Services (IDMDS) library systems, Setup installs Oracle8i client libraries. There are known problems using Oracle8i with:
IDM Web Services
IDM clients that run multi-threaded Panagon Toolkit-based applications against IDMDS library systems
For these configurations, as a temporary workaround you must downgrade the Oracle8i client libraries to version 7.3.4 on the IDM Web server or IDMDS client machine. This downgrade is supported for Windows NT and Windows 98 clients.
Note: Due to the above restrictions, IDM Web Services cannot be installed on any IDMDS server.
To downgrade an Oracle8i client:
Using IDM Configure, add a library entry for each Oracle8i-based IDMDS library system that you wish to access. For each library that you configure, note the property server host name, port number, and Oracle SID. You will need this information later in this procedure.
If you want to configure your client to access additional Oracle-based library systems later, see Configuring Additional Oracle-based Libraries below.
Open the Windows Control panel and start the ODBC Data Sources tool. Go to the System DSN tab and remove all entries that use Oracle ODBC drivers.
Rename the Oracle home directory (default name \Oracle). For example, rename \Oracle to \Oracle.OLD.
Note: If the Oracle client files were installed during IDM Desktop or IDM Web Services installation, \Oracle is the name given to the directory containing these files. Depending on your OS platform and how the Oracle client files were installed, this directory name may be different on your system (for example, \Orawin95).
Using the Windows Start > Run command, start regedit. Then:
Go to \HKEY_LOCAL_MACHINE\SOFTWARE and rename:
ORACLE to ORACLE.OLD
Go to \HKEY_LOCAL_MACHINE\SOFTWARE\odbc\odbcinst.ini\odbc drivers and rename:
Oracle ODBC Driver to Oracle ODBC Driver.OLD
Go back up a level to \HKEY_LOCAL_MACHINE\SOFTWARE\odbc\odbcinst.ini and rename:
Oracle ODBC Driver to Oracle ODBC Driver.OLD
Shut down regedit and reboot the machine.
On the Oracle 7.3.4 Client Files CD-ROM distributed by FileNET, run \OracleClient\Setup.exe.
Installation Notes:
This installation requires 49 MB of free disk space.
To install across a network using the Setup program in the \OracleClient folder, you must first map a drive to that location. If you are using a UNC path, run \OracleClient\Win32\Install\Setup.exe instead.
Because IDM Desktop and IDM Web Services installations place the Oracle client files in a directory named \Oracle, and by default the Oracle 7.3.4 installer places the client files in a directory named \Orant, you will be prompted during the installation with a dialog box about adding C:\ORANT\BIN to the path. Select Yes to allow the change.
For Windows 98 clients, the Oracle installer will display a warning if the updated path variable is longer than 127 characters. In that case, click OK to continue the installation; after the installation completes, edit your autoexec.bat file and update the path statement manually. We recommend that you delete the path to the Oracle8i client files (for example, C:\Oracle\bin) and add the path to the downgraded client files (for example, C:\Orawin95\bin).
Select the Custom installation option.
On the Software Asset Manager dialog box, verify that the right pane is empty. If it is not empty, there is still an \Orant or \Orawin95 folder on the machine. Exit and rename the folder, then restart Setup.
In the left pane of the Software Asset Manager dialog box, expand all options by double-clicking the plus (+) sign.
Hold down the Ctrl key and select all of the following components:
Oracle TCP/IP Protocol Adaptor 2.3.4.0.0
SQL*Net Client 2.3.4.0.0
Oracle 7 32-bit ODBC Driver version 2.5.3.1.0B
Oracle 7 Utilities 7.3.4.0.0
Required Support Files 7.3.4.0.0
Note: Some of the required components are nested within sublists. Be sure to expand all sublists and select all five of the required components.
Click on Install.
When the installation is complete, exit the Oracle installer.
In the \Orant\Odbc250 (or \Orawin95\Odbc250) directory, rename Sqo32_73.dll (dated 8/19/97) to Sqo32_73.OLD.
Note: For DLL files to be visible in Windows Explorer, you must select View > Options and in the Hidden Files section, change the setting to "Show all files." (By default, DLL files are hidden.)
Copy the newer Sqo32_73.dll (version 2.5.3.1.5, dated 6/18/98) from \OracleODBCPatch on the Oracle 7.3.4 Client Files CD-ROM to \Orant\Odbc250 (or \Orawin95\Odbc250).
Open the Windows Control Panel and start the ODBC Data Sources tool. For each Oracle8i-based library system that you configured in step 1, add a DSN as follows:
On the System DSN tab, click Add.
On the Create New Data Source dialog box, select Oracle 73 Ver 2.5, then click Finish.
For Data Source Name, enter the host name of the library system property server.
For the SQL *Net Connect String, enter the host name of the library system property server.
The other fields can be left blank. Click OK.
Reboot the machine.
Use the SQL Net Easy Configuration utility to edit your tnsnames.ora file as follows:
Note: If you have manually edited tnsnames.ora with another editor, you may not be able to use SQL Net Easy Configuration to edit it again without reverting to a previous version of the file. Also, if you are using a non-default Oracle database port number you will need to edit tnsnames.ora manually to enter the correct value. (See step 14.)
Start SQL Net Easy Configuration. For example, on Windows NT, click Start > Programs > Oracle for Windows NT.
Select Add Database Alias.
Enter the property server host name as the database alias name.
Select TCP/IP protocol.
Enter the property server host name.
In the database instance field, enter the SID.
Open a DOS command prompt window and enter:
tnsping servername
For example, to test communication with a property server whose host name is George, enter:
tnsping George
If tnsping returns a message saying OK(# sec), go to step 15.
If tnsping fails, manually edit the tnsnames.ora file. The default location is C:\Orant\network\admin. Once the file is correctly configured, run tnsping again to verify communication with the database.
The following example shows a correctly configured tnsnames.ora entry for a property server with host name George, SID=FILE, and port number 7777 in place of the default value 1521. (Note that the second port number that SQL Net Easy Configuration set, 1526, has not been changed.)
George.world =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(COMMUNITY = tcp.world)
(PROTOCOL = TCP)
(Host = George)
(Port = 7777)
)
(ADDRESS =
(COMMUNITY = tcp.world)
(PROTOCOL = TCP)
(Host = George)
(Port = 1526)
)
)
(CONNECT_DATA = (SID = FILE)
)
)
Verify that you can log on and check out or copy documents from the library system.
To make an additional IDMDS Oracle-based library system available to IDM users:
Using IDM Configure, add an entry for the library system. Be sure to select Microsoft SQL rather than Oracle as the database.
Open the Windows Control panel and start the ODBC Data Sources tool.
On the System DSN tab, select the DSN that was configured by IDM Configure in the previous step and click Remove to delete it.
On the System DSN tab, click Add.
On the Create New Data Source dialog box, select Oracle 73 Ver 2.5.
For Data Source Name, enter the property server host name.
For the SQL *Net Connect String, enter the property server host name.
The other fields can be left blank. Close the ODBC Data Sources tool.
Perform steps 12 — 15 of the previous procedure to add an entry to tnsnames.ora and verify access to the library system.