asg-rochade reconciliation toolkit release notes · asg-rochade reconciliation toolkit release...

ASG-Rochade® Reconciliation Toolkit Release NotesVersion 1.51September 6, 2007 RRT1100-151

This publication contains installation instructions for ASG-Rochade Reconciliation Toolkit (herein called Reconciliation Toolkit), information about getting started using Reconciliation Toolkit, and product modifications made since Version 1.50.000.

ISP Updates and Service PacksASG encourages you to visit http://www.asg.com/support/support.asp and sign onto the Intelligent Support Portal (ISP) to verify whether any product or documentation revisions, new maintenance, or service packs apply to this release of the product or its accompanying documentation.

Product OverviewReconciliation Toolkit is a prerequisite for ASG-Rochade Data Warehouse Application (herein called DW Application). It provides tools that allow you to transform and transport metadata in a consistent form in ASG-Rochade (herein called Rochade) from a source subject area to the central subject area of the DW Application. The metadata are organized and stored in compliance with the Data Warehouse Reconciliation Model, DWRRIM10.

Reconciliation Toolkit is implemented as a Java application using the Scriptable Rochade Application Platform (herein called SRAP) as the programming interface. You can think of it as a framework that realizes the required transformations on the basis of rules and JavaScript procedures that are stored in special control data within Rochade. In addition to the fixed rules defined in the framework, extensive options are available for the implementation of complex mappings by means of JavaScript via SRAP and ASG-Rochade Java API (herein called Java API). For a detailed description of the control data and their structure, see the ASG-Rochade Reconciliation Toolkit Technical Guide.

Copyright © 2007 ASG GmbH & Co. KG, a wholly owned subsidiary of Allen Systems Group, Inc. All rights reserved. All names and products contained herein are the trademarks or registered trademarks of their respective holders.

1

http://www.asg.com/support/support.asp

ASG-Rochade Reconciliation Toolkit Release Notes

You invoke Reconciliation Toolkit through a command file, for which you can find examples in the \Samples\rrt\cmd subdirectory of your Rochade installation directory after you have installed Reconciliation Toolkit.

Note:ASG may extend and modify the control data and command files included in the Reconciliation Toolkit package. Therefore, if you adapt these files for your own purposes, be sure to make copies of the files before adapting them.

Enhancements and Changes

Version 1.51.000These modifications and enhancements have been made to Reconciliation Toolkit in Version 1.51.000:

Information Model ChangesThese changes have been made to the information model DWRRIM10:

• Transformation-related changes reflect the fact that a transformation can refer to other transformations as source and target, and a transformation map can refer to other transformation maps as source and target.

• Item type DWR_TFM_TRANSFORMATION

The new target item type DWR_TFM_TRANSFORMATION has been added to the link attributes DWR_TFM_SOURCE and DWR_TFM_TARGET.

• Item type DWR_TFM_TRANSFORMATION_MAP

The new target item type DWR_TFM_TRANSFORMATION_MAP has been added to the link attributes DWR_TFM_FROM and DWR_TFM_TO.

• Activity-related changes reflect the fact that an activity can have two types of relationships:

• Namespace relationships, which describe activities that are valid only within the current activity.

• Links, which describe activities that the current activity can run.

2


These attributes have been added to the item type DWR_TFM_ACTIVITY:

• The link attribute DWR_TFM_RUNS, which enables links to items of type DWR_TFM_ACTIVITY.

• The namespace attribute DWR_TFM_HAS_TFM_ACTIVITY, which enables namespace relationships to items of type DWR_TFM_ACTIVITY.

• Column-related changes: The text attribute DWR_RDB_NULLS-ALLOWED has been added to the item type DWR_RDB_COLUMN.

New and Enhanced Reconciliation Toolkit Mappings• These Reconciliation Toolkit mappings are new:

• Support for RDBMS systems TeraData, Netezza, and UDB for UDB-RIM.

• Support Extract, Transform, and Load (ETL) tools BTEQ and Netezza.

• Support for the physical database model RDM-RIM.

• These Reconciliation Toolkit mappings have been enhanced:

• The Reconciliation Toolkit mappings for the RDBMS systems now support the Nulls allowed attribute.

• Reconciliation Toolkit mappings for Informatica and DataStage now support the DWRRIM10 changes.

New options in the command file enable either a summarized or detailed mapping:

