Export/Import Example

The Export/Import example shows you how to clone an EWM^™ process area from one repository to another. The example provides a project which you can download and import into your Eclipse^® workspace. The project contains example Ant scripts that can be used to export process area definitions from one repository, in Ant script format, that can then be run to import those definitions into another process area in another repository. Exporting definitions from a process area can be used to set up a test system based on production system definitions or to develop definitions in test and migrate them to production once the definitions have been tested.

Getting Started

The first step in using the example is to import the project into your Eclipse workspace. To do that, download the ExportImportExample project using the link above. Once the download has completed goto "File - > Import..." in your Eclipse client.

Choose "General - > Existing Projects Into Workspace" and click Next.

Choose "Select archive file:", then "Browse..." to locate where you downloaded the zip file, then click Finish. Once the import process is finished you will find the ExportImportExample project in Project Explorer.

Contents

• Contents:

  doc folder	Documentation on Ant tasks and processes in PDF format.
  exports folder	Ant export scripts that extract information from the export system.
  imports folder	Used to store the import scripts generated by the export scripts.
  tooling folder	Miscellaneous Ant housekeeping scripts to delete definitions and generate reports.
  export.login.properties	Configurable properties file for login and process information for the export system.
  import.login.properties	Configurable properties file for login and process information for the import system.
  readme.txt	A text document similar to this.

• Export scripts:

  Components.xml	Exports all component definitions owned by the specified process area.
  Streams.xml	Exports all stream definitions owned by the specified process area.
  SystemDefinitions.xml	Exports all Enterprise Extensions system definitions for the specified project.
  FileMetadtaExport.xml	Exports all Enterprise Extensions system definition file metadata for the specified workspace/stream.
  FolderMetadtaExport.xml	Exports all Enterprise Extensions system definition folder metadata for the specified workspace/stream.
  BuildEngines.xml	Exports all build engine definitions for the specified process area.
  BuildDefinitions.xml	Exports all build definitions for the specified process area.

• Import scripts:

  Generated scripts

  Scripts generated in the export step.

• Import scripts:

  CreateWorkspace.xml	Creates a workspace to define in the import properties.
  DeleteAll.xml	Calls all of the other delete scripts.
  DeleteBuildDefinitions.xml	Deletes all build definitions in the specified process area.
  DeleteBuildEngines.xml	Deletes all build engines in the specified process area.
  DeleteFileMetadata.xml	Deletes all system definition file metadata for the specified workspace/stream.
  DeleteFolderMetadata.xml	Deletes all system definition folder metadata for the specified workspace/stream.
  DeleteStreams.xml	Deletes all stream definitions for the specified process area.
  DeleteSystemDefinitions.xml	Deletes all system definitions for the specified project.
  DeleteWorkspace.xml	Deletes the specified workspace.
  FileMetadataReport.xml	Generates a report listing all file metadata properties.
  FileMetadataReport2.xml	Generates a report listing all file metadata properties using remoteFileMetadataReport.
  FolderMetadataReport.xml	Generates a report listing all folder metadata properties.
  FolderMetadataReport2.xml	Generates a report listing all folder metadata properties using remoteFolderMetadataReport.
  ListLanguageUuid.xml	List the names and UUIDs of all languages defined to the specified project.
  ListResourceUuid.xml	List the names and UUIDs of all resources (data sets) defined to the specified project.
  ListTranslatorUuid.xml	List the names and UUIDs of all translators defined to the specified project.

Instructions

The following is a list of step-by-step instructions to follow to export your definitions from one repository and import them in another.

1. Fill in export.login.properties:
   
   
   
   
   • Repository URL
   • User ID
   • Password
   • Project area name which contains the following:
     • Components
     • Streams
     • Workspaces
     • System definitions
     • Build engines
     • Build definitions
   • Process area name:
     • Generally the same as the project area
   • Workspace name
     • Used for file and folder metadata export
     • Used for build definition property value resolution

   Note: See the following Ant task documentation for more information on these property values.

   • Create Build Definition
   • Create Build Engine
   • Create Components
   • Create Streams
   • Create Workspace
   • Delete Build Definition
   • Delete Build Engine
   • Delete Streams
   • Delete Workspace
   • Export Build Definition
   • Export Build Engine
   • Export Components
   • Export Streams
2. Load workspace for file/folder metadata exports:
   
   
   
   
   • This should be a workspace that flows to the target buildable stream.
   • This should be the workspace identified in the properties file.
   • This should be a workspace defined on the export system.
   • Load all components, projects, and files.
3. Run exports/Components.xml:
   
   
   
   
   • Right-click on file
   • Choose "Run As > Ant Build..."
   • On the JRE tab of the displayed dialog chose "Run in the same JRE as the workspace"
   • Click on Run
   
   
   

   Note: The first time each Ant script is run you must set the JRE to use. After the JRE has been set, the script can be run by simply choosing "Run As > Ant Build", skipping the JRE step.

4. Review imports/Components.xml

   Note: During each review search for "ERROR:" to see if any errors occurred during the export.

   
   
5. Fill in import.login.properties

   Note: The import.login.properties file has two extra properties, buildagentPassword and buildagentUserid, which need to be filled in. The buildEngineExport task does not export the userid and password for a Rational Build Agent build engine, instead it inserts these two properties into the appropriate build engine elements. Fill in these two properties with the appropriate values for the import system.

6. Run toolkit/CreateWorkspace.xml:
   • Right-click on file and set JRE
   • Click on Run
   • Load workspace
7. Import projects from export to import workspace
   • Choose existing project.
   • Choose copy into workspace.
8. Move source code to import system
   • Set import system stream as flow target.
   • Share each project on the import system.
   • Specifying the same component for import as used for the project on export system.
   • Deliver changes to import system
9. Check-in and Deliver file metadata change sets