Using Rational Data Architect to import and export XML

Create XML files from Rational Data Architect, and create data models from XML files

Davor Gornik (dgornik@us.ibm.com), Product Manager, IBM, Software Group

Davor started his career as a software developer and architect in the early days of CASE, 4GL, and UNIX. His experience with technologies expanded to OO, UML, IE, SOA, RDBMS, II, and other acronyms. (Which explains why his writings do not contain any unexplained, three-letter abbreviations.) He is now a product manager with IBM and works with Common AD Tooling and DB Administration group. Outside of work he is a world traveler with a long history of international relocations, and many stories to tell about different parts of the world -- from San Marino to China, and including most of the continents. Additional hobbies include photography, remodeling, volleyball, and other sports. Contact Davor at dgornik@us.ibm.com.

Summary: XML files are used throughout software development and information management to describe data structures. In this article, you learn how to turn XML files into data models, and vice versa, with the help of IBM® Rational® Data Architect.

Tag this!

Date: 29 Nov 2006
Level: Intermediate
Activity: 2692 views
Comments:

Introduction

Rational Data Architect provides tools that can dramatically reduce design and development time. This software, built on the open source Eclipse platform, helps data architects to model, discover, map, and analyze data across multiple information sources, automating information integration in complex environments.

With Rational Data Architect and FixPack 1, you can import XML Document Type Definition (DTD) and XML Schema Definition (XSD) documents as logical data models. It's not possible to import as a physical model because physical data models in Rational Data Architect require database specification, which is not part of the import.

Various XML formats are supported by import and export. The most important are:

Format	Description
XML DTD	A document that defines basic XML structure with containment relationships between them
XML XSD	A more precise specification of structure, data types, and rules for an XML document
Object Management Group (OMG) CWM	Common Warehouse Model (CWM) specification for a database schema in XML

The first two formats are basically an extract from an XML structure and are commonly used wherever XML documents are found. The CWM is a complete model description with more details, such as detailed constraints, complex relationships, super and subtypes, and many kinds of constraints. CWM is typically found as an import/export format from tools, and is only created manually in exceptional cases.

Rational Data Architect configuration

It is assumed that you have a working version of Rational Data Architect installed which includes FixPack 1. Several configuration changes are needed to enable XML import and export interfaces in Rational Data Architect, so let's get started.

Enabling XML DTD import

Assuming that Rational Data Architect is installed in C:\Program Files\IBM\Rational\RDA\V6.1, to enable XML DTD support you need to change the configuration parameters in the file:

C:\Program Files\IBM\Rational\RDA\V6.1\rda_prod\eclipse\plugins\com.ibm.datatools.metadata.wizards.miti.win32_1.0.0\MetaIntegration\conf\MIRModelBridges.xml

The parameter that needs to be changed is:

<Bridge name="W3cXmlDtd" enabled="true" windowsOnly="false">
  <DisplayName enabled="true">- XML DTD 1.0 (W3C)</DisplayName> 
</Bridge>

For XML DTD documents, only import is possible.

Enabling XSD import/export

Assuming that Rational Data Architect is installed in C:\Program Files\IBM\Rational\RDA\V6.1, to enable XSD support you need to change the configuration parameters in the file:

C:\Program Files\IBM\Rational\RDA\V6.1\rda_prod\eclipse\plugins\com.ibm.datatools.metadata.wizards.miti.win32_1.0.0\MetaIntegration\conf\MIRModelBridges.xml

The parameter that needs to be changed is:

<Bridge name="W3cXmlXsd" enabled="true" windowsOnly="false">
 <DisplayName enabled="true">- XML Schema 1.0 (W3C XSD)</DisplayName> 
 <DisplayName enabled="true">- XML Schema (Microsoft XDR)</DisplayName> 
</Bridge>

You will find this entry in the <import> and <export> part of the configuration file. Although W3C and Microsoft® specifications are similar, they are not identical. Please be sure to select the one you need.

Enabling OMG CMW import/export

Assuming that Rational Data Architect is installed in C:\Program Files\IBM\Rational\RDA\V6.1, to enable OMG CWM support you need to change the configuration parameters in the file:

C:\Program Files\IBM\Rational\RDA\V6.1\rda_prod\eclipse\plugins\com.ibm.datatools.metadata.wizards.miti.win32_1.0.0\MetaIntegration\conf\MIRModelBridges.xml

The parameter that needs to be changed is:

<Bridge name="OmgCwmXmi" enabled="true" windowsOnly="false">
 <DisplayName enabled="true">OMG CWM 1.0 and 1.1 XMI 1.1</DisplayName> 
 <DisplayName enabled="false">Adaptive Repository & Foundation (CWM)</DisplayName> 
 <DisplayName enabled=" false">BusinessObjects Data Integrator (CWM)</DisplayName> 
 <DisplayName enabled=" false">SAS ETL Studio (CWM)</DisplayName> 
 <DisplayName enabled=" false">Hyperion Application Builder (CWM)</DisplayName> 
 <DisplayName enabled=" false">IBM DB2 Warehouse Manager (CWM)</DisplayName> 
  <DisplayName enabled=" false">Oracle Warehouse Builder (CWM)</DisplayName> 
</Bridge>

You will find this entry in the <import> and <export> part of the configuration file. The names displayed are just alternative names. You can enable the displayed names according to the tool you are using.

Required import steps

To start the import, use the File > Import function of Rational Data Architect.

In the displayed list of import filters, select Data Model Import Wizard, as shown in Figure 1.

Figure 1. Import selection dialog

This step starts the wizard that lets you specify what you want to import, the format of the import, and the expected result.

Selecting the parameters

The panel shown in Figure 2 requires the selection or input of all parameters.

Figure 2. Selection of import parameters
The parameters dialog

Model format: The type of the input model. In this case the input file (model) is in XML DTD 1.0 format as defined by the W3C organization.
Model: The complete path to the source file (model). You can use Browse to search for the file.
Target project: Name of the project in the current workspace where you would like to see the results.
Model type: Type of the result, which could be logical model, physical model, or automatic recognition by the import. For this case, select Logical only.
File name: Name of the resulting model. In this case, a logical model ofxdtd.ldm will be created in the selected Target project.

Following the basic specification about the source for the import and desired target, you can specify detailed parameters about the import, as shown in Figure 3.

Figure 3. Specification of import options

Elements content name: Defines which element will be mapped to an attribute. In this case, all elements defined as #PCDATA will be transformed to an attribute.
Collapse Level: Opportunity to collapse several elements into one to reduce the number of entities.
Collapse Star: Filters the DTD elements with a link ("*") from the generation.
Class Type: Defines whether an entity will be created when collapsing input information.
Any: Specifies if the XML concept "Any" will result in an entity or not.
Strict Multiplicity: Allows users to define the interpretation of regular expressions in XML regarding order.
Generate IDs: Generates additional primary keys if needed.
HL7: Used only when importing HL7 DTD to check additional syntax.

In addition to the parameters, you can also influence the workflow:

Validity check: Defines the level of checks that are executed before the import (basic, detailed, none). It is recommended to execute at lease some validity checks.
Target database: Defines the type of the target database for physical models.

Evaluating results

You should always evaluate the status summary, as shown in Figure 4, after the execution of the import. It may contain important information.

Figure 4. Evaluate the summary

There are several types of messages:

<INFO>: Informational message about the configuration or finish of an activity.
<STATUS>: Information message about process of an activity, displayed after each phase of a longer activity.
<WARNING>: Informs you of either an encountered minor problem (for example, a missing link in the source), or about the generated model (for example, diagrams do not have layout information).
Warnings typically mean that you should either check the part of the model the warning refers to and validate the content, or that you have to do a manual step in the tool after the import is finalized.
<ERROR>: A message that has a serious effect for the resulting model. Either a concept was not understood, the source could not be validated, or the source could not be opened.
<FATAL>: The import tool failed and was not able to create any result.

Required export steps

To start the export, use the File > Export function of Rational Data Architect. In the displayed list of export filters, select Data Model Export Wizard.

Selecting the parameters

To select parameters, the procedure is identical to the import.

Evaluating results

To evaluate results, the procedure is identical to the import.

XML schema import example

This section provides an example for importing the XML schema. Start with the XML file in Listing 1.

Listing 1. Source XML schema