— In the case of summarized mapping, a transformation task will have just one transformation contained that is a summary of all transformations defined in the ETL tool for that task. Consequently, the contained DWR_TFM_TRANSFORMATION_MAP instances reflect the summary of the maps on the field level across all transformations in one task.

— In the case of detailed mapping, each transformation defined in the ETL tool will be mapped into an individual DWR_TFM_TRANSFORMATION item.

• All mappings have been improved to be consistent with all available RDBMS mappings.

3


Version 1.50.004These improvements and bug fixes were made to Reconciliation Toolkit in Version 1.50.004:

• The Reconcilation Toolkit mapping was improved by adding these functions:

— Synonyms in the transformation of data created by ASG-Rochade SCANORAC.

— Transformation of data created by ASG-Rochade Scanner for BusinessObjects more efficiently.

— ASG-Rochade Scanner for UDB 1.10 or later. Mappings referencing the UDB mapping have to include the item type mapping schema DWR UDB/SERVER.ID additionally.

• With the rrt.jar file, Version 1.50.004 nested isType and isAttribute statements are no longer ignored.

Version 1.50.002These improvements were made to Reconciliation Toolkit in Version 1.50.002:

• The Reconcilation Toolkit mapping was improved to support the transformation of data created by ASG-Rochade Scanner for DataStage more comprehensively.

• The ASG-Rochade AutoPilot (herein called AutoPilot) user exit procedure was improved that loads the mapping descriptions to an XML editor. It previously failed when blanks were part of the path name for the temporary file directory.

Version 1.50.001These improvements and bug fixes were made to Reconciliation Toolkit in Version 1.50.001:

• Reconcilation Toolkit mapping was improved to support the transformation of data created by ASG-Rochade Scanner for Informatica more comprehensively.

• Missing control data was provided that was required for migrating DW Application data originating from releases earlier than 1.50.000.

• The rrt.jar file Version 1.50.001 was provided with these bug fixes:

— Problems in case a period was passed as parameter to a script was solved.

— Mapping statements in <OnEmpty> elements are no longer ignored.

4


Hardware RequirementsThese are the minimum system requirements for Reconciliation Toolkit:

• 64 MB RAM (ASG recommends 2GB or more)

• 5 MB hard disk space

• 200 MHz Intel Pentium processor or equivalent (ASG recommends 2 GHz or more)

Software Requirements These are the minimum software requirements for Reconciliation Toolkit:• AutoPilot 3.70.004 or later• Java API 2.00.007, or later with SRAP• JDK1.4 / Java 2• Rochade 7.00 or later

To check if Java is installed and in which version

Execute this command in a Windows command shell:

java -version

The result should be something like this example:

java version "1.4.2"Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b28)Java HotSpot(TM) Client VM (build 1.4.2-b28, mixed mode)

If this method does not work, complete these steps:

1 Use the search user interface to look for a file named java.exe:

• Under Windows 2000, select Start Search For Files and Folders.

• Under Windows XP, select Start Search.

2 Execute the command java -version for the paths found in step 1.

5


Installation InformationNote:If you have a DW Application subject area that was created with a release earlier than Version 1.50, ASG strongly recommends that you make a backup copy of your Rochade databases before proceeding with any installation effort.

The installation of Reconciliation Toolkit follows the general installation procedure for Rochade applications, which is described in the readme_en.pdf file and consists of two parts:

1 ADM installation

The ADM installation imports the DWRRIM10 information model, including its submodels, which play a central role for the DW Application.

Further, in the course of the ADM installation, you must complete a dialog in which you specify the control area for the storage of control data for Reconciliation Toolkit. The control area is based on the information model DWRCTL10, and you have these options:

• In the case of a first-time installation, the control area is created at this point and, by default, is named RRT-CONTROL ADMIN.

• In the case of an update installation, the existing control area is offered for reuse, but you have the option to specify a different control area.

Subsequently, the control data supplied with the Reconciliation Toolkit package are automatically imported into the specified control area.

2 Application installation

The Application installation deposits the Java archive rrt.jar, which is relevant for the execution of Reconciliation Toolkit, in the \bin subdirectory of the Rochade directory. Further, it stores command files (*.cmd) to execute Reconciliation Toolkit under Windows in the \Samples\rrt\cmd subdirectory and generates a file RRT-dataspace.xml in that directory to specify the communication parameters for the Rochade environment (e.g., server name, host name, and port number).

Items containing descriptions of relevant models and a description of the transfer parameters for the JavaScripts called by Reconciliation Toolkit in the manner of a user exit are stored in the \TechDoc\rrt subdirectory.

