Switch between remote and local deployment

You can move to a remote deployment from a local deployment, or the other way around, using the procedures that follow. The installer handles the configuration file settings for whatever SQL Server deployment you opted for during installation. However, after AVEVA Production Management has been installed and you decide to change your current deployment model, you need to manually make some changes to the configuration settings and perform additional tasks.

Switch from local to remote deployment

1. Update some of the items under the <appSettings> section of the application configuration file SE.SPO.AmplaService.exe.config. You can access this file from this AVEVA Production Management installation directory ...\Program Files\AVEVA\AVEVA Production Management.

   Updates to the file include changing the values of some key entries with the following:

   • <add key="SQLServerName" value="<RemoteSQLServerInstance>" />

   • <add key="DependentService" value="" />

   • <add key="StateDatabaseDisableBackground" value="false" />

   • <add key="StateDatabaseServerName" value="<RemoteSQLServerInstance>" />

2. Run this command at the command prompt:

   sc config AmplaServer depend=RabbitMQ/W3SVC

3. Take the SQL Server database backup from the local SQL Server instance and restore it in the remote SQL Server instance.

4. Restart AVEVA Production Management service.

Switch from remote to local deployment

5. Update some of the items under the <appSettings> section of the application configuration file SE.SPO.AmplaService.exe.config. You can access this file from this AVEVA Production Management installation directory ...\Program Files\AVEVA\AVEVA Production Management.

   Updates to the file include changing the values of some key entries with the following:

   • <add key="SQLServerName" value="<LocalSQLServerInstance>" />

   • <add key="DependentService" value="MSSQLServer" />

   • <add key="StateDatabaseDisableBackground" value="true" />

   • <add key="StateDatabaseServerName" value="<LocalSQLServerInstance>" />

6. Run this command at the command prompt:

   sc config AmplaServer depend=MSSQLServer/RabbitMQ/W3SVC

7. Take the SQL Server database backup from the remote SQL Server instance and restore it in the local SQL Server instance.

8. Restart AVEVA Production Management service.