Reuse Repository Data

If you want to reuse existing repository data, such as workflows, forms into a new repository, complete the following steps:

1. Create new Repository Data source

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

   2. Create a new Repository Data source in production environment from Central Configuration.

   3. Create a new Repository in production environment with the same Repository name as in 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.

2. Attach existing Repository Data source

   1. Take a backup of Repository Data Source database from Development machine and recover this data source database in Production machine. (Let us say that the restored database's name is 'BackedUpdatabase')

   2. Create a new Data source in Production machine and use the same database created in step c. (Example: Data source is created with name ProductionDatasource. Restored database named 'BackedUpdatabase' is used to create this data source.)

   3. Create a new repository – Choose attach data source option.

   4. Select Data source created in step c. This will list all the repositories in selected data source. Give name to the Repository and continue with creating 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 proceed with Repository creation.)

   5. You can retain the resource providers in the attached data source by checking the Attach Providers option or create your own resource provider. Ensure that it is the same as the resource provider of the attached repository.

Note: The product installed version and data source version should be same for attaching data source.

Example:

Attaching a data source that was created in 5.0.0.0 build should not be performed in the 6.0.0.0 build.

Note: Choose the version number appropriately based on the environment.

To attach such a data source:

3. If the data source was created in 5.0.0.0 build, then the entire 5.0.0.0 build should be first upgraded to 6.0.0.0 build.

4. The 5.0.0.0 build should be upgraded to 6.0.0.0 build by running the latest msi file.

5. The Farm, Data Sources , Repositories, and Lists of 5.0.0.0 build should be upgraded to 6.0.0.0 by running the AVEVAWorkTasksUpgradeManager.exe located in the BIN folder.

6. After upgrading all the components to 6.0.0.0 build, that data source can be used in the 6.0.0.0 build that is installed in any machine by using this feature.

7. This will Copy the repository details of Development environment to Production environment.

Repository Data Cleaning

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

truncate table SKWorkItem

truncate table SKHWSActivity

truncate table SKWorkItemTransaction

truncate table SWTaskList

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 SWFECount

truncate table SWRaw

truncate table SKScheduler

truncate table SKEventBindings

truncate table SKEEventAssociations

truncate table SKExecutionInstanceData

Note: You need to recreate all associations and BAM scheduling.

Queue Data:

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

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

• SKQueue

• SKQueueAccessRights

• SKQueueParticipants