Unified Task List Developer Pack

Transcription

1 Unified Task List Developer Pack About the Developer Pack The developer pack is provided to allow customization of the UTL set of portlets and deliver an easy mechanism of developing task processing portlets and dynamic portal page processing. There are 2 WEF ( WebSphere Experience Factory ) pkg files bundled into the developer package. Together they offer a start to finish business process solution for WebSphere Portal Server. 1. Unified Task List PKG file to add the Unified Task List portlet feature set to Web Experience Factory 2. Unified Task List Business Process Support PKG feature set exposing task processing portlets for use with the Unified Task List portlet and Process Server and dynamic portal page processing. There are also sample WEF models provided to show how to quickly and easily create human task processing Portlets for WebSphere Portal Server using WEF builders included in the Unified Task List catalog bundle. Developer Pack Prerequisites Runtime: WebSphere Process Server WebSphere Portal Server 7.x/8.x The Unified Task List Portlet for WebSphere Portal Server Download link : for portal 7.x action=editdocument&documentid=b83a591cd238d9aa ae752 Documentation: Development: WebSphere Integration Developer 6.1,6.2,7.0 (this is only required if you are using your own business processes for WebSphere Process Server.) WEF 8.0 (this is required if you plan on developing new task processing Portlets for custom business processes or customization to the UTL itself ) The Unified Task List Portlet for WebSphere Portal Server Download link: for portal 7.x, (Note: the UTL is packaged into portal 8.x.) action=editdocument&documentid=b83a591cd238d9aa ae752 Documentation: Copyright IBM Corporation, All Rights Reserved 1

2 Verifying the Developer Pack Contents About this task After downloading the Unified Task List Developer Pack you should verify that it contains the following files. 1. UnifiedTaskList.pkg Unified Task List portlet feature set 2. UnifiedTaskListBusinessProcessSupport.pkg Human Tasks, Business Processes and dynamic page processing ( Feature set ) 3. WebspherePortletFactoryArchiveGeneratorUpdateSite A plugin for WebSphere Integration Developer which can be used to export Business Process meta-data for use with the Human Task Processing Action builder to create task processing Portlets. 4. HRSupport.ear A support application for the sample HR business process for WebSphere Process Server. This must be installed before the HRMod.ear application file. 5. HRMod.ear The HR sample business process for WebSphere Process Server. 6. PA_SamplePortlets.war This is a sample war file generated in WebSphere Portlet Factory which contains two task processing Portlets for the sample HR business process. It also contains a sample Portlet for initiating the approve standard application human task in the HR business process. 7. SamplePortletsWPF.zip This Portlet Factory archive includes the required wsdl files for each Human Task in the HR business process and the Portlet Factory models used to create the sample task processing Portlets. There is also a wsdl file and a Portlet for starting an instance of the HR business process Human Task. 8. License.zip This archive contains the licence files for the Unified Task List Developer Package. Copyright IBM Corporation, All Rights Reserved 2

3 Importing the feature set(s) into WEF 1.Copy the 2 pkgs listed above into the packages folder of the WEF installation, for example \WEFactory8\Designer\FeatureSets\Web-App_8.0.0\Packages. 2.Restart the WEF application. 3.Create a new WEF project called unifiedtasklist 4.From the feature set page of the wizard add the Portal Accelerators, Dojo Extension - 1.x and Lotus Collaboration Extension 5.Complete the wizard. 6.Expand the newly created project. Access is now available to the complete source base. 7. Adding translated files to source path As seen directly above. Copyright IBM Corporation, All Rights Reserved 3

