WorkTime Professional - How to setup Client-Server Mode
WorkTime can work in a client-server mode: it means, that all client WorkTime Professional
application(s) store and access data at single separate computer (database server).
To run WorkTime Professional in a client-server mode, you need to
1)
install Firebird database
server and WorkTime database on your server PC; and
2)
configure WorkTime
client application(s) to use the server database.
As a server you can use any PC in your local network. (Dedicated server
is not required - you can run WorkTime on that PC as well.)
1. Setup WorkTime database and database server
Download and install installation
This package will run Firebird database server installation. Installation is very simple: you don't need to change any options, just
click Next, .., Next, Finish.
On the Finish page do not remove mark from the Start Firebird Service now?.
Installations screenshots (also more information about Firebird) are here
Note: If there is a third-party firewall on your server
machine - make sure port TCP/3050 is enabled.
Note: Database file (wt4.fdb) must reside on
a hard drive that is physically connected to the host machine - not on the filesystem share or a network filesystem.
Also, it cannot be placed on a subst-ed or mapped drive.
2. Setup WorkTime Professional client computer(s)
Setup all WorkTime client applications (including WorkTime installed on the
server, if any) to connect to the server: Options menu, Database tab, click Change Database and enter server
name or IP address (here it's SERVER_PC) and local database path (default is
c:\WorkTime\wt4.fdb).
Note: Local database path means server's
local path - where the file is physically stored on the server.
That's it, now WorkTime uses server database for storing data.
Troubleshooting
If WorkTime cannot connect to the server with the message
Unable to complete network request to
host "SERVER_PC".
Failed to establish a connection.
unknown Win32 error 10060
1. Make sure that you have Firebird server installed and started on the SERVER_PC
computer
(check Control Panel - Firebird 2.1 Server Manager applet)
2. Disable your server firewall or add entry to allow communications on port
TCP/3050
3. Check your antivirus software to make sure it doesn't blocks network communication
4. Check that server name is resolved correctly (or use IP address)
5. To manually check if Firebird is accessible, run from your command prompt: telnet SERVER_PC 3050
Telnet should connect without showing any errors.