Installing, Updating or Relocating
The standard Server installer creates a complete BiblioTECH Server environment onto the 'Server' computer. Please note this does not have to be dedicated server infrastructure; many BiblioTECH Servers are run on standard desktop PCs. Determining the specification of hardware you require is entirely dependent upon either the infrastructure available upon installation at any given site, or any hardware you plan to purchase to operate BiblioTECH on.
This section provides a very simplified overview of the installation process. You should download and carefully read the BiblioTECH Server Installation Guide.
Steps followed by the installer:
- Checks for an existing BiblioTECH license – if a valid licence is NOT found (i.e. a new installation) or the information indicates that the license has expired, the SETUP process will request a new key. If a valid key is not entered, the process will abort.
- Uninstalls ALL BiblioTECH Server services (both 'Core' and 'Add-On' services).
- Installs/upgrades all executable files in the BT8 installation.
- Note: Any existing configuration files and data files will not be modified.
- Installs the 'Core' BiblioTECH services.
- Starts the services in sequence.
- As the services start, they perform 'in depth' housekeeping to ensure all required data structures are in place and have been checked to ensure internal consistency.
- If you had any 'Add-On' modules installed, you will need to download and install the updated versions now.
If you want to completely remove BiblioTECH from a Server, you will need to manually remove the data files in the BiblioTECH program and data structures. By default these folders are located in C:\Program Files (x86)\BiblioTECH and C:\ProgramData\BiblioTECH (hidden by default).
Installing a Client
Librarians and other users access the library system through a BiblioTECH Client. There are two Client options:
The BiblioTECH Client modules provide comprehensive access to the functionality of the BiblioTECH Library System.
BiblioTECH implements a web-server which provides a Search facility for all users with browser access to the BiblioTECH Server. The Web interface does NOT require any Client installation - just direct a browser to the URL http://10.1.2.3:8181 (replace 10.1.2.3 with the IP address of your local BiblioTECH Server).
Obtaining the BiblioTECH Client installation files
- On the BiblioTECH Server, start the BiblioTECH Client (the Client with all optional modules is always installed on the BiblioTECH Server).
- Open the System Utilities module. The default system password at installation is INDIG0 <-- note the last character is a zero.
- On the left panel, select and open the General section.
- Select the Installation Sets page.
- Click on the Client Install Set button; you will be asked for a folder (later, the files will need to be accessed from the target Client computer - select a network drive, USB drive, etc). Two files will be placed in the selected location, setup_BT8client.exe & setup_BT8client.ini.
Installing the Minimal Client
The minimal BiblioTECH Client consists of the Launcher/Menu & Search module. The other Client modules are optional and can be added/removed as required. On the target computer:
- Login using a 'local administrator' account.
- Open the location where you saved the installation files.
- Run the setup_BT8client.exe to install the Client. This will establish the required environment and copy the base-level files. It will then connect to the BiblioTECH server and download the additional files required to establish a minimal Client.
When a BiblioTECH Client Launcher is activated, it checks to see if there are any of the optional modules installed. If so, it will display the BiblioTECH Menu to allow the user to start their required module. Otherwise, it will automatically start the Search module.
Installing/Removing Optional Modules
Note: Once the Client environment has been established during the 'minimal Client installation', optional modules can be added/removed under a 'user level' account - there is no need to login as a 'local administrator'.
As the Menu is required to add optional modules, if Search is the only installed module, the menu would normally not be displayed. You will need to force the Menu to be displayed:
- Close all applications.
- On the desktop, locate the BiblioTECH Client icon and click once (to select it).
- Press and hold the CTRL key down.
- Press and release the M key (keep the CTRL key down until the menu is shown).
- On the BiblioTECH Menu, select the menu option File - Install Client Modules.
BiblioTECH is designed to give sub-second response to most queries and provides an extremely sophisticated search and data retrieval technology for the user. To achieve this, the BiblioTECH Server software requires uninterrupted access to multiple fast CPUs, ample system memory and a responsive network connection. A dedicated computer providing the Server functionality is the ideal solution. However, if you decide to proceed with the installation of the BiblioTECH Server within a virtual server environment, be sure to dedicate the necessary resources to the virtual machine.
- At least two CPUs (preferably 4)
- 4 GB of RAM
- Clear access to a high-speed network adapter
- At least 10 GB of high speed disk access
Care must be taken when installing other software on the same computer as the BiblioTECH Server. This is especially true when working with virtualised environments. If several virtual machines are to be hosted on a single computer and, any of those are disk or network intensive, they may impact the performance of the BiblioTECH Server.
Further, ensure the host computer has sufficient physical resources to allow all of the virtual machines' dedicated resources. Do not over allocate.
At the BiblioTECH offices we use virtual machines for almost all of our work. However, we have noted that performance can be adversely affected if you do not tune the virtual machine resources and make careful decisions about which virtual machines are hosted on the same host computer.
Hyper-V Dynamic Memory
This BiblioTECH TechNote discusses the use of dynamic memory when running a BiblioTECH Server in a Hyper-V based virtual machine. Microsoft Server includes the ability to allocate memory to Hyper-V based virtual machines both statically and dynamically.
Note: please refer to this article for details about Hyper-V memory allocation.
On top of the memory required by the operating system, memory consumed by all services and any running applications, a BiblioTECH Server will make three types of demands on memory.
During start up, the BiblioTECH Server will build ‘in-memory’ lists. These will need memory to roughly the size of your database plus around 10%. Once the server has started, while there may be minor variations, this memory allocation is effectively fixed in size.
During normal operations, while processing client requests, additional memory needs to be allocated. This memory is consumed on demand and then released.
Note: there could be several such transactions occurring at the same time.
Server Tasks memory
At various times throughout the day, a BiblioTECH Server will perform server-based tasks (sending emails, backups, etc.). These can require the allocation of significant amounts of additional memory for each task.
Memory Usage and Performance
If memory is allocated in Hyper-V as static, then the memory will be available on demand – no issues. However, if memory allocation is part static and part dynamic, a number of potential issues could arise:
- Allocation of dynamic memory is not instantaneous – there must be a delay (however small). This may have an impact on the responsiveness of the system.
- Over-Commitment of Memory – in situations where there are multiple virtual machines running on the same host computer, there is a temptation to over-commit the memory assigned to those virtual machines. This can be a good solution in that expensive server resources are utilised effectively.
However, each of the virtual machines running on the same host computer will make their own demands on memory. There is a chance that when the BiblioTECH Server makes a memory allocation request, there will not be enough memory available. If this did occur, there would be a performance hit to BiblioTECH (possibly severe).
The allocation of virtual machine resources (esp. CPUs & Memory) from the host computer's pool of resources is something that requires careful tuning. Each scenario is different and the requirements of a VM needs to be considered both for its own needs and for the impact on other VMs on the same host computer.
If you decide to utilise dynamic memory, you will need to tune the various parameters. As an initial starting point, try the following settings:
Start Up = 2GB (i.e. 2GB of static memory).
Maximum = 4GB (i.e. 2GB of additional dynamic memory).
Buffer = 30% (i.e. hold a reasonably sized chunk of memory available for this VM).
Priority = 70% (i.e. give the BiblioTECH VM a higher then average priority).