IBM Cognos 8 Framework Manager - Durable Models

Transcription

1 Proven Practice IBM Cognos 8 Framework Manager - Durable Models Product(s): Framework Manager Area of Interest: Modeling

2 IBM Cognos 8 Framework Manager - Durable Models 2 Copyright Copyright 2008 Cognos ULC (formerly Cognos Incorporated). Cognos ULC is an IBM Company. While every attempt has been made to ensure that the information in this document is accurate and complete, some typographical errors or technical inaccuracies may exist. Cognos does not accept responsibility for any kind of loss resulting from the use of information contained in this document. This document shows the publication date. The information contained in this document is subject to change without notice. Any improvements or changes to the information contained in this document will be documented in subsequent editions. This document contains proprietary information of Cognos. All rights are reserved. No part of this document may be copied, photocopied, reproduced, stored in a retrieval system, transmitted in any form or by any means, or translated into another language without the prior written consent of Cognos. Cognos and the Cognos logo are trademarks of Cognos ULC (formerly Cognos Incorporated) in the United States and/or other countries. IBM and the IBM logo are trademarks of International Business Machines Corporation in the United States, or other countries, or both. All other names are trademarks or registered trademarks of their respective companies. Information about Cognos products can be found at This document is maintained by the Best Practices, Product and Technology team. You can send comments, suggestions, and additions to cscogpp@ca.ibm.com.

3 IBM Cognos 8 Framework Manager - Durable Models 3 Contents 1 INTRODUCTION PURPOSE MODEL DESIGN MODELLING FOR MULTIPLE LANGUAGES... 15

4 IBM Cognos 8 Framework Manager - Durable Models 4 1 Introduction 1.1 Purpose There is no guarantee when creating a model that aspects of the underlying database, or user requirements change and thus affect your model. The goal is to create a model that can survive as many of these changes as possible without impacting the end user and their existing queries. This document will point out some concepts which will help you to create models that will be as flexible as possible and help survive changes to the requirements. 1.2 Model Design The most important aspect of the model which can be done to ensure durability is to use a layered approach. The term layered approach means the use of at least a database (also known as import) layer and a business (or presentation) layer. The concept is that any modifications that are needed to be done to the query subjects are done to the Business view, this includes security. Changes that should minimize the impact on existing reports are those done on calculations, security or descriptions of Query Items. Changes to the actual naming conventions will impact existing reports and require the author to modify them.

5 IBM Cognos 8 Framework Manager - Durable Models 5 Report Prior to Business View Change Example of the Business View in the FM model changing due to client requirements. In this case we re changing Order Number to Order No.

6 IBM Cognos 8 Framework Manager - Durable Models 6 Once this change has been made, the Report built against the Business view is no longer valid as it has a reference to a Query Item which no longer exists. Error Opening the report in Report Studio.

7 IBM Cognos 8 Framework Manager - Durable Models 7 To fix the report simply delete the previous Query Item and add in the altered Query Item. In this case it s a simple resolution however any calculations or references built off of the old Query Item Order Number will also have to be changed. Notice that the filter also had to be changed. The database or import view should be left alone, and where possible import only what is needed rather than everything in the underlying database. Changes done to the Import view should minimize the impact on the end user, depending on the type of changes. Issues like changing of database column names should not impact the business view assuming you then modify the Import view query subject to point to the new database table/column and then associate the Query Item in the Business view in the modified Query Item from the Import View. In the example below a change is to be made to the Order Details Table on the database. Order Number is being changed to Order No. and as a result the model will need to be changed.

8 IBM Cognos 8 Framework Manager - Durable Models 8 Report Prior to Database Change.

9 IBM Cognos 8 Framework Manager - Durable Models 9 Change Made to Database

10 IBM Cognos 8 Framework Manager - Durable Models 10 After the change has been made on the database an error will occur in the FM model, to fix the error the Query Subject needs to be updated to reflect the new information in the database.

11 IBM Cognos 8 Framework Manager - Durable Models 11 Once the Import View has been changed you will also need to change the Business View to include the changed Query Item. Verifying the model in Framework Manager will result in a message like the one below.

12 IBM Cognos 8 Framework Manager - Durable Models 12

13 IBM Cognos 8 Framework Manager - Durable Models 13 Once all changes in the model have been made and the package has been republished there should be no impact on the reports created against he package assuming the report author used the business view to create their reports. Changes to Query Item names in the Import View will have no impact on the reports.

14 IBM Cognos 8 Framework Manager - Durable Models 14 To simplify things, when changing any part of a model check to see what reports will be impacted by the change. This can be done using the Find report dependencies task in Framework Manager.

15 IBM Cognos 8 Framework Manager - Durable Models Modelling for Multiple Languages Another option for building a durable model is to create a model with a base language other than that which you have within your business requirements. For example assume that you re users work in both English and French. An option is to create your model and use something other than English or French as the design language for the model. English (Zimbabwe) would be an alternative for the design language which you could create the necessary structure. Create a new Model using English (Zimbabwe) as the design language.

16 IBM Cognos 8 Framework Manager - Durable Models 16 You would then add the languages that the users need into the model, for the above mentioned scenario you would then add English and French into the model. A translation is then performed on the project. Assume that you have a query item called order number in the design language. English users want the item to say ORDER NUM and French users want the item to say ORDER NO.

17 IBM Cognos 8 Framework Manager - Durable Models 17 Your report authors should now create reports in the design language, then any necessary changes to Query Items done in each of the reporting languages can be done without impacting the reports Report Created with English as the Content Language

18 IBM Cognos 8 Framework Manager - Durable Models 18 Report Created with English (Zimbabwe) as the Content Language If the English requirements change once the model is published, then any changes done to the model will not impact previously created reports that were created with English (Zimbabwe) as the Content Language at the time of creation.

19 IBM Cognos 8 Framework Manager - Durable Models 19 Change made to the Framework Manger project. Note the Active Language and the change to the ORDER NUM object.

20 IBM Cognos 8 Framework Manager - Durable Models 20 Report created with English (Zimbabwe) as content language after the change to the Order Number object for the English language. The user that ran this report had their Content Language to English at the time of execution.

21 IBM Cognos 8 Framework Manager - Durable Models 21 However if you used English as the design language instead of English (Zimbabwe) then all reports using ORDER NUM would need to be recreated. Attempting to run these reports regardless of the language will result in the following error.