Workbench uses the Borland InterBase Server as the database. This is a separate product supplied by PQ as part of Workbench. The current version is V7.1 for Windows 2000/2003 Server. It is installed onto the server prior to installing Workbench.
PQ Systems strongly recommends a separate server for Workbench. If you do not use a separate server, the performance may be severely affected proportional to the other processes that server is providing. Also we cannot guarantee there will be no inter-operability issues. Users do not require authentication to the InterBase Server to connect to the databases, therefore a 5 User Server License will be sufficient.
Windows 95/Windows 98/Windows NT Workstation (4.x)/Windows 2000/Windows XP/Windows Vista
* Protocol Support: Clients using TCP/IP must have a compliant Windows TCP/IP stack and WINSOCK support. Windows 95/98/NT/2000/XP/Vista can support multiple protocols. This is important if you are using a different server for the InterBase server than the Shared Area! Clients are strongly advised to use the UNC1 convention rather than drive mappings. This will require the ability of a client to support the use of a UNC.
(UNC = Universal/Uniform Naming Convention - \\Computername\Sharename)
Your Intranet should be configured and working, so that users' have the ability to access the IntraVista Web Server and appropriate URL's (e.g. www.myserver.co.uk).
You will need access to the Web Server at an administrative level to install the software and configure the appropriate Registry entries.
Local clients must have their browsers configured to allow creation of a cookie. In order for your browsers to take advantage of our new JAVA macro applet–you must configure the browsers to accept the IntraVista server as a trusted site.
Unlike the Windows client software, which obtains a license and retains it for the duration of the user's active session, the Web Module uses a standard Internet Browser. Due to the 'stateless' nature of a browser, it is not possible for the server to detect if the user's session has been completed successfully, or crashed, or if he or she is still using the software but has gone to lunch. This would obviously use up legitimate licensed connections to Workbench very rapidly. To prevent this happening, the License manager service must be run on the Workbench Server. This will actively enforce a strict, preset timeout value if the session is inactive longer than that value, and recycle the license back into the license pool for use by other users.
The product supports the Windows Code Page 1252 Character set. Languages that use this character set are:
The product does not support variants of this: i.e. Code Pages 1250,1251, 1253. These include: Albanian, Byelorrussian, Bulgarian, Croatian, Czech, Estonian, Greek, Hungarian, Latvian, Lithuanian, Macedonian, Romanian, Russian, Serbian, Slovak, Slovarian, Turkish or Ukranian. Other unsupported character sets include: Cyrillic, Greek, Chinese, Hebrew, Japanese.
Workbench Professional may not work properly you implement incorrect keyboard/character support at either client or server.