Page Comparison

...

For another example, assume your action sequence is called global-department-list.xaction, it exists in the repository under bi-developers/secure, you want the action sequence to run when the system starts up with the output placed in global scope, and you want the output of the action sequence to be available in a portlet, then your addition to sessionStartupActions.xml would look like this:

<bean class="org.pentaho.platform.engine.core.system.SessionStartupAction">
  <property name="sessionType" value="org.pentaho.platform.webengine.security.portalsession.PentahoPortletSessionTrustedSystemStartupSession"/>
  <property name="actionPath" value="bi-developers/secure/global-department-list.xaction"/>
  <property name="actionOutputScope" value="global"/>
</bean>

...

• We make the output of the action sequence available to portlets by specifying a sessionType of org.pentaho.platform.web.portal.PentahoPortletSession.
• We make the output of the action sequence available to servlets/jsps by specifying a sessionType of org.pentaho.platform.web.http.session.PentahoHttpSession.
• We make the action sequence run at system start time and make output available in global scope by specifying an actionOutputScope of global and specify a sessionType of org.pentaho.platform.engine.security.session.TrustedSystemStartupSession.
• We make the action sequence run at session start time and make output available in session scope by specifying an actionOutputScope of session.
• We identify the name and location of our action sequence by specifying actionPath.

...