Starting the applications
| Table of contents |
ContentCreator
ContentCreator does not require a Java environment and can be accessed directly via the web browser. To start the client, simply click on the relevant entry on the FirstSpirit start page.
When starting ContentCreator, a project selection dialog appears after a connection is established; the dialog contains a list of projects available to the user who is logged in. To appear in this list a project must be activated for editing in ContentCreator (see ContentCreator settings).
For detailed information about FirstSpirit ContentCreator please see also respective documentation.
SiteArchitect
SiteArchitect is started via the FirstSpirit Launcher. The FirstSpirit Launcher is used to pass FirstSpirit product software updates to client systems automatically when started. File creation rights must be configured on system or user level (see FirstSpirit Launcher: Installation and permissions).
To start the application, simply click on the relevant entry on the FirstSpirit start page.
When starting SiteArchitect, a project selection dialog appears after a connection is established; the dialog contains a list of projects available to the user who is logged in.
For detailed information see Project selection (→Documentation FirstSpirit SiteArchitect).
 |
The use of window management tools under macOS may result in unstable behavior in SiteArchitect (freezing, increased memory usage). |
ServerManager
ServerManager is started via the FirstSpirit Launcher. The FirstSpirit Launcher is used to pass FirstSpirit product software updates to client systems automatically when started. File creation rights must be configured on system or user level (see FirstSpirit Launcher: Installation and permissions).
Software updates of the FirstSpirit products are automatically forwarded to the client systems via the FirstSpirit Launcher when starting. Among other things, the required authorisation configurations (e.g. file creation rights) must be made at system or user level for this
To start the application, simply click on the relevant entry on the FirstSpirit start page.
For detailed information see FirstSpirit ServerManager.
Note: Additional messages and information may be displayed depending on the browser used. For example, when starting SiteArchitect or ServerManager for the first time, Google Chrome requires confirmation from the user to run the FirstSpirit Launcher for this file type. To prevent this message from being displayed during future starts, you can open the context menu for the corresponding message and select the entry “Always open files of this type” (if that is desired).
|
Launch problems with macOS: The aim of the “Gatekeeper” security function on Apple Macintosh systems were reset to the “Mac App Store” default value with version 10.9.5. When the FirstSpirit SiteArchitect or ServerManager is launched, the following message may be displayed: “config.fslnch can't be opened because it is from an unidentified developer.” To enable SiteArchitect and ServerManager to be restarted, the settings must be reset to “Anywhere” under “Apple menu / System Preferences / Security & Privacy / General / Allow applications downloaded from”. All FirstSpirit versions 4.x and 5.x are affected by this problem. This problem may also be remedied with integrated macOS tools, namely scripts and Automator. |
ServerMonitoring
ServerMonitoring does not require a Java environment and can be accessed directly via the web browser. To start the application, simply click on the relevant entry on the FirstSpirit start page. This is where the license file can be easily installed, for instance.