4 8. Add dependencies "AppServer/plugins/com.ibm.icu.jar" "AppServer/plugins/com.ibm.ws.portletcontainer.jar" "AppServer/plugins/com.ibm.ws.runtime.jar" "AppServer/plugins/org.eclipse.equinox.common_.jar" "AppServer/plugins/org.eclipse.equinox.registry.jar" "PortalServer/pzn/prereq.pzn/lib/pznquery.jar" "PortalServer/pzn/prereq.pzn/lib/pznresources.jar" "PortalServer/pzn/prereq.pzn/lib/pznruntime.jar" "PortalServer/base/wp.ac.api/shared/app/wp.ac.api.jar" "PortalServer/base/wp.auth.base/shared/app/wp.auth.base.jar" "PortalServer/base/wp.base/shared/app/wp.base.jar" "PortalServer/base/wp.cmd.base/shared/app/wp.cmd.base.jar" "PortalServer/base/wp.dynamicui.api/shared/app/wp.dynamicui.api.jar" "PortalServer/base/wp.engine.impl/shared/app/wp.engine.impl.jar" "PortalServer/base/wp.model.api/shared/app/wp.model.api.jar" "PortalServer/base/wp.model.controller.api/shared/app/wp.model.controller.api.jar" "PortalServer/base/wp.pe.api.standard/shared/app/wp.pe.api.standard.jar" "PortalServer/base/wp.portletservices.api/shared/app/wp.portletservices.api.standard.jar" "PortalServer/base/wp.processintegration/shared/app/wp.processintegration.jar" "PortalServer/base/wp.propertybroker.core.api/shared/app/wp.propertybroker.core.api.jar" "PortalServer/base/wp.propertybroker.standard.api/shared/app/wp.propertybroker.standard.api.jar" "PortalServer/base/wp.resolver/wp.resolver.api/shared/app/wp.resolver.api.jar" "PortalServer/base/wp.resolver/wp.resolver.json.api/shared/app/wp.resolver.json.api.jar" "PortalServer/base/wp.resolver/wp.resolver.json.impl/shared/app/wp.resolver.json.impl.jar" "PortalServer/base/wp.user.api/shared/app/wp.user.api.jar" "PortalServer/shared/app/tpir.jar"/> 9 Clean and build project Custom Builders that are now exposed Copyright IBM Corporation, All Rights Reserved 4

5 Customization Once the feature sets are added a developer can change any UTL component and leverage it for custom development, e.g. Create a new task provider for custom developed workflow engines Change the user interface to display tasks in maps Enrich the task list with business data, e.g. add custom attributes Leverage Portlet Factory based products for additional customisation's. Main components of the UTL The architecture of the UTL separates the user interface from the data access The UTL includes different Task Providers implementing the data access to a specific workflow system. The Task Dispatcher is responsible for aggregating tasks delivered by all task provider configured by the portlet administrator It leverages the Service Provider / Service Consumer concept of WEF. 1.Task providers Task providers are services that access backend systems to retrieve tasks. The task providers also use a WebSphere Experience Factory Transform builder to provide a uniform data set that displays in the Unified Task List user interface. You can create multiple task providers to aggregate tasks from several backend systems. 2. Task provider instances A task provider instance is based on a task provider and is specific to a certain back-end service They reside in the Task Provider Instance Registry (TPIR) and contain the parameters that you specify in task providers. 3.Task provider instance registry (TPIR ) 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 backend system and a unique ID to map the parameters to the appropriate task provider. The TPIR service resides in WebSphere Application Server and stores the task provider configurations in an XML variable. The TPIR service also provides a service to get and modify task provider instances. Copyright IBM Corporation, All Rights Reserved 5

6 4. Task dispatcher The task dispatcher acts as a link between the Unified Task List user interface and the task providers. When an action occurs in the user interface, the task dispatcher retrieves task provider instance configurations from the TPIR service and calls a Service Operation on the task providers. You can also configure the Unified Task List to use a cached task dispatcher if you do not want to access the backend systems each time an action occurs in the user interface. The cached task dispatcher uses dynamic caching in WebSphere Application Server to store and retrieve tasks. 5.Task handler Task handlers define what the Unified Task List does when an end user selects a task to advance a workflow. The task handlers determine how the Unified Task List connects to the tasks that the end user must complete. You can configure task handlers to connect the Unified Task List to tasks in the following ways: 1. Use the property broker of Portal to open a portlet where the end user can complete the task. The portlet that opens can reside on the same portal page as the unified task list portlet or a different portal page. 2. Use dynamic portal pages, or task pages, to open task processing and task supporting portlets. 3. Provide an external URL that launches a Web application Working with the default task providers By default the Unified Task List provides several task providers that let you retrieve tasks and workflow actions from various backend systems. The following steps provide instructions for accessing and working with the default task providers. Navigate to the following directory in the Unified Task List project: models/accelerators/utl/services/taskprovider. The following task providers display: DemoTaskProvider.model Provides sample data that you can use to test the UnifiedTask List. The sample data for this task provider is located in the following XML file: wpf_project/webcontent/accelerators/utl/demotaskprovider/sampletasklist.xml. You can open this file and customize the information in any of the XML elements. Copyright IBM Corporation, All Rights Reserved 6

