Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
The tool is distributed as standalone jar which should be run from the command line:
Code Block |
---|
java -jar blueriq-studio-migration.jar > migration.log |
Info | ||
---|---|---|
| ||
Java 11 is required to run this tool |
Configuration
Configuration properties may be specified in an application.yml file in the same directory as the blueriq-studio-migration.jar. That file is used by default when running the tool.
Studio Connection
The tool uses the Management Service of Blueriq Studio so you should configure a Studio connection with authentication details:
Code Block | ||
---|---|---|
| ||
migration: studio: url: http://localhost:93/Studio/Server/Services/ManagementService auth-type: basic | ntlm | kerberos username: admin password: welcome domain: (only used with ntlm authentication) |
Info | ||
---|---|---|
| ||
At least Studio version 12.12.3/12.13 is required. Upon running the tool it will check the Studio version to verify it is compatible. |
Migration scope
You may specify for which repository/branch/project the migrations should be run. It is allowed to omit the list of projects, branches and even repositories in which case the tool iterates over all projects/branches/repositories. A complete example is provided:
Code Block | ||
---|---|---|
| ||
migration: repositories: - name: Repo branches: - name: Trunk projects: - Project1 - Project2 |
Migrating Formats to Presentation Styles
This migration creates presentation styles for all used formats on the AQ_CaseList, AQ_WorkList, AQ_InstanceLinker containers and replaces all usages of formats with usages of presentation styles instead.
Target Project
All presentation styles are created in a dedicated project which is intended to be distributed as library. The details of this project should be configured as follows:
Code Block | ||
---|---|---|
| ||
migration: r13: formats: target-project: repository: Library branch: Trunk project: Styles |
If you leave out the properties above, the migration for formats will be skipped.
The migration tool does not automatically ensure that each project has a library include of this target-project, so you may see validation errors for missing presentation styles. If this is the case, ensure that the target-project is configured as library include such that its presentation styles are available.
Format splitting behavior
By default, each format is considered as a single presentation style. If you have used a convention of using spaces, commas or other characters as a delimiter for multiple styles, the migration tool can be configured with such delimiters:
Code Block | ||
---|---|---|
| ||
migration: r13: formats: delimiters: - "," |
Using the above configuration, each format is first split by a comma to obtain the individual presentation styles that will be created.
Want to use it?
UI Button | ||||||||
---|---|---|---|---|---|---|---|---|
|
Release notes
1.1.2 -
Bug fix:
Identifier | Issue | Solution |
---|---|---|
CSD-3835 | In some cases the migration tool clears the Selection parameter in AQ_InstanceLinker containers. | The Blueriq management service module, which is used, had an outdated model of the studio Studio management service. This resulted in that the AQ_InstanceLinker Selection parameter would be cleared. The model is updated to the Selection parameter is not cleared anymore. |
1.1.1 -
- Initial public release of r12 → r13 Studio migration tool
Info | ||
---|---|---|
| ||
We advise to run this tool on the same server as Blueriq Studio to avoid network overhead, which may have a severe impact on the performance. For very large projects we also advise to run the tool for each repository separately and restart the Studio service in between runs, otherwise the Studio server may run out of memory causing the migration tool to fail. |
Table of Contents | ||
---|---|---|
|