Difference between revisions of "Database and Server Set Up"

From EHS Help
Jump to: navigation, search
(First draft)
 
m (Client App Installation)
Line 34: Line 34:
 
==Client App Installation==
 
==Client App Installation==
  
#Run the client app installation
+
#Run the client app installation & start the app.
 +
#Click "Connection" and enter the address of your server.
 
#[[Access AquilaCRS|Log in]]
 
#[[Access AquilaCRS|Log in]]

Revision as of 14:01, 13 March 2012

There are 3 elements to the AquilaCRS application:

  • Database
  • Application Server
  • Client (User) App

Database Installation

AquilaCRS supports any of the following database systems:

  • MS SQL Server @005 or later
  • MySQL 5.0 or later
  • Interbase 6 or later
  • Firebird 1.5 or later
  • Oracle 10 or later

Installation of the database is essentially down to your database team creating the database using the script or backup file available for us as part of your contract. If you need assistance please create a new support ticket on our [1].

Once the database has been created, you need to create a user for the application server to access the database.

Application Server Installation

There are two choices of installation for the application server:

  • Windows service
  • IIS web server

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
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.
IIS web server
for use in WAN environments where clients need to access the database outside of the LAN or you prefer not to open specific TCP ports on your server.
  1. Run the appropriate installer wizard to install the service.
  2. Edit the INI file to configure the database connection string


Client App Installation

  1. Run the client app installation & start the app.
  2. Click "Connection" and enter the address of your server.
  3. Log in