Laserfiche WebLink
CRDSS <br />TASK MEMORANDUM 1.05-5 <br />Study of System Integration Issues <br />Database - Remote Access of Database <br />1.0 ISSUE <br />The CRDSS database will reside at RTi during initial development. However, other workstations <br />will have to access the database from remote locations. The following issues must be addressed in <br />order to make such capabilities available while providing reasonable performance: <br />What INFORMIX products are necessary to allow an application on a remote machine to <br />? <br />access the database server? What configuration must be performed on both machines? <br />What are the performance issues and how can they be addressed? Can alternate <br />? <br />database/network configurations be used to increase performance? <br />2.0 DISCUSSION/ANALYSIS <br />What INFORMIX products are necessary to allow an application on a remote machine to <br />? <br />access the database server? What configuration must be performed on both machines? <br />The State has purchased several products from INFORMIX that access an INFORMIX database. <br />The chosen core configuration for the CRDSS includes INFORMIX Embedded SQL for C (ESQL/C) <br />and INFORMIX-OnLine. INFORMIX-OnLine is the name of the INFORMIX database engine, and <br />ESQL/C is the product used to create executable program written in the C language with Embedded <br />SQL calls to a database. When the workstation executing the ESQL/C application does not have the <br />database located locally, then two other INFORMIX products are required. INFORMIX has two <br />connectivity products for client/server configurations. One product, INFORMIX-Star, is placed on <br />the database server machine. When installed and running, INFORMIX-Star listens for and validates <br />incoming connections from users on a network. The other product, INFORMIX-Net, is placed on the <br />client or local workstation. When installed and running, INFORMIX-Net is responsible for <br />establishing connections and transmitting relevant user validation information to the database server <br />machine(s). <br />Given that these connectivity products are added to an already exiting network, the remaining <br />configuration tasks usually require minimal assistance from the UNIX Systems Administrator. For <br />the database server, the Systems Administrator must edit one network file (usually called <br />) and two system files, one for startup (usually called ) and one <br />/etc/services /etc/rc <br />shutdown file (usually called ). This facilitates the startup and shutdown of <br />/etc/shutdown <br />required network listening processes and registers these programs with the network. For the client <br />workstations, the Systems Administrator must edit one network file (usually called <br />). This facilitates the registration of the client connection program with the <br />/etc/services <br />network. <br />1 <br />A275 05.10.94 1.05-5 Malers, Rohlfs <br />