Difference between revisions of "GXtest Daemon User's Manual"
(→GXtest Daemon) |
|||
| (8 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | [[ | + | {{Idiomas |
| + | |Manual de Usuario de GXtest Daemon | ||
| + | | GXtest Daemon User's Manual | GXtest Daemon ユーザーズマニュアル}} | ||
| + | [[Category: GXtest Guides]] | ||
GXtest Manager allows you to schedule the tasks which will run the test case sets. For greater flexibility in execution is that there GXtest Executor and GXtest Daemon components. The Executor is the engine that actually runs the tests and record the results in the database. Of these components could be multiple distributed instances. The Daemon is the component that allows GXtest Manager to communicate with the various Executors. | GXtest Manager allows you to schedule the tasks which will run the test case sets. For greater flexibility in execution is that there GXtest Executor and GXtest Daemon components. The Executor is the engine that actually runs the tests and record the results in the database. Of these components could be multiple distributed instances. The Daemon is the component that allows GXtest Manager to communicate with the various Executors. | ||
| Line 6: | Line 9: | ||
It installs as a Windows service, generally on the same machine where GXtest Manager is installed, but this is not a constraint. It is necessary to properly configure the Daemon to allow it to access to the database (String connection and authentication). | It installs as a Windows service, generally on the same machine where GXtest Manager is installed, but this is not a constraint. It is necessary to properly configure the Daemon to allow it to access to the database (String connection and authentication). | ||
| − | This component will be checking for Tasks to be performed (it monitors the database every | + | This component will be checking for Tasks to be performed (it monitors the database every 30 seconds). If there is some pending task to run, the Daemon invokes the corresponding Executor giving it the same Connection String. This provides the convenience of not having to configure each Executor after every configuration change to access to the database. Instead of that, this task is made centrally. |
| − | == | + | == Starting the service == |
| − | + | Everytime you start the machine this service will start automatically. | |
| + | To start the service manually just follow the following steps: | ||
| + | * Right-click "My Computer" then choose "Manage" | ||
| + | * In the tree on the left, go to "Services and Applications" and then "Services" | ||
| + | * Find the service "GXtest Daemon" and then do right click and select "Start" | ||
| − | + | == Settings == | |
| + | This component uses the same settings for connection to the database that the one indicated to GXtest Manager at the installation. If you need to change it, it can be configured in the file GXtestDaemon.exe.config in the installation directory (usually c: \ Program Files \ Abstracta \ GXtest Daemon). | ||
| − | === | + | Example:<br> |
| − | + | <connectionStrings><br> | |
| − | + | <add name="GxTest.Daemon.Properties.Settings.GXtestConnectionString" connectionString="Data Source=ABSTRACTA00\SQLEXPRESS;<br> | |
| + | Initial Catalog=GXtest; Persist Security Info=True;User ID=sa; Password=sa1234" providerName="System.Data.SqlClient" /><br> | ||
| + | </connectionStrings><br> | ||
| + | |||
| + | == Viewing the Logs == | ||
| + | To see the GXtest Daemon log messages you have to go to Windows Event Viewer here: | ||
| + | # Right-click "My Computer" then choose "Manage" | ||
| + | # In the tree on the left, go to "Event viewer" and then "Application" | ||
| + | |||
| + | You will find there the corrisponding logs of GXtest Daemon. | ||
Latest revision as of 02:53, 21 February 2014
 |
 |
 |
GXtest Manager allows you to schedule the tasks which will run the test case sets. For greater flexibility in execution is that there GXtest Executor and GXtest Daemon components. The Executor is the engine that actually runs the tests and record the results in the database. Of these components could be multiple distributed instances. The Daemon is the component that allows GXtest Manager to communicate with the various Executors.
It installs as a Windows service, generally on the same machine where GXtest Manager is installed, but this is not a constraint. It is necessary to properly configure the Daemon to allow it to access to the database (String connection and authentication).
This component will be checking for Tasks to be performed (it monitors the database every 30 seconds). If there is some pending task to run, the Daemon invokes the corresponding Executor giving it the same Connection String. This provides the convenience of not having to configure each Executor after every configuration change to access to the database. Instead of that, this task is made centrally.
Starting the service
Everytime you start the machine this service will start automatically. To start the service manually just follow the following steps:
- Right-click "My Computer" then choose "Manage"
- In the tree on the left, go to "Services and Applications" and then "Services"
- Find the service "GXtest Daemon" and then do right click and select "Start"
Settings
This component uses the same settings for connection to the database that the one indicated to GXtest Manager at the installation. If you need to change it, it can be configured in the file GXtestDaemon.exe.config in the installation directory (usually c: \ Program Files \ Abstracta \ GXtest Daemon).
Example:
<connectionStrings>
<add name="GxTest.Daemon.Properties.Settings.GXtestConnectionString" connectionString="Data Source=ABSTRACTA00\SQLEXPRESS;
Initial Catalog=GXtest; Persist Security Info=True;User ID=sa; Password=sa1234" providerName="System.Data.SqlClient" />
</connectionStrings>
Viewing the Logs
To see the GXtest Daemon log messages you have to go to Windows Event Viewer here:
- Right-click "My Computer" then choose "Manage"
- In the tree on the left, go to "Event viewer" and then "Application"
You will find there the corrisponding logs of GXtest Daemon.
