Federated SAP Portals - a walk through
No Comment
Federated Portal Network, (often known as FPN) is desigend exclusively for remote content sharing between enterprise portals. It is a framework which enables each portal to act as a producer, exposing the content to other portals or as a consumer, using the content shared by other producer portals. For e.g. to distribute applications according to different services.
SAP also supports implementation of FPN using the SAP NetWeaver platform to share content between portals. This implementation allows existing content and configurations to be utilized, and to minimize necessary administration efforts.
Major Benefits of implementing FNP are:
- Reuse of content and applications throughout the network.
- Increased autonomy of business units.
- Integration of non-SAP portals into the SAP NetWeaver platform, allowing the exchange of WSRP-compliant applications within SAP NetWeaver Portal.
- Higher return on investment (ROI) achieved by optimized reuse of human capital and hardware resources within the company
Implementation Scenario:
The implementation scenario comprises two different parts, which are Content Federation & Portal Federation. Content Federation is the one where one portal is used for login of the users and other acts as a content providers. SAP Marketplace is a good example of such implementation. Portal Federation is the one where each portal can function as an autonomous entity serving its own content and users, but also exposing and consuming content to and from other portals in the federation.
As there are advantages, there are ought to some disadvantages of FPN, you can access SAP Note 880482 for more clarification.
FPN Caching
SAP NetWeaver Portal provides a dedicated caching service (FederatedPortalCache) for the federated portal scenario. Its primary purpose is to reduce network trafficking to the producer by storing semantic objects on the consumer-side for reuse. You specify the amount of time an object is kept in the cache. If a requested object is cached and is within its validity period, the consumer reuses the object instead performing a call through the network to the producer. Objects without a defined validity period inherit the validity period of the closest parent group that has a defined validity period.
To set the size and storage location of the federated portal cache:
...
- In the consumer portal, navigate to System Administration –> System Configuration –> Service Configuration.
- Navigate to the com.sap.portal.ivs.global.gpcache application.
- Edit the FederatedPortalCache service.
Set following properties:
maxCacheSize, maxValidityPeriodInSec, cachePersistency
With is the FPN cache is set and you are all set to head start your FPN implementation.
Random Posts
- None Found
Leave a comment!