Modifying Content Repository Connection Details Using Fusion Middleware Control Modifying Content Repository Connection Details Using WLST

Managing Content Repositories 11-45 binaryCache. Caches binary property data. Only binaries that are smaller than the repository configuration property BinaryCacheMaxEntrySize are cached. The size of this cache either depends on the number and frequency of the smaller binary properties smaller than the BinaryCacheMaxEntrySize setting usage, or it is based on the total amount of memory to be used for binary caches. This cache expires based on when the binary data is refreshed and how many times this data is modified from another application. Key - The Node UID and binary Property UID nodeUid.propUid - String Value - The binary stream data - byte[] repo.ucm.searchCriter iaCache. Caches a set of search query to parameters based on the UCM search grammar. The size of this cache depends upon the number of unique searches expected to be repeatedly performed. The expiration must be set to eventually expire unused searches and save on the cache memory. Key - A set of search query parameters. Value - A set of search query parameters, in UCM terms. repo.ucm.indexedField sCache. Holds the indexed searchable system properties for the repository. There are three keys in this cache: ■ indexedFields holds all UCM indexed fields. ■ indexedFolderProps holds indexed system properties for folders. ■ indexedDocProps holds indexed system properties for documents. This cache expires based on the frequency of the indexed fields changes. Key - String Value - MapString,Boolean holds a key for each indexed property name, and a boolean indicating if that property is also sortable. repo.ucm.securityUser Cache. Caches the mapping between local user names current application and the name of the same user in UCM. The size of this cache depends upon the number of simultaneous andor frequent users. This cache expires based on the frequency of user identity mapping updates. Key - Local user Id - String Value - UCM user Id - String Table 11–9 Cont. Cache Entries in content-coherence-cache-config.xml Cache Entry Name Description 11-46 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter

11.9 Deleting Content Repository Connections

This section contains the following subsections: ■ Section 11.9.1, Deleting Content Repository Connections Using Fusion Middleware Control ■ Section 11.9.2, Deleting Content Repository Connections Using WLST

11.9.1 Deleting Content Repository Connections Using Fusion Middleware Control

To delete a content repository connection:

1. Log in to Fusion Middleware Control and navigate to the home page for

WebCenter Spaces or the WebCenter Portal application: ■ Section 6.2, Navigating to the Home Page for WebCenter Spaces ■ Section 6.3, Navigating to the Home Page for WebCenter Portal Applications

2. Do one of the following:

■ For WebCenter Spaces - From the WebCenter menu, choose Settings Service Configuration . ■ For WebCenter Portal applications - From the Application Deployment menu, choose WebCenter Service Configuration.

3. From the list of services on the WebCenter Services Configuration page, choose

Content Repository .

4. Select the connection name, and click Delete.

5. To effect this change you must restart the managed server on which the

WebCenter application is deployed.

11.9.2 Deleting Content Repository Connections Using WLST

Use the WLST command deleteConnection to remove a content repository connection. For command syntax and examples, see deleteConnection in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference. repo.ucm.profileTrigg erValueCache. Caches the profile trigger value for a given profile, so it is available when documents are created. The maximum number of entries in this cache is implicitly limited to the maximum number of profiles on the UCM server. The cache entry size is small. The primary entry to vary is the expiration, which depends upon how often the profile trigger field values are modified in UCM. These values change rarely once a profile is configured on the UCM system. Therefore, the expiration should be set appropriately. Key - The UCM profile name - String Value - The UCM profile trigger value - String Caution: Delete a content repository connection only if it is not in use. If a connection is marked as active, it should first be removed from the active list, and then deleted. Table 11–9 Cont. Cache Entries in content-coherence-cache-config.xml Cache Entry Name Description