Updates

This function updates the FirstSpirit Server to a new software version.

For further information on updating the FirstSpirit server and the FirstSpirit backend, see:

• Updating the FirstSpirit server (general information) and
• Manual update via ServerMonitoring

Information display

The following information is displayed on this page:

(1) Name, license type, and current version of the FirstSpirit Server

(2) Name and current version of the installed modules

Depending on the server update configuration settings made via the corresponding parameters in the fs-server.conf file (see Area: server update parameters) page, a

• manual update via the update service (3)
• manual update via local files (4)
• or both (default setting)

will be possible. In the latter case, the required method must be selected by clicking the corresponding radio button.

Manual update via the update service

Update server (3)
The file(s) required for the update is/are then downloaded and installed from the Crownpeak update service (web interface) in a software-supported process. This requires an Internet connection.

Update to version: The required FirstSpirit version for the FirstSpirit Server update can be selected from the list. See also the Update service page for more information.

Update modules: If this option is selected, FirstSpirit modules are also updated. If the option is not activated (default setting), the modules are not updated.
Notice: For every FirstSpirit Server update, we recommend updating all installed modules which are supplied by Crownpeak as well as recreating and updating all self-created modules using the latest FirstSpirit version.Self-created modules are not included in this variant of the server update. A manual module update can be carried out via the ServerManager or ServerMonitoring.    
This area is not used to install modules. This means that only modules already installed on the server can be updated. Module files added here for which no earlier version was installed on the server are not installed or updated.

If the update service is not available, a corresponding error message will be displayed in FirstSpirit ServerMonitoring (“An error occurred while accessing the update service...”).

Manual update via local files

Update server (4)
The .jar or .fsm file(s) required for the update must first be downloaded outside of FirstSpirit. An update can thus be carried out independently of the Crownpeak update service.

Select update file: Click on this icon to open a window in which the required fs-isolated-server.jar file can be selected. The file is selected from the local file system.

Module file: Click on this icon to open a window in which the required module file (.fsm) can be selected. The file is selected from the local file system. Once the required file has been selected, another form field is displayed for the next module.
Notice: For every FirstSpirit Server update, we recommend updating all installed modules which are supplied by Crownpeak as well as recreating and updating all self-created modules using the latest FirstSpirit version.    
This area is not used to install modules. This means that only modules already installed on the server can be updated. Module files added here for which no earlier version was installed on the server are not installed or updated.

Module files already selected can be removed by clicking on this button. 

Starting a server update

Start server update (5)
Once the required FirstSpirit version (3) or the required files (4) have been selected, the update process can be started by clicking on this button. First, the files are uploaded to the server (see Update files). After this, an internal integrity and signature check is carried out. If this is successful, the server is shut down and then restarted automatically.

Any client connections to the server should be terminated before the server update to prevent any loss of data. Maintenance mode can be used to do this.