What You Should Know About BPEL Connections

Managing the Worklist Service 22-9 Figure 22–3 Configuring Worklist Connections 5. Enter a unique name for the Worklist connection and set it as the active connection Table 22–3 . This connection is picked up after you restart the managed server. 6. Enter connection details for the BPEL server Table 22–4 . Table 22–3 Worklist Connection - Name Field Description Name Enter a unique name for the connection. The name must be unique across all connection types within the WebCenter application. This name may be displayed to users working with the worklist feature in the WebCenter application. Users may organize their worklist assignments through various sorting and grouping options. The option Group By Worklist Server displays the name you specify here so its important to enter a meaningful name that other users will easily recognize, for example, Human Resources. Active Connection Select to activate this worklist connection in the WebCenter application. Once activated, worklist items from the associated BPEL server display in users worklists. Multiple worklist connections may be active at a time, enabling WebCenter users to monitor and manage assignments and notifications from a range of BPEL servers. If you need to disable a connection for any reason, deselect this option. Edit mode only. Check boxes indicate whether other components share this connection: ■ Worklist Indicates whether the Worklist service displays items associated with this connection. ■ WebCenter Spaces Application Indicates whether WebCenter Spaces uses the same BPEL server connection for internal workflows, such as Space membership notifications, Space subscription requests, and more. The BPEL server that provides this functionality is the BPEL server included with the Oracle SOA Suite. For more information, see Section 9.3, Specifying the BPEL Server Hosting WebCenter Spaces Workflows. Although not shown here, the Notification service might be set up to use the BPEL server connection too. See, Section 18.2, Setting Up a Notifications Connection Type . Before modifying connection properties, consider impact to any other components that share this connection. 22-10 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter

7. Click OK to save this connection.

8. Click Test to verify if the connection you created works. For a successful

connection, the Test Status message displays the advice that to start using the new Table 22–4 Worklist Connection - Connection Details Field Description BPEL Soap URL Enter the URL required to access the BPEL server. Use the format: protocol :host:port For example: http:mybpelserver.com:8001 Note: WebCenter Spaces uses the BPEL server included with the Oracle SOA Suite to implement WebCenter Spaces workflows. If you are setting up the workflow connection, make sure you enter the SOA Suites BPEL server URL here. For more information, see Section 9.3, Specifying the BPEL Server Hosting WebCenter Spaces Workflows. SAML Token Policy URI Select the SAML Security Assertion Markup Language token policy this connection uses for authentication. SAML is an XML-based standard for passing security tokens defining authentication and authorization rights. An attesting entity that has a trusted relationship with the receiver vouches for the verification of the subject by method called sender-vouches. Options available are: ■ SAML Token Client Policy oraclewss10_saml_token_client_policy - Select to verify your basic configuration without any additional security. This is the default setting. ■ SAML Token With Message Protection Client Policy oraclewss10_saml_token_with_message_protection_client _policy - Select to increase the security using SAML-based BPEL Web Services. If selected, you must configure keys stores both in your WebCenter application and in the BPEL application. For information, see Chapter 32, Configuring WS-Security. Recipient Key Alias The recipient key alias to be used for message protected SAML policy authentication. Only required when the BPEL server connection is using a SAML token policy for authentication and the application’s Worklist service is using multiple BPEL server connections. For example, myKey To determine the recipient key alias for a complex topology, see Section 32.3, Configuring WS-Security for a Complex Topology. Link URL Specify the URL used to link to the BPEL server. Only required if it is different to the BPEL SOAP URL, for example, when SSO or HTTPS is configured. Use the format: protocol:host:port For example, http:mySSO.host.com:7777 For performance reasons, in an HTTPS or SSO environment, the Link URL specifies user access to BPEL worklist items, through HTTPS or SSO Web servers, whereas the BPEL SOAP URL specifies direct access to BPEL Web services, without redirection through HTTPS or SSO Web servers.