The XML schema RRT-MappingSchema.xsd, which is used for validation of Reconciliation Toolkit control data, is stored in the \XMLSchema subdirectory of the Rochade directory.

6


Getting StartedReconciliation Toolkit provides functionality to transform and transport metadata in Rochade from a source subject area to the DW Application subject area.

This summary lists the metadata sources by relevant areas of the data warehouse process along with the corresponding submodels of DWRRIM10. Also listed are the information models on which the source subject areas are based and the corresponding metadata sources along with the interfaces available to populate the source subject areas with the metadata from those sources.

• Online Analytical Processing (OLAP) and Information Reporting— Submodel of DWRRIM10: DWRRIM10_ANALYSIS— Source subject area based on ASG-Rochade CGN-RIM

— Metadata source: Cognos

— Interface: ASG-Rochade Scanner for COGNOS

— Source subject area based on ASG-Rochade BO10-RIM

— Metadata source: BusinessObjects

— Interface: ASG-Rochade Scanner for BusinessObjects

• Extract, Transform, and Load (ETL)— Submodel of DWRRIM10: DWRRIM10_TRANSFORMATION— Source subject area based on ASG-Rochade INFORMATICA RIM

— Metadata source: Informatica— Interface: ASG-Rochade Scanner for Informatica

— Source subject area based on Rochade DSTAGE RIM— Metadata source: DataStage

— Interface: ASG-Rochade Scanner for IBM WebSphere DataStage

— Source subject area based on ASG-Rochade BTEQ RIM

— Metadata source: Teradata BTEQ

— Interface: ASG-Rochade Scanner for BTEQ (FDI)

— Source subject area based on ASG-Rochade NETEZZA RIM

— Metadata source: Netezza SQL

— Interface: ASG-Rochade Scanner for Netezza (FDI)

7


• Database Systems— Submodel of DWRRIM10: DWRRIM10_RDBMS— Source subject area based on Rochade I-RIM

— Metadata source: DB2— Interface: DB2BUS for ASG-Rochade

— Source subject area based on ASG-Rochade UDB RIM

— Metadata source: UDB

— Interface: ASG-Rochade Scanner for UDB— Source subject area based on ASG-Rochade ORACLE RIM

— Metadata source: Oracle— Interface: ASG-Rochade SCANORAC

— Source subject area based on ASG-Rochade SQLSERVER RIM— Metadata source: MS SQL Server— Interface: ASG-Rochade SCANSQLSRVR

— Source subject area based on ASG-Rochade SYBASE RIM

— Metadata source: Sybase

— Interface: ASG-Rochade Scanner for Sybase

— Source subject area based on ASG-Rochade TERADATA RIM

— Metadata source: Teradata

— Interface: ASG-Rochade Scanner for Teradata

— Source subject area based on ASG-Rochade NETEZZA RIM

— Metadata source: Netezza

— Interface: ASG-Rochade Scanner for Netezza (FDI)

• Logical Data Models

— Submodel of DWRRIM10: DWRRIM10_ER_MODEL

— Source subject area based on ASG-Rochade CDM-RIM

— Metadata source: ER models

— Interfaces: ARTSBUS for ASG-Rochade, ASG-Rochade BUS for Casewise Corporate Modeler, CASE4BUS for ASG-Rochade, COOLGENBUS for ASG-Rochade, ORACDBUS for ASG-Rochade, ASG-Rochade Bus for Rational Data Architect, SABUS for ASG-Rochade, and PWRDESBUS for ASG-Rochade

8


• Physical Database Models

— Submodel of DWRRIM10: DWRRIM10_RDBMS

— Source subject area based on ASG-Rochade ERWBUS RIM

— Metadata source: ERwin RDBMS models

— Interface: ERWINBUS for ASG-Rochade

— Source subject area based on ASG-Rochade RDM RIM

— Metadata sources: ERwin and Rational Data Architect models

— Interfaces: ERWINBUS for ASG-Rochade and ASG-Rochade Bus for Rational Data Architect

For an overview of the supplied mappings, see the file: Rochade\TechDoc\rrt\RRT-Type-mapping.xls, where Rochade is the target directory of your Rochade installation.

Setting Up the DW Application Subject AreaReconciliation Toolkit works with these subject areas:

• The source subject area, which holds the original metadata that are to be integrated into the DW Application.

• The DW Application subject area, which holds the metadata for the DW Application. Its name, including its version name, is left to you to decide; for this description, DWR INTEGRATION is assumed.

