WBM-RDA Integration. User Guide

Transcription

1 WBM-RDA Integration User Guide Level: Intermediate Ray W. Ellis Daniel T. Chang Mei Y. Selvage User Guide WBM and RDA Integration Page 1 of 30

2 Contents 1. Introduction Installation Install RDA Plug-in Install Uninstall Integration Scenarios Top-Down Development Create Business Item in WBM Export WBM Business Items to XSD Convert XSD to LDM in RDA Create Physical Data Model from LDM in RDA Bottom-Up Development Create LDM model in RDA Convert LDM to XSD in RDA Import XML Schema into WBM Meet-in-the-Middle Development and Round-trip Considerations Merge in RDA Merge in WBM Authors Appendix A Intermediate XML Schema Business Item XSD Correlation Naming Inconsistencies Structural inconsistencies Logical Data Model XSD Correlation XML schema to logical data model Logical data model to XML schema...26 User Guide WBM and RDA Integration Page 2 of 30

3 1. Introduction Business process modeling and data modeling are intimately related to each other in a SOA design. Business process modeling captures key business information structures during process modeling, which may then become the basis for enterprise data models and ultimately relational database schemas. Moreover, existing data models often have a significant impact on the design of new business processes, as architects forced to accommodate existing legacy and third-party applications. IBM tools support both business process modeling and data modeling, and they recognize the importance of integrating these activities. Thus IBM has developed a plug-in for RDA to integrate WebSphere Business Modeler (WBM) with Rational Data Architect (RDA). Its installation and use is described in this User Guide. User Guide WBM and RDA Integration Page 3 of 30

4 2. Installation This RDA plug-in converts RDA Logical Data Models (LDMs) to and from XSD files. Since WBM Business Items and Business Service Objects can be exported as and imported from XSD files, the plug-in makes it possible to integrate RDA and WBM. To run both applications on the same computer requires the following hardware: Processor Pentium III 500 MHz or higher Available RAM 1 GM (2GB recommended) Available disk space 1.5 GB for installation and additional disk space for file storage Windows 2000 SP4 or later or Windows XP SP2 or later Rational Data Architect (RDA) v or later is supported. Installing RDA in the same location as Rational Software Architect (RSA) is supported. For more information about RDA see WebSphere Business Modeler (WBM) Advanced v is supported. If you have WBM v6.0.2 installed, you will need to upgrade to V6.0.2 is not suitable for the Bottom-Up scenario described in this guide, since it does not support the ability to import Business Items described by XML schemas. Note, too, that although the Basic version supports many of the features of the Advanced version, it cannot export business process definitions to XML schema and thus is unsuitable for several of the scenarios discussed below. For more information about WBM see or You should have both these installed before proceeding with the RDA Plug-in installation. 2.1 Install RDA Plug-in Download the RDA plug-in (RDA XSD-LDM Transformations Update.zip) and the read-me (RDA XSD-LDM Transformations Readme.zip). The RDA plug-in may be installed into an existing RDA installation in the same way as any other plug-ins. The best way to manage extra plug-ins, especially if you routinely install and remove new features, is to create a separate extension location for it. For this example we will install the RDA plug-in into a new extension location C:\eclipse-extensions\WBM-RDAIntegration. Create this directory outside RDA and proceed with the following installation procedure Install To install the RDA Plug-In: 1. Download the RDA Plug-In 2. Create a directory for the new extension location using the local operating system utilities. For this example we will use C:\eclipse-extensions\WBM-RDAIntegration. 3. Unzip the RDA plug-in distribution file to a temporary local directory. We will use C:\tmp for this example. User Guide WBM and RDA Integration Page 4 of 30

5 4. Start RDA 5. Open the Find and Install wizard using menu item Help > Software Updates > Find and Install 6. Select Search for new features to install and click Next 7. Create two new local sites, one for com.ibm.datatools.transform.ldm.xsd.update and one for com.ibm.datatools.transform.xsd.ldm.update. a. Click New Local Site b. Browse to the temporary directory containing the site.xml file, C:\tmp\com.ibm.datatools.transform.ldm.xsd.update in this example, select it, and click OK. c. Edit the local site name to com.ibm.datatools.transform.ldm.xsd.update for this example. Click OK. d. Once more click New Local Site e. Browse to C:\tmp\com.ibm.datatools.transform.xsd.ldm.update, select it, and click OK. f. Edit the local site name to com.ibm.datatools.transform.xsd.ldm.update for this example. Click OK. 8. Make sure both new update sites, com.ibm.datatools.transform.ldm.xsd.update and com.ibm.datatools.transform.xsd.ldm.update, are checked, and click Finish. User Guide WBM and RDA Integration Page 5 of 30

