...
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 |
|---|
| title | What is session and global scope? |
|---|
|
TODO |
...
| Code Block |
|---|
<org.pentaho.core.session.PentahoHttpSession scope="global">
samples/filters/setCompanyName.xaction
</org.pentaho.core.session.PentahoHttpSession>
|
| Info |
|---|
|
Let's break it down a bit using the previous exampleexamples. - 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.
|
...