User manual BUSINESS OBJECTS DATA INTEGRATOR 6.5.1 CORE TUTORIAL

[. . . ] Data Integrator Core Tutorial Data Integrator Core Tutorial Version 6. 5. 1 COPYRIGHT No part of the computer software or this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage and retrieval system, without permission in writing from Business Objects. The information in this document is subject to change without notice. If you find any problems with this documentation, please report them to Business Objects in writing at documentation@businessobjects. com. Business Objects does not warrant that this document is error free. [. . . ] In this instance, enter: ($recovery_needed = 1) " T define the normal mode work flow o You will reuse the data flow created in chapter 4. 1. In the object library, click the Data Flows tab. In the Data Flows list, drag DF_SalesOrg into the lower (Else) box of the conditional. This data flow is for the "false" branch of the conditional. 140 Data Integrator Core Tutorial Recovery Mechanisms Specifying a recoverable job 10 " T specify the recovery mode work flow o The recovery mode work flow will call a modified version of DF_SalesOrg. The only difference is that the Update control for the salesorg_dim target table will have the Auto correct load option enabled. The Auto correct load option causes the table loader to check for existing rows with the same key as each INSERT/UPDATE. When there is a match, the preexisting row will be deleted before inserting a new row (UPDATEs are mapped to INSERTs). To minimize work in defining this new data flow, the following procedure replicates, renames, and edits DF_SalesOrg for the recovery branch. 1. In the object library, click the Data Flows tab. In the Data Flows list, right-click DF_SalesOrg and click Replicate. The replicated data flow will be named Copy_1_DF_SalesOrg. 3. Click the highlighted name and rename the data flow to ACDF_SalesOrg. 4. Drag ACDF_SalesOrg to the upper (Then) box of the conditional. This data flow is for the "true" branch of the conditional. " T specify auto correction for the target table o 1. Open the target table SALESORG_DIM. Data Integrator Core Tutorial 141 10 Recovery Mechanisms Specifying a recoverable job 3. Click the Options tab and select the Auto correct load box. Adding the script that updates the status This script executes after the work flows in the conditional have completed. Its purpose is to update the status table with the current timestamp to indicate successful execution. " T add the UpdateWFStatus script o 1. Add a script to the right of the recovery_needed conditional and name it UpdateWFStatus. 3. Open UpdateWFStatus. 142 Data Integrator Core Tutorial Recovery Mechanisms Specifying a recoverable job 10 4. Enter the script contents, which depend on the RDBMS on which status_table resides, as shown in the following table. Be sure the entire statement is contained on a single line (not on multiple lines, as shown). RDBMS Oracle Script sql('Target_DS', 'update status_table set end_time = SYSDATE where start_time = (select max(start_time) from status_table)'); sql('Target_DS', 'update status_table set end_time = getdate() where start_time = (select max(start_time) from status_table)'); sql('Target_DS', 'update status_table set end_time = current where start_time = {$max_start_time}'); sql('Target_DS', 'update status_table set end_time = current timestamp where start_time = (select max(start_time) from status_table)'); Microsoft SQL Server, Sybase Informix DB2 5. Validate the script. Specifying job execution order Connect the objects in the Job_Recovery job so that they execute in the following order: 1. [. . . ] Local variables pertain to the work flow in which they are defined. You can pass the value into another work flow or data flow using a parameter. Data Integrator Core Tutorial 245 A Glossary Global variables pertain to the job in which they are defined. With global variables, there is no need to define parameters between objects in the job. Global variables can also be selected at execution time. [. . . ]