Verifying Change and Configuration Management

After a successful server rename operation, and after you complete the steps in the server rename verification wizard, you perform a final verification of the Change and Configuration Management application and its associated components.

The verification wizard displays the renamed URLs in your deployment and allows you to flag any incorrect URLs. These incorrect URLs must be corrected before you complete the rename. The wizard will instruct you to stop the server, create a new mapping file with the supplied template, and rerun the importUrlMappings command to perform another rename.

After the rename completes, you should rerun the verification wizard and then perform the following steps to complete the verification process.

Engineering Workflow Management Eclipse and Microsoft Visual Studio clients

  1. Update the repository connection:
    1. In the Team Artifacts view, expand Repository Connections and select the particular repository connection.
    2. Choose Properties from its pop-up menu.
    3. In the Jazz Repository Connection page, change the URI to the new Engineering Workflow Management server URI, for example, https://newserver:9443/ccm.

      You should see a dialog warning that the server state has changed and that the client must be restarted.

    4. Accept the prompt to exit.
    5. After it has exited, restart the client.
    6. If auto-login is not selected for the connection, select Log In from the pop-up menu for the connection.
    7. Verify that the connection logs in successfully to the new server.
  2. Verify links for feeds:
    1. In the Team Artifacts view, expand Feeds and select a feed.
    2. Choose Properties from its pop-up menu.
    3. Check the Link field.
  3. If you are using distributed SCM:
    1. Start your Eclipse client. In the workspace editor, open the workspace(s) or stream(s) that have one or more flow targets pointing to the server that was renamed. Verify that the workspace editor shows the flow target correctly. Otherwise, it will say unreachable.
    2. Additionally, verify that you can accept and deliver changes from this workspace to and from the target on the renamed server. (Perform this task after read-only mode is disabled.)
    3. Verify that you can open work items and change requests that are linked to change sets.
    4. Verify that the workspaces and streams involved in distributed SCM can accept and deliver as expected after the server rename and mapping were applied. (Perform this task after read-only mode is disabled.)
    5. If the server to be renamed is CCM friends with other servers that are involved in SCM distributed workflows, make sure the mapping is applied to each friend server. This is to ensure that change requests linked to change sets and flow table entries in workspaces and streams have the correct mappings applied.

Engineering Workflow Management web client

Verify that all of the following links have been renamed:

  • User and work item links in the summary and description
  • Project level links to other work items under the links section
  • IBM® Engineering Lifecycle Management (ELM) level links to other artifacts in the repository
  • Links in release and iteration plans

In addition, verify that queries return correct data after the rename.

SCM Command Line Interface (CLI) client

  • Verify that the repository registry entry for the renamed repository is updated with the new server URL. This URL will be mapped only when the user runs lscm login against the new server URL. Repository registry entries can be listed using lscm ls cred.
  • After running 'lscm login' against the new server URL, verify that pre-server rename aliases can still be used.
  • Verify that the old server URL does not surface in the CLI output.
  • Verify that the loaded workspaces from the renamed server can accept and deliver changes.
  • Verify that the workspaces and streams involved in distributed SCM can accept and deliver as expected after the server rename and mapping were applied.

Engineering Workflow Management ISPF client

Update the repository connection as follows:

  1. In the Engineering Workflow Management Primary Option Menu, enter a 1 on the Option line and press the Enter key.
  2. Enter an E next to the repository connection you want to edit and press the Enter key.
  3. Change the Repository URI to the new Engineering Workflow Management server URI and press the Enter key for the specified changes to take effect.
  4. Restart the ISPF Client.
  5. Open a workspace that flows with the renamed server and verify that you can accept and deliver change sets.

Jazz™ Team Build

  • Verify external links in build results.
  • Verify linked downloads and logs in build results, that is, those published as links to an external system, not uploaded to Engineering Workflow Management.
  • Check the Build Forge®, Build Agent, or the Hudson build engines, and ensure that the external servers they refer to are correct for the intended post-rename usage. If renaming from a production to a staging environment, you should deactivate or delete these engines to ensure that the staging environment does not run builds on production build servers.
  • Check build properties on build engines and build definitions for any URL properties, such as hostname and port). These are not mapped automatically and might need to be updated manually. Similarly, any URLs in build scripts might need to be updated.

Planning

  • Verify that the Planned Items work items point to new server URL.
  • Verify existing links (Reference columns such as Children, Implements Requirements, Tested by Testcase, and so on) in the Planned Items tab.
  • Create new links to RM, QM, and CCM from the Planned Items tab. (Perform this task after read-only mode is disabled.)
  • Verify all existing links under the Planning Links tab.
  • Add new Tracks/Contributes Plan links to the plan. (Perform this task after read-only mode is disabled.)

Work items

  • Verify that all links embedded in work item summary, description, comments and custom string attributes point to the new server URL.
  • Verify that work item links, such as ELM links, related artifacts, and mentions links point to the new server URL.
  • Verify that you can add and remove new links to renamed ELM servers and that the rich hover works. (Perform this task after read-only mode is disabled.)
  • Verify that work item link labels that match the URL name are also updated to the new server URL.

Enterprise Extensions

  • Verify that all Enterprise Extensions System Definitions are still visible in the Team Artifacts view of the Engineering Workflow Management Eclipse client and that they can be opened.
  • Open an existing dependency build result. Verify that the Build Report is still accessible and uses the new server URL.
  • Perform a dependency build after the rename. Verify that the build can be completed successfully and that all system definitions used by the build are resolved.
  • Verify that all existing Source Code Data Queries are still visible in the Team Artifacts Navigator and that they can be successfully executed

video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki