Move from Development Environment to Production Environment

The following options are available when you to move from development environment to production environment:

• Option 1: To move the Farm database and Repository database

• Option 2: To recover only product database

Option 1: To move the Farm database and Repository database

Development Environment:

1. Stop all AVEVA Work Tasks Services.

2. Create backup copies of the following files from the development environment

   • Any custom dlls if added.

   • [AVEVA Work Tasks Installed Path]\AVEVA\Work Tasks\Locales folder for UI Localization

   • [AVEVA Work Tasks Installed Path]\AVEVA\Work Tasks\Logs folder that has all the log files

   • [AVEVA Work Tasks Installed Path]\AVEVA\Work Tasks\Web\BPMUITemplates folder

   • [AVEVA Work Tasks Installed Path]\AVEVA\Work Tasks\Workflow Elements folder

   • Farm Database

   • Repository Database

Production Environment:

3. Restore the backed up Farm database of development environment to production environment.

4. Install AVEVA Work Tasks in production environment.

5. Start the Farm Configuration Wizard on the production computer, and choose Farm Recovery.

6. Select Server or Client to be recovered.

7. Provide the database settings which will connect to restored the Farm database in production environment.

8. Install all the AVEVA Work Tasks Services, Central Configuration, and Enterprise Console.

9. In the Farm Configuration Wizard, go to the Enterprise Console Settings page, and update the URL of all the existing Enterprise Console to the URLs of the production environment.

10. Similarly, update the URLs in the Central Configuration with the production environment URLs.

11. In the Central Configuration, edit all the DataSources, and update the Server instance name, database name, connection settings.

Repository Data Source recovery:

Repository DataSource information is stored in the Farm database. If the database server is changed, you can edit the Server instance name, database name, and connection settings of Repository DataSource from the Central Configuration web site, and update the changes.

Recovery of AVEVA Work Tasks files:

During the installation of the product, AVEVA Work Tasks web sites will be created again. So here you need to consider the customized files are replaced correctly.

After the installation, replace all the existing AVEVA Work Tasks files with the original files. So that any customization done for XML file (for example, Actions.xml), images, html templates are replaced as before and if any custom actions or properties dlls added are replaced correctly. BPMUITemplates folder must be replaced under [AVEVA Work Tasks Installed Path]\AVEVA\Work Tasks\Web path.

Option 2: To recover only product database (With fresh Farm creation or recovered Farm, and if the Repository Data source does not exist in recovered Farm):

12. Creating new Repository DataSource:

    1. Export the workflow definition from development machine using Import or Export option in the Process Designer.

    2. Create a new Repository DataSource in production environment from the Central Configuration.

    3. Create a new Repository in production environment with the same Repository name as in the development environment.

    4. Import the exported (exported in step a.) workflow definition in production environment using Import or Export option in the Process Designer.

    5. Queues have to be re-configured if present in development environment. Queue will not get exported automatically.

13. Attaching existing Repository DataSource:

    1. Create a backup copy of the Repository DataSource database from the development computer.

    2. Recover this DataSource database in production computer.

    3. Create a new DataSource in production computer and use the same database created in step a. (For example, DataSource is created with name ProductionDatasource. Restored database named 'BackedUpdatabase' is used to create this data source. )

    4. Create a new repository. Choose Attach DataSource option.

    5. Select DataSource created in step b. This lists all the repositories in selected data source. Create the repository.(Example: Check Attach Data Source option. Select ProductionDatasource. This will list all repositories of ProductionDatasource. Now select the repository which needs to be copied and go ahead with Repository creation. )

    6. This will copy the repository details of the development environment to the production environment.

Repository Data Cleaning

14. If you do not want to keep Workflow runtime data, then run following script on the production database:

    truncate table SKWorkItem

    truncate table SKHWSActivity

    truncate table SKWorkItemTransaction

    Delete SWTaskList where cast(ClassName as nvarchar(max)) <> 'Skelta.WorkFlow.Scheduler.WorkFlowScheduler'

    truncate table SKMultipleTimeoutWarning

    truncate table SWActionEventLog

    truncate table SWActionEventLong

    truncate table SKWorkItemCounter

    truncate table SKChannelWorkItem

    truncate table SKWorkItemData

    truncate table SKWorkItemFields

    truncate table SWExecutionDetails

    truncate table SWExecute

    truncate table SWVariables

    truncate table SKWorkflowEvents

    truncate table SKChildWorkflows

    truncate table SWCustomTimerDetails

    truncate table SWClientTokenData

15. Queue Data:

    Queues will work fine only in case where Queue Participants are same in development and production environment. If different users need to be used in Queue on the production environment, user needs to create new Queue.

    To remove particular Queue data, see the following Queue tables:

    • SKQueue

    • SKQueueAccessRights

    • SKQueueParticipants