BPEL Server - Installation and Configuration

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. Managing the Worklist Service 22-11 active connection, you must restart the managed server on which the WebCenter application is deployed. For more information, see Section 8.2, Starting and Stopping Managed Servers for WebCenter Application Deployments. See Section 22.5, Troubleshooting Issues with Worklists if the test fails.

22.4.2.2 Registering Worklist Connections Using WLST

Use the WLST command createBPELConnection to create a BPEL server connection. For command syntax and examples, see the section, createBPELConnection in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference. To configure the Worklist service to actively use a new BPEL server connection some additional configuration is required. For more information, see Section 22.4.3.2, Activating a Worklist Connections Using WLST. For information on how to run WLST commands, see Section 1.13.3.1, Running Oracle WebLogic Scripting Tool WLST Commands.

22.4.3 Activating a Worklist Connection

In WebCenter applications, multiple Worklist connections may be active at a time. Multiple connections enable WebCenter users to monitor and manage assignments and notifications from a multiple BPEL servers. From time to time you may need to temporarily disable an active connection so no errors or warnings are logged or displayed in the UI if the Worklist service queries a SOA server which is undergoing maintenance. This section includes the following subsections: ■ Section 22.4.3.1, Activating a Worklist Connections Using Fusion Middleware Control ■ Section 22.4.3.2, Activating a Worklist Connections Using WLST

22.4.3.1 Activating a Worklist Connections Using Fusion Middleware Control

To activate or disable a Worklist connection: 1. Log in to Fusion Middleware Control and navigate to the home page for WebCenter Spaces or the WebCenter Portal application. For more information, see: ■ Section 6.2, Navigating to the Home Page for WebCenter Spaces ■ Section 6.3, Navigating to the Home Page for WebCenter Portal Applications 2. Do one of the following: Tip: To activate newly registered connections, perform the steps described in Section 22.4.3, Activating a Worklist Connection. Note: To activate newly registered connections, perform the steps described in Section 22.4.3, Activating a Worklist Connection. To start using the new active connection you must restart the managed server on which the WebCenter application is deployed. For more information, see the section, Starting and Stopping WebLogic Managed Servers Using the Command Line in the Oracle Fusion Middleware Administrators Guide.