Skip to main content
OutSystems

OutSystems Platform 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 are separated in two groups: 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, open the Services management console and operate on service OutSystems Scheduler Service;
  • In Java stack, use command service outsystems stop SCHEDULER followed by disabling the service with ./serviceconfigurator.sh -interactive 

OutSystems active Server[s] that should be deactivated

2

 

Start service OutSystems Scheduler Service and set as automatic

  • In .NET stack, open the Services management console and operate on service OutSystems Scheduler Service;
  • In Java stack, use command ./serviceconfigurator.sh -interactive to activate Scheduler and then use service outsystems start SCHEDULER 

OutSystems inactive Server[s] that should be activated

3

 

Start service OutSystems Deployment Service and set as automatic

  • In .NET stack, open the Services management console and operate on service OutSystems Deployment Service;
  • In Java stack, use command ./serviceconfigurator.sh -interactive to activate Deployment (if needed) and then use 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 in the OutSystems® Platform. Applications will continue to run for a few days or until the license expiry date. At the time this note was written, this period is five days, but this may change in future revisions.

It is therefore extremely important to recover a Controller after a failure occurs to regain full functionality of the OutSystems Platform.

The following table presents the required steps to move the Deployment Controller role to another front-end in the same environment farm.

Step Description Server

1

Stop and disable Deployment Controller service

  • In .NET stack, open the Services management console and operate on service OutSystems Deployment Controller Service;
  • In Java stack, use command service outsystems stop CONTROLLER followed by disabling the service with ./serviceconfigurator.sh -interactive 

Old OutSystems Deployment Controller server

2

Start service Deployment Controller service and set as automatic

  • In .NET stack, open the Services management console and operate on service OutSystems Deployment Controller Service;
  • In Java stack, use command ./serviceconfigurator.sh -interactive to activate Deployment Controller and then use 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:
    • Run the Configuration Tool from the Start menu;
    • In the Controller tab set the “Deployment Controller Server” with the IP address of the new Deployment Controller (the server used in the previous step).
    • Click Apply and Exit. Accept the restart of all OutSystems services. When prompted, do not run Service Center installation.
  • In Java stack:
    • Run the Configuration Tool - ./configurationtool.sh;
    • Set the “Deployment Controller Server” option with the IP address of the new Deployment Controller (the server used in the previous step).
    • Continue running the options. Accept the restart of all OutSystems services. When prompted, do not run Service Center installation

All front-ends of this environment. Starting with the Controller

4

Service Center Installation

  • In .NET stack:
    • Run the Configuration Tool from the Start menu;
    • Click Apply and Exit. When prompted run Service Center installation.
  • In Java stack:
    • Run the Configuration Tool - ./configurationtool.sh;
    • Keep the value for all options. 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 will become invalid. If you do not have the license file for the new Controller you need to request one.

  • Access Service Center in Start Menu -> Programs -> OutSystems -> Service Center.
  • Access tab Administration -> Licensing -> Request a New License. You will be redirected to the licensing back office where you can obtain an updated license file.
  • In case you need assistance contact Licensing

Service Center

6

Install the new OutSystems license

  • Access Service Center in Start Menu -> Programs -> OutSystems -> Service Center.
  • Login with a Service Center administration account.
  • Access tab Administration -> License -> Upload License. • Upload the license provided by OutSystems. 

Service Center

7

Republish all applications

  • Access Service Center in Start Menu -> Programs -> OutSystems -> Service Center.
  • Login with a Service Center administration account.
  • Access tab Factory -> Solutions.
  • Locate an all-content solution. If none exists, create a new solution and add all the eSpaces and Extensions to it.
  • Create a new version of the solution and publish it. 

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?