...
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 | ||
|---|---|---|
| ||
TODO |
In addition, the output is available to portlets and/or Servlets/jsps.
(scope="global")
(scope="session").
(org.pentaho.ui.portlet.PentahoPortletSession)
(org.pentaho.core.session.PentahoHttpSession)
--------------------------------------------
...
Configuring System Actions
| Anchor |
|---|
...
|
The first step in configuring a system action is to locate and edit the pentaho.xml. In the Pentaho Preconfigured Install, the pentaho.xml file is located in the pentaho-demo/system folder.
...
In order for our getActualsForRegion action sequence to run successfully, we need to configure the userNameToRegion action sequence to run when the user logs in. To do this we need to modify the pentaho.xml file. The pentaho.xml file is located in the system folder of the pentaho-solutions folder of the Pentaho Preconfigured Install. You should recall that in the section
Configuring System Actions
#cnfg_sys_act
[ #cnfg_sys_act]
linke alias
Configuring #Configuring System Actions
I discussed adding this xml element:
...