WebCenter Personalization Configuration Options

Managing WebCenter Personalization 19-7 Testing the Configuration The simplest way to validate cross domain trust is to create a People Connections WebCenter Personalization connection in the integrated WLS domain that points to the WebCenter domains WC_Spaces server. Then, create and deploy a simple scenario to the integrated WLS domain that fetches a People Connections property value. Finally, confirm that the Token Validate Operation message described above is logged on the WC_Spaces server.

19.4 Configuring Providers

WebCenter Personalization provides out-of-the-box providers for Activity Graph and the Oracle Content Server, and a locator for People Connections. For scenarios using any of these providers, you must configure them using the configureWCPY.py WLST script as described in the following sections. If you are using custom providers or locators, then you must also configure them as described in the section on configuring custom providers. You do not need to configure providers or locators if they are not being used in your scenarios. You can develop scenarios without the out-of-the-box providers, or exclusively with custom providers or downloaded from OTN. Also, if you are developing exclusively within the JDeveloper integrated domain, you do not ordinarily have access to these WC_Spaces-based services since WebCenter Spaces does not run in the integrated domain. With advanced configurations also supported by configureWCPS.py you can access the WebCenter Spaces services in the WC_Spaces domain from the integrated domain’s WebCenter Personalization server. This uses cross-domain trust and does require the provider connections to be configured. The configureTrustWCPS.py and configureConnectionsWCPS.py scripts located in the WC_Spaces domain, or configureWCPS.py for JDeveloper’s integrated WLS domain located in the DefaultDomainscrpts-wcps domain directory are used to configure the corresponding domains by pointing to the appropriate WLS Administration server. ■ Section 19.4.1, Creating or Modifying Provider Connection Settings ■ Section 19.4.2, Configuring the CMIS Provider ■ Section 19.4.3, Configuring the Activity Graph Provider ■ Section 19.4.4, Configuring the Oracle People Connections Locator ■ Section 19.4.5, Configuring Custom Providers

19.4.1 Creating or Modifying Provider Connection Settings

This section describes how to use WLST, JConsole, Fusion Middleware Control to create or change the connection information stored in wcps-connections.xml. It also describes how you can write a custom configuration class to configure a custom provider. This section contains the following subsections: ■ Section 19.4.1.1, Understanding WebCenter Personalization Connection Information ■ Section 19.4.1.2, Connection Configuration Attributes ■ Section 19.4.1.3, Configuring Connections Using WLST ■ Section 19.4.1.4, Configuring Connections Using JConsole 19-8 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter ■ Section 19.4.1.5, Configuring Connections Using Fusion Middleware Control ■ Section 19.4.1.6, Writing a Custom Configuration Class

19.4.1.1 Understanding WebCenter Personalization Connection Information

WebCenter Personalization connection information is maintained in wcps-connections.xml, which can be found in the domain directory at the following location: domain directory configfmwconfigwcps-connections.xml Although editing this file directly is not recommended, there are several ways in which you can modify connection information: ■ WLST - you can write a script with WLST commands to access the system MBeans representing the connection configuration. For more information on using WLST commands to configure connection settings, see Section 19.4.1.3, Configuring Connections Using WLST. ■ JConsole - you can use JConsole to view or edit connection configuration by creating or editing connection JMX MBeans. For more information on using JConsole to configure connection settings, see Section 19.4.1.4, Configuring Connections Using JConsole. ■ Fusion Middleware Control - you can use Fusion Middleware Control to view or edit the JMX MBeans deployed with WebCenter Personalization. For more information on using Fusion Middleware Control to configure connection settings, see Section 19.4.1.5, Configuring Connections Using Fusion Middleware Control.

19.4.1.2 Connection Configuration Attributes

The following shows the connection properties and attributes maintained in wcps-connections.xml that can be modified using WLST, JConsole, or Fusion Middleware Control. Note that each connection property is specific to the provider or locator that the connection is for. For example, the CMIS provider will have different connection properties than the Activity Graph provider. ■ connection-name - unique name for this connection. Connections can be retrieved by name. ■ connection-type - unique type for this connection. Connections can be retrieved by type. Note that connection-type only needs to be specified for custom connections. For the out-of-the-box data providers this field is set internally. ■ namespace - generally, this must match the namespace the accessing scenario is deployed within. The namespace is how the Conductor determines how to locate the appropriate connection for a given scenario. You can use a wildcard to make this connection element available in all namespaces. If left unspecified in the WLST script, namespace will default to ’’. ■ nameisDefaultname - marks this connection as the default connection if multiple are defined. Note that multiple connections can have the isDefault flag set to true. If this is the case, it is up to the individual provider to return the default connection.

19.4.1.3 Configuring Connections Using WLST

A set of WebCenter Personalization WLST commands is provided to allow easy configuration of your provider connections. You can combine these commands into a