7 IBMWebSphereProcessServer.model Connects to IBM WebSphere Process Server to retrieve tasks Also if using BPM advanced and running BPEL tasks. LombardiTaskProvider.model Connects to WebSphere Lombardi Edition to retrieve tasks IBMWebSphereProcessServer.7003model Connects to IBM WebSphere Process Server 7 to retrieve tasks. Using the Query table Api. Lombardi75TaskProvider.model Connects to IBM BPM server to retrieve tasks. Running BPMN tasks. Adding custom task providers Task providers are services that access and retrieve tasks from backend systems. Task providers contain several builder calls that connect to the backend system, transform the data from the backend system into a result variable, specify an action and provide a service operation. At run time, the task dispatcher calls the appropriate service operation in the task providers when an action occurs, such a user selecting a task to get the details. The service operation then calls the action to get the task details. You can create and add custom task providers to connect to different backend systems and perform different actions with the data. As there are numerous configurations,providing details on creating custom task providers to cover every possible scenario is beyond the scope of this documentation. However, this topic provides instructions for creating a simple model and information about which builders you need to add to your model and why these builders are necessary. The following steps provide instructions to guide you through the process of adding custom task providers. Create an empty model in the Unified Task List project. 1. Select New > WebSphere Portlet Factory Model. 2. Select the project that contains the Unified Task List feature set and click Next. 3. Select Factory Starter Models > Empty and click Next. 4. Select the following folder as the save location for the model: wpf_project/models/accelerators/utl/services/taskprovider. 5.Enter a name for the model and click Finish. Open the following model: 1.wpf_project/models/accelerators/utl/services/TaskProviderInterface.model. (Several builder calls display in the model outline.) 2.Select and copy all the builder calls in TaskProviderInterface.model. 3.Paste the builder calls from TaskProviderInterface.model into the model you created. Add an appropriate Data Integration builder to your model and specify the builder inputs. A Data Integration builder,such as the SQL Call builder, retrieves data from a backend system and creates a result variable. 4. Add a Transform builder to your model and specify the builder inputs. The Transform builder consumes the result variable that the Data Integration builder creates. The Transform builder creates Copyright IBM Corporation, All Rights Reserved 7

8 an XML variable that the Unified Task List receives to display a task or activity in the user interface. 5.Open the Action List builders that you copied into your model and add the XML variable from the Transform builder. The Action List builders contain the actions that the Service Operation builders call. For example, the gettasklist action retrieves a list of tasks from the backend system when the get Task List operation is called. 6.Open the Service Operation builders that you copied into your model and specify a value in the Action to Call field. The value that you specify corresponds to the Action List builder that contains the action you want to call. 7.Specify other builder inputs as appropriate and save your model. 8. Add your model to the list of task provider instances. When you create a new task provider, you must add it to the taskprovider instance list. The task provider instance list is saved in the Task Provider Instance Registry (TPIR). Adding your model to the list of task provider instances makes it available as a taskprovider you can select from the user interface. Add the following source folder to your build path: wpf_project/webcontent/pii/web-inf/work/source_nl. 1.Right click the project name in WebSphere Experience Factory Designer. 2.Select Build Path > Configure Build Path. 3.In the Java Build Path window, select the Source tab. 4.Select Add Folder, add the source folder to the build path, and click OK. Specify a resource key for your task provider in the following file: TaskProviderInstancesList.properties. 1. Locate and expand the following file in the Java Resources folder of your project:com.ibm.accelerators.utl.nl.tasklist_configure. 2.Locate and open the following file:taskproviderinstanceslist.properties. 3.Specify a resource key for your task provider in thefollowing section: # task provider types. For example,taskprovider.unique_name=task_provider_name. Tip: The value that you specify fortask_provider_name displays in the list of available task provider instances in the Unified Task List configuration view. 4.Save and close TaskProviderInstancesList.properties. 5.Locate and open to the following file in your workspace:wpf_project/webcontent/accelerators/utl/rdd/taskproviderinstanceslist.xml. 6.Add a look up entry under TaskProviderNamesLT for your model. For example, <entry> <value>accelerators/utl/services/taskprovider/model_name.model </value> <nameresource_key="taskprovider.unique_name"></name> </entry> 7.Save and close the model. Creating input forms for context variables When WebSphere Portal administrators add new task provider instances to the Unified Task List at run time, the administrators must typically provide several context variables,or connection parameters, for each task provider instance. You can create custom input forms and specify which context variables WebSphere Portal administrators must provide for a given task provider, such as a port number or user ID. The following steps provide instructions for creating input forms for context variables. 1. Create a resource bundle that contains the localized strings you want to display in the input form. 2. Create a Data Definition file. 3. Create a new model for the input form. 1. Select File > New > WebSphere Portlet Factory Model. 2. Select the project and click Next. 3. Select Factory Starter Models > Empty and click Next. 4. Select the following folder as the save location for the model: Copyright IBM Corporation, All Rights Reserved 8

