How to transfer data between BPMonline 7.x environments

Transcription

1 How to transfer data between BPMonline 7.x environments This manual covers schemas and data migration using subversion integration. If extra information is required please read introductory manuals: How to start development on BPMonline platform with Subversion, How to migrate from BPMonline to BPMonline BPM'online workspace is a sandbox application or in other words separate environment, which enables system customization. Changes made in one of application workspaces do not affect other workspaces, until they are explicitly loaded. These architecture aspects help to isolate developers and users work when using the same data base or even use different databases if necessary and then synchronize their data. Changes made in workspaces are transferred using subversion (SVN), so changed schemas should be primarily committed to SVN, after which update from SVN on another environment should be performed. After that changes will be applied to a recipient workspace. Changes made in workspace are stored in four types of workspace items: Schemas are base workspace items that contain the structure of database tables, pages, business processes and their items, reports, images, etc. Data items contain records of sections and lookups and are included in packages. These could be base lookup values, system settings, demo data, etc. External assemblies are DLL files used for integration with third party applications. SQL scripts can be used for performing additional operations on the database before or after a package is installed. 1) To migrate schemas please use "Commit to repository" action on source workspace and when it is completed perform action Update from Repository on recipient workspace, it will load changes to current configuration.

2 Then execute actions Generate where it is needed, Compile modified items to regenerate source code and recompile new workspace. If different databases are used, object structure update may be required. Please check

3 Database update required attribute of entity schemas in your package and if you see that some schemas, which structure should be updated, please execute Update where it is needed action. 2) To migrate data user should bind table (object) content to appropriate package, to do it please go to Data tab and click Add button. You will see designer, which helps user to bind necessary data: At first specify object, which content you want to bind, and then select installation type. There are three installation types of data bound: Initial installation data bound will be installed only when current package is installed for the first time. So if this package is whenever updated, data will not be installed anymore. This option is useful for some default lookups and settings content, which is not going to change, but to be honest this option is rarely used. Installation data bound will update existing data, if records do not exist, they will be added from data binding schema. This is the most common installation type as it provides cross-functional approach. Update existing data bound will just update existing data. Then configure filter to install only necessary data. Let me show this mechanism using example: imagine we created new section, which is called Contacts on original environment and want to migrate it to another environment

4 a) Specify object: Section b) Choose installation type: Installation c) Add filter: Title is equal to Contacts Then click Show data button to make sure necessary data was bound and save binding.

5 Commit schema to repository and update destination environment, and then perform Install selected items or Install where it is needed actions. Some most common use cases: A. To add new section use bind the following objects content: Section SysModule localization table Section in workplace Section in workspace B. To add new detail: Details lookup C. To add new page Section card D. To bind section or detail list column order User profile E. Dashboards and charts Dashboard F. Lookups registration and their folders Lookup folder Lookup G. System settings System settings folder System setting System setting value H. Lookup or other objects content Just find object by its caption 3) In some cases objects content should be removed or updated manually. Let us imagine that we do not want to see Projects section any more. The easiest way to remove it from left side panel is deleting its registration using SQL scripts. To add one go to SQL scripts tab and click Add button in case you want to write script inside built-in designer or Add file button if you already have script file and just want to upload it to BPMonline. Please specify DBMS type as BPMonline supports both MS SQL Server and Oracle DB, so designer should check if your script meets T-SQL (Transact-SQL) or PL/SQL (Procedural Language/SQL) requirements. Also select Installation type for current script, I guess the most common case would be applying script after package is saved. Then click Validation button and if script is correct, save it and commit to repository.

6 After that, update recipient environment from repository and execute script using Install selected items or Install where it is needed actions depending on your intentions: install only selected scripts or install all scripts marked by attribute Needs to be installed in database.