Managing Links Managing Linked Content with Link Manager

Managing Repository Content 2-29 LkReExtractOnRebuild=true configures Link Manager to extract links from documents as they are indexed into the system during a rebuild. This is the default setting. LkReExtractOnRebuild=false prevents Link Manager from extracting links from documents as they are indexed into the system during a rebuild For more information about file formats, conversion, and link extraction, refer to Link Extraction Process on page 2-23 and File Formats and Conversion on page 2-24.

2.6.2.10 LkIsSecureSearch

Use LkIsSecureSearch to manage security restriction checks for non-admin users during a link search. To implement the security check, Link Manager performs an inner join between the Revisions table and the ManagedLinks table, and applies standard Content Server security using security groups and accounts. LkIsSecureSearch=true configures Link Manager to perform a security check on non-admin users while implementing a managed link search. This is the default setting. LkIsSecureSearch=false prevents Link Manager from performing a security check on non-admin users while implementing a managed link search. Example If a document with the link is Secure and the linked document is public, a user without permissions to Secure will not be able to find the document containing the link in the Search Links results. If a document with the link is Public and the linked document is Secure, the document containing the link will be found in the Search Links results, but the same user will not be able to use the link that is, if it is a link to the web-viewable or the document information for the secure document.

2.6.3 Managing Links

The Link Manager component uses an extraction engine that references the link patterns defined in the resource table LinkManagerPatterns. These link patterns are rules that tell the extraction engine how to sort the different links, which links to filter out, which links to accept, and how to parse the links for more information. Note: Because Link Manager does all of its work during the indexing cycle, it will increase the amount of time required to index documents and to rebuild collections. See also LkDisableOnRebuild on page 2-27. However, the time taken may not be noticeable since most of the time is spent indexing the document into the collection. Although, the amount of time required does depend on the type and size of the documents involved. That is, if the file needs to be converted, this requires more time than text-based HTML files. Note: The security check using the LkIsSecureSearch configuration variable is limited and can be bypassed if a user uses the Site Studio-specific fields for searching. 2-30 Application Administrators Guide for Content Server This section covers the following topics: ■ LinkManagerPatterns Table on page 2-30 ■ Examples of Link Patterns and Customization on page 2-31

2.6.3.1 LinkManagerPatterns Table

The LinkManagerPatterns table includes the following columns: Note: The LinkManagerPatterns table is an hda table that is easily accessible by other components. The LinkManagerPatterns table is located in the following file: UCM_ORACLE_ HOMEucmidccomponentsLinkManager8resourceslinkmanag er_resource.htm Column Name Description lkpName Provides the name of the pattern and is considered to be the primary key of the table. It is used mainly in error handling and to allow other components to directly target the override of a specified rule. lkpDescription Provides an explanation of the purpose of the pattern. lkpType The type specifies the initial screening of the URL. Supported types include: prefix -examines the path or address of the URL for the specified parameters. If the path begins with one of the specified parameters, then the condition is met. contains -examines the path or address of the URL for the specified parameters. If the path contains one of the specified parameters, then the condition is met. service -examines the query string of the URL. If the URL contains a value for IdcService and if this value matches one of the parameters, the condition is met. Note: The extraction engine is actually a two-step engine and the three types above fall into two distinct groups. The ‘prefix’ and ‘contains’ types are used on the path part of the URL, while the ‘service’ type is used on the query string part of the URL. lkpParameters A comma-separated list of patterns or parameters used by the type. The parameters are Idoc Script capable and are initially evaluated for Idoc Script. The engine uses the following rules for extracting the patterns from the parameters: ■ The parameter string is evaluated for Idoc Script. ■ The parameters are parsed using the comma separator. The result is a list of patterns. ■ Each pattern is XML decoded. Consequently, one rule looks for a URL that begins with the resolved value for HttpRelativeWebRoot by setting lpkParameters to HttpRelativeWebRoot. A subsequent rule may look for a URL that literally begins with HttpRelativeWebRoot by setting the parameter to lt;HttpRelativeWebRootgt; Managing Repository Content 2-31

2.6.3.2 Examples of Link Patterns and Customization

A components resource table LinkManagerPatterns is included with the Link Manager component. Refer to this table for examples of link evaluation rules. This table is located in the UCM_ORACLE_ HOMEucmidccomponentsLinkManager8resourceslinkmanager_resource.htm file. The table can be customized by adding new rules or editing the existing default rules. You can customize the LinkManagerPatterns table using standard component architecture.

2.6.4 Link Manager Database Tables