Integrating SAP Portal Content into Other Portal Servers
Feature |
Type of Change |
Description |
---|---|---|
Setting Up Interoperability Between SAP and Third-Party Portals |
New |
A new set of procedures has been added to the portal documentation outlining the tasks you follow to configure SAP Portal content so that it can be integrated into content on non-SAP portals. The documentation covers creating the content, defining single sign-on, setting parameters to ensure smooth session management, and aligning the look-and-feel of the SAP Portal content with that of the target portal. For more information, see Integrating SAP Portal Content onto Other Portal Servers . |
Implementing a Federated Portal Network (FPN)
Feature |
Type of Change |
Description |
---|---|---|
Introduction of New 'FPN Connection' Concept |
New |
A new concept called FPN connections has been introduced in this release, and is aimed at lowering overall TCO of FPN in comparison to previous releases. Before two portals can interact and share content with each other, a system administrator needs to make a logical connection between the portals in the federated portal network. In previous releases, this connection could only be initiated and created from the consumer portal, and the sharing of content was uni-directional (from producer to consumer). In addition, if two portals shared content with one another in both directions, two separate FPN registration instances were required (each initiated from the respective producer portal). The new FPN connection concept provides the following enhancements:
For more information, see Managing FPN Connections . |
Addition of Consumer Capabilities |
New |
In SAP NetWeaver Composition Platform (CE) releases prior to this release, the SAP NetWeaver CE systems could only function as a producer portal. With SAP NetWeaver 7.3, if you install usage type EP Core - Application Portal (EPC), you can now configure the portal also as a consumer of remote content from any remote producer portal running SAP NetWeaver 7.0, SAP NetWeaver CE 7.1, SAP NetWeaver CE 7.2, or SAP NetWeaver 7.3. You can also consumer WSRP content from any third-party portal that is WSRP-compliant. For more information, see: |
FPN Integration with System Landscape Directory (SLD) |
New |
If you have incorporated the systems in your landscape in the SLD, you can quickly create FPN connections between your system and remote systems with a single click. There is no need to manually enter connection settings - the default connection settings of your system are already defined in the FPN Control Panel, and the connection settings of the remote system are already defined in the SLD. For more information, see: |
WSRP-Compliant Applications Available in GPAL Repository |
New |
A new WSRP Content repository has been added to the GPAL repositories folder in the Portal Catalog in the Portal Content Studio. The repository displays WSRP applications from SAP NetWeaver and non-SAP portals. A content administrator can create iViews from remote WSRP-compliant applications that are exposed via this repository. For more information, see Creating Proxy-to-Portlet iViews . |
New and Redesigned FPN Editors and Wizards |
New and enhanced |
To support the introduction of the new FPN connection concept, new and improved editors and wizards are now available in the FPN administration environment in the portal, which significantly improve productivity and reduce overall TCO for the remote role assignment and remote delta link usage modes:
For more information, see Managing FPN Connections . |
Improved Producer Connection Tests for RRA and RDL Usage |
Enhanced |
The existing Producer Connection test for federated portal networks 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. For more information, see: |
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.For more information, see Copying Remote Content . |
Renamed FPN Folder in Portal Catalog |
Changed |
The Remote NetWeaver Producers folder has been renamed to Remote FPN Producers . For more information, see Copying Remote Content . |
Changed Location of Registration Password Configuration |
Changed |
You no longer define the registration password in the AutoGenProducer1_0 service in SAP NetWeaver Administrator on the producer system. The previous REGISTRATION_PASSWORD property has been deprecated. You now define the registration password in the FPN Control Panel in the producer portal. For more information, see Setting a Registration Password . |
Portal Services for FPN Moved to a New Application |
Changed |
The following portal services have been reassigned to a new application called com.sap.portal.fpn.rdl :
The existing properties in each application remain the same as before and there is no change in functionality. Caution
If you are upgrading from an earlier release and have changed the default value of any property in any of these applications, you need to copy their values and then, after upgrading to the new release, apply them manually to the same service in their new application. For more information, see:
|
Changes to Cache Lifetime Settings on the Consumer Portal |
Changed |
The following changes have been introduced:
For more information, see Configuring the Federated Portal Cache on the Consumer Portal . |
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. For more information, see Transporting Content within a Federated Portal Network . |