Moving OutSystems Hub / Platform Server to a new location on your server

Back to Forums

AcacioPN

Staff

Moving OutSystems Hub / Platform Server to a new location on your server

Discussion

How-to

Context:

Your server has the OutSystems Platform Server installed in the C: drive, but it is running out of disk space and you have a D: drive which holds a lot of disk space, so you wish to move it there;
OutSystems Platform Server 4.0 or above installed;
You are using the .NET stack.

Preparing for it

This procedure involves redeploying all the eSpaces in that factory after the installation, and will cause the lost of the Personal Areas (versions deployed by using the Run feature). Make sure that all the developers are aware that changes that were not 1-Click-Published will be lost (i.e. all changes applied by using the Run option will not be saved). Also, considering this will cause downtime, make sure that the developers are aware when you do this intervention.

- Be careful if using this procedure in a production environment! -

Please read all the procedure before starting it.

Make sure you have the necessary files
Before starting the procedure, make sure that you have the necessary files, of the same revision currently installed:

OutSystems Hub Server installer;
(optional) OutSystems Service Studio installer (if you wish to move it too);
(optional) OutSystems Integration Studio installer (if you wish to move it too);

Create an all-content solution
Before starting the procedure, we recommend that you create an all-content solution with all the eSpaces and extensions in the factory, to ease the redeployment stage. To do this, follow these instructions:

Access Service Center, navigate to Factory | Solutions;
Create a new solution;
Add all the components of the factory to the solution, in the Components tab. To ease up the task, insert a dot (.) in the Associate Components to Solutions field and choose components from the drop-down that shows up. Remember to check the include dependencies checkbox, to minimize the number of times you need to do this. Select 4 or 5 components at a time and press Associate. Repeat this until no more options appear.
Press the Create version button. Choose a name for it, and press Save.
Your solution is created. This is the solution with the versions that will be redeployed.

Back up your database!
In case you do something wrong with the database, you need this to roll back. Don't say you did not get warned...

Moving the Platform Server
The procedure to actually move the Platform Server should be:

Stop all the OutSystems Services;
Make a backup copy of files server.hsconf and of all files *.exe.config found in the Hub Server installation folder;
New! since 9.0.1 Back-up file private.key as well!
Uninstall the OutSystems Platform Server;
- (optional) If you wish to move Service Studio to the new location, uninstall and reinstall Service Studio to the new location (e.g. D:\OutSystems\Service Studio);
- (optional) If you wish to move Integration Studio to the new location, uninstall and reinstall Integration Studio to the new location (e.g. D:\OutSystems\Integration Studio);
Install the OutSystems Platform Server to the new desired location (e.g. D:\OutSystems\Platform Server);
Place the backup copies of server.hsconf and of the *.exe.config files in the new location (e.g. D:\OutSystems\Platform Server);
New! since 9.0.1 Also put file private.key in the same folder!
In the Windows Services console, disable all 5 OutSystems Services to prevent errors during the next few steps.
Run the Configuration Tool, press all the Test Connection buttons and make sure that they don’t give any error; after this, exit the Configuration Tool by pressing Apply and Exit. Do not run Service Center installation.
Confirm in the database (OSSYS_PARAMETER table) that all settings with a folder name (column VAL) point to the correct place. If you have multiple front-ends, only update the lines for the correct server (column HOST).
You can locate the settings which contain folder locations by searching by the old path, e.g.
select * from ossys_parameter where val like '%C:\Program Files\OutSystems\Platform Server%'

If you are not comfortable editting values in the database, request help from someone who is.
If you do something wrong, you will need to restore the database from a backup.
In the Windows Services console, set all 5 OutSystems Services to automatic start.
Run the Configuration Tool, press Apply and Exit and wait for Service Center install, After it is complete, you should be able to successfully access Service Center.
Access Service Center with the admin user;
Navigate to Factory | Solutions, choose the solution you created before, and publish the version you created.

