In the following the installation of PackBench is described. PackBench can be used in one of the following scenarios:
•Standalone installation
PackBench components are installed on the same machine. The data is stored on a database server which can be either available locally, or hosted by a third machine. Each installation has to know the details of SQL database server connection.
•Server-client
PackBench components are split. Core components and services are installed on a central server, while other machines (clients) only require a thin PackBench client which then connects to the server. The data is stored on a database server which can be either available on the same machine where server components are installed, or hosted by yet another machine. The server components include a Windows Service which runs in the background and listens on a specific port. Each client only needs to know the URL and port that the server is listening to. The server configuration requires setting up the SQL database server connection. The server-client scenario allows easy abstraction, as the clients do not know anything about how and where the data is stored.
Regardless of whether the standalone or the client mode is installed, by the virtue of the fact that the database server can be hosted by any machine, both scenarios can be used to configure a shared workbench. Also, both scenarios are equally functional when the RayFlow interoperability is concerned.
|
Be aware: The standalone instance of PackBench can only operate as a shared server as long as it is running. After the instance has been closed all the server capabilities are gone. On the other hand, a server installation of PackBench will install a windows server which will run all the time.. |
In the following the installation for server, client, and the combined installation as a standalone device are described.