Application post-processing options

The key to building virtual applications is the addition of postprocessing functions or filters to the application’s applications. Post-processing functions can either transform an application’s content (for example, render the content as a chart), or create events For example, you can transform an application’s content into a chart or you can create events that are triggered when a user accesses an application’s content. You can add more than one post-processing function to handle an application’s content and configure the order in which the postprocessing occurs. When you use multiple postprocessing functions, each function operates on the output of the previous function—similar to a Pipes and Filter design.

Pipes and Filters is a design architecture where the components are known as filters and the connectors are the pipes. Filters read input data, perform some computation or transformation on the data, and produce output data. Pipes serve as conduits for the data streams, passing outputs from one filter to the inputs of another filter.

The post-processing options are available by right-clicking an application in the Application Builder left pane:

Define Events – launches an Event Definition wizard. See“Defining broadcast events” and “Defining events”.

Define Listeners – launches a Listener Definition wizard. See “Defining listeners”.

Create Chart – lets you chart an application’s structured content. See “Creating charts”.

Form Parser – lets you process form input and define which form parameters should be event default values or listeners for events from other sources. See “Adding form processing”.

Create JSP Filter – lets you write custom code to process application content. See “Adding a JSP filter”.

Text Processor – launches a text processor wizard that lets you define an event to occur when the user clicks on selected text. See “Processing text to trigger events”.

Order Post Processing – lets you sequence an application’s postprocessing options at anytime. See “Ordering filters”.

Invisible Status – lets you hide a specific application from the end user. See “Invisible status”.

All available post-processing modules are configured in the uwp.xml configuration file, which is located in %JAGUAR%\Repository\WebApplication\onepage\fw\properties if you are using EAServer, and %SYBASE%\UnwiredAccelerator70\tomcat\webapps\onepage\fw\properties if you are using Tomcat.

To add additional post-processing modules, use this interface:

</ApplicationWizards> <PortletContentPostProcesserFilters> <FilterDef name="jspfilter" class="com.onepage.fw.uwp.apps.jspfilter.UWPJSPFilterApp" multiple_occurance_allowed="true" use_app_object="true" desc="This is used to allow JSP code to operate on portlet content" /> <FilterDef name="charts" class="com.onepage.fw.uwp.apps.charts.UWPChartsApp" multiple_occurance_allowed="true" use_app_object="true" desc="This is used to allow JSP code to operate on portlet content" /> <FilterDef name="formparser" class="com.onepage.fw.uwp.apps.formparser.UWPFormParserApp" multiple_occurance_allowed="true" use_app_object="true" desc="This is used to allow JSP code to operate on portlet content" /> <FilterDef name="clickacross" class="com.onepage.fw.uwp.apps.clickacross.UWPClickAcrossApp" multiple_occurance_allowed="true" use_app_object="true" desc="This is used to allow JSP code to operate on portlet content" /> <FilterDef name="clickacross-text" class="com.onepage.fw.uwp.apps.textprocessor.UWPTextProcessorApp" multiple_occurance_allowed="true" use_app_object="true" desc="This is used to allow JSP code to operate on portlet content" /> <FilterDef name="listener" class="com.onepage.fw.uwp.apps.clickacross.UWPClickAcrossApp" multiple_occurance_allowed="true" use_app_object="true" desc="This is used to allow JSP code to operate on portlet content" /> </PortletContentPostProcesserFilters> </Framework>

There is a method in the UWPManager getPostProcessingFilters that returns a list of configured filters.