Importing product trees

Use product import to migrate data from other tools into Rational® Engineering Lifecycle Manager as products.

Before you begin

Tip: If you are importing a very large product tree, you might encounter an error. Increasing the WebSphere® Application Server settings to the following resolves the error. The settings can be reset after the import is finished if necessary.
  • Web container thread pool max: 200

Procedure

  1. In the Administration menu, select Settings.

    Image shows the "Administrative" menu icon and the Settings option.

  2. In the left pane, click Import Products.
  3. Click the Import File button, which is on the upper right.
  4. Browse and select the file that you want to upload. Be sure to set the file format to the appropriate format for the file that you are importing.

    The Import History section shows the status of all imports that are performed by all users.

    The Import History shows the status of the import. After the import is completed, you can see how many products were created. You can also view the top-level products that were created by clicking the View Top-Level Products link next to the imported file.

Example

This example shows a tree that consists of a root that is called parent and has a single child that is called child. The identifiers that are used in this example are simple strings. Typically, longer unique and opaque values are used. (Import stores and transmits opaque values, but does not attempt to interpret them.)

The following Turtle file was imported through the Import Products screen.

@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . 
@prefix dcterms: <http://purl.org/dc/terms/> . 
@prefix pd_ext: <http://jazz.net/ns/pd/extensions#> . 
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> . 

<> 
               pd_ext:product _:resource1 ; 
               pd_ext:product _:resource2 . 

_:resource1 
               dcterms:identifier "abcd" ; 
               dcterms:title "parent" ; 
               pd_ext:conceptIdentifier "item1" ; 
               pd_ext:property [ 
                    dcterms:title "weight" ; 
                    rdf:value "1.6" 
               ]; 
               pd_ext:property [ 
                    dcterms:title "material" ; 
                    rdf:value "steel" 
               ]; 
               dcterms:references <https://machine1:9443/workItem/3456> ;
               pd_ext:childIdentifier "efgh" . 

_:resource2 
               dcterms:identifier "efgh" ; 
               dcterms:title "child" ;
               pd_ext:conceptIdentifier "item2" ;
               pd_ext:dimensionValuePair [ 
                    pd_ext:dimensionTitle "geo" ; 
                    pd_ext:shared "true" ^^xsd:boolean ; 
                    rdf:value "uk" 
               ]; 
               pd_ext:dimensionValuePair [ 
                    pd_ext:dimensionTitle "volts" ; 
                    rdf:value "230" 
               ]. 

After the import is completed, click the View Top-Level Products link to see the top-level products that were imported, as shown in the following image.

Sample tree that shows imported parent and child products.


Feedback