Worklist Service Timed Out or is Disabled

23-2 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter ■ Several out-of-the-box producers are provided with Oracle WebCenter: OmniPortlet, Web Clipping, and WSRP Tools. The following EAR files are packaged with Oracle WebCenter: ■ portalTools.ear - OmniPortlet and Web Clipping ■ wsrp-tools.ear - WSRP Tools You can install the portalTools.ear and wsrp-tools.ear files using the registerOOTBProducers WLST command. For command syntax and examples, see registerOOTBProducers in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference. ■ Before users can add JSR 286 or Oracle PDK-Java portlets to a page, you must register the owning WSRP and Oracle PDK-Java producers. See also, registerSampleProducers in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference. ■ The Oracle Portlet Producer product server must be installed in the production environment and the wsrp-tools and portalTools URLs must be accessible. If the Oracle Portlet Producer is not installed, see the section Extending an Existing Domain in the Oracle Fusion Middleware Installation Guide for Oracle WebCenter to install it in the production environment. ■ When you create a connection to a portlet producer, the producer is registered with the WebCenter application and the connection is added to the connections.xml file. For WRSP producers, a Web service connection is also created, which follows the naming convention, connectionname-wsconn. For Oracle PDK-Java producers, an underlying URL connection is created, which follows the naming convention, connectionname-urlconn. During the registration, connection metadata is created in the Oracle Metadata Services MDS repository and in the producer being registered. When a producer is consumed, the user customizations are saved to the producer. During deregistration the producer connection and customizations are removed. ■ All post deployment connection configuration is stored in MDS. For more information, see Section 1.3.5, WebCenter Configuration Considerations. For detailed information about MDS, see the chapter Managing the Oracle Metadata Repository in the Oracle Fusion Middleware Administrators Guide. ■ Portlet producer registration is dynamic. New portlet producers and updates to existing producers are immediately available in the WebCenter application; it is not necessary to restart the WebCenter application or the managed server. ■ To migrate producers from one instance to another, use the migration utilities described in the appendix Portlet Preference Store Migration Utilities in the Oracle Fusion Middleware Developers Guide for Oracle WebCenter. ■ For information on securing portlet producers, see Section 33.1, Securing a WSRP Producer and Section 33.2, Securing a PDK-Java Producer.

23.2 Registering WSRP Producers

This section describes how to register WSRP producers for a deployed application, using Fusion Middleware Control and WLST commands. This section includes the following subsections: ■ Section 23.2.1, Registering a WSRP Producer Using Fusion Middleware Control ■ Section 23.2.2, Registering a WSRP Producer Using WLST Managing Portlet Producers 23-3 ■ Section 23.2.3, Adding a Grant to the Policy Store for a Mapped User Identity ■ Section 23.2.4, Registering a WSRP Portlet Producer in WebCenter Spaces ■ Section 23.2.5, Registering a WSRP Portlet Producer in WebCenter Portal Applications For information about how to register WSRP producers at design-time, using JDeveloper, see the section How to Register a WSRP Portlet Producer in the Oracle Fusion Middleware Developers Guide for Oracle WebCenter.

23.2.1 Registering a WSRP Producer Using Fusion Middleware Control

To register a WSRP portlet producer: 1. Log in to Fusion Middleware Control and navigate to the home page for your WebCenter Portal application or WebCenter Spaces. For more information, see: ■ Section 6.3, Navigating to the Home Page for WebCenter Portal Applications . ■ Section 6.2, Navigating to the Home Page for WebCenter Spaces 2. Do one of the following: ■ For WebCenter Portal applications - From the Application Deployment menu, choose WebCenter Register Producer. ■ For WebCenter Spaces - From the WebCenter menu, choose Register Producer .

3. In the Add Portlet Producer Connection section, enter connection details for the

WSRP producer. For detailed parameter information, see Table 23–1 . Table 23–1 WSRP Producer Connection Parameters Field Description Connection Name Enter a unique name to identify this portlet producer registration within the WebCenter application. The name must be unique across all WebCenter connection types. The name you specify here appears in Oracle Composer under the Portlets folder. Producer Type Indicate the type of this producer. Select WSRP Producer. 23-4 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter

4. Use the Security section to specify the type of security token to use for the identity

