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). Refer to the contents of this central note and to other related notes that may be linked to this note.
For a list of general known limitations of the portal in SAP NetWeaver 7.0 (2004s), see SAP Note 853509. We recommend you review the limitation note (853509) before reviewing this note.

Other terms

SAP NetWeaver Portal, federated portal network, WSRP, federation, remote role assignment, remote delta links, remote content copy, portal federation, content federation, producer, consumer, FPN
Reason and Prerequisites

-
Solution

General

Current considerations, workarounds & restrictions:
When a producer blocks access from a consumer, the block is applied only after the dedicated cache on the consumer is cleaned.When a consumer blocks access to a producer, the block is applied to the current users only after a new browser session is opened by them on the consumer portal.The consumer cannot monitor activities performed on the producer content (portal activity reporting and Activity Data Colector (ADC) cross-portals is not supported).Themes: To enable a continuous end user experience and display all local and remote content with the same theme (the theme of the consumer), you should import the consumers’ theme to all producers. You do not need to assign this theme to any users; however the same theme with the same ID should be available to render the content accordingly.Transitive content sharing is not supported. In other words, a portal cannot share remote-based content that is consumed from another remote producer portal. You can only have direct consumer-producer relationships, and not three or more levels in a federation.FPN administrative tasks like assigning remote roles to users or creating remote delta links to the local pcd should be performed only by registered users – not guest users. This is due to FPN services that require low security zoneModify registration option (available since NetWeaver 7.0 SPS 13): If the target host and port are changed and saved the previous values are not available and not restoreable anymore.Modify registration option (available since NetWeaver 7.0 SPS 13): The current flow requires some change in the producer object editor and only then the “modify registration” option is enabled.Configuring the Navigation Cache – Navigation Cache preloading – It is not possible e to preload remote roles using the CachePreloaderService. This service can be used to upload only locally defined roles. Configuring the navigation cache cannot be used for the gpn navigation connector. For more details, refer to note 1172433.Locality of portal services – In general, with all kinds of portal integration options (standard AppIntegrator or FPN), portal service that runs on remote portal runs locally on the machine it was called from. That it, in FPN scenario the portal service that is invoked from the producer portal is running on the producer local. This is unless the service is doing some special treatment for this scenario