<?xml version="1.0" encoding="utf-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="com.ibm.test.employee"
targetNamespace="com.ibm.test.employee">
  <xs:complexType name="DEPARTMENT">
    <xs:attribute name="DEPT_NBR" use="required">
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:maxLength value="3" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="DEPT_NAME" use="required">
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:maxLength value="29" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="MANAGER_ID">
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:maxLength value="6" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="ADMR_DEPT_ID" use="required">
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:maxLength value="3" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="LOCATION_NAME">
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:maxLength value="16" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
  </xs:complexType>
  <xs:complexType name="EMPLOYEE">
    <xs:attribute name="EMP_NBR" use="required" type="xs:short">
    </xs:attribute>
    <xs:attribute name="FIRST_NAME" use="required">
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:maxLength value="12" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="MID_INIT" use="required">
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:maxLength value="1" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="LAST_NAME" use="required">
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:maxLength value="15" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="WORK_DEPT_NBR">
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:maxLength value="3" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="PHONE_NBR">
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:maxLength value="4" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="HIRED_DATE" type="xs:date">
    </xs:attribute>
    <xs:attribute name="JOB_CLASS">
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:maxLength value="8" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="ED_LEVEL" use="required" type="xs:short">
    </xs:attribute>
    <xs:attribute name="SEX_CLASS">
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:maxLength value="1" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="BIRTH_DATE" type="xs:date">
    </xs:attribute>
    <xs:attribute name="CURRENT_SALARY">
      <xs:simpleType>
        <xs:restriction base="xs:decimal">
          <xs:totalDigits value="9" />
          <xs:fractionDigits value="2" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="CURRENT_BONUS">
      <xs:simpleType>
        <xs:restriction base="xs:decimal">
          <xs:totalDigits value="9" />
          <xs:fractionDigits value="2" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="CURRENT_COMM">
      <xs:simpleType>
        <xs:restriction base="xs:decimal">
          <xs:totalDigits value="9" />
          <xs:fractionDigits value="2" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
  </xs:complexType>
  <xs:complexType name="EMPLOYEE_PROJECT">
    <xs:attribute name="EMP_NBR" use="required" type="xs:integer">
    </xs:attribute>
    <xs:attribute name="PROJ_NBR" use="required">
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:maxLength value="6" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="EMP_CHARGED_TIME">
      <xs:simpleType>
        <xs:restriction base="xs:decimal">
          <xs:totalDigits value="5" />
          <xs:fractionDigits value="2" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="EMP_START_DATE" type="xs:date">
    </xs:attribute>
    <xs:attribute name="EMP_END_DATE" type="xs:date">
    </xs:attribute>
  </xs:complexType>
  <xs:complexType name="PROJECT">
    <xs:attribute name="PROJ_NBR" use="required">
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:maxLength value="6" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="Project_Name">
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:maxLength value="5" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
  </xs:complexType>
  <xs:element name="DEPARTMENT" type="DEPARTMENT">
    <xs:annotation>
      <xs:documentation></xs:documentation>
    </xs:annotation>
    <xs:key name="DEPARTMENT_PK">
      <xs:selector xpath=".//DEPARTMENT" />
      <xs:field xpath="@DEPT_NBR" />
    </xs:key>
  </xs:element>
  <xs:element name="EMPLOYEE" type="EMPLOYEE">
    <xs:annotation>
      <xs:documentation></xs:documentation>
    </xs:annotation>
    <xs:key name="EMPLOYEE_PK">
      <xs:selector xpath=".//EMPLOYEE" />
      <xs:field xpath="@EMP_NBR" />
    </xs:key>
  </xs:element>
  <xs:element name="EMPLOYEE_PROJECT" type="EMPLOYEE_PROJECT">
    <xs:annotation>
      <xs:documentation></xs:documentation>
    </xs:annotation>
    <xs:key name="EMP_ACT_PK">
      <xs:selector xpath=".//EMPLOYEE_PROJECT" />
      <xs:field xpath="@EMP_NBR" />
      <xs:field xpath="@PROJ_NBR" />
    </xs:key>
  </xs:element>
  <xs:element name="PROJECT" type="PROJECT">
    <xs:annotation>
      <xs:documentation></xs:documentation>
    </xs:annotation>
    <xs:key name="PROJECT_PK">
      <xs:selector xpath=".//PROJECT" />
      <xs:field xpath="@PROJ_NBR" />
    </xs:key>
  </xs:element>
