Difference between revisions of "Database and Server Set Up"
(Added NBID.ORG to the list of web service domains.) |
m (Added additional explanatory text & general proofreading) |
||
| Line 3: | Line 3: | ||
==Overview== | ==Overview== | ||
There are 4 elements to the AquilaCRS application: | There are 4 elements to the AquilaCRS application: | ||
| − | *Web Services | + | *Web Services |
*Database | *Database | ||
*Application Server | *Application Server | ||
*Client (User) App | *Client (User) App | ||
| + | |||
| + | Please note that the only currently available download is for the demo version of iBID that runs standalone and does not include the server modules. | ||
==Web Services URL== | ==Web Services URL== | ||
| Line 16: | Line 18: | ||
==Database Installation== | ==Database Installation== | ||
[[AquilaCRS]] supports any of the following database systems: | [[AquilaCRS]] supports any of the following database systems: | ||
| − | *MS SQL Server 2005 or later | + | *MS SQL Server 2005 or later (preferred solution) |
*MySQL 5.0 or later | *MySQL 5.0 or later | ||
*Interbase 6 or later | *Interbase 6 or later | ||
*Firebird 1.5 or later | *Firebird 1.5 or later | ||
| − | |||
| − | + | '''Please contact us if you are intending on using any database server other than MS SQL Server.''' | |
| − | Once the database has been created, you need to create a user | + | Creation of the database is should be done by your database team who will create the database & populate it using the script or backup file provided by us as part of the installation files. If you need assistance with this please create a new support ticket on our [http://www.evohelpdesk.co.uk helpdesk]. |
| + | |||
| + | Once the database has been created, you will need to create a single database user so that the application server can access the database. | ||
==Application Server Installation== | ==Application Server Installation== | ||
There are two choices of installation for the application server: | There are two choices of installation for the application server: | ||
| − | *[[Windows service]] | + | *[[Windows service]] (preferred) |
| − | *IIS web server | + | *IIS web server using a WinCGI module |
Both methods will operate successfully side-by-side, even on the same physical server. When to use which one depends on your requirements: | Both methods will operate successfully side-by-side, even on the same physical server. When to use which one depends on your requirements: | ||
| Line 40: | Line 43: | ||
====App Server Installation==== | ====App Server Installation==== | ||
| − | #Run the | + | #Run the installer wizard to install the service. |
##Open the correct port on your servers firewall. Defaults to 8099. | ##Open the correct port on your servers firewall. Defaults to 8099. | ||
#Edit the '''INI''' file to configure the [[database connection string]] | #Edit the '''INI''' file to configure the [[database connection string]] | ||
##The web server (aquilaweb.exe) settings filename is aquilaweb.ini. | ##The web server (aquilaweb.exe) settings filename is aquilaweb.ini. | ||
##The lan server (aquilaserver.exe) settings filename is aquilaserver.ini. | ##The lan server (aquilaserver.exe) settings filename is aquilaserver.ini. | ||
| − | ##Both files are located in | + | ##Both files are located in "Program Files" under a folder called "Evolution Healthcare Systems Ltd" |
==Client App Installation== | ==Client App Installation== | ||
| + | |||
| + | The client application is installed per-user, so each user needs to install their own copy of the client software. The installation is a one-click installation. This is vital to allow standard user profiles the ability to receive automatic program updates. | ||
#Run the client app installation & start the app. | #Run the client app installation & start the app. | ||
#Click "Connection" and enter the address of your server. | #Click "Connection" and enter the address of your server. | ||
| + | |||
| + | If your server is located on a machine called SERVER01 and is running on port 8099, the Connection will be '''http://server01:8099/bin'''. (The client application uses the HTTP protocol to communicate with the server, hence the use of "http://" in the connection string). | ||
| + | |||
| + | To discuss any aspect of the installation please raise a ticket on our [http://www.evohelpdesk.co.uk helpdesk] system, or call 01964 503400. | ||
| + | |||
#[[Access AquilaCRS|Log in]] | #[[Access AquilaCRS|Log in]] | ||
Revision as of 15:41, 13 July 2012
This is a Technical Instructions topic
Contents
Overview
There are 4 elements to the AquilaCRS application:
- Web Services
- Database
- Application Server
- Client (User) App
Please note that the only currently available download is for the demo version of iBID that runs standalone and does not include the server modules.
Web Services URL
AquilaCRS uses some web services for accessing updated data items (e.g. drop down list contents), for registering iBID systems & for accessing automatic software updates. The following domains need adding to the whitelist on your firewall/proxy server in order to prevent system failures:
Database Installation
AquilaCRS supports any of the following database systems:
- MS SQL Server 2005 or later (preferred solution)
- MySQL 5.0 or later
- Interbase 6 or later
- Firebird 1.5 or later
Please contact us if you are intending on using any database server other than MS SQL Server.
Creation of the database is should be done by your database team who will create the database & populate it using the script or backup file provided by us as part of the installation files. If you need assistance with this please create a new support ticket on our helpdesk.
Once the database has been created, you will need to create a single database user so that the application server can access the database.
Application Server Installation
There are two choices of installation for the application server:
- Windows service (preferred)
- IIS web server using a WinCGI module
Both methods will operate successfully side-by-side, even on the same physical server. When to use which one depends on your requirements:
- Windows service — AquilaServer.exe
- for use in a LAN environment where clients will connect over TCP/IP and you can safely open a port on your servers firewall. This configuration provides the best performance. Installs via a wizard to "Program Files".
- IIS web server module — AquilaWeb.exe
- for use in WAN environments where clients need to access the database outside of the LAN. Installs to the cgi-bin (or scripts) folder of your IIS installation.
App Server Installation
- Run the installer wizard to install the service.
- Open the correct port on your servers firewall. Defaults to 8099.
- Edit the INI file to configure the database connection string
- The web server (aquilaweb.exe) settings filename is aquilaweb.ini.
- The lan server (aquilaserver.exe) settings filename is aquilaserver.ini.
- Both files are located in "Program Files" under a folder called "Evolution Healthcare Systems Ltd"
Client App Installation
The client application is installed per-user, so each user needs to install their own copy of the client software. The installation is a one-click installation. This is vital to allow standard user profiles the ability to receive automatic program updates.
- Run the client app installation & start the app.
- Click "Connection" and enter the address of your server.
If your server is located on a machine called SERVER01 and is running on port 8099, the Connection will be http://server01:8099/bin. (The client application uses the HTTP protocol to communicate with the server, hence the use of "http://" in the connection string).
To discuss any aspect of the installation please raise a ticket on our helpdesk system, or call 01964 503400.
