|
There are significant changes in the ways Databuild handles larger networks with the introduction of the Databuild Hub
The hub centralizes control of the network in one spot under the control of an administrator
The main benefits of Databuild Hub are:
| • | You can now see what users are currently using Databuild, Job Control and Front End. |
| • | You can now see what users have been using Databuild and their last access date for Databuild, Job Control and Front End. |
| • | You can view and set INI files for each user. These can be stored on your server, rather than in local windows folders of each workstation. |
| • | You can view and set Common Databases for each user. Once again, these can be stored on your server, rather than on each workstation. |
| • | You can see what version each workstation is running, who has used it and when |
| • | You can download current version numbers |
| • | You can download latest software versions |
| • | You can force any users to automatically update their software. |
| • | Registration, Support PINs and additional users and modules are set once only. These no longer have to be done on all workstations |
| • | Registration can be done over the web. No need to ring Databuild for an install code |
| • | You set your database type and server details once only |
Installing the Hub
| • | Install Databuild Hub into a folder on your server |
| • | Run DBHub.exe from any workstation or server. This will initialise it |
| • | Install or update Databuild version 2-30 or later onto your workstations. This will install LaunchDatabuild.exe into the same folder, and create a shortcut this application |
| • | Instead of running Databuild directly, you run LaunchDatabuild.exe instead. This small applications then runs Databuild and closes itself, unless your supervisor has requested you update your software. The first time you run this application, it will ask you to point to DBHub.ini |
That’s it. For all intents and purposes, it’s no different to the average user. It just makes life a lot easier for your administrator.
You can locate the Hub program anywhere, but the Hub ini file (DBHub.ini), licence file (DBHub.lic) and the hub database (If you are using a MS Access hub database) must be in a folder accessible to all seats. If the hub program is not in the same folder, the hub folder must be passed as a parameter in the hub shortcut.
|