6 9. Select com.ibm.datatools.transform.ldm.xsd.update and com.ibm.datatools.transform.xsd.ldm.update from the displayed search results, and click Next. 10. Accept the terms in the license agreements and click Next. 11. Change the location you want the install the plug-ins. For this example we are installing them into a new extension location, C:\eclipse-extensions\WBM-RDAIntegration. a. Select both features, com.ibm.datatools.transform.ldm.xsd.feature and com.ibm.datatools.transform.xsd.ldm.feature, and click Change Location User Guide WBM and RDA Integration Page 6 of 30

7 b. When the list of existing extension locations is displayed, click Add Location to create a new extension location and browse to C:\eclipse-extensions\WBM-RDAIntegration. Click OK to create it. c. Ensure that the new C:\eclipse-extensions\WBM-RDAIntegration extension location is highlighted in the list of available installation locations, and click OK. 12. Click Finish to complete the installation. If a Feature Verification warning is raised because the feature is not signed, click Install All to ignore it and install anyway. 13. Restart RDA Uninstall Eclipse plug-ins should not be removed to disable their function; they should be disabled. The same Update Manager used to install the plug-ins can be used to disable them by disabling the individual features they belong to, or by disabling an entire extension location. You may disable the plug-ins installed above by: 1. Run Help > Software Updates > Manage Configuration 2. In the Product Configuration wizard that pops up, right-click on the C:\eclipse-extensions\WBM- RDAIntegration extension location User Guide WBM and RDA Integration Page 7 of 30

8 3. Click on Disable in the resulting pop-up menu 4. Confirm the action by clicking on OK in the resulting pop-up 5. Restart RDA by clicking on Yes in the pop-up after that. Since eventually the asset capabilities will be transitioned and delivered in the mainstream RDA release, however, at some point you may find it desirable to remove plug-ins entirely. To do this: 1. Stop RDA 2. Delete the extension location directory C:\eclipse-extensions\ WBM-RDAIntegration and all its contents 3. Restart RDA. If you have difficulty starting up Eclipse after removing the extension location directory you may find it necessary to start Eclipse once with the -clean command line option in order to remove cached data. User Guide WBM and RDA Integration Page 8 of 30

9 3. Integration Scenarios The WBM-RDA Integration asset supports are three general use cases supported: Top-down begin by defining business services/processes and business items, and proceed by transforming those models into logical data models and eventually into physical database models. Bottom-up begin with existing logical data models, perhaps inferred from physical database models, and use them in defining business items or business service objects in business processes. Meet-in-the-middle reconcile business items used in business services/processes with logical data models. Integration of WBM and RDA in these three scenarios is described further in the following sections. 3.1 Top-Down Development Top-down development denotes the case where a business analyst first models a business service or process and its associated business items in WBM, and then derives a logical data model from business items in RDA. This might be the normal course in the creation of a new service, for example, where there is no existing data model to consider Create Business Item in WBM This is a common development activity in WBM, done from Project Tree view, for example, by right-clicking on Business Items and selecting New > Business Item. Care must be taken if the names used in fields here are to translate correctly to XML Schema and then into LDM -- see Section Export WBM Business Items to XSD To export a Business Item created in the previous step to XML Schema format, follow these steps from the Project Tree view: 1. Right-click in the Project Tree view and click on Export in the context menu. 2. Choose the WebSphere Process Server format from the displayed list. 3. In the WebSphere Business Modeler Export Wizard, enter the name of the directory in which to place the resulting schema files in the Target directory field, C:\temp in this example. 4. Select the Export specific elements radio button, and highlight the Business Items you would like to export. 5. Click Finish to create the XML schema file. The XSD file will be created in the directory businessitems under the target directory entered in step 3, C:\temp\businessitems in this example. For more details about exporting business models to WebSphere Process Server in WBM, consult the WBM help under WebSphere Business Modeler Advanced > Exporting models > Exporting to WebSphere Process Server. User Guide WBM and RDA Integration Page 9 of 30