9 wpf_project/models/accelerators/utl/ui/configure. 5. Enter a name for the model and click Finish. The model that you create is included in the following model at run time:tasklistcustomizer_configure_taskproviderinstanceslist.model. 4. Add a Rich Data Definition builder to the model and specify the location of the Data Definition file you created. 5. Add a Schema builder to the model and specify the schema for the input form. The schema controls the sequence of context variables that display in the user interface. 6. Import the model that you created into TaskListCustomizer_Configure_TaskProviderInstancesList.model. 1. Navigate to wpf_project/models/accelerators/utl/ui/configure \TaskListCustomizer_Configure_TaskProviderInstancesList.model. 2. Open TaskListCustomizer_Configure_TaskProviderInstancesList.model. 3. Add an Imported Model builder to the model. 4. Specify a name for the builder call and the path to the model you want to import. 5. Save and close the model. Customizing the user interface The Unified Task List portlet that you deploy to WebSphere Portal has three sections in the user interface: the task list menu, the message area, and the task list table. The task list menu displays on the left side of the portlet and contains the filters that segregate tasks from different backend systems. The task list menus also contains the drag and drop menu that lets users claim and release tasks from the task list table. The message area displays at the top right of the portlet and contains user messages, such as error and status messages. The task list table displays beneath the message area and is a table with several columns that contain information about the tasks that users must complete. Customizing the user interface involves working with models in WebSphere Portlet Factory. The settings for the Unified Task List user interface arecontained in three models. These models correspond to the three sections that make up the user interface: the tasklist menu, the message area, and the task list table. In the models you can specify custom HTML pages, text, styleclasses, and images to localize and change the appearance of the Unified Task List. 1.Open the WebSphere Portlet Factory project that contains the Unified Task List feature set. 2. Navigate to the following directory: wpf_project/models/accelerator/utl/ui/view. The following models display: TaskDetailsContainer.model Displays extra information about tasks. TaskList.model Imports the following three models to create the user interface when you build the portlet Web Archive (WAR):TaskListMenu.model, TaskListMessageArea.model, and TaskListTable.model. TaskList.model also contains profiling settings at a high-level. For example, TaskList.model contains profiling settings that determine which sections of the deployed portlet display to the user. TaskListMenu.model Provides the user interface for the task list menu in the Unified Task List portlet. TaskListMenu.model also contains text,images, HTML pages, and style classes that you can change to customize the user interface. TaskListMessageArea.model Provides the message area in the Unified Task Listportlet. TaskListMessageArea.model also contains text, images,html pages, and style classes that you can change to customize the user interface. TaskListTable.model Provides the task list table in the Unified Task List portlet.tasklisttable.model also contains text, images, HTML pages,and style classes that you can change to customize the user inter face. 3. Open one of the preceding models and work with thebuilder inputs to customize the user interface. To specify custom HTML pages, images, or Cascading StyleSheets (CSS), ensure your files are located at the WebSpherePortlet Factory servable root directory. For example,wpf_project/webcontent/accelerators. The text that displays in the user interface is contained inresource bundles. To change the text in the user interface, openthe appropriate resource bundle and make the requiredchanges. Resource bundles are located in the Java Resourcesfolder of your project in the following folder WebContent/pii/WEB-INF/work/source_nl Copyright IBM Corporation, All Rights Reserved 9

