Core Platform Reload/Restart Best Practice

Core Platform Reload/Restart Best Practice

It’s generally a best practice to restart all servers once per week. To achieve this follow the directions below:

  1. Navigate to the Acrolinx Dashboard 
  2. Click Servers
  3. Click Restart All

More information about garbage collection, and general performance monitoring of your Core Platform can be found via the following article: 
Monitoring the Performance of Your Core Platform.

Some customers choose to restart servers regularly to ensure that the terminology changes are pushed live for checking. This also ensures the garbage collection cache is emptied.

When Do I Have to reload/restart Acrolinx Language Configuration or Servers?

Which of the following changes warrant a restart of the server to ensure that changes go live as soon as possible? And which servers do we restart (All Servers, Load language configurations, etc.)?

  • Terminology change (for example, add/delete discovered term, modify linguistic info, change description)
  • Guideline change (for example, changing to disabled or contextual)
  • Reuse Repository change
  • Other changes

The level of (language) server reload/restart depends on the task. Some changes take effect immediately, as specified in the following procedures:

To reload or restart your language servers follow the directions below:

  1. Navigate to the Acrolinx Dashboard
  2. Click "Servers"
  3. Click "Reload All Language Configurations"

For the most part, if you change settings in the Dashboard and a restart is required, you’ll be prompted to do so.

Changes to the terminology or reuse DBs (adding, deleting, updating entries) require language server reloads to push changes live. You won’t be prompted to reload the servers for these types of routine changes.