10 3.1.3 Convert XSD to LDM in RDA IBM Corporation 2007 To perform an XSD-to-LDM transformation you must first make an XSD-to-LDM transformation configuration, and then perform the transformation itself. Clicking on the Run XSD to LDM toolbar icon from the transformation configuration editor performs the transformation Create XSD-to-LDM Transformation Configuration An XSD-to-LDM transformation configuration is required to generate a high-level Logical Data Model from an XML schema. It may be re-used for many transformations; and its parameters, like the source and target, may be edited after it is created. You must be in the Data or the Modeling perspective. To create a new XSD-to-LDM transformation configuration: 1. Click File > New > Transformation Configuration from the main menu. 2. On the and Transformation page, enter the name you choose for the transformation and select the XSD-to-LDM type from the Data Model Transformations list. Then click Next. User Guide WBM and RDA Integration Page 10 of 30

11 (Note that all remaining information can be entered or changed later using the transformation configuration editor, but the transformation type cannot.) 3. On the Source and Target page, complete the following steps: a. Select an XML schema file as the source in the Selected Source field. You can transform from any XML schema in the project. b. Select a project in the Selected Target field in which to place the logical data model created by the transformation. c. Click Next. 4. On the Properties page you can determine, for example, whether you want to overwrite files without warning. Then click Next. 5. On the following Common page, you can specify whether you want to generate a log for the transformation. Then click Next. 6. Click Finish. A transformation configuration file with a.tc extension will be created and displayed in the Other Files folder of your target project. User Guide WBM and RDA Integration Page 11 of 30

12 Perform XSD-to-LDM Transformation To create an LDM from the XSD file exported from WBM, you execute an XSD-to-LDM transformation in RDA. This is done by opening a transformation configuration in the transformation configuration editor and clicking on the Run XSD to LDM toolbar icon. To perform an XSD-to-LDM transformation you must be in the Data or the Modeling perspective: 1. Right-click on a transformation configuration in the Project Explorer and open it with the Transformation Configuration Editor. 2. Make sure the transformation configuration parameters, such as the Source and Target fields, are correct. You may update them if necessary. 3. Click the Run XSD-to-LDM icon in the toolbar. (Import Note: The toolbar is immediately beneath the menu bar containing File, Edit,, Help menus at the top of the workbench. The Run XSD-to- LDM icon should be next to the rightmost icon in the toolbar. You can locate it by hovering over the icons and looking for the Run XSD-to-LDM help message.) A progress indicator will appear briefly, and the new logical data model will be created and displayed by the Data Project Explorer in the Data Models folder of the target project. The new model is named after the source schema file. User Guide WBM and RDA Integration Page 12 of 30

13 3.1.4 Create Physical Data Model from LDM in RDA Further uses of the LDM naturally include deriving a Physical Data Model (PDM) from the LDM, as described in the online help under Rational Data Architect > Overview of data modeling > Transforming data models > Generating physical data models from logical data models. 3.2 Bottom-Up Development Bottom-up development denotes the case where a logical data model exists in RDA that the business analyst wants to use when modelling a business process in WBM. This might be the normal course when creating a new service that uses a third party or legacy application, for example, or when there is a standards-based data model that influences the design Create LDM model in RDA This is a common development activity in RDA, done from Data Project Explorer view, for example, by rightclicking on a Project and right-clicking New > Logical Data Model. You can also create an LDM from a Physical Data Model (PDM), or by importing one from a variety of sources. For details see the RDA documentation Convert LDM to XSD in RDA To perform an LDM-to-XSD transformation you must first make an LDM-to-XSD Transformation Configuration, and then perform the transformation itself. The transformation is performed in the transformation configuration editor Create LDM-to-XSD Transformation Configuration An LDM-to-XSD transformation configuration is required to generate an XML schema from a high-level logical data model. You must be in the Data or the Modeling perspective. To create a new LDM-to-XSD transformation configuration: 1. Open the LDM you wish to transform by double-clicking on it in the Data Project Explorer. (If you don t perform this step you won t be able to set the source and target of the transformation using the wizard, though you will be able to edit these fields of the transformation configuration after it has been created, using the configuration editor.) 2. Click on File > New > Transformation Configuration from the main menu. 3. On the and Transformation page, enter the name of the transformation and select the LDM to XSD type from the Data Model Transformations list. Then click Next. User Guide WBM and RDA Integration Page 13 of 30