propagationassertion. The security token with the propagated or asserted user information is represented as an XML element in the SOAP header. The security token and the SOAP message body are then digitally signed to prove the authenticity of the SOAP message origin from the WebCenter application. WebCenter applications support six types of security tokens: WSS 1.0 Username Token Without Password, WSDL URL The registration URL for the WSRP producer. The syntax varies according to your WSRP implementation. For example, possible URL formats for a portlet deployed to the Oracle WSRP container include: http:host_name:port_numbercontext_rootportl etswsrp2?WSDL http:host_name:port_numbercontext_rootportl etswsrp1?WSDL http:host_name:port_numbercontext_rootportl ets?WSDL WSRP 1.0 for backward compatibility Where: ■ host_name is the server where your producer is deployed. ■ port_number is the HTTP listener port number. ■ context_root is the Web applications context root. ■ portlets wsrp1|2?WSDL is static text. All producers deployed to the Oracle WSRP container are exposed as WSRP version 1 and version 2 producers. In WebCenter Spaces, only v2 WSDLs are supported for Oracle WebLogic Portal Producers. For example: http:myhost.com:7778MyPortletAppportletsws rp2?WSDL For WSRP producers, you can obtain this registration URL by accessing the producer test page at: http:host_name:port_numbercontext_rootinfo Use Proxy? Select if the WebCenter application must use an HTTP proxy when contacting this producer. If selected, enter values for Proxy Host and Proxy Port. A proxy is required when the WebCenter application and the remote portlet producer are separated by a firewall and an HTTP proxy is needed to communicate with the producer. Proxy Host Enter the host name or IP address of the proxy server. Do not prefix http: to the proxy server name. Proxy Port Enter the port number on which the proxy server listens. The default port is 80. Default Execution Timeout Seconds Enter a suitable timeout for communications with the producer, in seconds. For example, the maximum time the producer may take to register, deregister, or display portlets on WebCenter pages. The default is 30 seconds. Individual portlets may define their own timeout period, which takes precedence over the value expressed here. Table 23–1 Cont. WSRP Producer Connection Parameters Field Description Managing Portlet Producers 23-5 WSS 1.0 Username Token With Password, WSS 1.0 SAML Token, WSS 1.0 SAML Token With Message Integrity, WSS 1.0 SAML Token With Message Protection, and WSS 1.1 SAML Token With Message Protection. Where SAML is an abbreviation for Security Assertion Markup Language. For detailed parameter information, see Table 23–2 . Note: PeopleSoft WSRP producers support two profiles: Username Token With Password and SAML Token With Message Integrity. Oracle Portal as a consumer supports three profiles: Username Token Without Password, Username Token With Password, SAML Token With Message Integrity. Other Oracle WSRP producers support all six profiles. For other WSRP containers, check with the specific vendor to determine the token formats they support. Table 23–2 WSRP Producer Security Connection Parameters Field Description Token Profile Select the type of token profile to use for authentication with this WSRP producer. Select from: ■ WSS 1.0 SAML Token With Message Integrity wss10_saml_token_with_message_integrity_client_policy—This policy provides message-level integrity protection and SAML-based authentication for outbound SOAP requests in accordance with the WS-Security 1.0 standard. A SAML token, included in the SOAP message, is used in SAML-based authentication with sender vouches confirmation. This policy uses WS-Securitys Basic 128 suite of asymmetric key technologies and SHA-1 hashing algorithm for message integrity. ■ WSS 1.0 SAML Token With Message Protection oraclewss10_saml_token_with_message_protection_client_polic y—This policy provides message-level protection integrity and confidentiality and SAML-based authentication for outbound SOAP requests in accordance with the WS-Security 1.0 standard. The Web service consumer includes a SAML token in the SOAP header and the confirmation type is sender-vouches. This policy uses WS-Securitys Basic 128 suite of asymmetric key technologies. Specifically, RSA key mechanisms for message confidentiality, SHA-1 hashing algorithm for message integrity, and AES-128 bit encryption. ■ WSS 1.0 Username Token Without Password oraclewss10_username_id_propagation_with_msg_protection_c lient_policy—This policy provides username with password token profile based identity propagation with certificate based message protection for outbound SOAP requests in accordance with the WS-Security 1.0 standard. Credentials username only are included in outbound SOAP request messages through a WS-Security UsernameToken header. No password is included. Message protection is provided using WS-Security 1.0s Basic 128 suite of asymmetric key technologies. Specifically, RSA key mechanisms for message confidentiality, SHA-1 hashing algorithm for message integrity, and AES-128 bit encryption.