Configuring Coherence Oracle Fusion Middleware Online Documentation Library

19-18 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter 2. In the Navigation pane, expand the WebCenter domain node wc_domain by default, expand the WebCenter node, expand the WebCenter Spaces node, and click webcenter11.1.1.4.0WC_Spaces.

3. From the WebCenter menu, select ADF - Configure ADF Connections.

The ADF Connections Configuration page displays see Figure 19–1 . Figure 19–1 ADF Connections Configuration Page

4. Set the Connection Type to Url, enter the Connection Name as Conductor, and

click Create Connection. The URL Connections section displays see Figure 19–2 . Figure 19–2 ADF Connections Configuration Page URL Connections

5. Click the Edit Pencil icon.

The URL Connection dialog displays see Figure 19–3 . Managing WebCenter Personalization 19-19 Figure 19–3 URL Connection Dialog 6. Edit the URL so that it points to the Content Server instance used by WebCenter Spaces. For example: http:example.com:8891wcpsapiconductor?namespace=CP_namespacerepoId=myhost -ucm11g

7. Update any other fields as required for your local connection and click OK.

19.6.2 Configuring the Content Presenter Task Flow Parameters

You can configure a Content Presenter instance through its task flow parameters. These can either be set at runtime in the Content Presenter Configuration dialog, or from JDeveloper as you add the Content Presenter task flow. To do this manually, you need to set two parameters: the Data Source Type parameter must be set to dsTypeScenarioResults, and the Data Source parameter should be set to something like: conductor-connection-name=ConductorConnectionName,namespace= ScenarioNamespace,scenario-name=ScenarioName,inputparam1=value1,inputparam2 =value2 Note that the conductor-connection-name value must match with a URL connection that points to a valid Conductor server. Also, the namespace used should be the name of the namespace to which the specified scenario belongs. Finally, any input parameters that the scenario may be expecting can appended as shown above, with a comma separating the namevalue pairs. For more information about configuring Content Presenter for WebCenter Personalization, see: ■ At runtime: Setting Content Presenter Task Flow Properties in the Oracle Fusion Middleware Users Guide for Oracle WebCenter ■ In JDeveloper: Content Presenter Task Flow Parameters and Out-of-the-Box Display Templates in Oracle Fusion Middleware Developers Guide for Oracle WebCenter.

19.6.3 Configuring the Conductor’s Scenario Tags

On the Conductor side, your Scenarios must have the correct tag in order for Content Presenter to see them. Content Presenter uses the tag ContentPresenterScenario, so any scenarios you want Content Presenter to pick up must have this tag associated with them. 19-20 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter Once you have everything set up on both the Conductor and WebCenter application side, everything else is fairly simple. When you open the Content Presenter Configuration dialog at runtime, the Content Source selection list displays Results of a Scenario . Selecting this displays a table of all of the scenarios that have been tagged for Content Presenter consumption. The first Scenario is always selected, and if it has any Input Parameters defined, they will be displayed below the table with input fields. As you select scenarios in the table, the Input Parameters below will be updated. After selecting a scenario and specifying any input parameters, you can either preview or save Content Presenter to get the results. The results will be displayed much like any other multi-valued content source and will ultimately depend on the template selected for display purposes.

19.7 Configuring Single Sign-on

Single sign-on is configured as part of running the configureTrustWCPS.py and configureConnectionsWCPS.py scripts for configuring the WebCenter domain, or the configureWCPS.py script for configuring JDeveloper’s integrated WLS domain. When you run these scripts they also set up Trust Services single sign-on, which allows single sign-on for REST HTTP requests between client JEE Web applications, the WebCenter Personalization Web application, and the WC_Spaces Web application REST services used by the out-of-the-box data providers. All these WebCenter applications are also configured to support OAMOSSO-provided single sign-on tokens, as well, without any additional Personalization-specific configuration. For more information, see Section 19.3.3, Configuring Cross-Domain Trust.

19.8 Overriding the Default Security Settings

By default, all access to WebCenter Personalization REST resources other than the resourceIndex requires authentication. In most cases this will be sufficient for development. However, for production environments, you may want to modify the default security constraints. The following sections describe how to set up less security to execute scenarios where anonymous access is needed, and more security to prevent the ability to create new scenarios. This section contains the following subsections: ■ Section 19.8.1, Allowing Anonymous Execution of Scenarios ■ Section 19.8.2, Disabling Scenario Creation by Anonymous Users ■ Section 19.8.3, Disabling Scenario Creation by Authenticated Users

19.8.1 Allowing Anonymous Execution of Scenarios

Adding the following security constraint to the domains conductor-extensions-library\WEB-INF\web.xml, file will honor default descriptor authentication required security, plus allow anonymous GETPOST on scenarios created or deployed from an anonymous application or namespace: security-constraint web-resource-collection Note: Any results that are returned from a scenario for use within Content Presenter must return a valid CMIS query as Content Presenter takes the return value and runs it as a CMIS query against the repository specified within the Conductor URL.