14 (Note that all remaining information can be entered or changed later using the transformation editor.) 4. On the Source and Target page, complete the following steps: a. Select a package in a logical data model (not the logical model itself) as the source in the Selected Source field. You can transform from any package in the model. b. Select a project in the Selected Target field in which to place the XML schema to be created by the transformation. User Guide WBM and RDA Integration Page 14 of 30

15 c. Click Next. 5. On the Properties page you can determine, for example, what the base target namespace is, whether you want to overwrite files without warning, and what the target namespace and target namespace prefix should be. When done, click Next. 6. On the following Common page, you can specify whether you want to generate a log for the transformation. When done, click Next. 7. Click Finish. A transformation configuration file with a.tc extension will be created and displayed in the Other Files folder of your target project Perform LDM-to-XSD Transformation To create an XSD file that can subsequently be imported into WBM from the LDM, you execute an LDM-to- XSD transformation in RDA. This is done by opening a transformation configuration in the transformation configuration editor and clicking on the Run LDM to XSD toolbar icon. To perform an LDM-to-XSD transformation you must be in the Data or the Modeling perspective: 1. Right-click on a transformation configuration in the Project Explorer and open it with the Transformation Configuration Editor. User Guide WBM and RDA Integration Page 15 of 30

16 2. Make sure the transformation configuration parameters, such as the Source and Target fields, are correct. You may update them if necessary. 3. Click the Run LDM to XSD icon in the toolbar. (Important Note: The toolbar is immediately beneath the menu bar containing File, Edit,, Help menus at the top of the workbench. The Run LDM to XSD icon should be next to the rightmost icon in the toolbar. You can locate it by hovering over the icons and looking for the Run LDM to XSD help message.) A progress indicator will appear briefly, and the XML schema will be created and displayed in the XML Schemas directory of the target project. The new object is named after the source package Import XML Schema into WBM The XML schema created by the LDM-to-XSD transformation can then be imported into WBM as a Business Item or a Business Service Object. Business Items can be exported as XML schema, but the exported schema may not be identical to the one used to create them. Business Service Objects created from schema can be used to recover the exact schema from which they were created, which may be important in some cases. However, Business Service Objects created in this way may not be edited Import XSD as Business Item To import an XSD file as a Business Item, follow this process in the Project Tree: User Guide WBM and RDA Integration Page 16 of 30

17 1. Right-click in the Project Tree view and select Import in the context menu. (Note that this is not the same as navigating File > Import.) 2. Select Type definition XML schema (.xsd) from the list of formats displayed, and click Next. a. A message may be displayed to remind you that importing a schema as a Business Item does not preserve the schema. Click yes to dismiss the message and proceed. 3. In the Source directory field browse to the directory containing the schema you want to import, then expand the directory in the field below and check the file(s) you want to import. Multiple files may be imported at once. 4. In the Target project field select the project you wish to import into. 5. Click Finish to complete the import. The Business Items will be created in the specified project. Note that if the project already contains the objects named in the schema, the import will complete with a warning and the new objects will be created with _1 ( _2, _3, etc.) appended to the name Import XSD as Business Service Object The procedure to import an XSD file as a Business Service Object is very similar to that used to import it as a Business Item: 1. Right-click in the Project Tree view and select Import in the context menu. 2. Select Business services and service objects (.wsdl,.xsd) from the list of formats displayed, and click Next. 3. In the Source directory field browse to the directory containing the schema you want to import, then expand the directory in the field below and check the file(s) you want to import. Multiple files may be imported at once. 4. In the Target project field select the project you wish to import into. 5. Click Finish to complete the import. Business Service Objects will be created in the specified project. They may be viewed by double-clicking on them, but they may not be modified. If they are exported as XSD files the original schema will be exported exactly. For more details about importing business services and business service objects in WBM, consult the WBM help under WebSphere Business Modeler Advanced > Importing models > Importing business services and business service objects. 3.3 Meet-in-the-Middle Development and Round-trip Considerations Meet-in-the-middle describes the common case in which a business process modelled in WBM must be reconciled with high-level logical data models in RDA, resulting in changes to either the business process or the logical data model. This can happen for a variety of reasons: The business process represents a new activity that must be integrated with existing applications The business process has been extended and the existing application support must be extended to support it The existing application support has changed and it is necessary to integrate the business process with the new application support There are two general ways meet-in-the-middle development is supported. If the business process changes, it may be exported to RDA as described under Top-Down development and the changes merged with the User Guide WBM and RDA Integration Page 17 of 30

