This is a portlet that I've had cause to use in the past, so I went straight to the Catalog to download it: -
Description: The IBM WebSphere Portal Unified Task List Portlet version 5.0 for WebSphere Portal 7.0 aggregates tasks and activities from multiple systems into a single user interface. WebSphere Portal 7.0 users access the Unified Task List portlet to view all tasks relevant to them. They can then complete these tasks using task processing portlets created with the included Unified Task List Business Process Support package for Web Experience Factory. The Unified Task List portlet in this release contains a task provider for WebSphere Process Server 6, WebSphere Process Server 7.0.0.4, IBM WebSphere Lombardi Edition 7.2, IBM Business Process Manager 7.5 and 7.5.1. Also Included are two Coach portlets for Lombardi and Business Process Manager Coach processing in Portal Server.
However, having noticed that it only listed WebSphere Portal 7, I asked a colleague when the version for WebSphere Portal 8 would be released.
Imagine my surprise when she told me that it's shipped as a component with WP8, so it's already there in the box :-)
She also kindly drew my attention to the WP8 documentation that covers UTL: -
Review concepts about the Unified Task List portlet to understand the different elements.
Task providers are services that access back-end systems to retrieve tasks. The task providers also use a Web Experience Factory Transform builder to provide a uniform data set that display in the Unified Task List user interface.
Task provider instances are services that access back-end systems to retrieve tasks. Task provider instances reside in the Task Provider Instance Registry (TPIR) and contain the parameters that you specify in task providers.
The Task Provider Instance Registry (TPIR) contains task provider instance configurations. A task provider instance configuration contains a set of parameters required to connect to a back-end system and a unique ID to map the parameters to the appropriate task provider. The Task Provider Instance Registry service resides in WebSphere Application Server and stores the task provider configurations in an XML variable. The Task Provider Instance Registry service also provides a service to get and modify task provider instances.
The task dispatcher acts as a link between the Unified Task List portlet and the task providers. When an action occurs in the portlet, the task dispatcher retrieves task provider instance configurations from the task provider instance registry service and calls a getTaskList service operation on each task provider instance configuration.
Task handlers define what the Unified Task List portlet does when users select a task to advance a workflow. The task handlers determine how the Unified Task List portlet connects to the tasks that the users must complete.
Task providers
Task providers are services that access back-end systems to retrieve tasks. The task providers also use a Web Experience Factory Transform builder to provide a uniform data set that display in the Unified Task List user interface.
Task provider instance
Task provider instances are services that access back-end systems to retrieve tasks. Task provider instances reside in the Task Provider Instance Registry (TPIR) and contain the parameters that you specify in task providers.
Task Provider Instance Registry
The Task Provider Instance Registry (TPIR) contains task provider instance configurations. A task provider instance configuration contains a set of parameters required to connect to a back-end system and a unique ID to map the parameters to the appropriate task provider. The Task Provider Instance Registry service resides in WebSphere Application Server and stores the task provider configurations in an XML variable. The Task Provider Instance Registry service also provides a service to get and modify task provider instances.
Task dispatcher
The task dispatcher acts as a link between the Unified Task List portlet and the task providers. When an action occurs in the portlet, the task dispatcher retrieves task provider instance configurations from the task provider instance registry service and calls a getTaskList service operation on each task provider instance configuration.
Task handler
Task handlers define what the Unified Task List portlet does when users select a task to advance a workflow. The task handlers determine how the Unified Task List portlet connects to the tasks that the users must complete.
So, there you have it, UTL is now an integral part of WP8, which is nice :-)
No comments:
Post a Comment