Show TOC

Configuring the Federated Portal Cache on the Consumer PortalLocate this document in the navigation structure

Use

Content usage mode: remote role assignment, remote delta link

Applies to: consumers

Note

The functionality described in this topic does not apply to an SAP NetWeaver Composition Environment system without usage type EP Core - Application Portal (EPC).

SAP NetWeaver Portal provides a dedicated caching service for the consumer portals running in a federated portal scenario. Its purpose is to reduce network traffic to the producer by storing semantic objects on the consumer-side for reuse.

This topic describes how to define consumer-side cache settings.

Note

  • Once remote-based content has been cached on the consumer, any changes made to their source objects on the producer are only updated on the consumer after its cache has been updated. Cache updates occur after the cache validity expires or the cache was cleared.

  • The settings described below are global settings; you cannot define a different configuration for each producer portal.

Prerequisites

  • You have access to SAP NetWeaver Administrator.

  • You are assigned to the portal role that contains the Federated Portal workset. By default this is the System Administration role.

Procedure

Configuring Content Cache Settings on the Consumer

The following procedures (cache mode and lifetime) apply to:

  • Runtime content that has been cached on the consumer through the use of the remote role assignment mode.

  • Content viewed through a remote Portal Catalog on a consumer portal (refers to the remote delta link mode). See Copying Remote Content .

  • Specific remote delta link use cases, such as SAP transaction iViews embedded in remote delta link pages, in which case the Application Integration service retrieves properties from objects located in the Portal Content Directory (PCD) of the remote producer.

The federated portal cache has two modes:

  • Shared cache: Stores less content in the federated portal cache, in both memory and database, and reduces the amount of SOAP calls between consumer and producer portal. However, if for any reason a user inadvertently causes corrupted data to be stored in the federated portal cache, this will also have a negative impact on all other users, and the only way to resolve this is to completely clear the federated portal cache.

    This is the default mode and the one recommended by SAP.

  • User cache: If for any reason a user inadvertently causes corrupted data to be stored in the federated portal cache, other users are not impacted. However, this mode has a higher impact on system performance, higher memory and database consumption (for federated portal cache), and higher network traffic as each user triggers a unique SOAP call to fill its own cache.

To configure the federated portal cache mode:

  1. In the SAP NetWeaver Administrator tool, access the following portal application and service:

    • Portal application: com.sap.portal.ivs.global.gpcache

    • Service: FederatedPortalCache

    For information about accessing and configuring portal services in the SAP NetWeaver Administrator tool, see Accessing Portal Services in SAP NetWeaver Administrator .

  2. Set the value of the userCache property as follows:

    Value

    Description

    false

    Disables the user cache mode. In other words, it enables the shared cache mode.

    This is the default setting.

    true

    Enables the user cache mode.

  3. Save your changes.

  4. Restart the service

    More information: Starting and Stopping Portal Services

To set the lifetime of content cached in the federated portal cache:

  1. In the portal, navigate to Start of the navigation path System Administration Next navigation step Federated Portal Next navigation step  SAP NetWeaver - FPN Connections Next navigation step  Control Panel End of the navigation path.

  2. Choose the Cache and Content Synchronization tab.

  3. In the Cache Lifetime Setting section, enter the maximum cache time (in minutes) in the Cache Lifetime property.

    Note

    • Set a long validity time if you know the remote content on the producer is static and undergoes few changes over a long period of time. Set a short validity time if you know the remote content on the producer is dynamic and changes frequently over a short period of time. SAP does not recommended setting a very short time period.

    • To disable the clearing of cached content, enter a value of zero ( 0 ).

  4. Click Save .

Note

For information about manually clearing the cache before the cache lifetime has been reached, refer to Clearing the Remote Role Assignment Cache .

Configuring System ID Cache Settings on the Consumer

The cache setting described here allows you to instruct the consumer to store system IDs mapped to federated portal aliases in the cache. This setting is relevant only to remote role assignment and remote delta link usage modes.

Caution

Do not activate this cache setting if you have implemented dynamic system resolution in your portal landscape. For this reason, the cache setting is deactivated by default. More information: Dynamic System Resolution .

