Re-Install the OutSystems Platform on a different path

In the deployment controller server

In the server with the Deployment Controller role, do the following:

1. Stop IIS: open IIS Manager and click Stop on the right pane under Manage Server > Actions.

2. Stop all OutSystems Services. You can do this in the Services application in Windows to all services that start with "OutSystems".

3. Backup the private.key and server.hsconf files present in the installation folder (by default, "C:\Program files\OutSystems\Platform Server").

4. Remove RabbitMQ Service. To do this, open the installation folder, navigate to "\thirdparty\RabbitMQ Server\rabbitmq_server-%version%\sbin", and open the command prompt in this folder. Execute the following command: rabbitmq-service.bat remove

5. Uninstall RabbitMQ using the operating system's features to manage installed programs (for example, in Windows Server use Control Panel > Programs and Features).

6. Uninstall Erlang OTP using the operating system's features to manage installed programs.

7. Uninstall the current OutSystems platform using the operating system's features to manage installed programs.

8. Delete all entries in the ossys_parameter database table that contain the older installation folder path (depending on the platform version these entries may not exist).

9. In the .NET configuration files, delete all settings related to the previous installation folder. We can find these configuration settings in the machine.config file, in each of the following folders: "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config" and "C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config"

10. Delete all environment variables related to Erlang and RabbitMQ (such as ERLANG_HOME, OUTSYSTEMS_RABBITMQ, RABBITMQ_BASE, RABBITMQ_NODENAME). To do this, open the Advanced System Settings option and click Environment variables. Then, select the system variable and click Delete.

11. Re-install the OutSystems platform on the new path (for example, "D:\Program files\OutSystems\Platform Server"). To do this, you need to run the OutSystems Platform Server installation package (PlaformServer-<version>.exe) of the same version.

12. Restore the private.key file and server.hsconf files backed up on step 3 on the new installation path overwriting any files that may be present.

13. Start IIS: open IIS Manager and click Start on the right pane under Manage Server > Actions.

14. Open the Configuration Tool and navigate to the Cache tab. Then click on Create/Upgrade Service.

15. Click Apply and Exit.

16. A popup will be shown asking you to run the Service Center installation. Accept by clicking Yes.

17. Publish the System Components.

18. Re-publish all applications.

In any additional front-end server

If your OutSystems environment has additional front-end servers, after executing the above steps on the deployment controller server, execute steps 1 through 16 on each of the front-end servers.