When Rational® Change
is configured as an OSLC provider or consumer with other servers, Rational Change stores the
OSLC links in change request (CR) attributes. With a Sync server integration, Rational Change stores the
links to the artifacts of the integrated servers in CR attributes.
If any server in the OSLC integration or Sync server integration is
renamed, you must update the server URL references so that the links
stored in the CR attributes continue to work.
About this task
You must use the Rational Synergy
CLI command and you must be in the ccm_admin role.
The
CR attributes that contain the old URL can be of web type OSLC_LINK,
text attributes, string attributes, or any user customized attribute.
Procedure
- Turn off DCM and process all pending receives to ensure
that DCM is in a clean and stable state.
You do not
want DCM transfers to occur in any of the databases that are involved
in the reference update.
- Stop the Rational Change
server so that users cannot use the system while the server rename
is in progress.
- In the Rational Synergy
CLI, start a single user mode session to the database that contains
attributes that reference the old server.
- Set your role to ccm_admin.
You
must be in the ccm_admin role to run this update
operation.
- Run the ccm update_urls command.
Provide
the base part of the old and new server URLs. Also provide a list
of attribute names whose value might reference the old URL. The
update_urls command
updates only the renamed part of the URL in all of the specified CR
attributes. For more information, see:
- Stop the Synergy CLI session.
- Restart the Rational Change
server.
- Repeat steps 1 - 7 on all the databases of all the Rational Change servers in
the cluster that have attributes that reference the old server.
- Turn on DCM.
- If you are using a central server configuration, you must
resync the CRs if any of the updated attributes are ghost CR attributes.
Example
Assume that Rational Change
is integrated with Rational Team Concert™ and is using a Sync server. Also, the CR attribute url_mappings in Rational Change is configured
to contain the links to Rational
Team Concert work items.
For example, two CRs have the
following url_mappings:
CR 1: https://rtchost-test:1234/ccm/resource/itemName/WorkItem/68
CR
2: https://rtchost-test:1234/ccm/resource/itemName/WorkItem/69
Then
the update_urls command would be as follows:
ccm
update_urls -change -old_url "https://rtchost-test:1234/ccm" -new_url
"https://rtchost-prod:1234/ccm" url_mapping
The updated url_mappings attributes
of the CRs are as follows:
CR 1: https://rtchost-prod:1234/ccm/resource/itemName/WorkItem/68
CR
2: https://rtchost-prod:1234/ccm/resource/itemName/WorkItem/69
Example
script:
script_to_update_urls.sh
!/bin/sh
if test $# -ne 3; then
echo "Usage: script_to_update_urls old_url new_url database"
exit 1
fi
CCM_ADDR=`ccm start -d $3 -nogui -m –q –pw xxxxxx -single “Rename servers”`; export CCM_ADDR
ccm set role ccm_admin
ccm update_urls -change -old_url $1 -new_url $2 problem_description
problem_synopsis relatedChangeRequests
ccm stop