User manual MACROMEDIA BREEZE-MANAGING EXTERNAL BREEZE REPORTS

[. . . ] 6 Chapter 1: Understanding Breeze Reports. 7 Chapter 2: Using Breeze Reporting Views . 9 Database schema views used in reporting . 9 Database views and data relationships . [. . . ] Breeze Integration Guide includes information necessary to make application programming interface (API) calls on the Breeze server from your external system, such as a web application. It also explains how to interpret the XML results that Breeze returns. In addition, the documentation contains reference material about each API and its parameters. Additional resources Additional documentation, white papers, and articles are available at the following websites: Breeze Resource Center This site, at www. macromedia. com/resources/breeze, is updated regularly with tutorials, simulations, best-practices information, and links to procedures. Breeze Support Center This site, at www. macromedia. com/support/breeze, contains current support information, including TechNotes, helpful Breeze presentations, and support program details. Contact us For additional assistance, please contact Technical Support. 6 Introduction CHAPTER 1 Understanding Breeze Reports The Macromedia Breeze platform allows users to share online meetings, presentations, and training courses over the Internet. Reporting access to Macromedia Breeze data allows you to track learning effectiveness, participation, system usage, and content analysis. 1 The Breeze database Macromedia Breeze requires a database to store information about users, content, courses, meetings, and reports. The database is created as part of the Breeze installation and setup procedure by the Breeze database engine or Microsoft SQL Server 2000. User activity (such as viewing or submitting data) within Breeze populates the database. The collected data can then be viewed in customized reports using external tools such as Crystal Reports, Macromedia ColdFusion Studio, or SQL-based tools. About stored data The following data from Breeze sessions can be captured in Breeze reports. Breeze Presentation: content views, slide views, and presentation views Breeze Training: course management facilities such as course attendee statistics, content viewing statistics, and quiz results Breeze Meeting: meeting attendance, meeting duration, and meeting content About reports Breeze reports are available out of the box; you can also create customized reports. You can export the underlying report data in CSV format. 7 8 Understanding Breeze Reports CHAPTER 2 Using Breeze Reporting Views This chapter describes each of the database schema views used in Macromedia Breeze 5. 1. The external views allow you to develop custom reports that are based on user activity within Macromedia Breeze. This chapter describes the following: 2 Column name data type Length of data contained in each column Primary keys used to map relationships Reporting data is accessible using an SQL-compliant tool. Database reporting views are intended for read-only access and usage. NO T E Database schema views used in reporting Breeze supports external reporting through a set of integrated database views. You use SQL queries to develop customized reports. The following database views are supported in Breeze 5. 1: EXT_TRANSACTIONS EXT_TRANSACTION_DETAILS EXT_TRANSACTION_VIEWS EXT_USERS EXT_USER_FIELDS EXT_USER_ GROUPS EXT_OBJECTS 9 The following are not supported: Use of any other views besides the ones identified in this chapter Any alterations of these views Direct access to the underlying database schema Database views and data relationships The following entity relationship diagram shows the seven external reporting views. The arrows depict how data maps back to the view it was created from. You can view data relationships within any diagramming tool that allows you to connect to databases. 10 Using Breeze Reporting Views Unique identifiers and data relationships Relationships between views are defined by unique identifiers, which are columns that share the same name. The following table shows the columns that are mapped between views. Unique identifiers URL TRANSACTION_ID View(s) used in EXT_OBJECTS EXT_TRANSACTIONS EXT_TRANSACTIONS EXT_TRANSACTIONS _DETAILS EXT_TRANSACTIONS _VIEWS EXT_USERS EXT_TRANSACTIONS EXT_USER_GROUPS EXT_USER_FIELDS LOGIN EXT_TRANSACTIONS A unique transaction ID is generated each time a user accesses an object. The EXT_TRANSACTIONS view uses the data listed in the following table: Column name TRANSACTION_ID LOGIN URL STATUS SCORE DATE_VISITED Data type INT NVARCHAR NVARCHAR NVARCHAR FLOAT DATETIME Description Unique ID for this transaction. The name of user who accessed this transaction. Can be passed, failed, complete, or in-progress. The date this transaction was taken or viewed. The following user actions generate data in this view: Attending a meeting Viewing a piece of content Taking a course Database views and data relationships 11 EXT_TRANSACTIONS sample entries TRANSACTION _ID 26 122 LOGIN URL STATUS SCORE DATE_ VISITED 12/15/2004 11:17:38 PM 12/06/ 2004 11:18:48 PM 12/05/2004 11:22:44 AM brice@adobe. com /r18595812/ completed 8. 0 ccarr@adobe. com /p7096354/ inprogress lblue@adobe. com /p8145026/ userpassed 0. 0 150 10. 0 Constraints The EXT_TRANSACTIONS view excludes the following fields: Certificate number, which does not exist in the database Max score, which is often unavailable EXT_TRANSACTION_DETAILS The EXT_TRANSACTIONS_DETAILS view manages questions and answers per user transcript. This view retrieves data from meeting polls, user forms, and quizzes. [. . . ] Built-in groups, like the Account Administrators Group, use code names in the schema, as in the following SQL query: SELECT * FROM EXT_USER_GROUPS where group='{admins}. The code name distinguishes built-in groups from user-defined groups. EXT_OBJECTS This view lists all system objects (such as meetings, content, courses, and so on) and their attributes. The EXT_OBJECTS view uses object data listed in the following table: Column name URL TYPE NAME DATE_BEGIN DATE_END DATE_MODIFIED DESCRIPTION Data type NVARCHAR NVARCHAR NVARCHAR DATETIME DATETIME DATETIME NVARCHAR Description Unique identifier for the object. Either a presentation, course, flv, swf, image, archive, meeting, curriculum, folder, or event. [. . . ]