As with every software you should test a new WEBCON BPS version. The first step would be updating your development environment. It would even better to clone it before doing the update. Regardless of your approach, if you want to be sure, you will need to test it with production data. For this you will copy (restore) the production database to the development database. The restore and all the involved steps is the topic of this post.
Info: This is only a guideline / checklist, you will have to modify it to fit your environment. This is very important for the provided SQL script which is provided as is. Make sure to read through the whole post before you start.
Restore database script
I put together a script for restoring a backup as a new database in an existing/new environment. The script utilizes variables and has to be executed in SQL command mode. If you are using the SQL Management Studio, you can enable it in the Query actions.
- The content database has one attachment and one archive database.
- The attachment and archive database name follow the default naming convention. Their name begins with the content database name and either a
_Archsuffix is added.
- You have a dedicated SQL user.
- The SQL user and the application pool should get db_owner privileges.
Remark: These are just some general information and should make you aware of obvious differences to your environment. You should take a look at the script anyways and verify whether you want to use any of it.
The script does the following:
- Restoring the databases
The script restores the content database, one attachment database and one archive database as new databases on the SQL server. The backups, data and log file location and new database name are set by variables. There’s only one
targetDatabasevariable which is used for the process database. The archive and attachment database name will be created using the default suffixes
- Updating the references in the tables
There are few tables which contain references to the old/source databases.
- Adding the new content db
The script adds a row for the new content database in the config database. I have no idea, whether there’s a better/supported way of doing so. Maybe adding the database via
Tools and application managementand overwriting these during the restore would be one option.
- SQL and application pool account are added
The SQL user and application pool account will receive db_owner privileges to all three databases.
The result and errors of the script are saved to a text file.
Modify V_WFElements in archive db
Info: This is only a necessary if the name of the content database was changed.
The archive database contains a V_WFELements view, which references information from the content database. Therefore, you need to update the view using the new content database name.
Remark: I have no idea, whether this view is used, but upgrading to BPS 2023 will fail otherwise. BPS 2023 will add the calculated columns to the view and if the references database doesn’t exist, it will throw an error.
The easiest way is to use the
CREATE OR ALTER To action from the context menu, update the database name and execute the script.
WEBCON BPS Tools
Change database type
Remark: While there’s a difference between the environment and database type you won’t be able to access the environment at all.
I haven’t found a better official documentation than this chapter. 11. Reset the WEBCON BPS license
My personal checklist is:
- Stop the workflow service
- Start the resource toolkit
It is located in the WEBCON BPS installation folder at
- Display the change database type
- Provide the connection details in the configuration window.
- Switch to
Change database type.
- Change database (1) and save (2)
- Restart the workflow service
You may loose the license information and need to download the licenses again.
Upgrade the database
In case you restored a database on a server with a newer WEBCON BPS version, you need to upgrade the database version. Execute the setup.exe, choose the “Update” and click through. The upgrade will check what needs to be done and it will only upgrade the new database.
Associate to workflow service
The restore script will add an entry to the
ContentDatabases table of the configuration database. That’s not enough though. You still need to associate the new database to the workflow service.
Tools for application managementfrom setup.exe.
Farm services configuration.
- Click on add.
- Select the new database from the drop down.
Grant admin permissions
Old version without admin access
In case you are accessing the Designer Studio with a user, which is not available in the new environment, you have to grant new system administrator privileges. For this you can use the
WEBCON BPS System administrators.exe tool.
- Provide the connection details
- Connect to the server
- Select the database
- Modify the existing administrators using the actions at the right.
I sort the folder by
File type. This way I will have the .exe files at the top.
Newer version with admin access option
WEBCON BPS 2023 added the
Admin access, which is enabled by default when installing environment. You can activate this for existing environments using the administrators tool.
With the admin access you will be able to access the Designer Studio and change the system administrators.
Restart WEBCON Workflow Service and application pool
If you haven’t done so, you should restart the workflow service and the application pool hosting the WEBCON BPS web site.
Run user synchronization
If the new environment uses a different source for user synchronization or you have utilized local accounts, you should trigger a full user synchronization.
I have no idea whether and how it would be possible to transport and connect the search database. Depending on the database size you should at least trigger the reindexation of the BPS Portal navigation.
Same application multiple databases
Copying a database will allow you to have the same application multiple times in the same environment. If you tried this via the export/import mechanism you may have received an error, that this is not possible. The error would be something like
the process GUID is already used in another database..
This behavior is controlled by the global parameter
ImportValidateAppProcPresUniqueness in the config database. If it is set to 0 you will be able to import the same application into multiple databases.
The only technical problem I’m aware of is, that embedding BPS Portal elements is limited to unique application ids. The generated URL doesn’t contain a database id, so it won’t work.