These instructions are for the 2-user or multi-user version of MiDatabank
and covers the installation of the database onto a SQL Server, and
the installation of the MiDatabank software on client PCs.
This information is also contained in two printable pdfs:-
Once installed please ensure that regular backups are scheduled using
the backup facilities within SQL Server. For further information regarding
backups please see the backup documention in the Help tab, or click here.
If you would like any technical advice regarding installation, please
call Keith Brown on 01225 385100 or email Keith.Brown@coacs.com
If you are upgrading to version 2.0 from a previous installation
please click here, otherwise read
on.
Requirements
Client Machines:
The recommended specification for Client Machines as follows:
Pentium 2.0 GHz with 256Mb of RAM or better
Screen resolution of 1024 x 768 or higher
Windows 2000 or Windows XP with the .NET Framework:
.NET Framework 1.1 for versions 1.0, 1.1 and 1.2 of MiDatabank
.NET Framework 2 for version 1.3 and 2.0 and 2.1 of MiDatabank
Server:
Midatabank requires a database hosted on Microsoft SQL Server (SQL
Server 2000 or SQL Server 2005). Many hospitals already have one or
more servers running Microsoft SQL Server and it is possible to host
the database on one of these existing servers. However, in some cases
a Trust IT department may ask that you purchase a new server and SQL
software.
In addition, a file storage area is used for storing any attachments
for an enquiry. For example, a scanned image of a letter or a pdf
attachment that was sent in an email.
If possible, it is recommended that a highly-redundant dedicated server
is used for hosting the SQL database - this should include dual power
supplies and RAID 5. Examples of suitable servers that could be used
include HP DL360 or DL380, and Dell PowerEdge 2950. The exact specification
will depend on the anticipated number of simultaneous users, and the
volume of enquiries taken.
Size of Database: A very rough estimate is about 20Mb to 1Gb for
around 50,000 enquiries, depending on the amount of text entered for
each enquiry.
Installation Disks
MiDatabank is supplied with 2 CD-ROMs. In most cases your IT department
will be responsible for installing the software from both CDs.
Database CDROM This disk is used to install the MiDatabank database on a SQL
Server. This database will store all the enquiries taken at your MI
Centre.
Software CDROM This disk is used to install the MiDatabank software onto workstations.
Once installed, the Systems Administrator configures the software
to connect to the database above.
Installation Overview
Install the database on your SQL Server using the Database
CDROM
Create a shared directory on your File Server for storing file
attachments
Install the applications on workstations using the Sofware
CDROM. Configure the applications with the location of the
database on your SQL Server
Launch the MIAdmin application and enter location of the shared
directory for storing attachments
Installation Details
Step 1 - Install the MiDatabank Database:
The MiDatabank Database is installed on the SQL Server using the
SQL script contained on the Database CDROM. This is usually
done by the Database Administrator.
From SQL Enterprise Manager, locate the SQL instance that you wish
to install the database, open the sql script
contained on the Database CDROM and execute this sql script. This
creates and populates a database called mi. The script may take several
minutes
to complete.
Once completed, the Database Administrator adds logins (either Windows
users or SQL logins) to the mi database, depending on whether Windows
or SQL Authentication is used.
There are two roles contained in the database:
MIAdministrator
MIPharmacist
In the case that the database uses Windows Authentication, the usual
practice will be to create a Windows group for the two types of user,
and to add the group to the corresponding role. For example, create
a group called MIAdministratorUsers and add this to the MIAdministrator
role, and create a group called MIEnquiryManagerUsers and add this
to the MIPharmacist role.
In the case that the database uses SQL Authentication, the usual
practice will be to create SQL logins for the two types of user and
add these to the corresponding role.
Once the database has been configured as above, the connection string
can be made available to the person responsible for installing and
configuring the windows applications (Step 3)
In addition, regular backups of the database should be scheduled
by the Database Administrator. For busy MI Centres this could be as
often as every two hours. For further information regarding backups
please see the backup documention in the Help tab, or click here.
Step 2 - Creating a Shared Directory: the
Systems Administator configures a shared directory for storing attachments
relating to enquiries. The shared area must have read/write permissions
for MI pharmacists using the Enquiry Manager windows application,
and could be located on the SQL Server or another server on the network.
Step 3 - Installing the Software: the Systems
Administrator installs the two windows applications (Enquiry Manager
and Administrator) on client machines. Following installation, the
windows applications must be configured with a connection string that
provides information about the location of the SQL database (see Step
1 above) and authentication details.
This can be achieved in several ways. For example:
Installing the software locally on each computer using the Software
CDROM, and manually editing the Init.xml files with the connection
string
or
Creating a custom msi installer containing the connection string
used at your institution. This could be used for installation to
workstations
using Active Directory, or for local installation from a CDROM.
Note: The windows applications must be configured
with the location of the MiDatabank database that was installed in
Step 1 above. This is done by editing the Init.xml file for both windows
applications. Click here to
see example connection strings.
Step 4 - Launch the MIAdmin application: the
last job is to launch the MIAdmin application and finish configuration.
The login details for MIAdmin are as follows:
Username: Administrator
Password: Equinox
Once you have gained access to MIAdmin, please ensure that you enter
the location for the shared directory where enquiry file attachments
will be stored. There is a field called 'Attachment Storage Directory'
that can be found inside the Configuration tab.
Note: It is strongly recommended that the password is changed. This
will prevent unauthorised access to MiDatabank administration functions.
Lastly, it is highly recommended that the list of resources is updated
from the master list which is centrally maintained by the UKMI. This
is done by navigating to the tab 'Sources Master List' and clicking
the button 'Check for Resource Updates'. In the event of any problem
with updates please click here
