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...

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 the SAP GUI 7.10 an error popup with the text
“SAPGUI: Not all data for SAP GUI shortcut is available. System ID is unknown. Enter missing data.”
will be displayed. Starting with patch 15 of the GUI 7.10 the user will be informed that the specified file does not exist.
Other terms

SAP GUI for Windows, SSF, Portal, IE6
Reason and Prerequisites

This problem only occurs with Internet Explorer 6. The SAP Shortcut file is download by Internet Explorer but it is deleted by the IE again prior to trying to start the SAP GUI. Therefore SAP GUI cannot open the connection.
This problem does not occur with Internet Explorer 7 or later.
Solution

Since both Internet Explorer 6 and Windows XP are in the extended support phase, Microsoft does not provide any non-security relevant bug fixes anymore for these products.
Even if a fix could be obtained from Microsoft, every customer who would like to have this fix would have to pay a subtantial price for it.
Therefore, SAP recommends upgrading to IE 7.

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. 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...
3. 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 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 issues relating to Portal
Platform in NW04s EhP1 SP4.

Solution

This note serves as an entry point for issues relating to Portal
Platform in NW04s EhP1 SP4.

1. 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...
2. 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...
3. 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...
4. 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...
5. KMC in EHP1 for SAP NetWeaver 7.0 SPS4: Add-On ComponentsSymptom Upgrade of KMC Portal Add-On to SAP enhancement package 1 for SAP NetWeaver 7.0 SPS4. Portal Add-On comprises the following components: FORUMS, KMC-UI and KMC-WPC. Reason and Prerequisites Release date: The...
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. 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,...
8. 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...

EP-KM

Release with approval of SAP or after consultation with SAP
For external facing portals: Untrusted external users supported with functional restrictions only
The usage of KM & Collaboration in scenarios where named untrusted or anonymous users are accessing the portal is recommended in a restricted way only. Technically, anonymous KM & Collaboration can be realized (see SAP note 728106 for details). However, it is in the responsibility of the customer project to judge whether e.g. uploading of files (virus hazard), formatted XML forms (cross site scripting) or user search in user management for external users should be allowed. SAP recommends to to run external facing scenarios only with a restricted feature exposure to users (e.g. file upload for trusted internal users only).
( Changed at 31.08.2004 )

No release
Accessing Windows file shares via JCIFS on HP-UX 11.x
Scenario: The portal server runs on HP-UX 11.x (PA-RISC or IA64 Itanium) and a KM repository manager is used to connect a Windows file share via JCIFS. Problem: If the Windows file share is accessed via the repository manager with a high load (e.g. during indexing or massive user interaction) the communication between portal and file share might fail and cause error messages. Loss of document meta data (stored in the KM database) might also occur. Repair: The root of this problem is not yet completely determined and might originate in the HP-UX libraries. Therefore, a specific date for a planned fix can not be given at this point in time.
( Changed at 04.03.2005 )

EP-KM-COL

Release with restrictions
‘Who Is Who’ iView & LDAP Search Size Limit
The number of users indexed by TREX is limited by the LDAP search size limit parameter set on the LDAP server. This means that only the number of users specified in this parameter are indexed and displayed in the Who’s Who iView. Make sure that the value of the search size limit parameter is higher than the number of users defined in LDAP. If the search size limit of the LDAP cannot be increased, the WhoIsWho will not work correctly.
( Changed at 27.12.2004 )

EP-KM-RTC

No release
Real-time collaboration (RTC) does not work in a cluster failover situation
In a clustered EP environment, real-time collaboration will not be automatically restarted after the cluster has crashed and is starting up again. A date for a fix can not yet be provided.
( Changed at 01.09.2004 )

EP-PIN

Release with restrictions
Accessibility Support (Screenreader Support)
SAP Enterprise Portal 6.0 SP2 is not yet fully accessible. Problems are occuring when using the ScreenReader software JAWS. SAP and Freedom Scientific are curently evaluation the problem and fixing as soon as possible.
( Changed at 11.05.2004 )

Fixed Limitation(s)

EP-KM

Release with approval of SAP or after consultation with SAP
Massive crawling/indexing of repositories might lead to system instabilities
Massive crawling/indexing of repositories (above ~ 500.000 documents depending on system landscape and document format) might lead to system instabilities and termination of the crawling process. This limitation is fixed with EP6.0 SP2 Patch 5.
This restriction is no longer valid.
Fixed with EP6.0 SP2 Patch 5 Content Management
( Changed at 23.05.2005 )

EP-KM-FWK-RF

No release
For EP server running on UNIX: Connecting Windows file systems not supported
Connecting Windows file systems directly via the repository framework of KM is not possible if the portal server is running on UNIX (!). A workaround via 3rd party or open source products might be applicable and would have to be done on project base. Even with a workaround in place, existing ACLs on the Windows file system will not be respected. This restriction is planned to be fixed with EP6.0 SP2 Patch 5.
This restriction is no longer valid.
Fixed with EP6.0 SP2 Patch 5 Content Management
( Changed at 22.10.2004 )

EP-KM-RTC

No release
Real-time collaboration (RTC) not supported with Japanese
Real-time colaboration is not supported for Japanese. This restriction is fixed with EP6.0 SP2 Patch 5.
This restriction is no longer valid.
Refer to SAP Note 0000761224
( Changed at 20.05.2005 )

1. Release Restrictions For SAP EP 6.0 on Web AS 6.40Symptom Information on release restrictions for SAP Enterprise Portal 6.0 on Web AS 6.40. Other terms business packages Reason and Prerequisites The statements made here, especially those referring to availability dates, reflect...