18 existing logical data model in RDA. Similarly, if the logical model changes, it may be translated to XML schema and then imported into, as described under Bottom-Up development Merge in RDA One option for supporting meet-in-the-middle development is to merge the models in RDA. This would happen naturally if you changed the business process model and wanted to propagate the changes to the high-level logical data model. The business model can be translated into XML schema, as described under Top-Down development, and imported into RDA as a new logical data model. RDA then has a powerful graphical compare and merge editor to reconcile the old and new models, which makes this approach particularly attractive. Assuming you have created two versions of the logical data model, either directly in RDA or by importing from XSD, you can compare them in the data perspective in the following way: 1. Highlight the logical data models you would like to compare in the data project explorer 2. Right click, select Compare > Each Other (his will create a graphical comparison of the two LDMs) 3. Reconcile the models by inspecting the differences in the compare editor and editing them in the appropriate model editor. You can also perform basic cut and paste in operations in the data project explorer; and you can use the editing capability in compare editor for limited changes, especially finegrained features. 4. Save the reconciled model by right-clicking on the model in the Data Project Explorer and clicking on Save in the context menu that pops up. Be careful to distinguish between copying an object from one model to another and inserting a reference to an object in one model into another model. Note that you may need to re-compare the models after they have been edited and saved to update the comparison view Merge in WBM Another option to support meet-in-the-middle development is to merge the models in WBM. This might happen, for example, if the logical data model were changed and you wanted to modify the business process accordingly. The LDM may be translated to an XML schema, as described under Bottom-Up development, and imported into WBM. WBM can merge the imported model with existing model elements automatically, though it does so differently depending on whether the schema is imported as business items or business service objects. If the XML schema is imported as Type definitions for business items and there are existing types with the same name, new objects will be created with a _1 ( _2, _3, etc.) appended to the name. Thus, if you attempt to import a Customer type and there is already a business item type named Customer, a new type named Customer_1 will be created. You can replace the old Customer type by removing the old version and renaming the new one to Customer, but instances of the old Customer type will not pick up the new type and will appear corrupted. If you have instances of the old type and wish to preserve them you can compare and merge the two manually, but the editor is not well suited for this task and the process is painstaking. If instead you import the schema as a business service object and there is already a business service object with the same name, WBM will give you the option of overwriting the existing definitions. Since business service objects created from schema in this way cannot be modified, there is no way to compare and merge old and new definitions wholesale replacement is the only option. User Guide WBM and RDA Integration Page 18 of 30

19 4. Authors Ray Ellis is a senior software engineer in SOA Design Center at IBM Austin. He has been involved with numerous IBM Information Management, WebSphere and Rational product development. Daniel T. Chang is a senior software engineer at IBM Silicon Valley Lab. He has been with the RDA Core team since Mei Selvage is a SOA data architect with extensive experience in various information management areas and SOA. She is a frequent speaker of conferences and author for many articles. User Guide WBM and RDA Integration Page 19 of 30