10 Tip: To add WebContent/pii/WEB-INF/work/source_nl to you rproject, do the following: 1. Right click the project name in WebSphere PortletFactory Designer. 2. Select Build Path > Configure Build Path. 3. In the Java Build Path window, select the Source tab. 4. Select Add Folder, add the source folder to the buildpath, and click OK. Adding columns to display custom attributes in the task list table You can add columns to the task list table in the Unified Task List if you want to display custom attributes for tasks. 1. Locate and open the following file: wpf_project/webcontent/accelerators/utl/schemas/tasklist.xsd. 2. Add a new element and specify the column name and type.for example, <element name="example_column" type="string"></element> 3. Save and close TaskList.xsd. 4. Locate and open the following file: wpf_project/webcontent/accelerators/utl/rdd/tasklist.xml. 5. Add a new data definition for the column. For example, <DataDefinition name="example_column> <Labelresource_key="example_column">example_column<Label> <Required>true</Required> <DataType>string</DataType> </DataDefinition> 6. Map the column to the attribute you want to display in theunified Task List. 1. Open the task provider models. 2. Open the Transform builder call. 3. In the Child Node Mappings section, specify a value for the source node field that corresponds to the column you created in the target node field. 7. Rebuild your project. 8. Open the Data Column Modifier builder call in TaskListTable.model. The column you created should display inthe list of columns in the Settings for Add and Delete Row Operations section. Copyright IBM Corporation, All Rights Reserved 10

11 Property broker events for portlets The Unified Task List communicates with portlets through property broker events. When portal users select a task to open in the Unified Task List portlet, the Unified Task List fires property broker events to task processing portlets. If you plan to develop custom portlets to retrieve tasks and provide tasks through the Unified Task List, you must configure that portlet to receive and parse the property broker events from the Unified Task List. This topic provides information about the property broker event that the Unified Task List uses to communicate with other portlets. Review the information in this topic if you plan to create custom portlets that communicate with the Unified Task List. If you plan to design task processing portlets in WebSphere Portlet Factory, add a Cooperative Portlet Target builder to your portlet model along with any other appropriate builders. The Cooperative Portlet Target builder catches the property brokerevent that the Unified Task List fires. This event sends a string in JavaScript Object Notation (JSON) format as the argument. This JSON string has the following structure: "{"task":id,"task_provider_instance":"id"}" When portlets receive the property broker events from the Unified Task List, the portlets parse the JSON string for the taskprovider instance ID. The task provider instance ID lets portlets determine which backend system the task corresponds to. For example, your site can have several portlets that process tasks from several different backend systems. The Unified Task List fires property broker events to all the different task processing portlets on your site. However, the portlets only need to retrieve task details if the event contains an appropriate task providerinstance ID. Copyright IBM Corporation, All Rights Reserved 11

12 End to end sample for business process transaction Inside the Developer Pack you will find an end to end sample for business process transactions in WebSphere Portal Server using WebSphere Process Server as the business process engine. There are also sample WebSphere Experience Factory models provided to show how to quickly and easily create human task processing Portlets for WebSphere Portal Server using Portlet Factory builders included in the Unified Task List catalog bundle. Retrieving the HTM SOAP endpoint from your WebSphere Process Server About this task The following instructions show you how to retrieve the HTM SOAP endpoint from your Process Server. The HTM SOAP endpoint is required in the default_wps_server.properties file found in the WebContent/config/wps_config directory of the sample Portlet Factory project. Retrieving the HTM SOAP endpoint from your WebSphere Process Server 1.Open your Process Server Administrative Console, e.g. 2.Select Applications - Applications Types - WebSphere enterprise applications. 3.From the list of enterprise applications select the one named TaskContainer 4.On the Configuration tab in the Web Services Properties section select Publish WSDL files. 5.Select the link named TaskContainer WSDLFiles.zip and save the archive to your local file system. 6.Open the archive with an archive application 7.Open the following file within the archive TaskContainer.ear\h.jar\META- INF\wsdl\com\ibm\task\api\sca\HTMWS.wsdl 8.Scroll to the bottom of the file to the element named soap:address 9.Copy the location value to the WebContent/WEB- INF/config/wps_config/default_wps_server.properties file e.g. /sca/com/ibm/task/api/sca/htmws What to do next Update the PA_SamplePortlets.war file with the HTM SOAP endpoint from your Process Server Updating the PA_SamplePortlets.war file with the HTM SOAP endpoint Things to do before you start this task Retrieve the HTM SOAP endpoint from your WebSphere Process Server About this task This section describes how to update the PA_SamplePortlets war file with the HTM SOAP endpoint from your Process Server. Updating the Sample Portlets war file with the HTM SOAP endpoint from your Process Server 1.Using an archive program open the PA_SamplePortlets.war file included in the Developer Package download. 2.Locate the file WebContent/WEB-INF/config/wps_config/default_wps_server.properties 3.Open the file default_wps_server.properties and update the property HTM_SOAP_Endpoint with the HTM SOAP endpoint location value retrieved in the previous step. 4.Save your changes to the file and close it. 5.If prompted choose to save the changes to the archive war file. Copyright IBM Corporation, All Rights Reserved 12

