Difference between revisions of "Database and Server Set Up"
From EHS Help
m |
|||
| Line 25: | Line 25: | ||
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: | ||
| − | ;Windows service | + | ;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. | + | :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 | + | ;IIS web server module: AquilaWeb.exe |
| − | :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. | + | :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. Installs to the cgi-bin (or scripts) folder of your IIS installation. |
====App Server Installation==== | ====App Server Installation==== | ||
| Line 34: | Line 34: | ||
#Run the appropriate installer wizard to install the service. | #Run the appropriate installer wizard to install the service. | ||
#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 lan server (aquilaserver.exe) settings filename is aquilaserver.ini. | ||
| + | ##Both files are located in their respective program folders. | ||
==Client App Installation== | ==Client App Installation== | ||
Revision as of 13:06, 15 March 2012
This is a Technical Instructions topic
There are 3 elements to the AquilaCRS application:
- Database
- Application Server
- Client (User) App
Contents
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 helpdesk.
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
- 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 or you prefer not to open specific TCP ports on your server. Installs to the cgi-bin (or scripts) folder of your IIS installation.
App Server Installation
- Run the appropriate installer wizard to install the service.
- 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 their respective program folders.
Client App Installation
- Run the client app installation & start the app.
- Click "Connection" and enter the address of your server.
- Log in
