 |
|||||||||
|
|||||||||
|
The Multi-User Contact Manager Do you have an office with multiple workstations? Are you tired of goofing around with single user contact managers and out-of-date paper lists? Install and run the Diurnalis Server Software on your server. Install the client software on your regular workstations. Now everyone can connect and use the company contacts without any hassles! Visit the manual for a better overview. Visit the Forums to provide feedback or to ask questions. You need Java to run this software. Put That Server To Use Diurnalis is a true network application. Instead of wasting processor power sitting idle as a "file server" you can better utilize your hardware investment by giving it some real work to do. Let your office staff seamlessly access some of your most vital information. Save time and improve workflow by giving everyone an up-to-date contact list at their fingertips. BETA 2: Launch Google Maps for addresses with the click of a button; Diurnalis completes the tedious data entry functions and performs an address search on Google Maps; the results come up in your web browser. Diurnalis is currently capable of printing to Dymo or Co Star Labelwriters. Diurnalis can run on Windows, Linux, Unix, Mac and more. Diurnalis is in BETA 3 release!
The Windows Setups zip contains two Setup.exe files, one for the server and one for the clients. The Server and Client zip files can be used on any system with Java, just extract the file where you need it, no need to make a directory first. This version of Diurnalis shuts down when a sixth workstation accesses the system. I will fix this with the next release; I forgot to disable the maximum clients limit. [This is fixed in BETA 2] If you have many users I would suggest BEA JRockit 5; it is a Java implementation by BEA. It can run any Java application but handles memory and threads better for servers. Diurnalis is not yet tested on BEA JRockit 5. If you get stuck I will be glad to help you, just email: software@datavirtue.com; response in less than 24 hours.
Requirements
Technology Notes Behind the scenes the Diurnalis Server regulates requests to the database. Each time a client tries to obtain information (List of names, address) it first checks with the server to see if it is available, if not a busy signal is sent to the client and it has to try again. This can happen a thousand times in one second. Usually before that "second" is up the client has gained access to the information. If there are a lot of requests the user simply experiences a small delay but nothing abnormal. However, this occurrence is very rare in a small office. This system can handle many users, although the maximum number is not known. I have tested the server with four automated clients (Windows 2K, XP, Linux) all making many requests at once on a large database table; the server was Dual Core 1.8GHz configured properly on Windows XP SP2 w/ 1024MB RAM and SATA 250gig HD. One of the client automatons was on the server itself. Even under this unusually demanding condition it performed very well for hours on end. The server had to handle thousands of requests a second while the clients were trying to run a search I knew would traverse a whole table (40k+ "records") to find each time they were granted access. The Diurnalis database CAN possibly be spread over several servers for the ultimate in access speed and availability. This however is a custom modification tailored for a specific situation and need.
|
|
||||||||
|
Copyright Data Virtue 2007 |
|||||||||
