Migrating Pro Cloud Server to a New Server

1

On the old server, open the the Pro Cloud Server Configuration Client. Select 'Extended Properties', then use the 'Export Config' option to export your configuration to a .pcscfg file. See the 'Extended Server Properties' topic for details.

2

Browse to your Pro Cloud Server installation folder (e.g. "C:\Program Files\Sparx Systems\Pro Cloud Server\").

3

If you have a Pro Cloud Server license make a copy of the license allocations file:

.\Service\Licenses\SSAllocations.config

4

Make copies of these configuration files:

.\Service\ssprocloud.config

.\Service\ssflsgroups.config

.\Service\sskeys.dat

.\Service\server.pem

.\SBPI\*.config

5

Make a copy/backup of the 'Models' folder (ie .\Service\Models\*). This contains any Firebird (.feap/.fdb) or SQLite (.qea) repositories you have created.

6

On the new server, install Pro Cloud Server as described in the 'Pro Cloud Server Installation' topic.

7

Copy the license allocation and configuration files from the previous installation (mentioned in steps 3 and 4) into the corresponding subfolders on the new server (e.g. "C:\Program Files\Sparx Systems\Pro Cloud Server\").

8

Copy the Firebird and SQLite repositories (feap/fdb/qea files) from step 5 to the 'Models' folder in the new installation.

9

Restart the 'Sparx Systems Professional Cloud' service.

10

Open the Pro Cloud Server configuration client.

11

Import your Pro Cloud Server configuration file, which was exported in step 1. See the 'Extended Server Properties' topic for details.

12

If you have a Pro Cloud Server License you will need to request and add a license for the new server.

See the 'Pro Cloud Server Licensing' topic for details. When requesting the license from the Sparx Systems Sales Team please mentioned that the license is for the migration to a new server.

13

Again, restart the 'Sparx Systems Professional Cloud' service.

14

Test access to each of your model connections in EA.

• If your Pro Cloud Server installation path has not changed then then you should be able to access the existing Firebird and SQLite models.

• If you have database managers which use a native database connection (recognizable by the 'ssdb:' prefix) then these should be accessible without modification.
• If you have database managers which used an ODBC connection (to MySQL, SQL Server, Oracle, etc), we recommend manually re-creating these using the Pro Cloud Server Native connection. See the 'Add Database Manager - Native' topic for details.

15

For any newly created database managers update their configuration as required. See the 'Configure Database Manager' topic for details.

You can then remove any of the old/unused database managers.

16

Check the Configuration Client's 'Integrations' tab. If you have defined any data providers of type 'Custom Integration', 'Custom Service' or 'Translator' then these will need to be updated. Select the data provider then click Edit. On the 'Edit Data Provider' screen, update the DLL Path so that it refers to the new installation path.

Check the bindings for each of your integrations. If Database Managers had been removed/added during the migration then you will need to re-enable the bindings.

After updating integrations you will also need restart the 'Sparx Systems Professional Cloud' service.

17

Uninstall Pro Cloud Server from the old server.

18

You have now fully migrated Pro Cloud Server to the new server.