Please consult the TranslationStudio Release Notes and Technical Data Sheet for a detailed list of requirements.
If you update FirstSpirit, it is possible that a new
fs-access.jar has to be deployed to TranslationStudio’s
Consequently, we recommend you copy the newest
fs-access.jar into the
lib folder to avoid any problems. To do so, please stop TranslationStudio first and start it again once the update has been successful.
Please check if the file
api-key.local exists in your
./conf directory. If it does not exist, TranslationStudio creates this file automatically.
|The api key is necessary for FirstSpirit to send data to the TranslationStudio Application.|
Please make sure to also update any connector if necessary.
Unless you implemented your own connectors, the TranslationStudio connector’s will be updated automatically whenever you update the application.
Therefore, you are (usually) only required to install/update the connector’s FirstSpirit modules via the ServerManager application.
You have to update the TranslationStudio module and any connector you have been using.
Please update the modules uses (via the respective ServerManager module button).
You should restart the module and check the module’s configuration for new parameters, especially the connector’s you are using (if necessary).
Please check that your
Please install the project scripts by running the install script in the respective FirstSpirit projects again.
|If you activated the automatic distribution, you do not need to run the install scripts anymore. However, please consult the server log files for potential errors during the installation.|
Finally, open the service’s configuration panel and click on
OK. This will add new property values introduced with this version of TranslationStudio.