After this, the Platform Server is now installed in the new location. Make sure everything is up and running and then you can proceed to erase the previous Hub Server folder.

Please refer to the installation checklist if you have any doubts on any of the steps described.

07 Mar 2008

Nelson Freitas

Hi Acácio,

I'm having exactly this problema, but with 7.0 version.

What I did was:

- Open the configuration tool and export my current configuration
- Uninstalled Platform Server
- Deleted Outsystems folder from c:\program files
- Restart the machine
- Install Platform Server on D:\Outsystems and it did it
- Open Configuration Tool and import the configuration saved before
- Create/update database/session followed by apply
- It asked if I wanted to install Service Center wich I accepted
- A in that step, it created again the folder c:\Program files\Outsystems\Platform Server with several folders
- After that, all my publishing files are saved in c:\Program Files.....

What did I do wrong?

Thanks,

Nelson Freitas

06 Feb 2014

1 reply

09 Jul 2015

Show thread

Hide thread

AcacioPN

Staff

Hi all

For those that have been having issues with this operation, it seems that at some point the procedure above stopped working because of two distinct issues:
> At some point in version 7 some of the settings in the database are no longer updated automatically when you run ConfigurationTool (thanks Nelson!, I did not know how far back this went)
> Since version 9.0.1 it is not enough to just back up server.hsconf; you need to backup private.key as well. This is used to encrypt passwords in server.hsconf.

I will edit the original post with the changes.

Acácio

09 Jul 2015

Harry Marrenga

As indicated by support following steps are also needed (I had to clean these records twice):

To overcome the error that you are experiencing, you should indeed proceed with the Clean up of the Environment security context as suggested in this forum post.

Clean up the Environment security contexts, as follows:

Open SQL Server Management Studio (or another query editor), connect to the restored database and execute the following SQL statement:

delete from ossys_parameter where name = 'ClientApplicationToken';
delete from ossys_parameter where name = 'privateKeyValidation';
delete from ossys_Parameter where name = 'OutSystems.HubEdition.MobileLogin_AuthenticationHMACKey';
delete from ossys_Parameter where name = 'OutSystems.HubEdition.MobileLogin_AuthenticationEncryptKey';

26 Apr 2018

Rafael Christófano

Hi Team!

I would like to know if I can follow this same procedure when I will do to change the installation to other machine. Eg. I have a on-premises machine and I would to transfer the installation to other machine. The database will continue the same.

03 Jun 2020

2 replies

Last reply 28 Dec 2020

Show thread

Hide thread

Ronny

Hi Rafael,

How did you manage to install to other machine?

I also have the same problem. In my case, my old production machine windows server 2012 in outsystems 10 and I want to migrate to the new machine windows server 2019 with outsystems 11.

If you are okay, can share the steps?

19 Nov 2020

Henrique Matos

Rafael (and Ronny),

I believe what you're looking for is as simple as adding another server to your environment. You can check how this is done in the platform instalation checklist (according to your platform version); add the new server as a new front-end and, afterwards, change roles with the old server.

Ronny, your task adds another level of complexity, as you also want to upgrade the platform from v10 to v11. Check this document; please consider that the upgrade must be executed in all your environments and it should start with the development environment (where all the breaking changes must be tackled).

Best regards,

Henrique

28 Dec 2020

Nitish Kumar

Hi All,

I am using OutSystems 11 of on-premises setup and initially, it was installed In the C drive only but now due to memory issues I have to move it to another drive.

Do I have to follow the same steps given by @AcacioPN?

As I see this post is very old now and I assume now there might be some easy steps to achieve this.

Regards

Nitish

20 Aug 2023

1 reply

15 Mar 2024

Show thread

Hide thread

Ivo Frazão

Hello, Nitish.

There is this documentation, that is much more up-to-date: https://success.outsystems.com/support/enterprise_customers/maintenance_and_operations/re_install_the_outsystems_platform_on_a_different_path/.

Best regards,

Ivo Frazão

15 Mar 2024

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.

See the full guidelines