Solved restrictions:
‘External host name’ value is copied by default from the ‘P4 host name’ property instead of from the ‘Host name’ property.
FIXED WITH SAP NETWEAVER 7.0 SPS 16: The correct producer object property – ‘Host name’ is set to ‘External host name’ property by default. This property is editable using the property editor of the producer object.The detailed navigation entry “Configure My Producer Profile” does not contain any content.
FIXED WITH SAP NETWEAVER 7.0 SPS 12: The option has been removed from the Detailed Navigation entry under “Federated Portal”.All producer systems must also be created on the consumer.
FIXED with SAP NetWeaver 7.0 SPS 07: Systems do not have to be created on the consumer anymore.Consumer and producer portals must reside in the same domain.
FIXED with SAP NetWeaver 7.0 SPS 09: This can be achieved using reverse proxies that support portals in multiple domains. A detailed document that describes how to implement a federated portal network whereby the producer and the consumer are not in the same domain, is available at https://www.sdn.sap.com/irj/sdn/howtoguides SAP NetWeaver 2004s, User Productivity Enablement, Running an Enterprise Portal.Reverse proxy is not supported: Despite being documented in the release notes as supported, usage of a reverse proxy in FPN scenario has not been validated. Reverse proxy as part of the FPN environment is not supported when using remote role assignment.
FIXED with SAP NetWeaver 7.0 SPS 09: A configuration guide provides instructions on how to implement a federated portal network with reverse proxy as part of the environment (can be found at: https://www.sdn.sap.com/irj/sdn/howtoguides SAP NetWeaver 2004s, User Productivity Enablement, Running an Enterprise Portal, “How to Set up Federated Portal Network Scenarios with Reverse Proxies”).Setting up trust on the producer: The following documentation (http://help.sap.com/saphelp_nw2004s/helpdata/en/43/2235260b413fe1e10000000a11466f/frameset.htm) contains an error. For the parameter “trustedsys1″ in Visual Admin, Security Provider the right description is: “Client ID: Specifies the client ID as specified in the login.ticket_client property of the UME Provider in the consumer portal. For a Java stack, the default client ID is 000; however, in an Add-In installation, the client ID must be unique and therefore cannot be 000.”
DOCUMENTATION FIXED with SAP NetWeaver 7.0 SPS 11.When registering the consumer to the producer (”Producer Registration”), the option “Your Consumer URL” must contain the P4 port of the consumer minus 4. (For example, if the consumer’s P4 port is 50005 then the consumer URL should be as follows: http://myportal.com:50001)
FIXED with SAP NetWeaver 7.0 SPS 13: The UI for registering the producer were adjusted (no consumer URL field available anymore).The portal does not enforce using unique names for the consumer name. However, to avoid runtime errors, you must ensure that each consumer portal uses a unique name.
FIXED with SAP NetWeaver 7.0 SPS 14: you cannot register two producers objects with the same consumer name.When an administrator creates a new producer with the id that is already used by an existing system as an alias, the primary alias for the producer is not created automatically (as expressed by the warning message). When administrator adds manually a primary alias to the producer (in producer alias editor), the UME is not notified and the primary alias does not appear in the data source list for the Identity Management UI. Workaround: Create a new producer with id that is different from an existing system alias.
FIXED with SAP NetWeaver 7.0 SPS 18 / EHP1 for SAP NetWeaver 7.0 SPS 03When an administrator creates a new producer with an id that is already used by an existing system as alias, the primary alias for the producer is not created automatically (as expressed by the warning message). When administrators tries to delete this producer, the delete wizard hangs without any progress. Workaround: Delete the producer object manually using the PCD inspector tool. The producer is located at pcd:NetWeaver_content_producers.
FIXED with SAP NetWeaver 7.0 SPS 18 / EHP1 for SAP NetWeaver 7.0 SPS 03
Please find below list of dedicated notes per topic:
1295703 FPN: User Persistence
1295704 FPN: Remote Role Assignment
1295705 FPN: Remote Content Copy
1295706 FPN: Remote Delta Link
1295708 FPN: Applications
1295709 FPN: WSRP
1080080 FPN: System copy

1. Performing SAP System Copy in a Federated Portal LandscapeSymptom You are performing a SAP system copy to systems that are part of a federated portal landscape. Other terms SAP system copy, guidelines, SAP NetWeaver, federated portal network, FPN, producer, consumer,...
2. FPN: Remote Role AssignmentSymptom 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...
3. SAP NetWeaver Portal Platform NW7.0, SPs19 Central noteSymptom This is the Central Note for Portal Platform as part of SAP NetWeaver 2004s SP Stack 19. Reason and Prerequisites This note serves as an entry point for issues related to...
4. SAP NetWeaver Portal Platform NW701, EhP1 SP4Symptom This is the Central Note for Portal Platform as part of SAP NetWeaver 2004s EhP1 SP4. Other terms 7.01 SP04 Reason and Prerequisites This note serves as an entry point for...
5. SAP Shortcut doesn’t get started using IE6 from SAP PortalSymptom When trying to launch transactions from the SAP Portal using an SAP Shortcut file (SSF, extension: .sap), an error popup may be displayed. For GUIs upto and including patch 14 of...
6. KMC in SAP NetWeaver 7.0 SPS19Symptom Upgrade of the functional unit KMC to SAP NetWeaver 7.0 SPS19. This functional unit consists of KMC-BC, KMC-CM and KMC-COLL. Reason and Prerequisites Release date: The date of the release of...
7. KMC in EhP1 for SAP NetWeaver 7.0 SPS4Symptom Upgrade of the functional unit KMC to SAP Enhancement Package 1 for SAP NetWeaver 7.0 SPS4. This functional unit consists of KMC-BC, KMC-CM and KMC-COLL. Reason and Prerequisites Release date: The...
8. Known Issues: Visual Composer, EHP1 for SAP NetWeaver CE 7.1Symptom Known issues related to features of Visual Composer for SAP enhancement package 1 for SAP NetWeaver CE 7.1 Other terms Known issues Reason and Prerequisites Known issues of Visual Composer for...

You are performing a SAP system copy to systems that are part of a federated portal landscape.
Other terms

SAP system copy, guidelines, SAP NetWeaver, federated portal network, FPN, producer, consumer, test system, development system, production system
Reason and Prerequisites

-
Solution

SAP provides a standardized set of procedures that enables you to copy a SAP system#both ABAP and Java#to create consistent duplicates for test, production, or development purposes or to build up your landscape. You can also migrate an SAP system to another operating system or database. The system copy for an SAP NetWeaver installation is based on the standard system copy for SAP systems. For detailed information about planning a system copy, copying SAP systems, and testing your system copy, go to http://service.sap.com/systemcopy on SAP Service Marketplace.
This note provides information regarding use of SAP system copy in a federated portal network (FPN) landscape. Before the system copy takes place, certain prerequisites and guidelines need to be implemented in order to maintain the functionality of remote-based content consumption and the relationships between portals on the new systems after the system copy has taken place.

IMPORTANT: For SAP NetWeaver 7.0 SPS13 and earlier, SAP system copy does not support FPN-based content on consumer portals.

As of SAP NetWeaver 7.0 SPS14, SAP system copy supports FPN-based content on consumer portals. For guidelines on how to ensure data integrity when performing a SAP system copy in an FPN landscape, see the “How to Copy SAP Systems in a Federated Portal Network” guide on SAP Developer Network (https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/60cc9073-4f53-2c10-3aac-a51f8c60bc1b).

1. Central Note: Federated Portal Network (SAP NetWeaver 7.0)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...
2. FPN: Remote Role AssignmentSymptom 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...
3. SAP Shortcut doesn’t get started using IE6 from SAP PortalSymptom When trying to launch transactions from the SAP Portal using an SAP Shortcut file (SSF, extension: .sap), an error popup may be displayed. For GUIs upto and including patch 14 of...
4. SAP NetWeaver Portal Platform NW701, EhP1 SP4Symptom This is the Central Note for Portal Platform as part of SAP NetWeaver 2004s EhP1 SP4. Other terms 7.01 SP04 Reason and Prerequisites This note serves as an entry point for...

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 Role Assignment issues in FPN. Please refer to note 880482 as the entry point for all other categories

Other terms

SAP NetWeaver Portal, federated portal network, federation, remote role assignment, portal federation, content federation, producer, consumer, FPN

Solution

Current considerations, workarounds & restrictions:
Remote roles cannot be displayed when using the “light framework page” (which is described more in detail in the IT scenario variant “Implementing an External-Facing Portal”).Anonymous users on the consumer must not be assigned to remote roles. This is due to the fact that anonymous guest users cannot use the FPN services that are included in low security zone (anonymous users reside in security zone: none).You should use one central user repository for all portals in your federation in order to take full advantage of RRA.
If you use multiple user repositories in your federated portal network (for example, consumer portal uses LDAP directory server and the producer portal ABAP CUA) then remote roles can be assigned to users only, not to groups. This is because the groups themselves and the users included might not be consistent in the federation, and thus a security risk might occur when remote roles are assigned to groups. In case you foresee these issues, you could consider using Remote Delta Links for roles instead and assign those RDL-roles then to groups on the consumer portal.Moving and renaming producer roles: If a consumer has assigned a remote role to users and this role is moved or renamed on the producer, then the remote role assignment on the consumer will be lost. In such an event, the consumer administrator needs to reassign the remote role to the users.When using a central Identity Management tool, some conflicts might occur when using RRA. When assigning a remote role to a user on the consumer portal, the same assignment automatically takes place on the producer portal for this user. This might conflict with the assignments done with the Identity Management tool. In case you encounter or foresee this issue in your landscape, you could consider using remote delta links (RDL) instead: Thus copy the remote role as an RDL to the PCD (Portal Content Directory) of the consumer portal and then assign this role to the consumers’ users with the help of the Identity Management tooThe remote role assignment feature may not work properly if a custom PCD filter is deployed, and the filter returns different nodes for different users. In such cases, an administrator can integrate remote content by using the remote delta link feature.

Solved restrictions
It is not possible to transport proxy-to-remote roles.
FIXED with SAP NetWeaver 7.0 SPS 09 : new UME based user interface for Remote Role Assignment is available and proxy-to-remote roles don’t have to be created anymore.Proxy-to-remote roles cannot be deleted using the portal UI, but only using the Identity Management dedicated interface.
FIXED with SAP NetWeaver 7.0 SPS 09.RRA supported only in cases where the producer and consumer are both running the same SPS version.
FIXED with SAP NetWeaver 7.0 SPS 09 by removing the need to create a proxy-to-remote role, and instead being able to directly assign users/groups to remote roles using the standard role assignment UI.The remote roles of a producer are not displayed in the User Administration of the consumer after restart of the server. There are two workaround for SAP NetWeaver 7.0 SPS 10 and SPS 09 available for this issue: 1. Give read permissions to group “Everyone” for the producer object on the consumer – then after server restart the producer will successfully be registered with UME. 2. Restart the com.sap.portal.ivs.global.gpnavigationconnector service once after each server restart to register the producers with UME.
FIXED with SAP NetWeaver 7.0 SPS 11.If one producer is down, the consumer cannot display any content (you might receive a blank screen with an error message).
FIXED: patches available for SAP NetWeaver 7.0 SPS 09, SPS 10 and SPS 11 – see note 1025374.If one producer portal is down, no remote content can be displayed at all (even if only one portal is down, all connected producer portals are affected).
FIXED: patch available for SAP NetWeaver 7.0 SPS 10 and SPS 11 – see note 1033804.In SAP NetWeaver 7.0 SPS16 and earlier, when a user administrator unassigns a remote role from a user in the consumer portal, there may be cases where the remote role is successfully unassigned in the consumer portal, but the local unassignment in the producer portal is incomplete. Workaround: Manually unassign the local role from the specific user at the producer portal. FIXED: This issue has been fixed as of SAP NetWeaver 7.0 SPS17

1. Central Note: Federated Portal Network (SAP NetWeaver 7.0)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...
2. FPN: Remote Delta LinkSymptom 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...
3. Performing SAP System Copy in a Federated Portal LandscapeSymptom You are performing a SAP system copy to systems that are part of a federated portal landscape. Other terms SAP system copy, guidelines, SAP NetWeaver, federated portal network, FPN, producer, consumer,...
4. Task list assignment to users with identical namesSymptom You would like to create an ad-hoc task list and use the “Add task” button. You select such a recipient who exactly has the same first and last name like another...