Once  is installed, the Setup Assistant can be accessed at any time. To access this menu, open the Setup.exe or Setup.sh file located in your  installation directory. A browser window will open and display the main menu. 

Status

The Status window tells you whether  is currently running, and the landing pages to access it. 

Settings

The Settings window allows you to manage the amount of RAM allocated for the database and application servers. Make sure the RAM is set to at least 50% the recommended amount.

In addition, you can add configuration options for the database and Wildfly, and select the database connection type. To see a list of the available Wildfly configuration options, click More... in the Wildfly options text.

Web Server

Web server settings are defined during initial installation, but can be changed later in the Web server section of the Setup menu. You may change all parameters related to external web server integration, as well as those for the built-in Apache Tomcat server. The input fields are described in more detail in the Database Server section of  Setup. 

Service Control

The Service Control menu contains the settings for  services. These include:

Software Update

For more information on updating to a newer version of , see Upgrade Guide. 

Backup

The Backup window allows you to store all  projects in platform-independent format in a default or chosen directory. These files may be stored as backups, moved to another computer for restoring, etc.  services are unavailable during the backup process, which may be lengthy depending on the amount of data. For more information, see Set Up Knowledgebase Backups.

To create a backup...

  1. Click Backup in the Setup Assistant.
  2. Select a folder path - either the default, or a custom folder.
  3. Click Perform backup.

Restore

The Restore window restores all projects stored in  format from a default or chosen directory. If the user selects "Purge the database before KnowledgeBases are loaded", all existing projects are deleted before restoration runs. In this case, the admin console KB stored in the file admin.xml.ew should be present in the backup directory. If no database cleaning is performed before restoration, then to avoid overwriting the active admin console KB, admin.xml.ew should not be in the directory.

Product Reset

Database resetting performs a low-level erase of the entire  database and returns the database to a new-install state. For obvious reasons, this option should be used with extreme caution. 

Snapshots

A snapshot in  is a set of files for restoring  to some previous state of your knowledgebase. A snapshot consists of three parts:

  1. Installer file.
  2. Stored project files.
  3.  configuration file.

If snapshot storing is enabled, project backups and configuration files from the ‘old’ installation are stored at the beginning of an update. The installer file from the ‘new’ installation is stored at the end of the update. Snapshot names contain the date the update was performed and part of the installer name. The number of snapshots to track is set by the user, but 1-3 snapshots are usually enough.

 

Maximum number of snapshots: The default value for the maximum number of tracked snapshots is 0 - snapshots are not enabled.  To enable snapshots, enter a non-zero value and click Change. If the user enters a number that is less than the number of already existing snapshots, the oldest snapshots are removed.

Delete snapshot: Snapshots can be deleted from the hard disk by selecting the radio button in the Delete column and then pressing the Delete snapshot button.

Restore from snapshot: Restoring from a snapshot installs  in a special mode and restores projects from stored data. To restore  from a snapshot, the user must select the Restore column radio button for the selected snapshot, then click Restore from snapshot.

This operation cannot be undone; the current state - code, data, and configuration - will be overwritten.

Mail Settings

The Mail settings Setup page allows the user to configure the most common mail system properties.  processes both inbound and outbound mail. You can disable one or both of these processes by clearing the corresponding check box. For instance, it is typically necessary to turn off email processing before importing a knowledgebase onto a new server. 

Disabling email processes is also useful for debugging. The option 'Add a prefix to the subject of all sent mail' can be used for debugging, or to label all emails sent from the server as belonging to a test server.

To disable outgoing or incoming email message processing...

  1. Navigate to the Mail Settings page of the Setup utility.
  2. To turn off outbound email, deselect the checkbox next to 'Enable automatic mail sending.'
  3. To turn off inbound email processing, deselect the checkbox next to 'Enable automatic processing of incoming mail.'

When inbound or outbound mail processing is disabled, messages still waiting to be processed are stored in queues. When mail processing is re-enabled, these messages will be sent or delivered. In order to prevent this, clear the outbound or inbound mail queue before re-enabling email processing.

To clear email queues for the whole server...

  1. From the Mail settings page, use the following buttons:
    1. Clear outgoing mail messages queue – this clears any outbound emails stored in the system but not sent.
    2. Clear incoming mail message queue – this clear any inbound emails received but not yet processed by the system.

Uninstall

To uninstall , the user must run the uninstall utility from the  installation directory. There are two ways to do this.

Or

After confirming that you really want to uninstall the software, the uninstaller removes the current instance of . Backups will be saved in the the $AL_DIR/data/backups directory, so you can restore or re-import them later. 

Related articles