Always use Fusion Middleware Control or WLST command-line tool to review and configure back-end servers for WebCenter Portal. Any changes that you make to WebCenter Portal post-deployment are stored in MDS metadata store as customizations. See Oracle WebCenter Portal Configuration Considerations.
Changes that you make to the SOA connection through Fusion Middleware Control or using WLST are not dynamic, so you must restart the managed server on which WebCenter Portal is deployed for your changes to take effect. See Starting and Stopping Managed Servers for WebCenter Portal Application Deployments.
This chapter includes the following topics:
To perform the tasks in this chapter, you must be granted the WebLogic Server
Admin role through the Oracle WebLogic Server Administration Console and the
Administrator role in the deployed application:
Administrator role granted through Oracle WebCenter Portal Administration.
For more information about roles and permissions, see Understanding Administrative Operations, Roles, and Tools.
For troubleshooting issues with BPM worklists, see Email Notifications Not Working
Table 17-1 in this section provides an overview of the prerequisites and tasks required to use Oracle BPM Worklist in WebCenter Portal.
Table 17-1 Configuring Workflows for WebCenter Portal
2. Create the BPEL connection and enable the WebCenter Portal Workflow using either:
3. Deploy the WebCenter Portal workflows:
Note: During the SOA installation, if you select the option Oracle Webcenter Portal Composites - 184.108.40.206 [wcportal] on the Templates page,
5. Secure the connection to the BPEL server
6.a (Optional) Configure Single Sign-OnIf using OAM R2 or later, exclude Webcenter Portal Workflows URL
6.c (Optional) Configure SSL
7. Test that the integration to the Oracle BPM Worklist application is working in WebCenter Portal
7.a In WebCenter Portal, create a portal and invite members.
See Managing Members and Assigning Roles in a Portal in Building Portals with Oracle WebCenter Portal.
7.b Log in to Oracle BPM Worklist and view the worklist items.
7.c Select the invitation worklist item and click Accept.
See Using Oracle BPM Worklist in Developing SOA Applications with Oracle SOA Suite
7.d Log out and then log in as the portal manager and view the Members tab. Confirm that the user is now a member in the selected role and the status is not set to Invited anymore.
See Inviting a Registered User in Building Portals with Oracle WebCenter Portal.
Consider the following while working with BPEL connections:
By configuring a default BPEL server, WebCenter Portal users can manage memberships through notifications that can be viewed in the SOA BPM worklist. For more information, see Using Oracle BPM Worklist in Developing SOA Applications with Oracle SOA Suite.
WebCenter Portal workflows require a single connection to the BPEL server included with the Oracle SOA Suite. For more information, see Specifying the BPEL Server Hosting WebCenter Portal Workflows.
Consider the following to ensure smooth functioning of worklists:
Make sure that the Oracle BPM Worklist application is part of the SOA server. The URL is in the following format:
If Oracle BPM Worklist is not running in the same domain as the Oracle SOA Suite BPEL server, then the identity store (LDAP) should be either shared (recommended) or contain identical user names.
Clocks on the WebCenter managed server and the Oracle SOA Suite BPEL's 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
/integration/worklistapp. Hence, verify that
/integration/worklistapp can access the Oracle BPM Worklist application.
If the Oracle SOA Suite BPEL's managed server is configured to use an identity store and that store does not contain
weblogic by default, then the
BPMWorkflowAdmin user must be configured, as described in Enabling the weblogic User for Logging in to the Worklist in Developing SOA Applications with Oracle SOA Suite
wsm-pm application must be running on both worklists and Oracle SOA Suite's BPEL server's managed servers without any issues. This can be validated through the URL:
For information on how to resolve BPEL server issues, see Troubleshooting WebCenter Portal Workflows.
This section includes the following subsections:
WebCenter Portal uses the BPM Worklists on the Oracle BPEL Process Manager (BPEL) server, which is included with Oracle SOA Suite.
To work with worklist, you must install Oracle SOA Suite. For information about how to install Oracle SOA Suite, see Installing and Configuring Oracle SOA Suite and Business Process Management.
After installing Oracle SOA Suite, you can configure WebCenter Portal to use the BPEL server for viewing and managing worklists.
Worklists display tasks for the currently authenticated user. For portal 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 BPEL Server and WebCenter Portal.
For example, if the user
rsmith wants to store and retrieve tasks from the BPEL server, you must ensure that the user
rsmith exists on both the BPEL server and within WebCenter Portal.
To access BPEL worklist task details sent from WebCenter Portal, without incurring additional login prompts, WebCenter Portal and Oracle SOA Suite servers must be configured to a shared Oracle Single Sign-On server. For more information, see Configuring Oracle Access Manager.
For a secure connection you can configure WS-Security between SOA and WebCenter Portal. For information, see Configuring Web Services Security.
WebCenter Portal uses the BPEL server included with the Oracle SOA Suite to host internal workflows, such as worklists, portal membership notifications, portal subscription requests, and so on. To enable workflow functionality for WebCenter Portal, a connection to this BPEL server is required.
WebCenter Portal workflows must be deployed on the SOA managed server that WebCenter Portal is configured to use. See also, Back-End Requirements for WebCenter Portal Workflows in Installing and Configuring Oracle WebCenter Portal.
To configure a connection for worklist notifications:
Figure 17-1 WebCenter Portal Application Configuration Menu
The Application Settings page opens (Figure 17-2).
Figure 17-2 Choosing the BPEL Server Where Workflows are Deployed
The SOA server name that you specify here will contain the BPM worklists for WebCenter Portal.
WebCenter Portal provides human workflows (requiring human interaction), which are integrated with SOA workflows. The SOA server can configure email so that notifications are delivered to a user's inbox, where the user can accept or reject the notification.
This section briefly explains how to enable email notifications and configure your mail server details to have WebCenter Portal workflow notifications sent to users by email. For a more detailed description, see Configuring Human Workflow Notification Properties in Administering Oracle SOA Suite and Oracle Business Process Management Suite.
Figure 17-3 SOA Administration - Workflow Config
Figure 17-4 Email Notification Mode Properties
Figure 17-5 Associated Drivers
To test notifications, in the portal administration settings Members page, you can add people and edit email notification messages. For more information, see Managing Members and Assigning Roles in a Portal in Building Portals with Oracle WebCenter Portal.
When the Oracle SOA Suite BPEL server is configured to use OAM 11g R2 or later, WebCenter Portal Workflows endpoints need to be excluded from the OAM server.
Auto configured out-of-the-box