Managing a Rational Programming Patterns local workspace

You are strongly advised against reusing a local workspace that was created with a previous version of the product. However, running a new migration from Pacbase is not necessary.

You are advised to start from an empty local workspace and to load the content of the repository workspace into it. You can reuse the repository workspace that was used before. The metadata will then be correctly reset for Rational® Programming Patterns and its required products.

Even if it is not advised, reusing a local workspace remains possible. If updating the local workspace is required in a new Rational Programming Patterns version, then a migration process for the existing local workspace will be provided as far as possible. This process might be simple, that is to say an individual migration upon the opening of an editor, or the migration of an entire workspace in a command-line mode. In any case, this process will be documented with the version.

To fully benefit from the evolutions of this new version, you are advised to reindex the content of the existing local workspace. If you are an administrator, you are also advised to reindex the content of the Rational Team Concert™ server.
  • To reindex the content of an existing local workspace, open the Pattern Driven Programming perspective and the Design Explorer view. Right-click each location and select Rebuild Local Workspace. Then, select Rebuild the mapping between the designs and the generated files.
  • To reindex the content of the Rational Team Concert server, open the Work Items perspective and the Team Artifacts view. Expand each project area and expand Enterprise Extensions. Right-click Source Code Data and select Reset Source Code Data.

When you open a local workspace that was created before Rational Programming Patterns 9.6, you must rebuild the mapping between the designs and the generated files. To do so, right-click each location and select Rebuild the mapping between the designs and the generated files. This rebuild can be requested independently of the local workspace rebuild. If you do not rebuild the mapping between the designs and the generated files, all the generation requests fail with an error that indicates that pattern names are not found for the super references.


Feedback