Editing Connection Settings Using JConsole

Managing WebCenter Personalization 19-13 Connection settings for the People Connections ILocator are maintained in wcps-connections.xml in the wc_domain conductor extensions directory domain scoped. Although it is not recommended that you edit this file directly, there are several other ways in which you can modify connection settings. Use one of the methods described in Section 19.4.1, Creating or Modifying Provider Connection Settings. to configure the connection settings for the People Connections ILocator. Connection Element and Property Descriptions connection-name - unique name for this connection. Connections can be retrieved by name. 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. Use a wildcard to make this connection element available in all namespaces. nameisDefaultname - marks this connection as the default connection if multiple are defined nameschemename - protocol to access the CMIS REST service HTTP or HTTPS for SSL. Defaults to HTTP if not explicitly specified. namehostname - machine name hosting the PC REST service. This is the machine name of the WC_Spaces managed server. nameportname - machine port number hosting the PC REST service. This is the machine port number of the WC_Spaces managed server. nameusername - Optional the username to use when connecting to the People Connection REST service. Can be used to force a connection to a fixed username. namepasswordname - Optional the password to use when connecting to the People Connections REST service. Used in conjunction with username, can be used to force a connection to a fixed usernamepassword. Not recommended for use outside of development environment since password access is not secured. namerestResourceIndexname - appended to the PC REST service hostport, pointing to the location of the resourceIndex available REST services page for example: restapiresourceIndex Bootstrapping the Person class to the Properties Provider In order for the Property Service to know about and use the results of the People Connections REST calls, it needs to know about a Person. This means creating a Person property set definition, along with its individual attributes set as property definitions, before a Person can be instantiated and its properties set. The People Connection ILocator code does this by bootstrapping that process in a servlet listener, configured in its web.xml file as shown in the example below: ?xml version=1.0 encoding=UTF-8 ? web-app xmlns=http:java.sun.comxmlnsj2ee xmlns:xsi=http:www.w3.org2001XMLSchema-instance xsi:schemaLocation=http:java.sun.comxmlnsj2ee http:java.sun.comxmlnsj2eeweb-app_2_4.xsd version=2.4 -- Allows connection config classes to be loaded from the connections.xml file -- listener 19-14 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter listener-classoracle.wcps.connection.lifecycle.VersatileModuleLifecycleCallback listener-class listener listener listener-classoracle.wcps.people.util.BootstrapPropertiesListenerlistener-clas s listener web-app Accessing the PC REST connection configuration information Because the People Connections ILocator is not an actual provider, you cannot access its connection information in provider code, as for example Activity Graph. Instead, internal code uses the VersatileModuleLifecycleCallback class to make that configuration information available, and consequently makes this is a required listener to be configured in web.xml. Once that listener has been activated, the code can make calls to access connection information and parameterize the ILocator code to point to the PC REST server. Tying the PC ILocator to the Properties Service Provider The Properties Service Provider PSP knows about the People Connections ILocator through the namespaces. In the bootstrapping process above, the PropertySetDefinition and its definitions are namespaced with people.connections.person and a locator class oracle.wcps.people.property.PeoplePropertyLocator. In using the PSP, the namespace and PropertySetDefinition are passed to the PSP. The PSP uses the locator class defined in the PropertySetDefinition to instantiate and delegate to property values Person values from the People Connections REST service. The locator and namespaces are critical in this process. They are defined as constants in the internal PropertyDefConstants class. Note that these do not need to be configured.

19.4.5 Configuring Custom Providers

Connection settings for Activity Graph are maintained in wcps-connections.xml in the wc_domain conductor extensions directory domain scoped. Although it is not recommended that you edit this file directly, there are several other ways in which you can modify connection settings. Use one of the methods described in Section 19.4.1, Creating or Modifying Provider Connection Settings. to configure the connection settings for your custom provider. Refer to Section 19.4.1.2, Connection Configuration Attributes for information about the configuration file elements and property descriptions.

19.5 Configuring Coherence

If your installation is using Coherence for caching a requirement for HA environments, four separate caches must be set up: one each for Namespaces, Property Definitions, Property Set Definitions, and Property Sets. The sample wcps-cache-config.xml configuration file below shows how to configure simple Coherence local caches. For more advanced cache types, refer to the Coherence documentation. Note that Coherence classes must be accessible via the