If the DW Application subject area does not yet exist, your first preparatory step before applying Reconciliation Toolkit must be to create it, based on the Data Warehouse Reconciliation Model DWRRIM10.

The DW Application subject area must support the extended Rochade naming concept, so you must create it as a subject area with tree-like structure. For details, see the ASG-Rochade AutoPilot System Administrator’s Guide.

9


Note:ASG recommends that you make sure that the namespace attributes are assigned to the system table of the DW Application subject area.

To achieve this in AutoPilot versions earlier than 3.70.008, you must enable the option New functionality is required before you generate the DWRRIM10 (e.g., System Model Administration Information Models or System Model Administration Model Generation Settings).

To achieve this in AutoPilot 3.70.008 or later or in ASG-Metability (herein called Metability) 2.10.001 or later you must use the Update Release function within Subject Area Administration for assigning namespace attributes to the system table of a subject area.

In both variations, the DW Application subject area needs to have the internal &RELEASE attribute set to the value 3.7 to support system table-controlled namespace attributes. For details, see ASG-Rochade AutoPilot System Administrator’s Guide, ASG-Metability System Administrator's Guide, and ASG-Rochade AutoPilot Release Notes.

Once all the required subject areas are in place, you can apply Reconciliation Toolkit. It functions as a two-step process:

1 The data of the source subject area are consolidated into the virtual intermediate subject area in a form that complies with the Data Warehouse Reconciliation Model DWRRIM10.

2 The data consolidated in the virtual intermediate subject area are integrated into the DW Application subject area DWR INTEGRATION.

10


Configuring the Control Data for Reconciliation ToolkitThe control data included in the Reconciliation Toolkit package are deposited in the control area specified during the ADM installation. By default, RRT-CONTROL ADMIN is the name of that control area and its version name (see step 1 on page 6). It also is used in this description.

Understand the control data included in the package as templates. Extensions and modifications in the source metadata will usually require adjustments in these data.

Note:Later versions of Reconciliation Toolkit will extend the scope of the supported categories and complete various details of existing transformations. For this reason, ASG advises that you not modify the ASG-supplied control data templates with extensions of your own, but instead, produce your own copies and modify those as needed.

Reconciliation Toolkit requires consistency of the control data as an indispensable prerequisite for successful transformations. Therefore, be sure to review the detailed description of the control data and their structure in the ASG-Rochade Reconciliation Toolkit Technical Guide.

To ensure the consistency of the control data, you must validate the descriptions stored in XML format validated against the XML schema RRT-MappingSchema.xsd in the \XMLSchema subdirectory of your Rochade directory.

When you access the control data in AutoPilot to modify them, AutoPilot will load these data in the XML editor that is configured as the default XML editor on your machine.

If you need to adjust the NO-EDIT interface that AutoPilot uses to open the control data, do this by adjusting the Rochade Procedure Language (RPL) procedure DWR-NOEDIT- DWR-MAPPINGSCHEMA, which is included in the Reconciliation Toolkit package. For information on NO-EDIT interfaces, see the ASG-Rochade AutoPilot System Administrator’s Guide.

