AuditWizard - Installation Types - Multiple User
From Layton Support
(Difference between revisions)
SupportTech1 (Talk | contribs) |
m (Added headers, added links, bolded links) |
||
| Line 1: | Line 1: | ||
<p align="right">[[File:btn_back_up.png|link=User Guide for AuditWizard]] [[User Guide for AuditWizard|<u>Back to Contents</u>]]</p> | <p align="right">[[File:btn_back_up.png|link=User Guide for AuditWizard]] [[User Guide for AuditWizard|<u>Back to Contents</u>]]</p> | ||
| + | __FORCETOC__ | ||
| + | =Overview= | ||
In this configuration, each workstation has the application installed on it. They all use a common database, hosted on a SQL Server. | In this configuration, each workstation has the application installed on it. They all use a common database, hosted on a SQL Server. | ||
| − | |||
| − | |||
| − | + | [[File:aw_multiple_user.png|center|link=]] | |
| − | |||
| − | Pros | + | Start by installing the application on a server. This server will host the AuditWizard Service, which does a number of operations such as uploading of assets. It will have an embedded database. On launch, run the '''[[AuditWizard™ - Using AuditWizard - Administration - General - Database Maintenance - Change Database Wizard - SQL Migration|Change Database Wizard (SQL Migration)]]''' to migrate to the database to your SQL Server. Configure the AuditWizard Service on this computer in '''[[AuditWizard™ - Using AuditWizard - Administration - General - AuditWizard Services|Administration > General > AuditWizard Services > Service Control]]'''. |
| + | |||
| + | Then install the application on each computer as per '''[[AuditWizard™ - Installation|Installation]]'''. Each will also have an embedded database that you won't be using. On launch, run the '''[[AuditWizard™ - Using AuditWizard - Administration - General - Database Maintenance - Change Database Wizard - SQL Migration|Change Database Wizard (SQL Connection Change)]]''' to change the connection to the database on your SQL Server. | ||
| + | |||
| + | =Pros= | ||
*Multiple instances of the application can read the same data. | *Multiple instances of the application can read the same data. | ||
*If a full version of SQL Server is in use, not an Express version, the database can be automatically backed up using SQL Server's backup feature. | *If a full version of SQL Server is in use, not an Express version, the database can be automatically backed up using SQL Server's backup feature. | ||
*Users can use the application on their own workstation rather than logging into the server to run it. | *Users can use the application on their own workstation rather than logging into the server to run it. | ||
| − | Cons | + | =Cons= |
*Application must be updated on all workstations each time. | *Application must be updated on all workstations each time. | ||
*Deployment has to be centralised, in other words, done from the server, as Scanner and Agent configurations are stored locally, not in the database. | *Deployment has to be centralised, in other words, done from the server, as Scanner and Agent configurations are stored locally, not in the database. | ||
<p align="right">[[File:btn_back_up.png|link=User Guide for AuditWizard]] [[User Guide for AuditWizard|<u>Back to Contents</u>]]</p> | <p align="right">[[File:btn_back_up.png|link=User Guide for AuditWizard]] [[User Guide for AuditWizard|<u>Back to Contents</u>]]</p> | ||
Revision as of 00:42, 22 April 2014
Contents |
Overview
In this configuration, each workstation has the application installed on it. They all use a common database, hosted on a SQL Server.
Start by installing the application on a server. This server will host the AuditWizard Service, which does a number of operations such as uploading of assets. It will have an embedded database. On launch, run the Change Database Wizard (SQL Migration) to migrate to the database to your SQL Server. Configure the AuditWizard Service on this computer in Administration > General > AuditWizard Services > Service Control.
Then install the application on each computer as per Installation. Each will also have an embedded database that you won't be using. On launch, run the Change Database Wizard (SQL Connection Change) to change the connection to the database on your SQL Server.
Pros
- Multiple instances of the application can read the same data.
- If a full version of SQL Server is in use, not an Express version, the database can be automatically backed up using SQL Server's backup feature.
- Users can use the application on their own workstation rather than logging into the server to run it.
Cons
- Application must be updated on all workstations each time.
- Deployment has to be centralised, in other words, done from the server, as Scanner and Agent configurations are stored locally, not in the database.
