Framework Manager 8 Workshop 1 - Create a Simple Model

download Framework Manager 8 Workshop 1 - Create a Simple Model

of 18

  • date post

    29-Aug-2014
  • Category

    Documents

  • view

    107
  • download

    3

Embed Size (px)

Transcript of Framework Manager 8 Workshop 1 - Create a Simple Model

Framework Manager Introduction Workshop OneCreate a Simple Model

1 Workshop GoalsWe are going to create a Framework Manager model in which we use data source query subjects to represent a physical layer in the model and model query subjects to represent the presentation layer of the model. We will use the model as the basic for many further workshops, so please follow the directions carefully. This workshop is a script that reads from top to bottom. Each step depends on you having followed the instructions for the previous steps correctly. This first workshop is VERY LONG. Time is LIMITED. Focus on getting the workshop COMPLETED in the time available. This workshop requires you to have the GO Sales and GO Retailers databases installed on your computer. If you do not, please go to Appendix A now and restore the databases.

2 Create a New ProjectOpen Framework Manager. Select Create a new project. Specify a project name of GO_ApplicationGO Sales FM WKSHP. Select English USA as your language: you must/should do this follow-on workshops depend on this. Apologies in advance to those who prefer to work in other languages. Notes: When I say must/should, I mean tested versus not-tested.If you want to add a project to a repository, you must set up the repository connection.

When you work in Framework Manager, you work in the context of a project. The Framework Manager project contains objects that you organize for reporting authors according to the business model and business rules of your organization. You view these objects in the project page.

A Framework Manager project appears as a folder that contains a project file (.cpf) and the specific .xml files that define the project. The files in a project folder are unique to each project. Tip: The project and the projects associated files are contained in a project folder. We recommend that you do not add any other files to this project folder.Project FolderThese are the contents of a project folder. Files that are used by all projects of the same type are stored in the templates folder. The templates folder also contains initial templates of the project and user preferences. File name .cpf Description The Framework Manager project file, which references the .xsd and .xml files used to define a project The actual model data created by Framework Manager users The preferences for Framework Manager projects The stored diagram information. For example, the diagram layout, notation, font, color, etc. The logged version history for each project or segment that has been added to a repository

model.xml Preferences.xml customdata.xml repository.xml

Files that are used by all projects of the same type are stored in the templates folder. The templates folder also contains initial templates of the project and user preferences.

Templates FolderThese are the contents of the templates folder. File name BMTModelSpecification.xsd CR1 Behaviors.xml Description The schema definition for Framework Manager projects. The user interface behavior of Framework Manager projects. This file also contains the mapping between actions and plug ins, XML tags and CR1 objects. A Framework Manager model template. The preferences template for Framework Manager Text to be translated for localization Text to be translated for localization, including icons and graphics

model.xml Preferences.xml projects. stringtable.xml resources.xml

We will not select an import method right now. Select Cancel to the Import process.

3 Create GO Sales Data Source Query SubjectsSelect import metadata. Select Database as your import source.

3.1 Create a Data SourceIf you have a connection to the samples database GO Sales, use it. Otherwise, create a new data source called GO Sales . The New database connection wizard starts. Type: Microsoft SQL Server. Isolation level: Use default object gateway Note: Isolation Levels The isolation level specifies how transactions that modify the database are handled. By default, the default object gateway is used. You can select from the following isolation levels. Not all types of database support each isolation level. Some database vendors use different names for the isolation levels. Server name: Database name: GO Sales ML Application name: Collation sequence: Userid: Yes (checked) Password: Yes (checked, even if you have a blank password) Create a signon that the Everyone group can use: Yes (checked) Userid: sa Password: sa Note: This assumes you have not changed the sa login information. Note: Customer Workshop should point to Note: If you have a problem with the data source connection, you cannot edit it from Framework Manager. You must go touse Cognos Connection administration and edit it there.

3.2 Use Import to Data Source Query SubjectsThe Import Wizard Select objects dialog open. Select all tables, and nothing else. Select the following check boxes Use primary and foreign keys