20 5. Appendix A Intermediate XML Schema Since the WBM-RDA Integration Asset works through an intermediate XML schema file, to fully understand the process it is necessary to understand the intermediate schema and how it relates to WBM Business Items and RDA Logical Data Models. 5.1 Business Item XSD Correlation Naming Inconsistencies Element names WBM restrictions s of reusable elements (i.e. elements appearing on the Project Tree) are restricted to maximum length 50 (because of Windows file system path limitations). WBM reserves certain characters for special use, and therefore does not allow names to contain these characters: These are: ~#*=+[]?/\<>:;" XSD restrictions s must conform to NC restrictions. A sample of special characters that WBM allows in names that are not NC compliant are: `!@$%^&()- {}', Note: Note: The above list includes the space character. For full details on NC restrictions, please see the NC specification Mapping between WBM names and XSD names For WBM element names that contains characters that are not valid for XSD names, the resulting corresponding XSD name on export has the offending characters stripped out. For example, the following valid WBM name is transformed into an XSD name as follows: Funds `!@$%^&()_-{}', => Funds_ Since XSD name constraints are more restrictive than WBM, in general, WBM names reflect XSD names exactly on import. An exception to this general statement is the case where an XSD contains a name that is of length greater than 50 characters. In that case, the WBM Business Item name is truncated to 50 characters Target namespace WBM restrictions User Guide WBM and RDA Integration Page 20 of 30

21 WBM does not support a target namespace attribute on Business Items. However, the WBM concept that corresponds reasonably closely with the XSD target namespace is the catalog structure that contains the Business Items XSD restrictions The target namespace URI in XSD does not allow for the inclusion of DBCS characters Mapping between WBM fully-qualified names and XSD target namespace On export of WBM Business Items to XSD, the XSD target namespace is derived from the hierarchy of catalogs that contains the Business Item. The general form of the target namespace value is catalog name>/.../<parent catalog name> WBM catalog names are mapped to XSD compliant names as described in the name mapping section above. So, as an example, given a Business item with the following catalog hierarchy, the resulting target namespace is Due to the DBCS restrictions in URIs, WBM treats these specially when deriving the XSD target namespace. The following extract from the WBM product documentation describes this: Concerning the use of double-byte character set (DBCS) characters: When the BPEL, WSDL, and XSD files are created, the names of the WebSphere Business Modeler catalogs are used as part of the path of the targetspace URI. Because the targetspace URI does not permit DBCS characters, any DBCS characters that you have used in the names of elements (such as catalogs, processes, and business items) in WebSphere Business Modeler will be encoded. This will result in a targetspace URI containing encoded names that may not be traceable to the original names. The encoded names will also be used in the names of the BPEL, WSDL, and XSD files as well as in the generated directory folder that is created based on the targetspace. On import of an XSD to create WBM Business Items, the catalog structure containing the Business Item is derived from the XSD target namespace. Since the target namespace segments that are used for derivation of the catalog names is more restrictive than WBM, in general, the names of the catalogs in the hierarchy reflect the XSD URI segment names exactly. An exception to this general statement is the case where an XSD target namespace segment is of length greater than 50 characters. In that case, the corresponding catalog name is truncated to 50 characters. User Guide WBM and RDA Integration Page 21 of 30

22 5.1.2 Structural inconsistencies IBM Corporation 2007 Following is a table that describes the mapping between XML Schema elements and WBM Business Items: XML Schema Element Built-in simple type definition Derived simple type definition Complex type definition Schema model group "choice" Business Item Element Base type Business Item Business Item or Business Item Template Business Item Attribute and Business Item Template Schema model Business Item Attribute and group "sequence" or Business Item or none "all" Attribute group definition Model group definition Business Item Business Item Attribute declaration Business Item Attribute or Business Item Annotation Schema facet Comment Rule Min and max occurs Business Item Attribute min and max occurrence Comments The Business Item Attribute is typed as the Business Item Template. In some cases, the sequence is ignored. Otherwise, the Business Item Attribute is typed as the "sequence" Business Item. If member of a "choice", maps to a Business Item that extends the "choice" Business Item Template. Note: In cases where there is no direct one-to-one mapping, WBM attempts to map to something semantically close as described in the comments above. The following XML Schema elements are not mapped to anything in WBM: Schema notation declaration Identity constraint definitions for Element declarations Type definition wildcard User Guide WBM and RDA Integration Page 22 of 30

