Stopping and restarting the GTServer service

It is advisable to restart the GTServer services of each instance regularly (a restart once a month is desirable).

The restart of a GTServer service should be done at a time of least demand (at night or on weekends).

The service should be configured to be launched at the start of the machine.

Purging Server Database History

The various server histories must be purged on a regular basis:

• Execution history (Main menu \ action history in GTAnswer)
• Polling history (Main menu \ polling history in GTAnswer)
• Login history (via the user management dialog box, button in the top toolbar of GTAnswer)

In GTAdmin, an option (in the Mail tab of the instance configuration) allows you to configure the number of days of polling logs to keep.

Deletion of old campaigns

Very old campaigns should be terminated and deleted (in agreement with those responsible/managers of these campaigns).

Cleaning the mailbox of the GTServer account

lf replies are sent by e-mail, the connection of GTServer to the mailbox (which is dedicated to it) may be slowed down if many messages not relevant to GTServer are present in the mailbox.

Reply emails from GTAnswer to GTServer are identified by a subject containing “Gathering Tools Answer Environment”.

All other messages are not relevant to the operation of GTServer and should be deleted from the GTServer mailbox.  They can be forwarded to another mailbox beforehand so that the people involved in the project can decide what to do with them.

Configuring the GTWeb PHP engine to accept large files

The PHP engine can be configured to accept response files larger than the default size.

This setting is made in the php.ini file.

The following entry in the php.ini file should be adjusted to the maximum size of .qstx files:

post_max_size = 8M

upload_max_filesize = 2M

The following entry in the php.ini file can also be adjusted :

max_execution_time = 30

Configuring the machine hosting GTServer

Separating the server on which GTServer runs from the database server can be advantageous in terms of performance.

Increasing the capacity of the GTServer machine (RAM, CPU, etc.) can be a lead.

The identification of the bottleneck (GTServer, database or, in a small number of cases, messaging) is an essential step in a performance diagnosis.  Enable all levels of logs in GTAdmin to get more information in the file logs and enable more accurate diagnosis.

Access to different sources (databases and messaging) outside of GTServer but within the same operating framework as the GTServer service is an avenue of exploration.

Switching to a POP or IMAP client rather than Exchange or Notes is always preferable.

If GTServer is running on a virtual machine, make sure that the host machine’s processors are not spread over too many virtual machines.

Shutting down other virtual machines on the host machine, moving the virtual machine to a dedicated host machine, or running GTServer on a physical machine instead of a virtual machine should improve performance and identify potential virtualization bottlenecks.

Gathering Tools Suite Update

Improvements and corrections are regularly made to the Gathering Tools suite.

Updating the suite, while remaining in the minor branch, should be done regularly to take advantage of these corrections and improvements.

To download the latest versions of the suite, you can:

• Contact support via email: support@gathering-tools.com) or via the support portal support.
• go to the download link of this site: Downloads