| [ <- Previous Page ] | [ ^ Table Of Contents ^ ] | [ Next Page -> ] |
This configuration demonstrates four types of interface programs, ptrkeys settings, logging, and interprocess communication.
The timer program (A) submits a transaction to the engine at some user defined time interval. When timer (A) submits a transaction, it sends a wake up message to sample client program (B). When client program (B) gets the wake up message, it retrieves the next record from the idata table in the database (E) and sends it to sample server program (C).
Sample server program (C) will insert the transaction into the database (E), send an acknowledgement to sample client program (B), and send a wake up message to file output program (D). File output program (D) will retrieve the next message from the database and write it to some user defined output file.
| Program | Source Directory | Config File | Script File |
|---|---|---|---|
| Timer Program | zwebit/source/ztimer1 | zwebit/test/config/ztimer1.pro | zwebit/bin/fromtimer |
| Sample Client | zwebit/source/zclient1 | zwebit/test/config/zclient1.pro | zwebit/bin/testclient |
| Sample Server | zwebit/source/zserver1 | zwebit/test/config/zserver1.pro | zwebit/bin/testserver |
| File Output Program | zwebit/source/zfilegen1 | zwebit/test/config/zfilegen1.pro | zwebit/bin/tofile |
There are four ptrkey entries required to run the four test interfaces. The following commands will load the ptrkeys into the test database.
Filename: zwebit/sql/testkeys.sql
To load the test ptrkey values
Verify the interfaces have been loaded in the ptrkeys table for the first test system. On the main web page menu, select View Interfaces for the test system. There should be four entries: FROMTIMER, TESTSERVER, TESTCLIENT, and TOFILE. If these do not exist, see the previous section in this chapter (Ptrkeys Entries) for instructions on how to add the items.
Review the configuration files for these programs and become familiar with them. From the main menu, select View Interfaces, select one of the interfaces and then, select the configuration file.
Start the interfaces
If they do not run, check the log files for error messages.
| [ <- Previous Page ] | [ ^ Table Of Contents ^ ] | [ ^ Top Of Page ^ ] | [ Next Page -> ] |
Visit the GNU home page.
FSF & GNU inquiries & questions to
gnu@gnu.org.
Comments on these web pages to
info@zhsac.com.
Copyright (C) 2003 HealthCare Systems and Consulting
Verbatim copying and distribution of this entire article is
permitted in any medium, provided this notice is preserved.
Last updated: 07/21/2003