Prev Next

Migrating from 32 bit to 64 bit

With the release Pro Cloud Server v5 users now have the choice between 32 and 64 bit architecture, prior versions (v4.2 and earlier) were all 32 bit. Additional steps are required for existing 32 bit environments wanting to migrate to 64 bit, see steps below:

Migrating from Pro Cloud Server 32 bit to 64 bit

Step

Description

See also

1

Before uninstalling Pro Cloud Server 32 bit, 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.

Extended Server Properties

2

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

3

If you have a Pro Cloud Server license make a copy of the license certificate/s and allocations file:

.\Licenses\*.crt

.\Licenses\SSAllocations.config

4

Make copies of the following 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. This contains any Firebird (.feap/.fdb) or SQLite (.qea) models you have created.

6

Uninstall Pro Cloud Server 32 bit.

7

Install Pro Cloud Server 64 bit as described in the 'Pro Cloud Server Installation' topic.

Pro Cloud Server Installation

8

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

9

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

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.

Extended Server Properties

12

Restart the 'Sparx Systems Professional Cloud' service.

13

If you have database managers which use a native database connection (recognizable by the 'ssdb:' prefix) then these do not require any modification.

14

For any Firebird models which were added via the ODBC connection option (recognizable by the 'firebird:' prefix), you will need to create a new model connection. Add a new database manager as described in the 'Add Database Manager - Native' topic. In the filename field enter the name (including extension) which matches the file in the 'Models' folder (mentioned in step 7).

Configure Database Manager

15

For other ODBC model connections (to MySQL, SQL Server, Oracle, etc) you have two options:

  • (Recommended) Create a new native connection to your existing database as described in the 'Add Database Manager - Native' topic. Note, you should ensure the 'alias' of the new connection matches that of the old one, however it is not possible to define two connections with the same alias. Before creating the new connection, modify the alias of the old one (e.g. append '_odbc').
  • Or, install the 64 bit version of the ODBC database driver and define a 64 bit ODBC DSN connection to the database. If the name of this DSN connection matches the old 32 bit ODBC DNS then the Pro Cloud Server can make use of the existing database manager (it is not necessary to add a new one).
Add Database Manager - Native

16

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.

Configure Database Manager

17

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.

Add/Edit Data Provider

18

You have now fully migrated to Pro Cloud Server 64 bit.