Note:The templates provided by ASG were produced using Altova XMLSpy (see http://www.altova.com/download_spy_enterprise.html).

Configuring the control data is described in “Control Data Configuration Example” on page 12, using an example that involves the transformation of DB2 metadata for DB2BUS. Other transformations follow the same steps in a similar manner.

The ASG-Rochade Reconciliation Toolkit Technical Guide contains a detailed description of the meaning, structure, and relationships of the Reconciliation Toolkit control data. The explanations that follow present only a highly abbreviated summary of those explanations.

11


Control Data Configuration ExampleThis example demonstrates how to configure the control data for a DB2 metadata transformation. It starts with these assumptions:

• DB2BUS has created metadata in a Rochade subject area named DB2 and with a version named CATALOGUE.

• The metadata in this subject area conform to the unmodified DB2 subset of the C-RIM included in ASG-Rochade I-RIM.

• The subject areas reside in a Rochade database named AP-DATA and are named as stipulated in “Setting Up the DW Application Subject Area” on page 9.

Based on these assumptions, it is your task to configure for the subject area DB2 CATALOGUE an environment in which the transformation and transport of DB2 metadata to the DW Application subject area DWR INTEGRATION can be executed.

To configure control data for a DB2 metadata transformation

1 Select the appropriate job template:

• If DB2BUS was run in its standard configuration, open the item DWR-DB2 of type DWR_CTL_JOB in the control area RRT-CONTROL ADMIN, and create a copy of this job template item (e.g., with the name RUN-DB2).

• If a different DB2BUS naming convention is used, select the template with the respective name suffix:

— DWR-DB2: Template for DB2BUS with creator links

— DWR-DB2-w/o_CreatorLinks: Template for DB2BUS without creator links

— DWR-DB2-w/o_CreatorLinks_butPrfx: Template for DB2BUS without creator links but name prefix

— DWR-DB2-w/o_CreatorLinks_butSffx: Template for DB2BUS without creator links but name suffix

— DWR-DB2-with_CreatorPrefix: Template for DB2BUS with creator links and name prefix

— DWR-DB2-with_CreatorSuffix: Template for DB2BUS with creator links and name suffix

For information on the configuration of DB2BUS, see the DB2BUS for ASG-Rochade User’s Guide.

2 Modify the attribute DWR_CTL_INSTRUCTIONS of the item copy DWR_CTL_JOB RUN-DB2 created in step 1 on page 12 by replacing the placeholders as in this example:

<Transformation Database="AP-DATA">

12


<Source Database="AP-DATA" Type="S" Name="DB2" Version="CATALOGUE"/> <Integrator Database="AP-DATA" Type="S" Name="DWR" Version="INTEGRATION"/></Transformation>

This code specifies the subject area DB2 CATALOGUE as the source of the transformation and the subject area DWR INTEGRATION as its target.

Configuring the Command File for Reconciliation Toolkit

The command files delivered with the Reconciliation Toolkit package are deposited in the \Samples\rrt\cmd subdirectory of your Rochade directory during the Application installation of the product. The data space file RRT-dataspace.xml is stored in the same directory.

To configure the command files

1 In the data space file, check these specifications and adjust them as needed:

• Specification of the database in which the control area for Reconciliation Toolkit resides:

<DATABASE Name="AP-DATA">

• Specification of the control area for Reconciliation Toolkit:

<APPLICATION applType="RTC" Name="RRT-CONTROL" Version="ADMIN"/>

• Specification of the Rochade server:

<SERVER Name="SERVER1" host="host" port="port"/>

2 In the command file RRT-set-env.cmd for configuring the Reconciliation Toolkit environment, check these specifications and adjust them as needed:

• Specification of the Rochade root directory:

set _ROCHADE_HOME=Rochade

• Specification of the Java Home directory:

set _JAVA_HOME=JAVA_HOME

3 Create a copy of the template command file DWR-DB2.cmd (or of the command file that corresponds to the DWR_CTL_JOB file that you selected in step 1 on page 12) under a name such as RUN-DB2.cmd.

13


4 Enter these specifications in the file RUN-DB2.cmd:

• Specification of the AutoPilot user who has READ rights for the subject areas RRT-CONTROL ADMIN and DB2 CATALOGUE and has WRITE rights for the subject areas DWR CONSOLIDATION and DWR INTEGRATION:

set _DWRT_USR=AutopilotUser

• Specification of the password for this AutoPilot user:

set _DWRT_PWD=PassWord

• Specification of the transformation start item of type DB2/SYSTEM:

set _DWRT_ITM=SeedItemName

Running a Transformation

Once you have set up the DW Application subject area and configured the control data and the command file for the intended transformation, you are ready to run the transformation.

To run the transformation

Execute the command file.

For the example used in earlier sections on setup and configuration, this is the file RUN-DB2.cmd.

A log similar to this example will be created and will appear on your computer screen:

ASG-Rochade(TM) Reconciliation Toolkit - Version 1.50.004-20070507141745Copyright (c) 2005-2006 ASG GmbH & Co. KG, a wholly owned subsidiary of Allen Systems Group, Inc. All rights reserved.I0005 Rochade Reconciliation Toolkit started at 2007-09-03 09:35:50I0048 Job File : Test-CDM-Darren-Empty.xmlI0044 Control application : S RRT-CONTROL ADMIN in database AP-DATAI0026 Job defined variable stage = 'DataWarehouse'I0026 Job defined variable technicalSteward = 'a technical test steward'I0026 Job defined variable businessSteward = 'a business test steward'I0035 Mapping DWR-CDM/ENTITY defined variable stage = ''I0036 Mapping DWR-CDM/ENTITY uses variable stage = 'DataWarehouse'I0035 Mapping DWR-CDM/ENTITY defined variable businessSteward = ''...I0035 Mapping DWR-CDM/ATTRIBUTE_2_DATA_TYPE defined variable stage = ''I0036 Mapping DWR-CDM/ATTRIBUTE_2_DATA_TYPE uses variable defaultDataTypes = '$$DefaultDataTypes'I0043 Source application : S AEGONPOC INITIAL in database DARRENI0045 Integrator application : S DWR TEST-EMPTY in database AP-DATAI0046 Rochade Reconciliation Toolkit processing seed item 1 of 1 CDM/MODEL Daily_IMDWI0034 Consolidator : identify items.I0040 Consolidator : 4646 Rochade items

14


I0047 It took 1 minutes and 11 secondsI0037 Consolidator : CDM/ATTRIBUTE, mapping=DWR-CDM/ATTRIBUTE, 3973 itemsI0047 It took 1 minutes and 59 secondsI0037 Consolidator : CDM/ATTRIBUTE, mapping=DWR-CDM/ATTRIBUTE_2_DATA_TYPE, 540 itemsI0047 It took 0 minutes and 0 secondsI0037 Consolidator : CDM/DATA-TYPE, mapping=DWR-CDM/DATA-TYPE, 3 itemsI0047 It took 0 minutes and 0 secondsI0037 Consolidator : CDM/DATA-TYPE, mapping=DWR-CDM/DATA-TYPE_FUNDAMENTAL, 3 itemsI0047 It took 0 minutes and 0 secondsI0037 Consolidator : CDM/ENTITY, mapping=DWR-CDM/ENTITY, 44 items.I0047 It took 0 minutes and 1 secondsI0037 Consolidator : CDM/IDENTIFIER, mapping=DWR-CDM/IDENTIFIER, 40 itemsI0047 It took 0 minutes and 1 secondsI0037 Consolidator : CDM/MODEL, mapping=DWR-CDM/MODEL, 1 itemsI0047 It took 0 minutes and 0 secondsI0037 Consolidator : CDM/MODEL, mapping=DWR-CDM/MODEL_2_DAT_PACKAGE, 1 itemsI0047 It took 0 minutes and 0 secondsI0037 Consolidator : CDM/RELATIONSHIP, mapping=DWR-CDM/RELATIONSHIP, 35 itemsI0047 It took 0 minutes and 1 secondsI0037 Consolidator : CDM/SUBJECT-AREA, mapping=DWR-CDM/SUBJECT-AREA, 4 itemsI0047 It took 0 minutes and 0 secondsI0040 Consolidator : 4644 Rochade itemsI0047 It took 3 minutes and 16 secondsI0006 Rochade Reconciliation Toolkit finished at 2007-09-03 09:39:09

In addition, an item of type DWR_CTL_JOB_LOG will be created in the control area DWR-CONTROL ADMIN. The name of the item will be derived from the date, time, and AutoPilot user name relevant to the command file execution. The attribute DWR_CTL_JOB_LOG will be filled with content analogous the example log above.

This concludes the successful transformation and transport of metadata to the DW Application subject area.

Compatibility with Earlier Versions

Data Warehouse Reconciliation Model DWRRIM10The DWRRIM10 contains a number of significant changes since earlier releases that required migrating existing data created with releases before 1.50.000.

These changes are the most significant:

• New item types

— DWR_ANL_DIMENSION_MAP

— DWR_ANL_MEMBER

— DWR_ORG_MEMBER

15


— DWR_ORG_MEMBER_FUNCTION

— DWR_ORG_MEMBER_POSITION

— DWR_ORG_ORGANIZATIONAL_UNIT

— DWR_ORG_ORG_UNIT_FUNCTION

• Removed item types

— DWR_ANL_CONTENT_MAP

— DWR_ANL_CUBE_DEPLOYMENT

— DWR_ANL_DIM_DEPLOYMENT

— DWR_ANL_MEASURE (renamed to DWR_ANL_MEMBER)

— DWR_ANL_OLAP_DEPLOYMENT

— DWR_ANL_RPT_DEPLOYMENT

— DWR_ANL_STRUCTURE_MAP

Note:ASG recommends that you make sure that the namespace attributes are assigned to the system table of the DW Application subject area. See also “Setting Up the DW Application Subject Area” on page 9.

Make sure that the DWRRIM is generated with the option you consider as adequate.

If you have a DW Application subject area that was created with a release earlier than 1.50, consider taking these steps:

1 Invoke the AutoPilot application administration.

2 Suspend and reorganize the DW Application subject area.

3 Update the view according to the item type changes listed at the beginning of this section.

4 Set status to in-work and close AutoPilot application administration.

5 Open the DW Application subject area.

6 If you have existing data and have chosen to enable the new functionality during model generation, you must execute the AutoPilot migration procedure AP-TR37-MIGRAT.SA. You can find detailed instructions in the ASG-Rochade AutoPilot Release Notes. (Check in the ISP for the most recent version of this migration procedure before execution.)

16


7 If you have existing data, you also must execute the Data Warehouse data migration as explained under “Migrating Data Warehouse Data” on page 17.

For more detailed instructions, see also the ASG-Rochade AutoPilot System Administrator’s Guide and ASG-Rochade AutoPilot Release Notes.

Migrating Data Warehouse DataThis section describes how the migration procedure is called, how you can influence the migration, and how the process works.

Note:You can ignore the instructions in this section if you have no data created with earlier releases. Otherwise, it is a prerequisite that you have completed the instructions described under “Data Warehouse Reconciliation Model DWRRIM10” on page 15 before starting this migration effort.

To be able to work with your existing data according to the new model, you must migrate your application data.

Starting Migration

To start the migration in dialog

1 Open your Data Warehouse subject area.

2 Call Menu System - Command Interpreter.

3 Enter the migration procedure name DWR-RIM-MIG-150.

Note:A message box shows you the migration progress. When the migration ends, a log is displayed with statistics and, possibly, error messages.

To start the migration in batch

1 Create a client startup file that opens the reorganized application using AP-TOOL+BATCH and calls the migration procedure DWR- RIM-MIG-150.

2 Start a batch client using that bat file.

17


Note:Under Windows, you can catch the migration log by routing the result to a specific file (e.g., ROCLIGXN MIG C:\ROCHADE\APPL\ROCHADE.INI > C:\TEMP\MIG.LOG).

Migrating Control ItemDuring the migration, the procedure DWR-RIM-MIG-150 uses the control item ROSHELL-SYSTEM DWR-MIG-RIM-150 to influence the behavior of the migration process. ASG recommends that you not change the content of this item directly, but instead create a copy under the name DWR-MIG-RIM-150.UD, then change the new item’s content. During the execution, the original item is read first, then the user-defined one.

You can use the control item to set these variables:

Variable Meaning

MIGBUSR Defines whether the content of attribute DWR_BUSINESS_RESPONSIBILITY is migrated to link attribute DWR_BUSINESS_STEWARDSHIP. These are its valid values:

NIL Default. The attribute is not migrated. The old content is deleted.

F The procedure named in MIGBUSRP is called for all items that have the attribute filled.

A The procedure named in MIGBUSRP is called for all items. So it can be used also to set an initial value for yet unfilled attributes.

MIGBUSRP Provides the migration procedure for DWR_BUSINESS_RESPONSIBILITY.If the procedure does not exist, the parameter is ignored and MIGBUSR is regarded as NIL.The parameters have these meanings:

ARG1 Item type.

ARG2 Item name.

ARG3 Work area with current attribute content.

ARG4 Work area for new content.You must fill this work area with item type and item name per line. The item name is restricted to one Rochade word and a maximum of 32 characters.

MIGDTPCK Defines the name of the DWR_DAT_PACKAGE, which will be the parent for all DWR_DAT_DATA_TYPE items that are not yet within a namespace.Default: $$MigratedDataTypesThe name is restricted to one Rochade word and a maximum of 32 characters. If you skip the at sign (@) in front of the name, the item name is transformed to uppercase.

18


Executing MigrationWhen the migration procedure is started, it first checks whether an application using the new model is opened.

Then the control items ROSHELL-SYSTEM DWR-RIM-MIG-150 and DWR-RIM-MIG-150.UD are read and the settings are checked. The DWR_DAT_PACKAGE to receive the migrated root DWR_DAT_DATA_TYPE items is created, if it does not yet exist.

All items of these item types are removed from the subject area:

• DWR_ANL_CONTENT_MAP

• DWR_ANL_CUBE_DEPLOYMENT

• DWR DWR_ANL_OLAP_DEPLOYMENT

DWR_ANL_STRUCTURE_MAP items are migrated to items of item type DWR_ANL_DIMENSION_MAP, and they are moved to the corresponding namespace of the grandparent DWR_ANL_DIMENSION. The intermediate DWR_ANL_DIM_DEPLOYMENT items are deleted after their links to source items are copied to the parent DWR_ANL_DIMENSION.

All DWR_ANL_MEASURE items are moved to items of type DWR_ANL_MEMBER. The links to the items are adjusted accordingly.

DWR_ANL_RPT_MAP items are moved to the corresponding namespace of the grandparent DWR_ANL_REPORT. The intermediate DWR_ANL_RPT_DEPLOYMENT items are deleted after their links to source and target items are copied to the parent DWR_ANL_REPORT.

MIGRECON Defines whether attribute DWR_RECONCILED is filled for all items automatically. These are its valid values:

NIL Default. The attribute is not changed.

T The value true is set into the attribute for all items.

F The value false is set into the attribute for all items.

MIGTECR Defines whether the content of attribute DWR_TECHNICAL_RESPONSIBILITY is migrated to link attribute DWR_TECHNICAL_STEWARDSHIP. These are its valid values:

NIL Default. The attribute is not migrated. The old content is deleted.

F The procedure named in MIGTECRP is called for all items that have the attribute filled.

A The procedure named in MIGTECRP is called for all items. So it can be used also to set an initial value for yet unfilled attributes.

Variable Meaning

19

DWR_DAT_DATA_TYPE items that are in the root namespace are moved into the namespace of the migration DWR_DAT_PACKAGE named in the control item. The references to these items are adjusted accordingly. For all links to DWR_DAT_DATA_TYPE items, the link qualifier is deleted after its content is put into the source item’s attributes DWR_DAT_LENGTH and DWR_DAT_SCALE.

For DWR_ERM_ATTRIBUTE items, the content of attributes DWR_ERM_AT_OF_TYPE, DWR_ERM_LENGTH, and DWR_ERM_SCALE are moved to the attributes DWR_DAT_OF_TYPE, DWR_DAT_LENGTH, and DWR_DAT_SCALE.

If the variable MIGRECON is set to T or F, the attribute DWR_RECONCILED is set to true or false for all items.

If the business and/or technical responsibility has to be migrated, the appropriate procedure is called for all respectively filled items.

Adapting Transformations

Note:Ignore the instructions in this section if none of your transformations were executed using earlier releases.

The most significant improvement is that, since Version 1.00.004, Reconciliation Toolkit has been running as a one-step process with a virtual intermediate consolidation area. This approach saves the time that used to be required to instantiate a potentially huge number of items in the consolidation area within the Rochade data store and to clean them up after the integration was completed.

Consequently, a transformation job requires only Source and Integrator to be specified; the Consolidator entry is obsolete and will be ignored. This sample code reflects this fact:

<Job Seedtype="<see-typ>" xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance xsi:noNamespaceSchemaLocation="RRT-MappingSchema.xsd"><Transformation Database="<db>"><Source Database="<s-db>" Type="<S|P>" Name="<s-name>" Version="<s-vers>"/><Integrator Database="<i-db>" Type="<S|P>" Name="<i-name>" Version="<i-vers>"/></Transformation></Job>

Revise all transformation jobs that you have created. All jobs delivered by ASG (i.e., those with a prefixed of DWR) have already been adapted (see also ASG-Rochade Reconciliation Toolkit Technical Guide).

20

http://www.w3.org/2001/XMLSchema-instance


Adapting Mappings

Note:Ignore the instructions in this section if none of your mappings were defined using earlier releases.

As a consequence of the virtual intermediate consolidation area, the interface of the attribute update procedures has been extended.

The existing ResultSet Update returned within the ResultSet Result works directly against the integration area without regard to the integration instructions.

For the ResultSet Result, a new ResultSet Contents is introduced that expects the contents of the attribute that will subsequently be processed in the integration step as defined by the integration instructions. You must explicitly add this ResultSet Contents to the ResultSet Result within the attribute update procedure in accordance with the attribute type based on the SRAP conventions for updating attributes.

Revise all mappings that you have created. All mappings delivered by ASG (e.g., those with a prefixed of DWR) have already been adapted (see also ASG-Rochade Reconciliation Toolkit Technical Guide).

TroubleshootingIf you have questions or problems concerning Reconciliation Toolkit, contact ASG Customer Support. Be prepared to supply an export of the DWR_CTL_JOB_LOG item and detailed information about any modifications of control data and command files to enable ASG to analyze problems effectively and efficiently.

21


22

asg-rochade reconciliation toolkit release notes · asg-rochade reconciliation toolkit release...

Documents