Publishing an OLAP Schema Activity

 

 

 

Step

Action

1. 

Begin by logging into JasperReports Server as the administrator.

 

Enter jasperadmin into the User ID field.

2. 

Enter jasperadmin into the Password field.

3. 

Enter organization_1 into the Organization field.

4. 

Click the Login button.

5. 

Note: The home page appears.

 

6. 

Navigate to the repository folders panel.

Point to the View menu.

7. 

Click the Repository menu item.

8. 

Note: The repository page appears. The Folders panel is at the left, and Repository panel in the center.

9. 

Click to expand the Organization folder.

10. 

Expand the Analysis Components folder.

11. 

Note: Resources in the Analysis Components folder are used for online analysis.

12. 

Click the Analysis Data Sources folder to display its contents in the Repository panel.

13. 

Note: Selecting a folder displays its content resources in the Repository panel at the right.

 

Subfolders are displayed in the Folders panel only when you expand a folder.

14. 

Now, test the data source connection to make sure it works properly.

Right-click the Foodmart Data Source list item to display the context menu.

15. 

Click the Edit menu item.

16. 

Note: The Edit Data Source page opens.

17. 

Click the Test Connection button.

18. 

Note: The success message at the bottom of the browser page indicates that the database connection is active.

19. 

Click the close link if the success message remains visible.

20. 

Return to the repository view.

Click the Cancel button.

21. 

Next, upload to the repository the OLAP schema file you created with the Workbench.

Right-click the Analysis Schemas folder.

22. 

Point to the Add Resource menu.

23. 

Point to the File menu.

24. 

Click the OLAP Schema menu item.

25. 

Note: The Add File page appears.

26. 

Navigate to find your schema file.

Click the Browse button.

27. 

Click the FoodMart_Schema1.xml list item.

28. 

Click the Open button.

29. 

Note: The schema file is selected for upload.

30. 

Enter Foodmart Example Schema into the Name field.

31. 

Note: The Resource ID field fills in automatically.

32. 

Click the Submit button to save changes.

33. 

Note: The OLAP schema file is saved to the repository.

Task 1: Import the OLAP schema file into the repository, is complete.

34. 

Now, configure an OLAP connection.

Right-click the Analysis Connections folder.

35. 

Point to the Add Resource menu.

36. 

Click the OLAP Client Connection menu item.

37. 

Note: The Add OLAP Client Connection window appears.

38. 

Note: Mondrian is the connection type you need.

39. 

Enter Foodmart Example Connection into the Name field.

40. 

Click the Next button.

41. 

Select the OLAP schema file.

Click the Select a resource from the Repository option.

42. 

Click the Browse button.

43. 

Expand the Analysis Components folder.

44. 

Expand the Analysis Schemas folder.

45. 

Click the Foodmart Example Schema list item.

46. 

Click the Select button.

47. 

Note: The schema file is identified.

48. 

Click the Next button.

49. 

No changes are needed on this page.

Click the Next button.

50. 

Verify that Select a Data Source from the repository is selected. Identify a data source for the connection.

Click the Browse button.

51. 

Expand the Analysis Components folder.

52. 

Expand the Analysis Data Sources folder.

53. 

Click to select the Foodmart Data Source list item.

54. 

Click the Select button.

55. 

Note: The data source is identified.

56. 

Click the Next button.

57. 

No configuration is needed on this page.

Click the Next button to save changes and exit the connection editor.

58. 

Note: The connection is saved to the repository and appears in the list at the right.

 

Task 2: Configure a Mondrian connection for the schema file, is complete.

59. 

Next, create an OLAP view that includes a MDX query.

 

Right-click the Analysis Views folder.

60. 

Point to the Add Resource menu.

61. 

Click the OLAP View menu item.

62. 

Enter Foodmart Example by Store into the Name field.

63. 

Click the Next button.

64. 

Select the Mondrian connection you configured earlier.

Click the Browse button.

65. 

Expand the Analysis Components folder.

66. 

Expand the Analysis Connections folder.

67. 

Click the Foodmart Example Connection list item.

68. 

Click the Select button.

69. 

Note: After naming the view and assigning a connection, specify a MDX query.

70. 

Click the Next button.

71. 

Enter the MDX query into the Query String field (the query is available in the copyAndPaste file).

 

Enter SELECT {[Measures].[Store Cost]} ON COLUMNS, {[Store Name].[All Stores]} ON ROWS FROM [Customer_Cube]

 

Check very carefully for typos.

72. 

Note: This is the same query you ran in the Workbench when you first tested the cube, so you know the query works properly.

73. 

Click the Submit button to save the view and exit the editor.

74. 

Note: The view is saved to the Analysis Views folder.

75. 

Next, create a second view with a different MDX query.

Right-click the Analysis Views folder.

76. 

Point to the Add Resource menu.

77. 

Click the OLAP View menu item.

78. 

Enter Foodmart Example by CA Customer into the Name field.

79. 

Click the Next button.

80. 

Select the Mondrian connection you configured earlier.

Click the Browse button.

81. 

Expand the Analysis Components folder.

82. 

Expand the Analysis Connections folder.

83. 

Click the Foodmart Example Connection list item.

84. 

Click the Select button.

85. 

Click the Next button.

86. 

Enter the second MDX query with which you tested the cube in the previous activity (the query is available in the copyAndPaste file).

 

Enter SELECT {[Measures].[Store Cost]} ON COLUMNS, {[Customer Location].[All Locations].[USA].[CA]} ON ROWS FROM [Customer_Cube]

 

Check carefully for typos.

87. 

Save the new view.

Click the Submit button.

88. 

Note: The view is saved to the repository.

89. 

Now, execute your first view to see how it looks.

Click the Foodmart Example by Store link to execute the OLAP view.

90. 

Note: The view opens for inspection.

91. 

Note: The dollar figure is the same value you saw in the Workbench when you tested the first MDX query. It represents total costs for all stores.

92. 

Expand All Stores to view costs per store.

93. 

Note: Only U.S. stores display sample data; Mexico and Canada stores do not.

94. 

Click the Hide Empty Rows/Columns button, the third button from the top, so only rows with a store cost value display.

95. 

Note: Hiding empty rows makes it easier to analyze data.

96. 

Display the data as a chart.

 

Click the Show Chart button, the sixth button from the top.

97. 

Note: A column chart displays the data. The first column illustrates the total for all the stores.

98. 

Remove the chart display.

Click the Show Chart button again.

99. 

Drill down to view detailed information on Store 11 costs. This opens in a new browser page.

Click the $21,948.94 link.

100. 

Note: The detail page displays information about Store 11 and its transaction costs.

 

Analysts drill into OLAP views in this manner to view detailed information on business events.

101. 

Note: The page counter at the lower left indicates that there are 827 pages in this report.

102. 

Close the Store 11 page and return to the application.

 

Click the X Close button at the upper-right corner of the window.

103. 

Task 3: Create two OLAP views and test one of them, is complete.

 

Click the Log Out link.

104. 

Congratulations!

 

You completed the following three tasks:

 

1. Import the OLAP schema file into the repository

2. Configure a Mondrian connection for the schema file

3. Create two OLAP views and test one of them

End of Procedure.