Implementing a Federated Portal Network (Enhanced & Changed) 
Function is |
Enhanced and Changed |
Release |
Software Component
|
Assignment to application component |
EP-PIN-FPN |
Country setting |
Valid for all countries |
The following features have been added and enhanced in this release:
Improved Producer Connection Tests for Remote Role Assignment (RRA) and Remote Delta Link (RDL) Usage (Enhanced)
The existing Producer Connection test for federated portal networks (FPN) has been enhanced. A system administrator on the consumer portal can now test the readiness and integrity of RRA and RDL configurations between the consumer and a remote producer. The tests can be run before consuming content or later if problems occur at runtime or design-time.
The tests check various aspects of FPN configuration and functionality. If problems are detected, the test results provide relevant explanations and solutions, where possible.
More Information: Testing Remote Role Assignment Integrity and Testing Remote Delta Link Integrity.
Adding Remote Delta Objects Directly to Roles, Worksets, and Pages (Enhanced)
In previous releases, before a content administrator on a consumer portal could add a remote object as a delta link to a local page, workset, or role, the administrator had to first create a copy of a remote object in the local Portal Catalog (using the context menu action) of the consumer portal. Only then could the copied unit object in the local Portal Catalog be added to a page, workset, or role.
Now, a content administrator on a consumer portal can add a remote object directly from a remote producer to a local page, workset, or role as a remote delta link, without having to first create a unit object in the local Portal Catalog.
The previous method of copying using is still available.
More Information: Copying Remote Content to Your Consumer
Existing Portal Services Moved to a New Application (Changed)
The following portal services have been reassigned to a new application called com.sap.portal.fpn.rdl:
OriginalContentSynConsumerService (originally in the com.sap.portal.fpn.contentmanagement application). This service allows an administrator from the consumer portal to set the automatic content synchronization interval of remote delta link objects and to set the cleanup interval of unresolved remote delta link objects in the consumer portal.
FPNProducerService (originally in the com.sap.portal.fpn.designtime.services application). This service allows an administrator to set the content invalidation policy for remote delta link objects.
The existing properties in each application remain the same as before and there is no change in functionality.
Caution
If you have changed the default value of any property in any of these applications, you need copy their values and then, after upgrading to the new Support Package Stack, apply them manually to the same service in their new application.
More Information:
Configuring Caching for the Federated Portal (for OriginalContentSynConsumerService)
Setting the Content Invalidation Policy for Remote Delta Links (for FPNProducerService)
Locating the P4 and SAP Message Server Connection Information (Documentation Update)
Documentation about finding the P4 and SAP Message Server connection information using Visual Admin has been corrected.
To obtain the P4 port on a SAP NetWeaver 7.0 portal, use the Visual Admin to access the property sheet of the P4 Provider service, then open the Runtime tab > Local Broker pane > Info tab.
To obtain host name and port information, use the Visual Admin to access the property sheet of the Message Info service, run the procedure described in Message Info Service, and then open the Runtime tab > Parameters tab. The host name and port are listed in the server host and ms/http_port parameters, respectively.
Setting Up a HTTP-Based Producer-Consumer Communication with HTTPS-Based Client-Consumer Communication (Documentation Update)
Documentation about setting up an HTTP-based producer-consumer communication with HTTPS-based client-consumer communication has been corrected.
A step that describes the need to create an additional property in the producer object and assign the HTTPS port number of the producer portal was added to the existing procedure.
More Information: Security Aspects (in Security-Related Information and Tasks for Consumers section)
Transporting Remote Delta Link Content (Documentation Update)
Unresolved delta links are generated on the target consumer portal if the source consumer contains remote delta link content that have dependencies in the com.sap.pct.* namespace on the source producer. This is standard behavior since the portal transport mechanism prevents the packaging of objects and dependencies of content in the com.sap.pct.* namespace so that SAP-reserved content is not overwritten on the target system. An automated feature has been added to this release that attempts to fix the unresolved delta links on a target consumer portal following the import of a transport package that contains remote delta link content.
The system administrator still needs to perform some additional manual steps following the import to the target consumer portal. These steps are now documented.
More Information: Transporting Content within a Federated Portal Network