Headers Parsers To delete field mappings, click Delete.

24-12 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter

2. In the Producer Type list, choose WSRP Producer and enter the URL to the WSDL

for the WSRP endpoint. 3. If an HTTP proxy is required when contacting the producer, select the Use Proxy? option and enter the host name and port for the proxy server.

4. Enter a suitable timeout for communications with the producer. The default is 30

seconds.

5. If the producer requires authenticaion, select the appropriate token profile and

enter any necessary configuration information.

6. To confirm that the configuration is correct, click Test.

7. If you registered the producer in Enterprise Manager, you must load the external registration in Pagelet Producer. Either restart the Pagelet Producer server, or complete the following steps:

a. Open the Pagelet Producer Console and select Producers from the drop-down

list.

b. Click Refresh, then click Save.

Once registration is complete, the WSRP producer will appear as a Resource in the Pagelet Producer Console, and the portlets associated with the WSRP endpoint will be listed in the Pagelets collection. The settings and parameters for the new pagelets are based on the portlet definitions in the WSDL for the WSRP producer. If modifications are made to the WSRP portlets, refresh the producer registration to import the changes. WSRP-based pagelets can be used like any other pagelets.

24.5.1 Using WSRP Producers

Auto-generated WSRP resources and pagelets cannot be modified. Primarily a convenience for initial testing, they are virtual entries and do not exist in Pagelet Producer metadata definitions. To make changes and create a permanent reference to the WSRP producer, the auto-generated resource must be cloned. To create a version that can be modified, choose the resource and click Clone. The cloned version of the resource can now be edited, and various elements such as injectors can be added to customize pagelet functionality. Cloned resources are stable and will be included in metadata exports.

24.6 Configuring Pagelet Producer Settings

In the Pagelet Producer Console, the Settings section provides access to important settings that affect all pagelets provided by the Pagelet Producer.

24.6.1 Logging

The Logging page allows you to set logging levels for individual Pagelet Producer components. Logging is viewed in the managed server log files. In Oracle WebLogic Note: Auto-generated resources and pagelets cannot be modified. To make changes to the WSRP-based pagelets, follow the steps in the next section, Section 24.5.1, Using WSRP Producers. Managing the Oracle WebCenter Pagelet Producer 24-13 Server, this would be domain_homeserversmanaged server namemanaged server name .log and managed server name-diagnostic.log.

24.6.2 Proxy

The Proxy page includes HTTP proxy access configuration URL, user name and password. This page also allows you to define a semicolon-separated list of URLs that will not be proxied wildcards are allowed. You must restart the Pagelet Producer after changing the proxy setting.

24.6.3 Transform

The Transform page allows you to enter the path to the credential vault provider and configure secure and insecure ports for the Pagelet Producer. This page also allows you to choose whether or not to intercept and transform Ajax requests, and whether or not to log pre- and post- transformation content useful for debugging, but should not be enabled in a production environment.

24.6.4 CSP

CSP is a platform-independent protocol based on the open standard of HTTP 1.1. CSP defines the syntax of communication between Oracle WebCenter Pagelet Producer and external resources. It also defines custom headers as well as outlines how services use HTTP to communicate and modify settings. The CSP section may be ignored if Oracle WebCenter Interaction is not present in your deployment. These settings are used for backwards compatibility with CSP portlets written for Oracle WebCenter Interaction. This page allows you to configure the Oracle WebCenter Interaction REST endpoint, SOAP API service, and image service.

24.7 Troubleshooting Pagelets

Keep the following common errors in mind when troubleshooting pagelets: ■ Pagelet Producer logs messages to the standard Oracle Diagnostic Logging facility. On Oracle WebLogic Server, the logs are stored at domain serversserver-namelogsserver-name-diagnostic.log. ■ If you are using SSL, make sure both HTTP and HTTPS ports are configured properly in Settings. ■ If you are proxying external sites on a network that requires an HTTP proxy, you must configure the proxy URL in Settings. ■ Due to restrictions in the Sun Java Virtual Machine JVM, pagelets cannot HTTPS content where the underlying certificate uses MD2 signing algorithm. ■ The Login Resource and Pagelet REST API Resource, which are created by default, are present and correct. ■ If you are proxying KD Browser or other CSP pagelets, make sure the Image Server URL is absolute and the CSP SOAP API URL is set in Settings. 24-14 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter 25 Managing External Applications 25-1 25 Managing External Applications An external application is any application that implements its own authentication process. Specifically, it is an application that does not take part in your WebCenter applications single sign-on process. System administrators can use Fusion Middleware Control or the WLST command-line tool to register and manage external applications for WebCenter application deployments. Application administrators can also register and manage external applications at runtime through out-of-the-box administration pages or using external application task flows. All external application changes that you make for WebCenter applications, post deployment, are stored in the MDS repository as customizations. This chapter includes the following sections: ■ Section 25.1, What You Should Know About External Applications ■ Section 25.2, Registering External Applications ■ Section 25.3, Modifying External Application Connection Details ■ Section 25.4, Testing External Application Connections ■ Section 25.5, Deleting External Application Connections Audience The content of this chapter is intended for Fusion Middleware administrators users granted the Admin or Operator role through the Oracle WebLogic Server Administration Console. See also, Section 1.8, Understanding Administrative Operations, Roles, and Tools.

25.1 What You Should Know About External Applications

If your WebCenter application interacts with an application that handles its own authentication, you can associate that application with an external application definition to allow for credential provisioning. In doing so, you use an external application definition to provide a means of accessing content from these independently authenticated applications. Note: External application configuration is dynamic. Configuration changes are immediately reflected in the WebCenter application; it is not necessary to restart the application or the managed server.