Overview of Page Execution and Event Processing

This section provides a detailed description of how MicroStrategy Web products handle page execution, from the initial user click to the final display of the resulting page. To perform efficient, effective customizations, you need to understand the standard page execution flow and know which MicroStrategy Web components are customizable at each step of the execution. The key to achieving high-quality customizations is to make the right change to the right component at the right point in the flow.

 

The diagram below illustrates a high-level perspective of the various phases of page execution and the major steps that take place within each phase. The steps where customization can take place are outlined in bold and include the main components that you would customize at that step in the flow. For example, the first major step in the Create Page phase of page execution is Select page, and the major component that is customized at that step is the events definition file.

 

A brief overview of each step follows the diagram, while a more detailed description can be found by clicking any of the steps in the diagram.

 

 

The overall page execution flow in MicroStrategy Web products is controlled by a single component, the Controller, while the page itself acts primarily as a container for the components (MicroStrategy Web Beans) that gather the data and display it to the user. In general, page execution follows the same execution flow for all pages. This is different from versions of the product prior to 7.3, in which each page had its own execution cycle. Centralizing the execution of page execution makes it easier for you to customize, debug, and upgrade.

 

When you plan and perform customizations, you need to understand what is taking place at each step in the page execution flow, what types of customizations are required (XML configuration changes, JSP/ASP.NET programming, or Java programming), and what types of information are available to help you troubleshoot problems. The detailed explanation for each step in the flow provides all of this information, as well as links to related topics and relevant customization scenarios.

 

 

 

 

Customizations performed at this step involve customizing the way the session is validated. This includes customizing the External Security Module.

 

 

 

Customizations performed at this step involve adding custom functionality and actions. They include making changes to event definitions, event handlers, and/or event maps.

 

 

 

 

 

Customizations performed at this step involve modifying the HTML output created when beans on the target page are transformed. They include one or more of the following actions: making changes to the Style Catalog Configuration file (the XML file that holds the styles used to render the beans on the target page), creating custom transform files (Java files), and/ or creating custom layout definition files (XML files). Transforms, transform parameters, and layout definition files are associated through a style definition.

 

 

Customizations performed at this step involve modifying the font, typeface, etc. that are used on the page that will be displayed to the user. They include making changes to the CSS (Cascading Style Sheet) files that will be used when the target page is rendered.