Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

A system action is simply an action sequence that is configured to run either at system start time (i.e. when the application server starts) or session start time (i.e. when the user logs in). The output of a system action is available to other action sequences as input parameters. System actions are configured by adding the appropriate child elements to the <system-action> element in the pentaho.xml file.

------------------------- - what to do with this junk? -------------

Info
titleWhat is session and global scope?

TODO

...

Info
titleLet's Break it Down

Let's break it down a bit using the previous examples.

  • We make the output of the action sequence available to portlets by creating the XML element <org.pentaho.ui.portlet.PentahoHttpSession>.
  • We make the output of the action sequence available to servlets/jsps by creating the XML element <org.pentaho.core.session.PentahoHttpSession>.
  • We make the action sequence run at system start time and make output available in global scope by adding the scope="global" attribute to our element.
  • We make the action sequence run at session start time and make output available in session scope by adding the scope="session" attribute to our element.
  • We identify the name and location of our action sequence by adding samples/filters/setCompanyName.xaction as a child text node of our xml element.

...

Now you know how to configure a system action, but what might a system action look like that will assist in filtering data?controlling access to data?

Developing an Action Sequence to Run As a System Action

Info
titlePentaho Preconfigured Install

This code was developed with the Pentaho

...

Preconfigured Install, using the SampleData database that comes with the

...

Preconfigured Install.

...

In this example we'll develop an action sequence to generate an HTML report containing financial data for the current user's region. This suggests that when the user logs in, we need to identify the user's region, and store this information someplace that we can user later in our action sequence.
To identify the user's region, let's create a new action sequence in Eclipse using the action sequence editor.

...