#Infosphere data architect update#
#Infosphere data architect software#

Follow the wizard pages to create library_D.dbm. Select the library_D.ldm and click context menu item Transform to Physical Data Model… to open Transform to Physical Data Model wizard. Run the new transformation configuration (.tc) to create library_D.ldm. Select the library.ldm and click main menu item Data > Transform > New Configuration to open New Transformation Configuration wizard, remember to choose Logical Data Model TO Dimensional-Logical Data Model. Create denormalized dimensional logical data model.For example, if the grain is one row per writer per book add Writer Fact fact table with attributes (say bookCost:FLOAT, bookPublishedYear:Date, and bookPages:INTEGER). Based on the BI/DW project requirement, manually add and edit facts and dimensions.Make sure to review the LDM aligning with project requirements. Select the library.ldm and click context menu item Discover Facts and Dimensions. Allow IDA to discover facts and dimensions.Select the library.ldm and click context menu item Use Dimensional Model. Correct the enumeration data type appropriately.A specific example is if the attribute lengths is (default) 32672 then change it to appropriate size.

#Infosphere data architect update#

Check the length of data type and avoid “ORA-00910: specified length too long for its datatype” during update database schema task.

(Please note, for several of these tasks there are IBM developerWorks articles and IDA product help with step-by-step details.) Below are high-level IDA tasks to build dimensional models. Dimensional modeling tasksĭepending on the dimensional modeling approach used in the BI/DW project one may diverge or use appropriate dimensional modeling features such as dimensional modeling notation and auto-generation of denormalized dimensional models. This library.ldm is chosen for discussion in this blog.

Open Library_LLD_Transformed.tc and click Run button.īy default the LLD ( library.ldm) created using Data Model Transformation wizard is much closer to the planned dimensional model work.

In the Source and Target page, select source library.xsd and target Data Design Project/folder.

Follow the wizard pages remember to select XML Schema to Logical Data Model.

Select the Data Design Project and click main menu item Data > Transform > New Configuration … to open New Transformation Configuration wizard.

(b) Import XSD using Data Model Transformation wizard

The Library_LLD_Imported.ldm is created.

Here is a sample snapshot of Select the Model page:

Follow Data Model Import wizard pages.

In Import wizard page, select Data Model Import Wizard.

In Data Project Explorer view, click context menu item Import… to open Import wizard.

(a) Import XSD using Data Model Import Wizard Please note rather than creating new XSD (with nicely ready for 3NF/facts/dimensions) some random library.xsd is used to focus on this blog purpose. This blog uses the sample XML Schema (XSD) library.xsd that is shipped with Eclipse EMF developer guide.

Using Transformation Configuration wizard with ‘XML Schema to Logical Data Model’ data model transformation.

Using Data Model Import Wizard with ‘W3C XML Schema 1.0 (XSD)’ as source model format.

There are a couple of ways to import XML Schema into InfoSphere Data Design Project: This blog shows the use of IDA to convert existing XML Schema (XSD) to Logical Data Model (LDM) and subsequent high-level tasks to create Dimensional Logical Data Model (DLDM) leading to Physical Data Model (PDM) and finally updating database schema. identify the facts) for designing a dimensional model. Modeling tools complement applying Kimball’s four steps (1. The modeling tools such as InfoSphere Data Architect (IDA) help to analyze existing and create new data models.

The business transformation initiatives with Business Intelligence/Data Warehouse (BI/DW) projects analyzing and baselining existing artifacts are critical because they contain working traits of the business.

#Infosphere data architect software#

Large enterprises (especially enterprise grown though acquisitions) are likely to have software engineering environments with variety of technologies including flavors of application modeling with XML Schema, Ecore, UML, Visio, etc.