13 Creating a new Task Provider Instance in the Unified Task List This task includes the steps required to create a Process Server Query Table API Task Provider Instance for the Unified Task List. For more information on the Unified Task List you can view the wiki document here: 1.Open the Unified Task List page 2.Open the portlet menu and choose Configure 3.Click the link for Task Provider Instances 4.Click Add, The Task Provider Instances page shows. 5.Select IBM WebSphere Process Server7 (Task Query Table API) from the dropdown 6.Type in a name for the Task Provider Instance 7.Check the Enable checkbox 8.Click next 9.On this page give change the SOAP Endpoint settings from the default to 10.Click Apply on the Provider Instances page and again on the main Configure page. 11.Click Ok. What to do next Install the Sample Business Process and Task Processing Portlets. Installing the Sample Business Process and Task Processing Portlets Update the Unified Task List Portlet war file with the SOAP endpoint from your Process Server About this task In this task you will install the sample HR business process to Process Server and the sample task processing Portlets to Portal Server. Installing the sample business process and task processing Portlets First install the HRSupport.ear on WebSphere Process Server accepting the default settings during the install. When it is installed, start it. 1.Open the Admin Console of WebSphere Process Server and login: 2.Select Applications - Application Types - WebSphere enterprise applications. 3.Select Install and Browse. Browse to the directory where you expanded the Developer Package archive and select the HRSupport.ear file. 4.Click Next, if prompted select Fast Path as the option to install the application. 5.On the page Step 1: Select installation options, accept the defaults and click Next. 6.On the page Step 2: Map modules to servers, ensure the modules for the application are assigned to server1. If not, select each module with server1 highlighted and click Apply. 7.Click Next 8.On the last page Step 3: Summary, review the settings and click Finish. 9.When the Application has finished installing select Save directly to master configuration. 10.On the Enterprise Applications page select the HRSupport and click Start. Once started the application has been successfully installed. Copyright IBM Corporation, All Rights Reserved 13

14 Next create the sample staff plugin configuration in your Process Server. You have to create this people directory configuration in your Process Server if it isn't already there: 1.Log into the Process Server admin console Select Resources - People directory provider 3.In the table of people directory providers select User Registry People Directory Provider 4.Under additional properties select People directory configuration 5.Select New 6.Browse to the following file in your process server installation, select it and click Next:$ {WBI_INSTALL_ROOT}/ProcessChoreographer/Staff/UserRegistryTransformation.xsl On a Windows OS the variable ${WBI_INSTALL_ROOT} resolves to C:\WPS\WebSphere\ProcServer 7.Enter a Name such as wpswmmconfiguration and Description 8.In the JNDI Name field enter bpe/staff/wpswmmconfiguration 9.Click Apply 10.Now you should be able to install and start the sample HR application. Finally Install the HRMod.ear business process on your Process Server and start it. Repeat the instructions for the HRSupport.ear, this time using the HRMod.ear business process. 1.Deploy the Unified Task List war file to your Portal Server. 2.Deploy the war file PA_SamplePortlets.war to your Portal Server. 3.Create a page, give it the unique name wps.utl and configure it as a Dynamic Page Extension Node using the following command:configengine.bat action-enable-page-as-extension-nodewp.dynamicui.config -DPageUniqueName=wps.utlNote: All three of the following Portlets can be found in the sample war file PA_SamplePortlets.war. 4.Create a page, give it the unique name com.ibm.standardapproval and add the Portlet titled 'Approve Standard Application' to it. This page should only be accessed as a dynamic page. 5.Create another page, give it the unique name com.ibm.foureye and add the Portlet titled 'Four Eye Approval' to it. This page should only be accessed as a dynamic page. 6.Finally create a third page and place the Portlet titled Start Task on it. As the title suggests this Portlet will be used to start the HR standard approval business process. This page can be accessed on a dynamic page or in the normal way. 7.Go to the page with the UTL on it and open the configure view by selecting it from the Portlet menu. 8.In the menu select Task Provider Instances and create a new Task Provider Instance for your Process Server. Next you have to configure the task handling for the Human Tasks surfaced in the UTL. You can create the configurations using the following two sample configurations as a guide: Copyright IBM Corporation, All Rights Reserved 14