</xs:schema>

We start the import from the File menu. Select Data Model Import Wizard, as shown in Figure 5.

Figure 5. Data model import wizard

Select the XML Schema import, and define the import file as the Model, as shown in Figure 6. The Target project is the location for the logical data model that will be created with the name employee1.

Figure 6. Define import parameters

As shown in Figure 7, accept all of the default options for importing the model.

Figure 7. Specify import options

The status messages confirm successful import, as shown in Figure 8.

Figure 8. Evaluate resulting messages

The resulting logical data model is shown in Figure 9.

Figure 9. Resulting logical data model

Logical data model export example

The logical data model used in the following example contains four entities with several attributes, as shown in Figure 10. All attributes have assigner data types. There are also three different relationships between the entities.

Figure 10. Existing logical data model

The first step is to start the export from the file menu by selecting Data Model Export Wizard, as in Figure 11.

Figure 11. Start the Data Model Export Wizard

As shown in Figure 12, select the W3C XSD export as the Model format for the export.

Figure 12. Specify export parameters

The target namespace is com.ibm.com.test.employee, as shown in Figure 13. All other parameters are the default.

Figure 13. Define export options

The messages report the status of the import, as shown in Figure 14.

Figure 14. Evaluate export results
Data model export wizard

And Listing 2 shows the resulting XML schema.

Listing 2. Resulting XML schema

<?xml version="1.0" encoding="utf-8"?>
<!-- This file was generated by W3C XML/XSD -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="com.ibm.com.test.employee"
targetNamespace="com.ibm.com.test.employee">
  <xs:complexType name="DEPARTMENT">
    <xs:sequence>
      <xs:element ref="EMPLOYEE" minOccurs="0" maxOccurs="1">
      </xs:element>
    </xs:sequence>
    <xs:attribute name="DEPT_NBR" use="required">
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:maxLength value="3" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="DEPT_NAME" use="required">
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:maxLength value="29" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="MANAGER_ID">
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:maxLength value="6" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="ADMR_DEPT_ID" use="required">
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:maxLength value="3" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="LOCATION_NAME">
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:maxLength value="16" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
  </xs:complexType>
  <xs:complexType name="EMPLOYEE">
    <xs:sequence>
      <xs:element ref="EMPLOYEE_PROJECT" minOccurs="0" maxOccurs="1">
      </xs:element>
    </xs:sequence>
    <xs:attribute name="EMP_NBR" use="required" type="xs:short">
    </xs:attribute>
    <xs:attribute name="FIRST_NAME" use="required">
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:maxLength value="12" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="MID_INIT" use="required">
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:maxLength value="1" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="LAST_NAME" use="required">
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:maxLength value="15" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="WORK_DEPT_NBR">
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:maxLength value="3" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="PHONE_NBR">
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:maxLength value="4" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="HIRED_DATE" type="xs:date">
    </xs:attribute>
    <xs:attribute name="JOB_CLASS">
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:maxLength value="8" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="ED_LEVEL" use="required" type="xs:short">
    </xs:attribute>
    <xs:attribute name="SEX_CLASS">
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:maxLength value="1" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="BIRTH_DATE" type="xs:date">
    </xs:attribute>
    <xs:attribute name="CURRENT_SALARY">
      <xs:simpleType>
        <xs:restriction base="xs:decimal">
          <xs:totalDigits value="9" />
          <xs:fractionDigits value="2" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="CURRENT_BONUS">
      <xs:simpleType>
        <xs:restriction base="xs:decimal">
          <xs:totalDigits value="9" />
          <xs:fractionDigits value="2" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="CURRENT_COMM">
      <xs:simpleType>
        <xs:restriction base="xs:decimal">
          <xs:totalDigits value="9" />
          <xs:fractionDigits value="2" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
  </xs:complexType>
  <xs:complexType name="EMPLOYEE_PROJECT">
    <xs:attribute name="EMP_NBR" use="required" type="xs:integer">
    </xs:attribute>
    <xs:attribute name="PROJ_NBR" use="required">
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:maxLength value="6" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="EMP_CHARGED_TIME">
      <xs:simpleType>
        <xs:restriction base="xs:decimal">
          <xs:totalDigits value="5" />
          <xs:fractionDigits value="2" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="EMP_START_DATE" type="xs:date">
    </xs:attribute>
    <xs:attribute name="EMP_END_DATE" type="xs:date">
    </xs:attribute>
  </xs:complexType>
  <xs:complexType name="PROJECT">
    <xs:sequence>
      <xs:element ref="EMPLOYEE_PROJECT" minOccurs="0" maxOccurs="1">
      </xs:element>
    </xs:sequence>
    <xs:attribute name="PROJ_NBR" use="required">
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:maxLength value="6" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="Project_Name">
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:maxLength value="5" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
  </xs:complexType>
  <xs:element name="DEPARTMENT" type="DEPARTMENT">
    <xs:annotation>
      <xs:documentation></xs:documentation>
    </xs:annotation>
    <xs:key name="DEPARTMENT_PK">
      <xs:selector xpath=".//DEPARTMENT" />
      <xs:field xpath="@DEPT_NBR" />
    </xs:key>
  </xs:element>
  <xs:element name="EMPLOYEE" type="EMPLOYEE">
    <xs:annotation>
      <xs:documentation></xs:documentation>
    </xs:annotation>
    <xs:key name="EMPLOYEE_PK">
      <xs:selector xpath=".//EMPLOYEE" />
      <xs:field xpath="@EMP_NBR" />
    </xs:key>
  </xs:element>
  <xs:element name="EMPLOYEE_PROJECT" type="EMPLOYEE_PROJECT">
    <xs:annotation>
      <xs:documentation></xs:documentation>
    </xs:annotation>
    <xs:key name="EMP_ACT_PK">
      <xs:selector xpath=".//EMPLOYEE_PROJECT" />
      <xs:field xpath="@EMP_NBR" />
      <xs:field xpath="@PROJ_NBR" />
    </xs:key>
  </xs:element>
  <xs:element name="PROJECT" type="PROJECT">
    <xs:annotation>
      <xs:documentation></xs:documentation>
    </xs:annotation>
    <xs:key name="PROJECT_PK">
      <xs:selector xpath=".//PROJECT" />
      <xs:field xpath="@PROJ_NBR" />
    </xs:key>
  </xs:element>
