Roadmap - Configuring the Worklist Service for WebCenter Spaces

22-6 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter topology contains several BPEL servers running various workflow types, such as Human Resource and General Ledger servers. ■ It is mandated that the BPEL connections are unique URLs. If this is not the case, then duplicate queries to the same server are created.

22.3 BPEL Server Prerequisites

Consider the following to ensure smooth functioning of the Worklists service: ■ Pages that include Worklists task flows must be secured through ADF security. ■ The Worklists service must be configured to use an Oracle SOA Suite BPEL server that is accessible through the BPEL Worklists application. The URL is in the following format: http:host:portintegrationworklistapp If the Worklist service is not running in the same domain as the Oracle SOA Suite BPEL server, the identity store LDAP should be either shared recommended or contain identical user names. ■ Clocks on the Worklists services managed server and the Oracle SOA Suite BPELs managed server must be synchronized such that the SAML authentication condition, NotBefore, which checks the freshness of the assertion, is not breached. ■ No configuration-related exceptions must exist. Use the WLST command listWorklistConnections to display the configured connections and validate the connection details. After listing the connections, validate them using the URL property appended with integrationworklistapp. Hence, verify that http:host:portintegrationworklistapp can access the BPEL Worklist application. ■ If the Oracle SOA Suite BPELs managed server is configured to use an identity store and that store does not contain BPMWorkflowAdmin, weblogic by default, then the BPMWorkflowAdmin user must be configured, as described in Section 22.5.2.2, Shared User Directory Does Not Include the weblogic User. ■ The wsm-pm application must be running on both the Worklists services and Oracle SOA Suites BPEL servers managed servers without any issues. This can be validated through the URL: http:host:portwsm-pmvalidator For information on how to resolve BPEL server issues, see Section 22.5, Troubleshooting Issues with Worklists. This section includes the following subsections: ■ Section 22.3.1, BPEL Server - Installation and Configuration ■ Section 22.3.2, BPEL Server - Security Considerations ■ Section 22.3.3, BPEL Server - Limitations in WebCenter

22.3.1 BPEL Server - Installation and Configuration

The Worklist service relies on the Oracle BPEL Process Manager BPEL server, which is included with Oracle SOA Suite. Managing the Worklist Service 22-7 To work with the Worklist service, you must install Oracle SOA Suite. For information about how to install Oracle SOA Suite, see the Oracle Fusion Middleware Installation Guide for Oracle SOA Suite and Oracle Business Process Management Suite. After installing Oracle SOA Suite, you can integrate the Worklist service into your WebCenter applications by setting up connections to the BPEL server.

22.3.2 BPEL Server - Security Considerations

The Worklist service displays tasks for the currently authenticated user. For WebCenter users to store and retrieve tasks on an Oracle SOA Suite BPEL server, their user names must either exist in a shared user directory LDAP, or be set up similarly on both the WebCenter application and the BPEL Server. For example, if the user rsmith wants to use the Worklist service to store and retrieve tasks from the BPEL server, you must ensure that the user rsmith exists on both the BPEL server and within your application. To access BPEL task details from the WebCenter Worklist component, without incurring additional login prompts, WebCenter and Oracle SOA Suite servers must be configured to a shared Oracle Single Sign-On server. For more information, see Section 30.2, Configuring Oracle Access Manager OAM and Section 30.3, Configuring Oracle Single Sign-On OSSO. For a secure connection you can optionally configure WS-Security between SOA and WebCenter Spaces. For information, see Chapter 32, Configuring WS-Security.

22.3.3 BPEL Server - Limitations in WebCenter

Worklist task flows function inside authenticated pages only. If Worklist task flows are placed on unsecured pages, that is public pages that are not navigated to from an application on which the user has logged in, the warning message You must log in to view Worklist content. is displayed. This is done to ensure that a session for the current users is available to determine which users tasks are to be queried.

22.4 Setting Up Worklist Connections

This section includes the following subsections: ■ Section 22.4.1, What You Should Know About Worklist Connections ■ Section 22.4.2, Registering Worklist Connections ■ Section 22.4.3, Activating a Worklist Connection ■ Section 22.4.4, Modifying Worklist Connection Details ■ Section 22.4.5, Deleting Worklist Connections

22.4.1 What You Should Know About Worklist Connections

The Worklist service enables WebCenter applications to show authenticated users a list of BPEL worklist items currently assigned to them. BPEL worklist items are open BPEL tasks from one or more BPEL worklist repositories. A connection to every BPEL server that delivers worklist items is required. Multiple worklist connections are allowed so that WebCenter users can monitor and manage assignments and notifications from a range of BPEL servers.