15 What to do next Complete the next section which covers how to process the tasks using the sample Portlets and UTL in Portal Server. Start to Finish Business Process Completion on WebSphere Portal Server Things to do before you start this task Installing the Sample Business Process and Task Processing Portlets. About this task This task will take you through the steps you need to take to complete the sample business process using the Sample Portlets provided and the Unified Task List. It also includes a figure of the business process flow. Copyright IBM Corporation, All Rights Reserved 15

16 Business process completion from start to finish 1.Open the page containing the Start Task Portlet, fill in the details required in all fields and click Complete. 2.Next open the page containing the Unified Task List Portlet. 3.You should see a new Approve Standard Application task when you click Refresh. 4Select the checkbox beside the new task and then click Claim. 5.The title of the task is now a clickable link. Click it to lauch a dynamic page. 6.The Approve Standard Application dynamic page should be launched. 7.Complete it by clicking the Complete button. The dynamic page should close and return to the Unified Task List page. 8.Click the Refresh button in the UTL, and you should see a new Four Eye Approval task in the list of tasks retrieved from Process Server. 9.Carry out the same steps 4 -> 7 on the Four Eye Approval task to complete the sample business process. Figure 3. Business Process Implementation. Copyright IBM Corporation, All Rights Reserved 16

17 What to do next Develop custom business processes and create task processing Portlets for them using the Unified Task List Business Process Support package for WebSphere Portlet Factory. Getting Started with Task Processing Portlet Development Requires WebSphere Experience factory version 8.0 Retrieve the HTM SOAP endpoint from your Process Server. About this task This task explains how to get started with task processing Portlets using the Unified Task List Business Process Support package for WebSphere Experience Factory and the sample task processing Portlets provided in the WebSphere Portlet Factory archive included in the Unified Task List Developer catalog bundle. 1.Copy the Unified Task List Business Process Support package to the Packages directory in your WEF installation. e.g C:\IBM\PortletFactory8.0\Designer\FeatureSets\Web-App_8.0.0\Packages 2.Restart WEF. Create a new WebSphere Portlet Factory project and include the following selected Feature Sets 1.Next import the WebSphere Portlet Factory archive from the UTL developer package download bundle. 2.Right Select the newly created WPF project and select import - WebSphere Portlet Factory Archive 3.Browse to the directory containing the developer package and select the file named SamplePortletsWPF.zip. 4.Select the root directory of the archive and ensure 'SamplePortlets/WebContent' is set as the directory to copy to. Copyright IBM Corporation, All Rights Reserved 17

18 5.Click Finish. 6.Now you are ready to build the WAR file for deployment to Portal Server. 7.Right Select the project and choose Export - WebSphere Portlet Factory Portlet WAR 8.Ensure the Portlet API is set to Java Portlet Standard 2.0 and click Finish. 9.The war file has been generated and is now ready to be imported into WebSphere Portal Server. The sample WebSphere Portlet Factory Models used to create the task processing Portlets for the developer package can be found in the models directory of the newly created Portlet Factory project. They can be used to understand quickly how to use the Business Process Support builders provided in the Unified Task List Catalog bundle to build task processing Portlets. Copyright IBM Corporation, All Rights Reserved 18

19 Useful links er.html Copyright IBM Corporation, All Rights Reserved Copyright IBM Corporation, All Rights Reserved 19