SAP EP – Netweaver Portal

Symptom
This note covers all information not included in the official “Implementing a Federated Portal Network” scenario documentation provided on SAP Help Portal at http://help.sap.com/saphelp_nw04s/helpdata/en/5b/9f2d4293825333e10000000a155106/frameset.htm. The information in this note includes known integration issues, workarounds, updated information and restrictions in SAP NetWeaver 7.0 (2004s).
This note is dedicated to cover all Remote Delta Link issues. Please refer to note 880482 as the entry point for all other categories
Other terms
SAP NetWeaver Portal, federated portal network, WSRP, federation, remote delta links, portal federation, content federation, producer, consumer, FPN

Solution
Current considerations, workarounds & restrictions:
RDL does not currently support the use of a workset within an RDL role. This issue is valid only for an FPN landscape with a NWCE 7.11 (EHP1) producer portal and a consumer portal of any release.An ‘operation failed” error occurs at runtime on a consumer portal (any supported release) that is consuming Visual Composer-based content (iView, page, or workset) from a producer portal of any supported release.Adding remote content to a local page in “end user” page personalization is not supported – remote content should not be copied to consumers where “end user” page personalization is enabled. Adding content to a remote page in “end user” page personalization is not supported – the page personalization is opened in read-only mode.When a business object copied from the producer is pasted in the Portal Catalog of the consumer, the business object folder is created automatically on the consumer as well.Copying and creating remote delta links of Web Dynpro iViews is blocked. You can only use Web Dynpro pages (or worksets / roles) for creating a Remote Delta Link to Web Dynpro-based portal content.RDL pages: If an iView is removed from the page in the producer and afterwards a property of this iView is changed in the consumer, a runtime error occurs. Currently you should perform synchronization by clearing the consumer cache or by waiting for a regular synchronization when accessing the content on the consumer.Navigating to remote-delta-linked Web Dynpro applications: On a consumer portal you should not use dynamic parameters for addressing remote Web Dynpro iViews or Web Dynpro pages (e.g. when addressing those objects with Object-Based Navigation or Relative Navigation). During runtime the dynamic parameters will not be forwarded from the consumer portal to the Web Dynpro application executed on the producer.If content properties have been updated on the producer portal by a content administrator, and the changes are not seen on the consumer portal, then the content admin on a consumer portal should refresh the display of the remote Portal Catalog to ensure that the most up-to-date Portal Catalog structure is displayed (by choosing Refresh in the content menu of the producer’s Portal Content folder). The reason for this is that a consumer portal caches the Portal Catalog structure exposed by a remote producer portal at preset intervals in order to improve portal performance by reducing roundtrips between the producer and consumer portals.
Note that if in your organization a content administrator does not know when content is updated on the producer, then whenever you browse the Portal Catalog of a remote producer you may want to first refresh the Portal Content to ensure that the most up-to-date Portal Catalog structure is displayed; this however has a drawback on performance while the update is being performed (as a result of roundtrips between the producer and consumer)The only objects that are supported for RDL usage are: iViews, pages, worksets, roles and folders. Although the portal might allow an administrator to copy other semantic object types in the Portal Catalog as an RDL, these are not supported.known interoperability issues, in specific versions, related to remote delta links (RDL) functionality used in an FPN landscape- refer to note 1272993.Changing JNDI identification (ID) of the object at the producer side is not supported. ID of the content object cannot be changed after performing an copying and pasting “as local content”. This operation will cause unresolved remote delta links of the dependant objects at the consumer side, and runtime errors.
Solved restrictions:
IMPORTANT: Remote delta link functionality (an enhancement to the ‘remote content copy’ mode) is supported as of SAP NetWeaver 7.0 SPS 10. This functionality must not be used in earlier SAP NetWeaver versions (SPS 09 and before).Remote delta links are only supported for iViews and pages.
FIXED with SAP NetWeaver 7.0 SPS 11: Worksets and roles are supported as well.If an end user wants to access RDL iViews / pages on the consumer, he/she needs ‘read’ permissions on the source iViews / pages on the producer as well, otherwise the iView at runtime will fail.
FIXED with SAP NetWeaver 7.0 SPS 11: The RDL permission mechanism was changed and now the permissions on the consumer object are sufficient for end users to display the remote content. This is analogous to standard delta link behavior with regard to permissions.Synchronization of changes made on objects (e.g., pages, iViews) residing inside worksets on the producer does not work correctly. The consumer portal will not receive any notification about the changes inside those objects and thus the changes are not reflected during runtime and design-time. Current workaround: change a property in the workset itself and the notification about the change will be triggered correctly (the changes are synchronized and reflected then on the consumer).
FIXED with SAP NetWeaver 7.0 SPS 14 (see note 1142111 as well).On remote pages, the included iViews inherit the property “Visible” from the producer-side iView. Thus consumer-side changes on this property will not take effect during runtime. Workaround – set the producer-side iViews in the page as visible or invisible.
FIXED with SAP NetWeaver 7.0 SPS 11.Related items (related links and dynamic navigation) are transferred to the consumer only on the initial remote delta link creation. Currently, any modifications to the related items on the producer require a full synchronization to take place before they are reflected during runtime on the consumer (using the “Synchronize” functionality).
FIXED with SAP NetWeaver 7.0 SPS 11.When a producer is deleted on a consumer, any RDL content to the respective producer will be displayed in the Portal Catalog of the consumer as legitimate content. In other words, the content will not be marked as a broken delta link. If the consumer tries to run this content it will not function.
FIXED with SAP NetWeaver 7.0 SPS 13.If a folder was created on the consumer portal using Remote Delta Links(RDL), then the name of this folder cannot be changed by a content administrator on the consumer portal. When trying to change the name of a RDL folder, the portal stops responding for that user and cannot complete the action.
FIXED with SAP NetWeaver 7.0 SPS 19 / EHP1 for SAP NetWeaver 7.0 SPS 03.
.