23 5.2 Logical Data Model XSD Correlation XML schema to logical data model Object mappings When you transform an XML schema into a logical data model, the XML schema objects are transformed into corresponding logical data model objects according to certain rules. Table 1 shows the correspondence between XML schema objects and logical data model objects. XML schema object or property Schema ( root ) SchemaLocation (XSD file name) Logical data model object or property generated by the transform Model Schema SchemaLocation (XSD file name) Targetspace Package Targetspace Simple Type Schema BaseType Length facet of BaseType TotalDigits facet of BaseType FractionDigits facet of BaseType Atomic Domain Owner BaseType Length Precision Scale Facets FractionDigits TotalDigits MaxLength MinLength Domain Constraint FractionDigit TotalDigits MaximumLength MinimumLength User Guide WBM and RDA Integration Page 23 of 30

24 Length MaxExclusive MinExclusive MaxInclusive MinInclusive Enumeration Pattern Length MaximumExclusive MinimumExclusive MaximumInclusive MininumInclusive Enumeration Pattern Complex Type / Element Schema BaseType Key of Element Entity (If both a Complex Type and an Element exist with the same name, only one Entity is generated with the former content and the latter constraints.) Owner Supertype of Generalization PrimaryKey Attribute / Content / Contained Element of SimpleType Schema Type Key field Attribute ( content if Content) Entity Data Type, Length/Precision, Scale Primary Key Contained Element(s) of ComplexType See Table 2 See Table 2 See Table 2 Owner Relationship Relationship Type ( Identifying, Non-Identifying, Many To Many ) Existence ( Optional, Mandatory ) Cardinality ( Zero or More, One or More, Zero or One, Exactly One, Range ) Owner Contained Element of ComplexType RelationshipEnd User Guide WBM and RDA Integration Page 24 of 30

25 ComplexType VerbPhrase / Inverse VerbPhrase MinOccurs / MaxOccurs Cardinality of Relationship inverseof AppInfo Pairing of RelationshipEnd Table 1. XML schema to logical data model object mappings The mapping from XML schema contained Element(s) to logical data model Relationship type / existence / cardinality is shown in Table 2. Contained Element(s) XML Schema MinOccurs / MaxOccurs of Parent Contained Element Unidirectional (0..1) / 1 / * / (1..*) Bidirectional (0..1) / 1 / * / (1..*) Bidirectional (0..1) / 1 / * / (1..*) MinOccurs / MaxOccurs of Child Contained Element Logical data model Relationship Existence Cardinality Type Identifying (Mandatory) 0..1 Non- Identifying 1 Non- Identifying Bidirectional * / (1..*) * Many To Many Bidirectional * / (1..*) 1..* Many To Many (0..1) / 1 / * / (1..*) Optional (0..1) / 1 / * / (1..*) Mandatory (0..1) / 1 / * / (1..*) Optional * / (1..*) Mandatory * / (1..*) Table 2. XML Schema Contained Element(s) to logical data model Relationship mappings Datatype mappings When you transform an XML schema into a logical data model, the XML schema datatypes are transformed into corresponding logical data model datatypes according to certain rules. Table 3 shows the correspondence between XML schema datatypes and logical data model datatypes. XML schema datatypes Logical data model datatypes generated by the transform string, normalizedstring, CDATA (if Length facet is set and <= 32672) string, normalizedstring, CDATA (if MaxLength facet is set and <= 32672) string, normalizedstring, CDATA (otherwise) base64binary, hexbinary (if Length facet is set and <= 32672) CHAR VARCHAR CLOB BINARY User Guide WBM and RDA Integration Page 25 of 30

26 XML schema datatypes and <= 32672) base64binary, hexbinary (if MaxLength facet is set and <= 32672) base64binary, hexbinary (otherwise) short, unsignedshort, byte, unsignedbyte integer, positiveinteger, nonpositiveinteger, negativeinteger, nonnegativeinteger, int, unsignedint long, unsignedlong float double decimal boolean date duration time datetime Logical data model datatypes generated by the transform VARBINARY BLOB SHORT INTEGER LONG FLOAT DOUBLE DECIMAL BOOLEAN DATE INTERVAL TIME TIMESTAMP Table 3. XML schema to logical data model datatype mappings Limitations Information on the file structure of source XSD files is not preserved Logical data model to XML schema Object mappings When you transform a logical data model into XML schemas, the logical data model objects are transformed into corresponding XML schema objects according to certain rules. Table 4 shows the correspondence between logical data model objects and XML schema objects. Logical data model object or property XML schema object or property generated by the transform Package Label Schema SchemaLocation (XSD file name) User Guide WBM and RDA Integration Page 26 of 30

