Site Studio Integration Managing Linked Content with Link Manager

Managing Repository Content 2-33

2.6.5.1 extractLinks Filter

The extractLinks filter is used during the Link Extraction Process when the extraction engine parses the accepted URL links. As links are extracted, Link Manager looks for specific HTML tags. However, you may decide that other HTML tags might also contain relevant links. In this case, you can use this filter to extract these additional links. The tag is passed to the filter as a cached object with the key HtmlTag. The value or link is passed back to the parse with the key HtmlValue. If the filter extracts extra information, you should be aware that the passed-in binder is flushed before being passed to the pattern engine. The service.setCachedObject and service.getCachedOject methods should pass and retrieve the extra information, respectively.

2.6.5.2 linkParseService Filter

The linkParseService filter is used during the Link Extraction Process when the pattern engine evaluates links. Specifically, the links that are identified to use the IdcService parameter. After evaluation, the link binder and service are provided for the linkParseService filter. The service contains the binder for the parsed URL and information map. You may choose to customize the values in the parsed URL binder by adjusting certain parameters. Or, you may decide to customize the information map which tells the parseService method what parameters to extract from the URL binder and how to map the data to resource types.

2.6.5.3 sortAndDecodeLinks Filter

The sortAndDecodeLinks filter is only available from the refresh option. That is, it is only called when users are refreshing the links. For more information about Link Manager refresh options, refer to Managed Links Administration Page on page 2-35. The service contains the LinkSetMap which includes a sorted list of links contained in the ManagedLinks table. The refresh validates the Site Studio links and the existence of all links referring to doc resources. However, you may decide to create a component that augments the standard validation.

2.6.6 Site Studio Integration

When configured to work with Site Studio, Link Manager obtains links from Site Studio by directly requesting a parsing of the links that Site Studio has identified. In return, Site Studio provides information about the links pertaining to its health and components. In particular, Site Studio provides information about the nodesection, if a content item is used, the state of the content item, the type of link friendly, page, or node, and if the link is valid. Note: By default, it looks for the following HTML tags: a, link, iframe, img, script, and frame. Important: When you are using Site Studio, you must set the HasSiteStudio configuration variable value to true. This variable enables the Site Studio-specific patterns for parsing friendly URLs for the pattern engine. For more information on the HasSiteStudio variable, see the Oracle Fusion Middleware Idoc Script Reference Guide. 2-34 Application Administrators Guide for Content Server When a user changes the links via the Site Studio designer, Link Manager listens to filter events. Consequently, if a node is deleted, Link Manager marks all links using the deleted node as invalid. This means that Link Manager successfully manages links that directly reference the node ID. Additionally, with information provided by Site Studio, Link Manager can accurately determine the state of the link. However, friendly URLs i.e., links that do not reference the node ID or dDocName are more difficult to manage and ensure accuracy. When a node property changes, Link Manager marks all friendly links using this node as invalid and broken. This includes both absolute and relative links. Although this may not actually be the case, Link Manager can not retrace the parent chain to determine what part of the link was changed, how to fix it, or determine if it is actually broken.

2.6.6.1 Types of Site Studio Managed Links

Site Studio uses two types of managed links: ■ Completely Managed Links: – Any links using the SS_GET_PAGE IdcService. – Links to nodes that include: javascript:nodelinkNode,Site javascript:nodelinkNode ssNodeLinkNode,Site ssNodeLinkNode ssNODELINKSiteNode ssNODELINKNode – Links to pages that include: javascript:linkDoc,Node,Site javascript:linkDoc,Node javascript:linkDoc ssLinkDoc,Node,Site ssLinkDoc,Node ssLinkDoc ssLINKSiteNodeDoc ssLINKNodeDoc ssLINKDoc ■ Provisionally Managed Links: The following Site Studio links are managed up to Site Studio node changes. The state of the links can be determined by using the refresh option from the Managed Links Administration Page . If the majority of links are of this form and nodes have changed dramatically, it is recommended to refresh or recompute the links. Note: Site Studio does not load its project information when the Standalone applications are launched. Therefore the Site Studio links will not be properly evaluated if a rebuild or index update cycle is started and completed by a standalone application. Managing Repository Content 2-35 – Absolute or full URLs: http:sitenodedoc.htm – Friendly links to nodes --ssServerRelativeSiteRoot--dirdirindex.htm [--ssServerRelativeSiteRoot--]dirdirindex.htm =ssServerRelativeSiteRootdirdirindex.htm – Friendly links to pages --ssServerRelativeSiteRoot--dirdirdoc.htm [--ssServerRelativeSiteRoot--]dirdirdoc.htm =ssServerRelativeSiteRootdirdirdoc.htm

2.6.7 Link Administration