SAP EP – Netweaver Portal

Symptom
Information on release restrictions for SAP Enterprise Portal 6.0
Other terms
business packages
Reason and Prerequisites
This note lists restrictions and cautions for the productive use of certain functions of SAP Enterprise Portal 6.0.
For a list of Business Packages released on EP 6.0 and corresponding restrictions consult SAP note 642775.
Solution

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 )