Configuring an existing system
To configure and update an existing system properties:
Applies to: On Premise Installations, before ASM Kratos.
Using Server Console, select the system you want to configure, then select Properties in the right-hand Actions panel.
Alternatively, right-click the system, then select Properties in the shortcut menu.
The System Properties window appears, with a selection of tabs relating to different system settings.
Make your changes:
For system settings, see Configuring general ASM System settings.
For database settings, see Configuring the database connection.
For general ASM-related server settings, see Configuring general server settings.
For diagnostics settings, see Configuring diagnostics.
For virus checker settings, see Enabling a virus check.
Select OK to save your changes and exit the System Properties window.
Exit Server Console.
A confirmation box appears.
Select Yes to save your settings and exit Server Console.
The application server cache automatically clears and refreshes. This may cause some slight performance delays.
You must restart the polling and IIS services for changes to the System Properties window to take effect.
Configuring general ASM System settings
On the System Properties General tab, you can change the following information:
Select Apply to save your changes.
Configuring the database connection
On the System Properties Database tab, you can configure the following database settings:
Select the License tab to change your license details.
If required, you can load the license key from a Server Manager License File (*.lic). Select Load From File to browse to the file and Open it.
Licenses control the number of analysts that can access the system. Contact your Alemba® Account Manager to increase the number of analysts on your licence.
Select Decode to view what your license provides.
Select the Website tab to configure the system virtual directory and MMA settings.
You may need to create a new virtual directory. For more information, see Configuring an existing system.
Ensure that your virtual directory is configured correctly, otherwise you will have difficulties running and upgrading your system, and using Chat. This is particularly important if you have multiple systems.
By default, the MMA URL points to the current server, using the following format: http://machinename/Virtual Directory/Core.aspx.
If you are using a qualified domain name for the Self Service Portal, specify the qualified domain name in the MMA URL field. This way, all the pages on the Self Service Portal will use the qualified domain name, rather than the name of the server/virtual directory.
When you create a new virtual directory, the Chat Virtual Directory field automatically populates with a path that exists within the selected virtual directory. We highly recommend that you use this default setting.
Select Apply to save your changes.
Configuring general server settings
On the System Properties Settings tab, you can change the following server settings:
Select Apply to save your changes.
Configuring diagnostics
If you select the check boxes on this tab, the relevant information is stored in the database. If you clear the check boxes, the information is not recorded.
On the System Properties Diagnostics tab, you can configure the following settings to help you troubleshoot issues that may arise:
If required, select Extract & Clear to extract all of the record queries into an XML file and place the file into the System/Diagnostics directory.
Everything is then deleted from the trace table.
Extracting data from the table into XML format can be slow.
If required, select Clear Trace to delete everything from the trace table.
Select Apply to save your changes.
Enabling a virus check
Alemba Service Manager™ can interface with a third-party virus checking application in order to scan uploaded files.
If you define a virus checker in the Server Console, the following will occur whenever someone uploads a file in Alemba Service Manager™:
The file is copied into a temporary location.
The specified virus checker application runs against the uploaded file.
Alemba® assumes that if the virus checker finds a virus, it will remove the virus if it is capable of doing so, and will delete any file with an unknown or irremovable virus.
If ASM finds the file in the temporary location, it will assume the file is clean.
If ASM cannot find the file in the temporary location, it will assume the file was infected and deleted.
To enable a virus checker:
On the System Properties Virus Check tab, you can configure the following:
Select Test to test the virus checking functionality.
The ASM Server Console attempts to create the virus checking directory and run the specified application.
Select Apply to save your changes.