Between the imported query subjects Convert to inner join ( 1..n ) This is important so your results mesh with later steps in this workshop. Open the GO Sales folder and you will see that Framework Manager has created one data source query subject per table you selected.

4 Examine the Imported Data Source Query SubjectsOpen a query subject (click the + sign). You will see that each column in the table has a matching query item. Click on any query item and examine the properties in the bottom centerd frame. Rename a query item in the property sheet. Undo and save often. Right click on any query subject and select edit definition. You will see that all of these query subjects are simple select * from queries. Notice the format of the table specification syntax in the query, especially the qualification. For example, the Country table is qualified by the data source connection name: [GO Sales IB 47].COUNTRY. In this dialog, you can modify the SQL query either by dragging and dropping database items into the query or had editing the query. We will do all this and more later in this workshop. Look at the tab. This shows you Framework Managers interpretation of the SQL youve specified. Good for debugging. Press the button. This runs the query. You may wish to resize the dialog. In the top right hand corner of this dialog, you will see several buttons. Hold your mouse pointer over each one in turn and read the tool tip text. Using these buttons the query. Determine the in the result. Use the to change the number of rows of data returned in the test result to 100. this. We will look at many more and the remaining buttons later. out of this dialog so you do not make anysave your changes.

5 Fun with DiagramsIn the center frame, click to open the model.:

You will see a list of objects in the model. This is a convenient view of the model for managing relationships and large numbers of objects. Using the Framework Manager toolbar buttons, switch to the view.

5.1 Zoom, zoom, zoomWorking with DiagramsUse these buttons to hide or show the project view, properties, Diagram, Dimension map and Explorer windows:

Use these buttons to zoom and re-draw your diagram:

Using the toolbar buttons, select as your zoom level. Using the toolbar buttons, select as your zoom level.

Look at the bottom right corner of the diagram (where the scroll bars intersect) for the icon. Click on this and figure out what it does. Using the toolbar buttons, switch to . Select a query subject in the model and Uusing the toolbar buttons, select then . It that more readable?to redraw the diagram.

Select the query subject called RETURN_REASON and press . Note that the auto layout feature used the table you selected as it starting point for the layout. Using the toolbar buttons, select as your zoom level.

5.2 Back to the DetailsUsing the toolbar buttons, switch to . In the Diagram View, right click on PRODUCT_LINE and click .select Locate in Diagram and click .

6 Clean Up the JoinsFramework Manager makes its best guess ondetermines cardinality based on the database structure. But, it is not perfect, as the databases do not provide sufficient information for Framework Manager to be 100% correct. You must examine the joins and ensure they are correct. You can work in either the Large Icons or Details view as you wish.Keep working in the Object diagram, details view. Select a relationship between two tables. and select . The Relationship Editor allows you to set properties of this relationship. For example, you can set the cardinality. Ensure the correct relationships as listed below. The other generated relationships should be ok as is. Hint: If you zoom in on the model, you can see the relationships and will not have to examine the properties of them all.

COUNTRY 1..1 COUNTRY 1..1 SALES_STAFF 1..1

0..n EURO_CONVERSION 0..n CONVERSION_RATE 0..n SALES_TARGET

7 Enhance the Query Subjects7.1 Order DetailsOver the next few workshops, we will enhance the default query subjects in several ways. The first thing we will do is to add some calculations to ORDER_DETAILS. In the on ORDER_DETAILS and select . Select and the tab. Note that this query uses Cognos SQL. from options and look at the SQL query. There are several calculations we wish to add to this query subject. Before we can do so, we must convert this from a select * query to one that selects individual columns. In the left pane of the Edit definition dialog, open up the ORDER_DETAILS table. Select all of the columns in this table and drop them onto the * in the query. Delete the *, from the query. You should now have something like this:Select ORDER_DETAILS.ORDER_DETAIL_CODE, ORDER_DETAILS.ORDER_NUMBER, ORDER_DETAILS.PRODUCT_NUMBER, ORDER_DETAILS.QUANTITY, ORDER_DETAILS.UNIT_COST, ORDER_DETAILS.UNIT_PRICE, ORDER_DETAILS.UNIT_SALE_PRICE from [GO Sales ML].ORDER_DETAILS