The benefits of caching system IDs for federated portal network implementations are:

  • Decreased number of round-trips between a producer portal and consumer portal.

  • Reduced number of sessions opened on the producer portal.

  • Improved response times and overall system performance.

To activate caching of system IDs:

  1. In the SAP NetWeaver Administrator tool, access the following portal application and service:

    • Portal application: com.sap.portal.ivs.global.jndibridge

    • Service: SLGP

    For information about accessing and configuring portal services in the SAP NetWeaver Administrator tool, see Accessing Portal Services in SAP NetWeaver Administrator .

  2. Set the SaveSystemIDAtCache property to true (set to false to deactivate caching).

  3. Save your changes.

  4. Restart the service

    More information: Starting and Stopping Portal Services

Setting the Synchronization Interval of Remote Delta Links Content

The cache settings in the OriginalContentSynConsumerService service define the frequency with which remote delta link content on the producer is updated when modifications are made to the source objects on a producer portal.

By default, the producer portal automatically updates content modifications made to source objects with their corresponding target delta link objects on the consumer portal once every 24 hours. A system administrator on the consumer can do the following:

  • Change the default interval at which remote delta link content is updated on the consumer portal (see below for instructions).

  • Manually synchronize remote delta link content with their corresponding source objects (see Synchronizing Remote Delta Link Content for instructions).

Note

An administrator on the producer portal cannot initiate a content update with its registered consumer portals. It can only be initiated from the consumer portal.

Caution

  • Synchronization can be a very time consuming process, especially if you are consuming large amounts of remote delta link content.

  • After delta link content synchronization, portal users must restart any live portal sessions to receive the latest updates.

To set the interval of automated remote delta link content synchronization:

  1. In the SAP NetWeaver Administrator tool, access the following portal application and service:

    • Portal application: com.sap.portal.fpn.rdl

    • Service: OriginalContentSynConsumerService

    For information about accessing and configuring portal services in the SAP NetWeaver Administrator tool, see Accessing Portal Services in SAP NetWeaver Administrator .

  2. In the sampleDelayMinutes property, enter the time delay in minutes from when the server starts up to when the first automatic synchronization takes place. The default value is 1,440 minutes (24 hours).

    Note

    Enter a positive value only.

  3. In the sampleRateMinutes property, enter the synchronization interval in minutes. The default value is 1,440 minutes (24 hours).

    Note

    To turn off the automatic synchronization, enter 0 or -1 .

  4. Save your changes.

  5. Restart the service

    More information: Starting and Stopping Portal Services

To set the cleanup interval of unresolved remote delta links on the consumer:

After content has been synchronized between a producer portal and a consumer portal, any source content that has been removed from a producer portal may result in corresponding unresolved remote delta links on a consumer portal.

If you replace the removed source content on the producer portal with new content that has the same object ID, functionality of the remote delta links on the consumer portal is restored. You can however, instruct the portal to delete the unresolved remote delta links if they have exceeded a predefined period of time. Doing so prevents unresolved content from congesting the Portal Content Directory (PCD) over time.

  1. In the SAP NetWeaver Administrator tool, access the following portal application and service:

    • Portal application: com.sap.portal.fpn.rdl

    • Service: OriginalContentSynConsumerService

    For information about accessing and configuring portal services in the SAP NetWeaver Administrator tool, see Accessing Portal Services in SAP NetWeaver Administrator .

  2. In the UnresolvedKeepDays property, enter the maximum time period (in days) to keep a content object that is tagged as an unresolved remote delta link on the consumer portal. The default value is 365 days.

    Note

    • Enter a positive value only.

    • Enter 0 to delete unresolved remote delta link content immediately.

  3. In the UnresolvedCleanupSampleRateMinutes property, enter the time interval (in minutes) at which the consumer portal checks if the source object of content, already tagged as an unresolved delta remote link, has been restored on the producer portal. The default value is 1,440 minutes (24 hours).

    Note

    • Enter a value equal to or higher than -1. Note that the lower the value, the greater the negative impact is on system performance.

    • Enter 0 or -1 to disable the deletion of unresolved remote delta links. If after an unresolved remote delta link check has run and any unresolved content has exceeded the maximum keep time, then the content is permanently deleted from the consumer portal.

  4. Save your changes.

  5. Restart the service

    More information: Starting and Stopping Portal Services

More Information