27 space (Package Structure) Annotation Targetspace (unless set in the Properties page) Atomic Domain Label Abbreviation Owner Annotation BaseType Length Precision Scale Simple Type Schema BaseType Length facet of BaseType TotalDigits facet of BaseType Scale of BaseType Domain Constraint FractionDigit TotalDigits MaximumLength MinimumLength Length MaximumExclusive MinimumExclusive MaximumInclusive MininumInclusive Enumeration Pattern Facet FractionDigits TotalDigits MaxLength MinLength Length MaxExclusive MinExclusive MaxInclusive MinInclusive Enumeration Pattern Entity Label Abbreviation Complex Type and Element User Guide WBM and RDA Integration Page 27 of 30

28 Owner Supertype of Generalization Primary Key Persistent ( true, false ) Annotation Schema BaseType of Complex Type Key of Element Entity Constraint Generalization See Entity Attribute Label Data Type, Length/Precision, Scale Primary Key Required Surrogate Key Foreign Key Entity Annotation Contained Element with Simple Type Type Key field of containing Element (Surrogate key attribute are not transformed.) (Foreign key attributes are not transformed.) Owning Complex Type Relationship Label Abbreviation Owner Relationship Type ( Identifying, Non-Identifying, Many To Many ) Existence ( Optional, Mandatory ) Contained Element(s) with Complex Type See Table 5 See Table 5 User Guide WBM and RDA Integration Page 28 of 30

29 Cardinality ( Zero or More, One or More, Zero or One, Exactly One, Range ) Annotation See Table 5 RelationshipEnd VerbPhrase / Inverse VerbPhrase Key, Attributes Cardinality Pairing of RelationshipEnd Contained Element with Complex Type MinOccurs / MaxOccurs inverseof AppInfo Table 4. Logical data model to XML schema object mappings The mapping from logical data model Relationship type / existence / cardinality to XML schema contained Element(s) is shown in Table 5. Relationship Type Many To Many Many To Many Non- Identifying Non- Identifying Identifying Logical data model Existence Cardinality Contained Element(s) XML schema MinOccurs / MaxOccurs of Parent Contained Element Optional * / (1..*) Bidirectional * / (1..*) * Mandatory * / (1..*) Bidirectional * / (1..*) 1..* Optional (0..1) / 1 / * / (1..*) Mandatory (0..1) / 1 / * / (1..*) (Mandatory) (0..1) / 1 / * / (1..*) Bidirectional (0..1) / 1 / * / (1..*) Bidirectional (0..1) / 1 / * / (1..*) Unidirectional (0..1) / 1 / * / (1..*) MinOccurs / MaxOccurs of Child Contained Element Table 5. Logical data model Relationship to XML schema contained Element(s) Datatype mappings When you transform a logical data model into XML schemas, the logical data model datatypes are transformed into corresponding XML schema datatypes according to certain rules. Table 6 shows the correspondence between logical data model datatypes and XML schema datatypes. Logical data model datatypes XML schema datatypes generated by the transform User Guide WBM and RDA Integration Page 29 of 30

30 Logical data model datatypes CHAR CHAR(length) VARCHAR(length) CLOB(length) BINARY(length) VARBINARY(length) BLOB(length) SHORT INTEGER LONG FLOAT(precision) DECIMAL(precision,scale) DOUBLE BOOLEAN DATE TIME TIMESTAMP INTERVAL DATALINK(length) ROWID XML XML schema datatypes generated by the transform byte String (with Length facet) string (with MaxLength facet) string (with MaxLength facet) base64binary(with Length facet) base64binary (with MaxLength facet) base64binary (with MaxLength facet) short integer long float (with TotalDigits facet) decimal (with TotalDigits and FractionDigits facets) double boolean date time datetime duration Table 6. Logical data model to XML schema datatype mappings Limitations Information on the package structure of the source logical data model is not preserved. User Guide WBM and RDA Integration Page 30 of 30