Skip to main content

 

 

 

 

Template:OutSystems/Documentation_KB/Breadcrumb_New_Layout

 

 

Template:OutSystems/OSLanguageSwitcher

 

 

 

OutSystems

OutSystems Platform Server failover procedures

This guide describes two procedures to execute during failover scenarios:

  • Activate a passive front-end in installations with active and passive servers;
  • Move Controller and Front-end roles to a different server.

Activate a passive front-end in active/passive installations

An active/passive OutSystems installation is an installation where two or more front-ends grouped in:

  • An active group (the front-ends which are executing requests, timers and asynchronous logic) and,
  • a passive group (the front-ends in standby should failover be required).

The following table presents the steps required switch the front-ends from the passive to the active group.

Step Description Server
1 Stop and disable OutSystems Scheduler Service:
  • In .NET stack:
    1. Go to Start > Services.
    2. Right click on the OutSystems Scheduler Service and chose Stop.
    3. Right click it again and chose Properties
    4. In the Startup type dropdown, chose Disabled. Click OK at the bottom.
  • In Java stack:
    1. Use the command service outsystems stop SCHEDULER to stop the service.
    2. Disable the service with the command ./serviceconfigurator.sh -interactive
OutSystems active Server(s) that should be deactivated
2 Start service OutSystems Scheduler Service and set as automatic:
  • In .NET stack:
    1. Go to Start > Services.
    2. Right click on the OutSystems Scheduler Service and chose Start.
    3. Right click it again and chose Properties
    4. In the Startup type dropdown, chose Automatic. Click OK at the bottom.
  • In Java stack:
    1. Use the command ./serviceconfigurator.sh -interactive to activate Scheduler
    2. Start Scheduller with the command service outsystems start SCHEDULER
OutSystems inactive Server(s) that should be activated
3 Start service OutSystems Deployment Service and set it as automatic:
  • In .NET stack:
    1. Go to Start > Services.
    2. Right click on the OutSystems Deployment Service and chose Start.
    3. Right click it again and chose Properties
    4. In the Startup type dropdown, chose Automatic. Click OK at the bottom.
  • In Java stack:
    1. Use the command ./serviceconfigurator.sh -interactive to activate Deployment (if needed)
    2. Enter the command service outsystems start DEPLOYER
Every OutSystems Server

Move controller and front-end roles to a different server

If the server with the Deployment Controller role fails, publishing becomes unavailable. Applications continue to run but cache invalidation mechanisms won't be operational.

If your application is highly dependent on cache invalidation, to ensure full functionality, it's extremely important to immediately recover a Controller after a failure to regain full functionality of the Platform Server.

The following table presents the required steps to recover the Controller by moving it's role to another front-end in the same environment farm.

Step Description Server
1 Stop and disable Deployment Controller service:
  • In .NET stack:
    1. Go to Start > Services.
    2. Right click on the OutSystems Deployment Controller Service and chose Stop.
    3. Right click it again and chose Properties
    4. In the Startup type dropdown, chose Disabled. Click OK at the bottom.
  • In Java stack:
    1. Use the command service outsystems stop CONTROLLER
    2. Disable the service with the command ./serviceconfigurator.sh -interactive
Old OutSystems Deployment Controller server
2 Start service Deployment Controller service and set as automatic:
  • In .NET stack:
    1. Go to Start > Services.
    2. Right click on the OutSystems Deployment Controller Service and chose Start.
    3. Right click it again and chose Properties
    4. In the Startup type dropdown, chose Automatic. Click OK at the bottom.
  • In Java stack:
    1. Use the command ./serviceconfigurator.sh -interactive to activate Deployment Controller service.
    2. Stat the service with service outsystems start CONTROLLER
New OutSystems Deployment Controller server
3 Update location of Controller in OutSystems configurations.
The value written for this setting must be equal in all front-ends of the environment.
  • In .NET stack:
    1. Run Configuration Tool from the Start menu.
    2. In the Controller tab on the Deployment Controller Server field, enter the IP address of the new Deployment Controller server (the one used in step 2).
    3. Click Apply and Exit.
    4. Accept the restart of all OutSystems services.
    5. Answer No when a pop-up asks you to run the Service Center installation.
  • In Java stack:
    1. Run the Configuration Tool with the command ./configurationtool.sh
    2. Set the Deployment Controller Server option with the IP address of the new Deployment Controller (the server used in step 2).
    3. Continue running the options and accept the restart of all OutSystems services. When prompted, don't run Service Center installation.
All front-ends of this environment. Starting with the Controller
4 Service Center Installation
  • In .NET stack:
    1. Run the Configuration Tool from the Start menu.
    2. Click Apply and Exit.
    3. Answer Yes when a pop-up asks you to run Service Center installation.
  • In Java stack:
    1. Run the Configuration Tool with the command ./configurationtool.sh
    2. Keep the values for all options.
    3. When prompted, run Service Center installation.
Deployment Controller server
5 Obtain a new license (optional).
After moving the Controller role to another machine your license may become invalid. If you don't have the license file for the new Controller you need to request one. Check the following instructions:In case you need assistance contact OutSystems Support.
Licensing Portal
6 Install the new OutSystems license.
Check the instructions at How to install a license file
Service Center
7 Republish all applications.
  1. Access Service Center.
  2. Login with a Service Center administration account.
  3. Access Factory > Solutions.
  4. Locate an all-content Solution, ensure it carries all the modules of the environment and publish the current running version. If none exists, skip to the next step.
  5. Create a new Solution and add all the eSpaces and Extensions to it. Publish the current running version. (execute this step only if you skipped step 4).
Service Center

More information

Check the OutSystems Platform installation guide to learn more about the steps to follow for your specific stack.

  • Was this article helpful?