Introduction / FirstSpirit Server configuration / Integration into an external application server

Integration into an external application server

The FirstSpirit web applications are provided as a WAR file. The WAR file is automatically created with appropriate configuration by the FirstSpirit Server during each startup. The connection parameters socket host and socket port between FirstSpirit web applications and the FirstSpirit Server are read from file fs-server.conf and entered into the deployment descriptor of the WAR file for configuring FirstSpirit web applications.

Carry out the following steps to configure the application of an external application server:

  1. The host name or the IP address of the FirstSpirit server must be entered in the configuration file /opt/firstspirit5/conf/fs-server.conf, so that it can be used as the destination address for the TCP connection (FirstSpirit SOCKET) from the servlet engines to the FirstSpirit server:
    HOST=my-local-FirstSpirit-hostname
  2. The ServerManager application can now be opened for integrating an external application server. The start page for invoking the application is provided by the web server integrated in FirstSpirit regardless of the external application server. This ensures that management of the FirstSpirit Servers continues to be possible if configuration problems occur with the external application server. Any web server control can be added and configured under Server properties. At first, add the desired external web server (see section Adding an external web server). When carrying out the installation by means of war files like in this case, the input box “Web directory” remains empty, because FirstSpirit does not have any access to the file system of the application server.
  3. Each FirstSpirit web application must be changed to the new configured external web server, as described in section Configuring an external web server for a web application.
  4. War files are available for installing the FirstSpirit web applications in order to integrate an external application server without access to the file system of the FirstSpirit Server. The war files can be automatically generated and downloaded via the ServerManager as described in section Configuring an external web server for a web application. Installation of the war files subsequently occurs manually via the respective web interface of the application server.
  5. The FirstSpirit web applications (e.g. ServerMonitoring) can now be installed on the web server (see section Configuring an external web server for a web application).

© 2005 - 2024 Crownpeak Technology GmbH | All rights reserved. | FirstSpirit 2024.11 | Data privacy