Portal, Express Beta Version 6.1 Operating systems: i5/OS, Linux,Windows

Contextual linking

Contextual linking is used in systems where content from one site is shared across multiple sites. When content is linked into a site, embedded links (link elements and links in HTML) will reference site the original content item is located in. Contextual linking is used so that when content is linked from another site, the link will be rendered relative to the current site if possible.

Contextual content linking

Contextual content linking will attempt to resolve a link by searching for content links. Contextual content linking assumes that only one content link exists within a single Web content library. It is used if context=current or context=autofill.

• <Element type="content" context="current" key="body" link="contextual" />

1. For links to Content:

   1. A content link for the same content item in the current library is looked for.
   2. If none are found, an item on the same relative path is looked for.
2. For links to Content Links, Site Areas, Sites Try an item on the same relative path is looked for.

Contextual path linking

Contextual path linking will attempt to resolve a link using a relative path technique. Contextual path linking assumes that each site framework that the linked content is stored in has the same site structure.

• <Element type="content" context="current" key="body" link="path" />

When contextual path linking is used a compatible link is searched for using the same relative path. If no link is found, a link using a similar path higher up in the site framework is searched for.

Set up the Missed Absolute Path Cache

To improve the performance of contextual linking you can enable a Missed Absolute Path Cache. The Missed Absolute Path Cache functionality requires a dynamic object cache to be setup in WebSphere Application Server before it can be utilized.

Non-clustered environment

1. Login to the WebSphere Administrative console for your server.
2. Go to Resources tree > Cache Instances .
3. Click Object cache instances.
4. In the scope section, select the node on which your server is located and then select the server on which the cache is to be set up.
5. Click Apply to save your choices.
6. Click New to create a new cache.
7. Enter missedabspath in the Name field and services/cache/iwk/missed in the JNDI name field. These values are used to lookup the cache and use it. Leave all other fields set to their default values.
8. Click OK at the bottom of the form and then Save.
9. To enable the cache for your Web content, edit the WCMConfigService.properties file and ensure missed_absPath.cache.enable=true .

   The WCMConfigService.properties file is located in the was_profile_root/PortalServer/wcm/config/ directory. You will need to restart WebSphere Portal to enable any configuration changes made to this file.

Clustered environment

1. Login to the WebSphere Administrative console for your server.
2. Go to Resources > Cache Instances > Object cache instances .
3. Click the Browse Clusters button and choose the cluster that you want to create the cache for.
4. Click Apply to save your choices.
5. Click New to create a new cache.
6. Enter missedabspath in the Name field and services/cache/iwk/missed in the JNDI name field. These values are used to lookup the cache and use it. Leave all other fields set to their default values.
7. Select Enable Cache Replication.
8. Go to the Full group replication domain drop-down box and select the name of the cluster you want to cache.
9. Select Choose Push-Only from the Replication type drop down box.
10. Enter 1 in the Push Frequency field. Leave all other fields set to their default values.
11. Click OK and then Save > Save > OK.
12. To enable the cache for your Web content, edit the WCMConfigService.properties file on every server in your cluster and ensure missed_absPath.cache.enable=true .

    The WCMConfigService.properties file is located in the was_profile_root/PortalServer/wcm/config/ directory. You will need to restart WebSphere Portal to enable any configuration changes made to this file.