CX ODBC Driver
Installation Guide Copyright 2001 Jenazabar, Inc. You may print any part or the whole of this documentation to support installations of Jenzabar software. Where the documentation is available in an electronic format such as PDF or online help, you may store copies with your Jenzabar software. You may also modify the documentation to reflect your institution's usage and standards. Permission to print, store, or modify copies in no way affects ownership of the documentation; however, Jenzabar, Inc. assumes no responsibility for any changes you make.
Filename: inodbc Distribution date: 08/30/2001
Contact us at www.jenzabar.com
Jenzabar CX, and QuickMate are trademarks of Jenzabar, Inc. INFORMIX, PERFORM, and ACE are registered trademarks of the IBM Corporation Impromptu, PowerPlay, Scenario, and Cognos are registered trademarks of the Cognos Corporation UNIX is a registered trademark in the USA and other countries, licensed exclusively through X/Open Company Limited Windows is a registered trademark of the Microsoft Corporation All other brand and product names are trademarks of their respective companies JENZABAR, INC. CX ODBC DRIVER INSTALLATION GUIDE
TABLE OF CONTENTS INTRODUCTION...... 1 Overview...... 1 Operation of the ODBC Link...... 1 Purpose of This Guide...... 1 Intended Audience...... 1 INSTALLATION INSTRUCTIONS FOR THE JENZABAR ODBC DRIVER ...... 3 Introduction...... 3 SMO Distribution ...... 3 Overall Process ...... 3 Preparing the Informix Driver Service on the Unix Host ...... 4 Introduction...... 4 Before You Begin ...... 4 Requirements for First Time Setup ...... 4 About the setup_odbc Script ...... 5 Preparing to Install the Driver on the PC...... 7 Location of Installation Software ...... 7 Removing the Client SDK...... 7 Entry in the PC's services File...... 7 Entry in the PC's hosts File ...... 7 Final Preparation ...... 8 Working Without Permanent Leases in DHCP...... 8 Defining ODBC DSNs...... 8 Use of Two Drivers ...... 8 Passwords for Administrative Users...... 8 If You Are an NIS User ...... 8 Installing the Driver on the PC...... 9 Introduction...... 9 Using the Wizard ...... 9 MIGRATING YOUR DATA SOURCES ...... 13 Introduction...... 13 How to Migrate Your Data Sources...... 13 TROUBLESHOOTING ...... 15
SUMMARY...... 17
INDEX ...... 19
i
INTRODUCTION
Overview Jenzabar, Inc. provides a proprietary ODBC (Open Database Connectivity) driver for SQL access to the Jenzabar CX database and processes. The Jenzabar ODBC driver supports the elements of ODBC standards required for Jenzabar CX application use. It is not guaranteed to work with products other than those that those distributed by Jenzabar. The driver is frequently updated as these products are upgraded in order to support Jenzabar CX products such as Campaign Management and Human Resources, as well as third-party products such as Impromptu which are resold by Jenzabar. A proprietary ODBC driver is provided because it allows features to be added to Jenzabar CX software which would otherwise not be practical or even possible. The best example of this is the use of virtual tables by Jenzabar CX PC software. For example, the Document Imaging software can do an ID lookup just the same as a libentry program would. It can use phonetic matching because the program uses the virtual table ids_aps which is implemented by the Appserver ids_aps. This proprietary ODBC driver will allow future additions to the Jenzabar CX PC software that could not be made if a commercial driver were used. The Jenzabar ODBC driver allows integration of Jenzabar CX information with any other sources of information for comparison and evaluation. With the Jenzabar ODBC driver, you can use Jenzabar CX data with third party tools, including Microsoft Office and Visual Basic.
Operation of the ODBC Link The C:\Windows\System directory contains a dll named cisodbc.dll (the name may have a trailing digit to indicate the version; e.g., cisodbc5.dll). This is the ODBC driver used by a Jenzabar CX program to link to either the Informix database or to Jenzabar CX Appservers. In operation, a program that needs to connect to an ODBC database will use the operator- supplied ODBC Data Source Name to pick a specific ODBC driver. It will then make calls to the code in the driver to connect to the required database and extract data from it. Generally, this database may be either on the local machine or accessed from a remote machine over the network. In the specific case of the Jenzabar ODBC driver, the data will be retrieved from the Jenzabar CX database server. With Jenzabar CX programs, the Jenzabar ODBC driver is used and connects to the host named in the ODBC Setup file using the port number specified in that file. Some programs open a single connection to the database, while others open two. The first of these connects through the specified port to the host program cisinf, which is the backend (host side) portion that interacts directly with the Informix database. If a second connection exists, it connects through the specified port to the host program cisaps. This program makes the connection to the AppServers that deliver data from the Jenzabar CX virtual tables (those with a suffix _aps; e.g., ids_aps).
Purpose of This Guide This guide serves as a learning tool and reference guide for installing the Jenzabar ODBC driver on your system.
Intended Audience This guide is for use by the system users in your institution’s computer center. System users include the Jenzabar coordinator, system administrator, and programmer/analysts.
Installing the ODBC Driver 1 Introduction
INSTALLATION INSTRUCTIONS FOR THE JENZABAR ODBC DRIVER
Introduction These instructions support the installation of the 32-bit Jenzabar ODBC driver, version 1.5.5. The installation of the ODBC driver to allow the connection of a PC to a host involves two separate actions. First you must install the server portion on the host, and second, install the client portion on the PC. The server portion is incorporated in the Unix component of your version of Jenzabar CX.
SMO Distribution All Jenzabar CX software is delivered via the SMO process. The setup components for the ODBC driver are deposited on the Jenzabar CX host machine and must be moved from there to a PC. The distribution can then be copied to a diskette or used directly from a network server.
Overall Process The overall installation consists of three components: • Preparation of the Driver Service on the Unix host • Preparation of the PCs • Actual PC installation This document addresses each of these components sequentially.
Installing the ODBC Driver 3 Installation Preparing the Informix Driver Service on the Unix Host
Introduction This section provides information to help you complete the setup of the Unix (server) component of the Jenzabar ODBC driver.
Before You Begin Whenever you perform maintenance on your system, Jenzabar recommends you back up your existing files. To save a copy of your current Unix ODBC setup: % SU csh password for user: # cd /opt/cisodbc/$CARSV # cp cisinf cisinf.`date +%y%m%d` # cp cisaps cisaps.`date +%y%m%d` # cd debug # cp cisinf cisinf.`date +%y%m%d` # cp cisaps cisaps.`date +%y%m%d` # exit
Requirements for First Time Setup In order for the Informix client SDK ODBC drivers to work after their first-time installation, changes in the configuration of the Informix engine may be required. These changes are required only if network access to the engine is not functional on your Jenzabar CX machine. To configure your network database access: 1. Create an entry in the /etc/services file to define the port number that Informix will use for a tcp/ip connection. Complete this step before the Informix engine is shut down and restarted. Notes: • Jenzabar recommends that an entry for this purpose be named istarcarsi for the production release. Make a back-up copy of the /etc/services file. The new entry should look like the following: istarcarsi1001/tcp# Port for istar connection • The number used here should not be one that is already in use by any other service. Since entries do not need to be in order, it is best to search for the number using vi before adding a new one. 2. Create an entry in the informix configuration file for the engine for which access is desired (e.g., onconf.carsi). This file must have an entry on the DBSERVERALIASES line for access to the engine. For example, you may want to name the file carsitcp, indicating a tcp/ip connection to the engine. In the case of the normal setup, the DBSERVERNAME name is for shared memory (shm) access to the engine, which is the method normally used for access to the engine by tools on the same host such as ACE, PERFORM, or ISQL. Make a backup copy of the onconf.cars file. The first new entry should look like: DBSERVERALIASEScarsitcp # List of alternate dbservernames 3. Create an additional NETTYPE entry for soctcp (you should already have an existing entry for ipcshm). The new entry should look like: NETTYPEsoctcp, 1, 50, NET # replace defaults 4. Create an entry in the $INFORMIXDIR/etc/sqlhosts file for network access to the engine. Make a back-up copy of this file. The new entry should be defined as follows: server nettype hostname service port
Unix Host Preparation 4 Installing the ODBC Driver carsitcp onsoctcp admin istarcarsi This example assumes admin is your hostname. You should use your actual hostname in its place. 5. Shut down and restart the engine so the new configuration parameters take effect. As in all cases where the configuration file is changed, Jenzabar recommends you make backup copies of the configuration files that were changed and do a level 0 archive of the engine before making the change. Once the engine has come back online, the system should be ready to accept Informix CLI ODBC driver connections.
About the setup_odbc Script The setup_odbc script sets up most of the required files and entries and uses an environment variable defining the release to determine the contents of the entries. Therefore if your site has two releases (e.g., carsi and carstrain), then the script must be run twice, once for each release. Note that the script will not work if your site has one release and two databases. In this latter case, the setup_odbc script creates the required entries for the release, and you must manually handle the second set of entries to attach to the carstrain database.
If you have two releases, then running setup_odbc twice (after doing a setdb to the training release for the second run) creates the following two directories: drwxr-xr-x 4 root carsctrl 1024 Nov 12 15:03 /opt/cisodbc/carsi drwxr-xr-x 4 root carsctrl 1024 Nov 12 15:03 /opt/cisodbc/carstrain The following example demonstrates how to add a new ODBC access mechanism to the Unix system. It involves three steps: creating new entries in the services file, creating new entries in the inetd.conf file, and creating a new directory in the directory /opt/cisodbc. For the purposes of this example, it is assumed that the site has two databases and one release. In this case the setup_odbc script will not work for the training database.
1. Edit /etc/services as follows: # vi /etc/services Find an existing line referring to the production database and copy it for train. Change the line as shown below. White space may be used to make the file more readable. The pound sign (#) is used to introduce a comment. The only change to be made in the copy is to change the port address to be the one desired for the new access (in this case 9065).
Original:
Cisinf_carsi 9055/tcp # For the Jenzabar ODBC Driver for carsi Copy
Cisinf_carstrain 9065/tcp # For the Jenzabar ODBC Driver for carstrain 2. Edit /etc/inetd.conf as follows: # vi /etc/inetd.conf Original: cisaps_carsi stream tcp nowait root /opt/cisodbc/carsi/cisaps.env cisaps.env cisaps_carsi_dbg stream tcp nowait root /opt/cisodbc/carsi/cisaps.env.dbg cisaps.env.dbg cisinf_carsi stream tcp nowait root /opt/cisodbc/carsi/cisinf.env cisi nf.env cisinf_carsi_dbg stream tcp nowait root /opt/cisodbc/carsi/cisinf.env. dbg cisinf.env.dbg
Installing the ODBC Driver 5 Unix Host Preparation Copy: cisaps_carstrain stream tcp nowait root /opt/cisodbc/carstrain/cisaps.env cisaps.env cisaps_carstrain_dbg stream tcp nowait root /opt/cisodbc/carstrain/cisaps.env.dbg cisaps.env.dbg cisinf_carstrain stream tcp nowait root /opt/cisodbc/carstrain/cisinf.env cisi nf.env cisinf_carstrain_dbg stream tcp nowait root /opt/cisodbc/carstrain/cisinf.env. dbg cisinf.env.dbg In this case, you are accessing a different database so the entries in inetd.conf must have a different path name to reflect the fact that the scripts are different. The scripts such as cisinf.env contain the code to initialize the environment variables necessary to access the correct database. In some other cases, the only difference between the copy and the original would be the first column, ie the service port name. An example of the latter is the setup for remote Jenzabar access to the client database. Because of the Jenzabar firewall the only two ports that can be used at Jenzabar to access a client database are 9055 and 9054.
3. Command inetd to reread its configuration file. • For HP systems: # /etc/inetd -c • For IBM systems, find the Process ID number for inetd and send a HUP signal to it, as follows: # ps -eaf | grep inetd root 147 1 0 Apr 12 ? 1:01 /etc/inetd jdoe 12365 12364 0 16:39:40 ttypb 0:00 grep inetd # kill -HUP 147 4. Make a new directory in /opt/cisodbc named carstrain. Copy the contents of carsi to carstrain. Edit the scripts in carstrain to set up properly for the carstrain database instead of the carsi database of the original directory.
Unix Host Preparation 6 Installing the ODBC Driver Preparing to Install the Driver on the PC
Location of Installation Software The software you need to install the Jenzabar ODBC driver on the PC resides in self extracting zip files in the SMO root directory. There is only one file. The preferred method of transferring the file depends on the local computer and network set-up. Typically, most institutions can use ftp on the PC to transfer files from the host to the PC. Note that you should use Binary mode to transfer the software files from the host to the PC. When you open either of these files (by double clicking on it in Windows Explorer for example) it will extract its contents to a directory of your choosing. Jenzabar recommends that it be extracted to a network server accessible to all administrative PCs. The extraction process creates a setup.exe program and the associated files needed for the Informix Client SDK. Run the setup program, allowing the Informix installation wizard to guide you through the process of installing the ODBC drivers which are in the client SDK. Unless you have local reasons to do otherwise, Jenzabar recommends you select the custom install. The first option after you select the custom install method is the destination folder. Jenzabar recommends that if you already have a Client SDK installed, change the destination to something like: C:\\Program Files\\Informix\\CSDK26 In this way, the previous version is not overwritten and the directory reflects the version of the Informix Client SDK. If this the first time a Client SDK has been installed on the client workstation, then pick the option to set INFORMIXDIR. Otherwise, if this is the second installation of the Client SDK, it is not necessary to set the INFORMIXDIR, since running the program setnet32 can change the value of INFORMIXDIR. You must consider what version you want to use if you choose not to set the INFORMIXDIR. In this way you can maintain and try multiple versions of the Informix Client SDK.
Removing the Client SDK If you run setup.exe a second time, the installation program will enable you to remove the entire Client SDK. During your second execution of the setup program your are prompted to select one of the following three options: Modify, Repair and Remove.
Entry in the PC's services File You must have an entry in the services file on the PC for the tcp port that the engine is using. For example, you can create an entry in /etc/services with a name istarcarsi. Regardless of the name selected, it must be duplicated in the services file on the PC in C:\\Windows (or whatever your windows directory is named). You can use the notepad editor to add this line to the PC's services file. It should duplicate the line in the /etc/services file on the host. Note that in Windows NT, the services file is in C:\\winnt\\system32\\drivers\\etc.
Entry in the PC's hosts File If the PC is not set up to use a name server, then the host name of the administrative machine must be in the hosts file in C:\\Windows (same as services for NT). If the PC is already being used to connect by tcp/ip to the host, then this requirement should have already been met. An exception to this might occur if a connection is always made currently using an IP address instead of a machine name. In this case, your institution might have decided to not put anything in the PC's hosts file.
Installing the ODBC Driver 7 PC Preparation Final Preparation For Informix driver, set up the Data Sources to be used by the programs which will access the database through the ODBC driver. Note that the configuration window for the Informix 3.3 driver has a test button which will immediately test for a connection to the database.
Working Without Permanent Leases in DHCP If you do not want to use permanent leases in DHCP, then a pool of addresses may be set up in which each administrative PC that will use ODBC is assigned an ip address. You must then assign a name for DNS purposes for each of these ip addresses. Each member of the pool should then correspond to an entry in the DNS and to an entry in the .rhosts file for each administrative user of ODBC.
Defining ODBC DSNs In order to use the CLI ODBC driver, you must define one or more ODBC DSNs. To perform this step, select Start/Settings/Control Panel/32bit ODBC. The first entry is the name of the DSN which will appear in any selection window that is presented to the user. For the Informix driver, you must provide the low level information when you configure the DSN.
Use of Two Drivers All Jenzabar Visual Basic PC programs require two database connections. The first connection is to the database and is accomplished when the CLI driver connects to cisinf to retrieve data from the database. The second connection occurs when the Jenzabar driver connects to cisaps to retrieve data from the virtual tables (appservers). The names of these two DSNs must be the same, except the latter will have "APS" appended to the end of the former (e.g., dbase and dbaseAPS. The names are case-sensitive.).
Passwords for Administrative Users When using the VB PC programs, observe the following restrictions when you select passwords for the administrative user: • The passwords must be less than or equal to eight (8) characters. • Do not use semicolons (;) in the password.
If You Are an NIS User If you use NIS on your campus, remember that changing network setup files such as the services file does not cause any changes to the data used by the systems until the NIS management program is used to publish the data.
PC Preparation 8 Installing the ODBC Driver Installing the Driver on the PC
Introduction After the Unix host is set up and the PCs have been prepared for installation, the actual installation process is accomplished through the use of an Install Wizard. This section details how to complete the wizard to obtain the desired results. The wizard displays a variety of dialog boxes, shown in the following pages for illustrative purposes.
Using the Wizard 1. Access the setup.exe program, located in the odbc32.v55 directory, using Windows Explorer or My Computer. 2. Click on the icon for setup.exe to execute the setup program. The Jenzabar ODBC Setup window appears, as follows:
3. Click on Continue. The Install Drivers window appears, as follows:
The listbox in the above window will contain two drivers for the 32-bit version of the driver. One of the two drivers is the debug version. Using the debug version displays a screen containing the SQL statements it is currently processing, providing problem solving information. On a user machine this version is optional, but Jenzabar recommends you install it on your institution's Jenzabar PC (i.e., the PC you must maintain to receive maintenance support on the PC-based products). 4. Highlight the desired driver(s), and then click OK. The ODBC driver is installed with the copying of some files onto the system. Notes: • When installing the 32-bit driver, do not choose only the debug version of the driver, since it displays an extra screen showing the SQL statements as they are being
Installing the ODBC Driver 9 PC Installation executed. In addition to being annoying to the user, the SQL display slows the operation slightly. • If the destination system does not already have ODBC installed, then setup will install the complete version 2.1 ODBC subsystem. If the destination machine already has a newer version of the ODBC subsystem installed, then setup will install only the Jenzabar ODBC driver. The way to determine which has occurred is to bring up the ODBC administrator after setup is complete. This is done using Start/Settings/Control Panel/32 bit ODBC. If the screen looks like the one shown below, then you have the 2.1 version. If the screen has tabs across the top of the window instead of buttons down the right side then, you have at least the 3.0 version. In the latter case, the About tab will give the versions of all of the important ODBC components. If at any time you need to call to the response center relative to ODBC, you should know the version of the ODBC subsystem. 5. Configure the Data Source. The Data Source window appears after the driver has been installed, but before the installation program exits.
The above window lists three different Data Sources; yours may list more or fewer sources depending on previous configurations. If this is the first installation of ODBC, then the window will be empty. 6. Add the first required source (the connection to cisinf) as follows: • Click Add. The Add Data Source window appears as follows, showing the available drivers:
• Choose the appropriate Jenzabar ODBC driver and click OK. The Setup Jenzabar CX ODBC Driver window appears (note that the Data Source Name and the TCP/IP Address fields may not contain the values shown in the following example):
PC Installation 10 Installing the ODBC Driver 7. Complete this window as follows: • At the Data Source Name field, enter a user-friendly name associated with this ODBC driver, such as: jenza (carstrn for training database) • At the TCP/IP Address field, enter the hostname or IP address of your machine, followed by a slash, then the port number that is specified in the /etc/services file on the host for accessing cisinf, such as: devi/9055 • Click OK. The Setup ODBC Driver window is replaced by the Data Sources Driver window, as shown below. In this example screen the Data Source Name chosen is jenza. In brackets, the screen also shows the driver that this Data Source uses. Note that Data Source names must be unique but that multiple Data Sources may use the same driver.
8. If required (i.e., if your institution runs the Document Imaging, Human Resources, or Institutional Advancement products from Jenzabar), click Add to add the second source (the connection to cisaps). The Add Data Source window appears, as follows:
9. Click on the desired installed driver to highlight it, then click OK. The Setup ODBC Driver window appears, as follows:
Installing the ODBC Driver 11 PC Installation 10. Complete this window as follows: • At the Data Source Name field, enter a user-friendly name for the connection using this ODBC driver to cisaps (AppServers), such as: jenzaAPS (carstrn for training database) Note: The second source name must be the same as the first, only with the appendage APS.
• At the TCP/IP address field, enter the hostname of your machine, followed by a slash, then the port number that was specified in the /etc/services file, such as: devi/9050 • Click OK, then Close until the setup is complete, as indicated by the window shown below. Click OK again to conclude the process.
PC Installation 12 Installing the ODBC Driver MIGRATING YOUR DATA SOURCES
Introduction If you have already used Jenzabar ODBC drivers for one or more Jenzabar PC applications, you may need to update the drivers to which the data sources refer when a new driver is released. For example, the end user may be accustomed to selecting the Data Service Name of jenza when launching Human Resources Administration, and that Data Service name may reference version 1.5.3 of the ODBC driver. When Jenzabar releases a new version of the ODBC driver (e.g., version 1.5.5), you want to ensure that jenza now references version 1.5.5. The simplest approach to updating your drivers is to use the ODBC configuration you can access from Start/Settings/Control Panel/Data Sources (ODBC).
How to Migrate Your Data Sources To migrate your data sources to a newer version of the ODBC driver: 1. Select Start/Settings/Control Panel/Data Sources (ODBC). The ODBC Data Source Administrator dialog box appears. 2. Click on the System DSN tab. 3. Highlight one of the Data Sources you want to update, then double-click it to select it. 4. Highlight the TCP/IP address, then press
Installing the ODBC Driver 13 Data Source Migration
TROUBLESHOOTING Note: This section is of primary benefit to new installations on a system, but may be of use in general troubleshooting. Depending upon what has preceded the problem, there are several potential problem areas in the ODBC system. The list given below contains some troubleshooting tips used at Jenzabar for each area. Not all apply to every problem. Starting at the lowest level program at the host and working towards the PC, the potential problem areas are:
The backend program, either cisinf or cisaps The actual backend program may not be working. Problems with the backend do not typically occur unless some process or event, such as an upgrade, takes place. Although Jenzabar does not supply a specific testing program, the following procedure may help you diagnose the problem. Go to the Unix directory containing the program (described above) and enter the command: ./cisinf or ./cisaps to directly execute it. If the program is working as required, it will start up (you can verify the startup using ps). Then, the cursor will return to the left and nothing more will display on the screen. If you press
The script that is executed by inetd, either cisinf.env or cisaps.env In the same directory containing the backend programs there are scripts which call those programs. If the normal setup was done, then inetd does not directly execute the programs when a connection is opened but instead executes the appropriate script. They set up environment variables needed by the backend programs, log the operation, and then execute the desired backend program. In this directory the script can be tested just like the program. Enter the command ./cisinf.env or ./cisaps.env. The response should be just as that for the programs. The script should run and as soon as you press
tcp/ip access to the script If neither of the previous tests uncovered the issue, then a problem could exist with tcp/ip access to the scripts. This is most likely due to incorrect entries in /etc/services or /etc/inetd.conf, which control network access to the backends. To test access through inetd, use this command:
telnet localhost 9055 (the port number for access to cisinf on carsi) This command will test the inetd.conf file entry. Follow this command with: telnet localhost cisinf_carsi (the service port name for access to cisinf on carsi) This command will test the services file entry. Substitute the ports for cisaps for those of cisinf if the problem is access to the AppServers. In each of these cases, the message should appear that connection has been made and the connection should drop as soon as you press
external access to the script from the PC Repeat the above sequence from the PC. Since each telnet program has different ways of determining the port with which to connect, the easiest process (at least on Win 95) is to use the Start/Run option to run the commands used above except that localhost is replaced by the hostname of the host computer. For example:
telnet admin 9055
Installing the ODBC Driver 15 Troubleshooting In each case a telnet window should pop up and as soon as you press
application access to the script from the PC If a Jenzabar PC program cannot access the database through ODBC, you need to determine whether the problem is with the cisinf connection or the cisaps connection. This is not always clear from the messages returned by the program. If you have a simple application such as the MSQuery program that comes with Office, you can use it to do a query individually on either connection. Alternatively, Informix provides a test program as part of the ODBC setup for Informix drivers. To locate the test program, complete steps 1-3 of the procedure titled How to Migrate Your Data Sources; click the Apply & Test button on the Connection tab of the dialog box to access the test program.
Tracing from ODBC Data Source Administrator is yet another tool to test ODBC drivers. Tracing can test drivers from any vendors. For cisinf, use “select * from id_rec where id = Known_id”. For cisaps, use “select * from ids_aps where id = Known_id”. If both of these work but the PC application still cannot connect, then the value stored in the registry for the last connection is probably incorrect. Each program has a method of dealing with this problem. This value is stored in the registry under the key HKEY_USERS\.Default\Software\VB and VBA Program Settings\application name\Settings and the name involves the word connect. If all else fails, then you can change this value manually. Everything after ODBC should be removed in regedit. license limitation In some cases the limitation to getting an ODBC connection may be due to the license manager. If this is the reason, it is usually readily apparent when examining the output of apstat. This listing will show the number of connections and also the number of denied connections. Running apstat will also free up orphan slots in the license table so may fix a problem as was described earlier. For more information about the apstat command, see volume one of the overall system manual.
Troubleshooting 16 Installing the ODBC Driver SUMMARY • The backend process on the UNIX side creates a file called /tmp/errors.log that logs messages from the Jenzabar CX backend processes. You can delete this file as needed. • For the Human Resources, Document Imaging, and version 2.0 of the IA applications to function properly, you must set up two different ODBC Data Sources. Typically, this will be carsi connected to port 9055, and carsiAPS connected to port 9050. You must consider two important items. First, the name of the second source must be identical to the first except for APS appended. Second, the first connection may use a different driver than the second connection. • You can confirm your installation through the Settings/Control Panel options available from your Windows® 95 Start menu. Select these options, then double-click on the ODBC driver icon to verify that your drivers are installed. • When the 32 bit drivers are installed, the information is stored in the registry. If the Data Source is added as a machine data source, then the Data Source information will be under the HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI key. If instead the Data Source is added as a user data source, then the information will be under the HKEY_CURRENT _USER\\Software\ODBC\ODBC.INI key. The information on the drivers is under the HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI key. • The setup_odbc script will install four entries in the /etc/services and /etc/inetd.conf files. Two are for the production backends cisinf and cisaps. The other two are for the debug versions of the same programs. You should exercise care about using these versions. They are slower and may generate very large log files in /tmp. They may, however, be of help in troubleshooting. • Remember that the purpose of the two ports, (which make up a pair) provided by the host are different. The higher number port is for accessing the Informix database directly. The lower port number is for accessing the virtual tables. It is normal, for example, to pass an SQL statement like, “select * from ids_aps where id = 10”, to cisaps. It is possible, for example, to pass an SQL statement like, “select * from id_rec where id = 10” to cisaps. When cisaps sees an SQL statement that accesses a real table it passes it off to cisinf. This should not be construed to mean that the cisaps port can be used indiscriminately. The cisaps program will not handle all of the situations that are handled correctly by cisinf. It is possible to use test programs against cisaps however. You should not expect that non-Jenzabar CX programs will necessarily work against cisaps. For example, you should use cisinf with Impromptu.
Installing the ODBC Driver 17 Summary
INDEX
data sources, 13 / N /etc/services, 5, 7, 11 NIS, 8 A O Add Data Source window, 10 ODBC driver C purpose, 1 cisaps, 1, 15 P cisinf, 1, 11, 15 cisodbc.dll, 1 PC hosts file, 8 PC services file, 7 programs D setup.exe, 9 data source, 10 data source name, 1 S Data Source window, 10 data sources scripts migrating, 13 setup_odbc, 5 debug version services file of driver, 9 on PC, 7 DSNs Setup Jenzabar CX ODBC Driver window, 10 defining, 8 setup program, 9 setup.exe program, 9 setup_odbc script, 5, 17 H steps, Unix system, 5 hosts file on PC, 8 T I troubleshooting, 15, 16 inetd.conf, 5, 6 U installation, 7, 9 Unix system, steps, 5 updating L ODBC references for Data Sources, 13 location of installation software, 7 V versions, 3 M virtual tables, 1 migrating
Installing the ODBC Driver 19 Index