r4 - 2020-01-01 - 13:28:14 - ArunKSriramaiahYou are here: TWiki >  Deployment Web > DeploymentMigratingAndEvolving > MovingAComponentToANewServer

Moving an Engineering Workflow Management (EWM) SCM component to a new EWM SCM server todo.png

Authors: ArunSriramaiah PaulEllis
Build basis: Engineering Workflow Management 6.0.6.1

This article relates to Engineering Workflow Management (ELM) Source Code Management (SCM) components, which was formerly known as Rational Team Concert. Renaming the IBM Continuous Engineering Portfolio explains more about the product renaming durint the ELM 6.0.6.1/7.0 timeframe.

Newly introduced in the ELM 6.0.6.1 release, there are now 2 repotool commands to allow you to refactor your components across your different server repositories.

Introduction

This document refers to new capabilities that become available in the 6.0.6.1 release of EWM. The document introduces the new capabilities, what they do, how they can be used and why this is important.

Component Import Export

The repotools-ccm command for the CCM server now supports Exporting a component and the contained SCM information into an export file. Importing a component and the contained SCM information from an export file.

These new capabilities can be used to migrate a component from one server to another with history references without the need to use distributed SCM.

The scmExportComponent command exports the contents of source-control management (SCM) components to a .tar file. The scmImportComponent command imports the contents of an exported .tar file.

The RTC SCM CLI functions described here must be executed by a user with sufficient administrative privileges.

This section will outline the process of migrating an ELM SCM Component to a new Server. It provides step-by-step instructions.

Supported Use Cases   The new capabilities support several use cases that are important to customers. The use cases are: Seeding a new server with SCM content with history. Migrating SCM Data to another server for several different reasons like for example Migrate SCM content to a new server to be able to remove it from the original server and reduce the SCM footprint in the database of the first server. Be able to separate the SCM data to a different server e.g. because the ownership of the source code changed. This usually makes it necessary to remove the source code from the original server, move it to a new server and continue developing there

Important considerations

The initial replication can be very long running Currently steps are executed using DB2 enterprise database.

Part 1 - Export the Component

The scmExportComponent command exports the contents of a database, scoped to a set of SCM components, to a .tar file.

The exported .tar file only contains data that is part of the specified SCM components and is not a full database export. You can import the .tar file onto a different server. Use the scmExportComponent command to export the contents of source-control management (SCM) components to a .tar file.
Before you import components, ensure that they do not exist on the server already. All components in the archive are imported together. The following data is included in an exported component archive:

  • The component,
  • Contained baselines
  • History
  • Change sets.
  • All files and folders modified by change sets in the component, and all content that is associated with those files.
  • Version identifiers, item permissions, and custom attributes for any files and folders that are part of the export.
  • Contributor information for all users who create or modify any exported item.

The following data is not included in an exported component archive:

  • The current state of the component in the workspace or stream, and the history of operations performed in a stream or workspace. Before you export, create baselines to record the current state of any notable streams or workspaces.
  • Snapshots are not included, but the individual baselines on components being exported are included.
  • Baseline hierarchies are not included, but the individual baselines on components being exported that make up the hierarchy are included.

UseCase

https://www.ibm.com/support/knowledgecenter/SSYMRC_6.0.6.1/com.ibm.jazz.install.doc/topics/r_scmExportComponent.html The export command requires a component UUID. To determine the UUID of the component use the RTC web browser, or use the RTC SCM Command Line command......

Example  Open a command prompt and enter this command: cd C:\Program Files\IBM\JazzTeamServer\server\ repotools-ccm.bat -scmExportComponent components=_iIfDAEKSEd2A5aJWEO8dbA,_pN8RYPi-Ed2J16MAqQXG5g toFile=exportComponents.tar

 Open a command line and enter this command: cd /opt/IBM/JazzTeamServer/server/ ./repotools-ccm.sh -scmExportComponent components=_iIfDAEKSEd2A5aJWEO8dbA,_pN8RYPi-Ed2J16MAqQXG5g toFile=./exportComponents.tar

The command can also be used also use for multiple components. Example:

Part 2 - Import the Component

Use the scmImportComponent command to import the contents of an exported source-control management (SCM) component .tar file into a database
All data in the previously exported SCM component .tar file is imported together. Components being imported must not previously exist on the server.

  • Imported components are initially owned by the default Admin user and are in an archived state. An administrator must unarchive the component and set the owner to an appropriate process area or contributor before users can access it.
  • Imported files and folders with permissions set to a context that does not exist on the server are reassigned to the Admin user. When you import components onto a new server, the permission context (that is, project area) might not exist.
  • Custom attributes are controlled by the project area that owns the component.
  • Custom attributes of the component that is imported to a new server are retained, but users cannot set new ones unless they are configured appropriately in the project area that owns the component.

Command Example:  Open a command prompt and enter this command: cd C:\Program Files\IBM\JazzTeamServer\server\ repotools-ccm.bat -scmImportComponent fromFile=exportComponents.tar

 Open a command line and enter this command: cd /opt/IBM/JazzTeamServer/server/ ./repotools-ccm.sh -scmImportComponent fromFile=./exportComponents.tar

Enable_JAS_SSO.jpg

Cleaning up and reclaiming space

In Database Growth - Strategies for minimizing the growth of repository databases, RosaNaranjo describes how to perform the final step.

In Rational Team Concert/Engineering Workflow Management (EWM), there are several items that can contribute greatly to database growth if not kept in check. These items are build results, work item attachments, and binary content in SCM as versioned content. There are several articles and presentations that have been written on this topic.

Related topics: Database Growth, Deleting data in Engineering Workflow Management

External links:

Additional contributors: PaulEllis, RosaNaranjo

Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r4 < r3 < r2 < r1 | More topic actions
 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.
Ideas, requests, problems regarding the Deployment wiki? Create a new task in the RTC Deployment wiki project