</xs:schema>

Summary

XML is the current standard for serialization of information. Rational Data Architect enables you to serialize data models and to create data models from serialized information. This capability allows you to integrate Rational Data Architect in your extended workflow. In addition to the import and export capabilities covered in this article, Rational Data Architect provides more functionality around XML like mappings, shredding, and editing of XML schemas. You will find more information about those in the product information pages.

Resources

Learn

Get more information about IBM Rational Data Architect.
Visit the XML area on developerWorks, which gives you a variety of resources, including articles and tutorials, to help you learn more about XML.

Get products and technologies

Download IBM Rational Data Architect and try it yourself.

Discuss

Participate in the discussion forum.
Check out the Data Modeling blog and get involved with discussions.
Check out developerWorks blogs and get involved in the developerWorks community.

About the author

Comments

Trademarks | My developerWorks terms and conditions

Close [x]

Help: Update or add to My dW interests

What's this?

This little timesaver lets you update your My developerWorks profile with just one click! The general subject of this content (AIX and UNIX, Information Management, Lotus, Rational, Tivoli, WebSphere, Java, Linux, Open source, SOA and Web services, Web development, or XML) will be added to the interests section of your profile, if it's not there already. You only need to be logged in to My developerWorks.

And what's the point of adding your interests to your profile? That's how you find other users with the same interests as yours, and see what they're reading and contributing to the community. Your interests also help us recommend relevant developerWorks content to you.

View your My developerWorks profile

Return from help

Close [x]

Help: Remove from My dW interests

What's this?

Removing this interest does not alter your profile, but rather removes this piece of content from a list of all content for which you've indicated interest. In a future enhancement to My developerWorks, you'll be able to see a record of that content.

View your My developerWorks profile

Return from help

static.content.url=http://www.ibm.com/developerworks/js/artrating/

SITE_ID=1

Zone=Information Management, XML, Rational

ArticleID=177612

ArticleTitle=Using Rational Data Architect to import and export XML

publish-date=11292006

author1-email=dgornik@us.ibm.com

author1-email-cc=