SAP Basis Tech Supports

Symptom
Release restrictions of SAP NetWeaver 2004s – Usage Type Enterprise Portal (EP)

Reason and Prerequisites
At the time of the release of SAP NetWeaver 2004s limitations existed concerning the productive usage of certain functions of the usage type Enterprise Portal. This note provides customer information on these restrictions.
Restrictions regarding the availability of SAP NetWeaver 2004s on specific platforms are documented in the Product Availability Matrix. Please find details about operating systems, databases, and browsers supported by SAP NetWeaver 2004s on SAP Support Portal:
http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000651812&
Solution

Open Limitation(s)

EP-BC-UWL

Release with approval of SAP or after consultation with SAP
UWL : Accessibiblity : UWL Tasks Table
UWL Accessibility Limitations related to UWL tasks table From performance and small memory footprint considerations UWL loads the WebDynpro context for the UWL Table only with the number of visible rows. The WebDynpro navigation is replaced with a UWL version to allow loading the next and previous pages as needed and it displays the actual tasks count. This leads to an issue during accessibility where the UWL Table announces the number of tasks incorrectly if there is more tasks than the visible rows. Currently there is no solution or workaround Another side effect from this UWL customizations of the UWL table is that when tabbed in the UWL table navigation area focus is set to the label of the editable text field. Ideally there should be no focus on the label. WebDybpro components do not allow turning off the Tabbing and there is no way for UWL to prevent this
( Changed at 08.12.2008 )

EP-KM

No release
Taxonomies in combination with versioning and statemanagement are not supported
KM Taxonomies based on Query based Classfication on top of repositories where both the statemanagement service and versioning are activated and actively used at the same time is not supported currently. Using KM in this combination causes functional issues when browsing taxonomies. Files might not be shown in the taxonomy although being published, different versions of the same file might be listed in a category.
( Changed at 19.01.2009 )

EP-KM-WPC

Release with restrictions
Web Page Composer (WPC): Adding portal iViews to WPC pages
There are two limitations when integrating iViews into a WPC page: 1. URL iViews They cannot be integrated into WPC pages. If an attempt is made to do this, a runtime exception occurs with error message ‘Cannot read parameter siteString from PCD’. Background: URL iViews redirect the request and must always be the topmost element in a page layout. There are several ways to overcome this situation: – Implement a custom iView. In the doContent method of this custom iView you can e.g. render an iFrame that displays content identified by a URL. – Add the URL iView directly to any container using a (custom) layout template JSP. If you do this, however, the URL iView cannot be changed in the WPC design time anymore. – You can setup the URL iViews via the so-called ‘Capture’ mode in iView properties – You can set them up in URL isolation mode 2. Web Dynpro iViews They can only be rendered in run-time mode but not in the design-time or preview mode. Comment: Drop Web Dynpro iViews on suitable containers in the page editor and ignore the error message in design-time and preview mode.
( Changed at 24.11.2008 )

EP-VC

Release with restrictions
Complex structured data service support
The use of SAP enterprise services is not fully supported by Visual Composer for NetWeaver 2004s SP08. This is due to an incompatibility between the “nested-table” structure of the services and the ability to expose them as such in the UI of Visual Composer Storyboard. “Nested tables” are datasets that are returned from a service in a hierarchical structure that includes array-type sub-nodes within array-type nodes. In order to extract this information, Visual Composer extracts the information to separate dedicated ports, so that information as to the context of the tables and sub-tables and their relationships is lost.
will be fixed in Convergence
( Changed at 07.07.2006 )
Models Created in Visual Composer 6.0 are not supported
Design time – Visual Composer models created in version 6.0 design time, cannot be exported to Visual Composer 2004s design time. It is not possible to open models created in Visual Composer 6.0 in Visual Composer 2004s.
( Changed at 07.07.2006 )
Visual Composer – Stored procedures support only single result sets
When using stored procedures that can return more than one result set, only the first result set is returned, or none of the results. When using JDBC-based stored procedures in SAP Visual Composer 2004s Flex runtime, note that the supported stored procedures return only a single set of results. Solution: Use stored procedures that return only a single set of results.
( Changed at 19.01.2009 )
Some functionality not supported by the Web Dynpro runtime
Some Visual Composer features are not supported by the Web Dynpro runtime, in SAP NetWeaver 2004s SPS 08: 1) Limitations in the Data model: – Data services other than Web Services are not supported – Combine operator only operates on the first set of input rows – User Data: user-specific properties maintained in the UME can not be used or displayed in the modelled application – Dynamic Entry Lists can not be sorted 2) Limitations with respect to UI Composition: – Images/mime resources are not supported and will not be displayed during runtime – Labels can only be positioned before another UI element, all other settings available in VC will be ignored – Toolbar is only available in Table View – Table View: multiple selection is not supported – Tile View: selection is not highlighted; mulitple selection not possible; paging not possible – Calendar View: previous/next navigation sometimes jumps to the wrong month 3) Infrastructure Limitations: – The absolute path length of the deployment archive may not exceed 255 characters on Microsoft Windows operating systems; please use short package and prefix names when creating new models
( Changed at 19.01.2009 )
Names limitation for controls within VC models
When defining a field in a model element (such as a form or a data service) and assigning a name that is known to be a reserved JavaScript keyword (such as ‘true’ or ‘function’), the control is created and saved with the model, but the next time the model is opened this control disappears.
( Changed at 08.12.2008 )
Visual Composer cannot manage an extremely large amount of data returned from a query to the client
The Flex client implemented with Visual Composer cannot manage an extremely large amount of data returned from a query. Because sorting and filtering is carried out in the client, the entire amount of data is delivered to the client, which may suffer an overload prior to the filtering.
( Changed at 08.12.2008 )

EP-VC-RTM-FLEX

Release with restrictions
Mozilla/Firefox limitations for Visual Composer Design Time
Visual Composer Design Time (i.e. Storybord) is not supported for FireFox browsers. This limitation does not include the Visual Composer run time, Visual Composer created iViews will run in FireFox browsers.
( Changed at 08.12.2008 )

Fixed Limitation(s)

BC-CTS-CBS

No release
System Copy for Usage Type Enterprise Portal (EP) not yet released
The system copy for usage type Enterprise Portal (EP) is not released yet. Please refer to the general note for the SAP NetWeaver 2004s Java System Copy (870863) for details.
This restriction is no longer valid.
Refer to SAP Note 0000870863
( Changed at 12.12.2005 )

BC-WD-JAV

Release with restrictions
Sizing Problem of iViews in WD pages – Automatic height of PortalIframe UI element doesn’t work
An iView can only be shown in a compressed form. It is opened but not shown completely and therefore it has a scrollbar.
This restriction is no longer valid.
Fixed as part of SPS05.
( Changed at 03.01.2006 )

EP

No release
NetWeaver 2004s BEx Web Applications Java in a NetWeaver 2004s Federated Portal Scenario
NetWeaver 2004s BEx Web Applications Java in a NetWeaver 2004s Federated Portal Scenario is not supported.
This restriction is no longer valid.
fixed with SP07
( Changed at 06.04.2006 )

EP-BC-JWF

Release with restrictions
Launch of Collaboration Task from Guided Procedures not working
It is not possible to launch a Collaboration Task from a Guided Procedure.
This restriction is no longer valid.
Fix is available in SPS06
( Changed at 02.02.2006 )

EP-BC-UWL

Release with restrictions
Number of Alerts is not displayed initially but only after clicking Alerts tab once
When the user initially logs on, he won’t see the number of alerts in the alerts tab. Only upon clicking on the alerts tab the user sees the correct number of alerts.
This restriction is no longer valid.
Handled for SPS05.
( Changed at 05.12.2005 )

EP-COL-APP-FOR

Release with approval of SAP or after consultation with SAP
Forums cannot be run productively on clustered installations with more than 8 server nodes
Forums cannot be run productively on clustered installations with more than 8 server nodes (Dialog Instances). This will lead to scalability issues which might deteriorate the performance of the complete enterprise portal installation.
This restriction is no longer valid.
Refer to SAP Note 0001149422
( Changed at 18.03.2008 )

EP-KM

Release with restrictions
Accessing Windows file share (or any SMB share) 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 or any SMB (Server Message Block protocol) 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. Solution: SAP has validated a more recent version of JCIFS for SAP NetWeaver 2004 SPS 20 / SAP NetWeaver 7.0 SPS 12 and above, which fixes this problem.
This restriction is no longer valid.
Limitation is fixed
( Changed at 17.07.2007 )
Room templates doesn’t work on IBM JDK 64-bit version
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 or any SMB (Server Message Block protocol) 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. Solution: SAP has validated a more recent version of JCIFS for SAP NetWeaver 2004 SPS 20 / SAP NetWeaver 7.0 SPS 12 and above, which fixes this problem.
This restriction is no longer valid.
Limitation is fixed
( Changed at 21.02.2008 )

No release
Knowledge Management and Collaboration for External-Facing Portal
Knowledge Management (KM) and Collaboration are released in a restricted way for scenarios where the external facing portal capabilities of NW2004s are used (i.e. reducing the network load by using the ‘light framework page’ concept of the portal): – KM and Collaboration iViews will work within the light framework page without errors. However, the network load will not be decreased since the navigation within the iViews requires the full range of scripts to be downloaded from the portal. – Browser Back/Forward navigation within KM will not work in all cases – Indexing of KM content by external search engines (Google, etc.) will not work on all content In addition, the general usage of KM and Collaboration in scenarios where untrusted (e.g.with a self-registered user ID) or anonymous users are accessing an external facing portal is recommended in a restricted way only to avoid upload of malicious files or code (e.g. disable file upload or discussion forum entries). This recommendation is true even if the ‘light framework page’ concept of NW2004s is NOT used. Please refer to SAP note 837898 for details on how to enable anonymous user access to KM (and Collaboration).
This restriction is no longer valid.
SAP NetWeaver Collaboration runs in external facing scenarios where the light framework page is used
( Changed at 26.01.2007 )
Knowledge Management & Collaboration features delivered with SAP NW 2004s SPS 05
The following features are mentioned in the documentation of SAP NetWeaver 2004s SP Stack 04 but will be solved with a later SP Stack: 1) Search with TREX across Portal Content Directory (PCD) objects; 2) Propagation of ‘Versioning’ settings across folder hierarchies; 3) ‘Portal drive’ for connecting KM repositories as mapped network drive to the Windows file exlorer; 4) Easier connection of web sites to KM by using a streamlined web repository manager configuration
This restriction is no longer valid.
Delivered features and documentation are in sync with NW2004s SP5
( Changed at 06.12.2005 )
KM does not work after upgrading from NW 2004 SPS 14 to NW 2004s SPS 05
Upgrading from SAP NetWeaver 2004 SPS 14 to SAP NetWeaver 2004s SPS 05 is not supported for KM. If there are crawlers available in the SAP NetWeaver 2004 SPS 14 installation, KM will not start up after upgrading to SPS 05. If there are no crawlers available in the system, KM will startup, but the crawler service will not work. This cannot be fixed on SAP NetWeaver 2004s SPS 05 due to technical reasons. Supported upgrade paths include: NW 2004 SPS 13 => NW 2004s SPS 05; NW 2004 SPS 13 => NW 2004s SPS 06; NW 2004 SPS 14 => NW 2004s SPS 06. If a KM installation has been upgraded from NW 2004 SPS 14 to NW 2004s SPS 05 resulting in KM not working this can be fixed by deploying NW 2004s SPS 06 on top.
This restriction is no longer valid.
Upgrade from NW04 SP14 to NW04s SP5 won’t work for KM. Customer will have to upgrade to NW04s SP6.
( Changed at 05.02.2006 )
‘Legacy CM Repository Manager’ of SAP NW 2004s SPS 06 not released
In the KM documentation of SAP NetWeaver 2004s SPS 06, the ‘Legacy CM Repository Manager’ was introduced as a possible way to perform backup / restore of KM objects (both document content and metadata). SAP recommends to not use this repository manager for productive backup & restore operations. The description of this feature has been removed in the documentation for SAP NetWeaver 2004s SPS 07.
This restriction is no longer valid.
The documentation for NW2004s SPS07 has been corrected
( Changed at 11.04.2006 )

EP-KM-COL

Release with restrictions
Knowledge Management and Collaboration: 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 Who’s Who iView will not work correctly.
This restriction is no longer valid.
Fixed with NW2004s SP6
( Changed at 23.12.2005 )

EP-PDK-HBJ

Release with restrictions
UNIX – Import from client side is not working
Can’t import any package from client side when the portal is on a UNIX machine.
This restriction is no longer valid.
The specific problem was solved as part of SPS05. The generic problem is described in note #866950
( Changed at 12.01.2006 )

EP-PIN

No release
“Implementing a Federated Portal Network” (aka Global Portal) not available with start of ramp-up
The IT scenario variant “Implementing a Federated Portal Network” (formerly known as Global Portal) will not be available with start of ramp-up.
This restriction is no longer valid.
Availble since SPS06.
( Changed at 07.11.2006 )

EP-PIN-BPO

No release
“Implementing a Multitenant Portal” not available with start of ramp-up
The IT scenario variant “Implementing a Multitenant Portal” will not be available with start of ramp-up.
This restriction is no longer valid.
Handled for SPS05.
( Changed at 05.12.2005 )

EP-PIN-FPN

No release
FPN Consumer’s CPU and Memory consumption regression
Performance Regression issues with FPN NW7.0 RRA (remote role assignment), Consumer memory and CPU show significant / critical regression from standard.
This restriction is no longer valid.
The limitation is fixed for SP15
( Changed at 25.02.2008 )
FPN Remote Delta Link – Workset Map iViews do not display expected content
Long description: When creating a Remote Delta Link from a Workset Map iView from a FPN producer and running it, the Workset Map iView on the consumer portal does not generate the expected content. See more details in note.
This restriction is no longer valid.
The limitation is fixed on SP15
( Changed at 25.02.2008 )
FPN Remote DeltaLink – Runtime error in page preview (PRT only)
A Runtime error while previewing a RDL iView inside a local page
This restriction is no longer valid.
The limitation is fixed on SP15
( Changed at 25.02.2008 )
FPN -Modify registration to a second producer and re-modify back to the original one is not possible
In the initial registration, resources are allocated on producer A under a specific name (e.g. 揷onsumerXXXRegistrationName?. When modifying the registration to Producer B, resources are allocated as well -> this is successful since the name above was never used with Producer B When modifying the registration BACK!!! to Producer A there is an attempt to allocate the resources again using the same name 揷onsumerXXXRegistrationName?and a protection that was added recently prevents this flow. The intention in this protection did not foresee the use case of modifying back the registration after is was once changed.
This restriction is no longer valid.
The limitation is fixed on SP15
( Changed at 25.02.2008 )
FPN:The first producer object created cannot be deleted.
The first producer object created cannot be deleted.
This restriction is no longer valid.
Refer to SAP Note 0000853509
( Changed at 07.10.2008 )
Changing layout in producer don’t take effect in consumer end-user
When changing layout of page (such as reordering the iViews) in the producer and synchronizing the changes using the cache management in the consumer, users won’t get the latest changes in the layout at the consumer Workaround: Administrator can edit the RDL page in the consumer and change the layout in order to make it similar to the changed producer.
This restriction is no longer valid.
The limitation is fixed on SP15
( Changed at 28.02.2008 )
FPN – Remote Delta Link – Permissions on the Remote Delta Link role
When working in a Federated Portal Network environment (FPN), implementing the Remote Delta Link (RDL) solution, the user should have read permissions on the RDL role, otherwise runtime will fail.
This restriction is no longer valid.
Fixed with SPs11.
( Changed at 10.06.2007 )
FPN – Remote Role Assignment – Synch does not work for deleted producer content
Synch does not work for deleted producer content: Producers objects aren’t shown in the drop down list of Data Source after restart of the server in the following scenario: 1. Create a Producer object and register it. 2. Navigate to User Administration, open the drop down list of Data Sources. The Producer object is presented. 3. Assign the remote roles from this producer and restart the Consumer server. 4. Navigate to the User Administration, open the drop down list of the data Sources. The Producer objects aren’t presented. Workaround for NW2004s SPs10 and SPs9: One of the two options 1. Give read permissions to Everyone for the producer objects. Now everytime the server will restart, those producers 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.
This restriction is no longer valid.
Fixed with SPs11.
( Changed at 10.06.2007 )
FPN- Support for SSL and P4 Security is disabled
Currently the support for P4 with SSL is disabled in SP13 and enabled as of SP14.
This restriction is no longer valid.
The limitation is now fixed for SP14
( Changed at 29.10.2007 )
FPN-Close browser session instead of logoff in order to keep the session secured
One user can see other user抯 content in the portal, despite the fact that the first one logged off. The workaround is to close the browser.It was fixed as of SPs13.
This restriction is no longer valid.
Refer to SAP Note 0001042841
( Changed at 13.11.2007 )

Release with restrictions
FPN – Remote Delta Links – Locales in the Consumers’ iViews
A problem might occure when using locales with the Remote Delta Link solution on a version interoperability landscape for federated portal network. Consumer portal (e.g. version SPs 10) consumes portal content from a producer portal that is on a higher release version (SPs 11, or later): In case the consumer portal uses a locale which doesn’t exist on the producer portal, the default title from the consumer is fetched. For example ?when using a Remote Delta Link page and changing the locale in the consumer to German, if the page on the producer does not have a translated German title, the page title on the consumer will be 損age?in German.
This restriction is no longer valid.
Fixed for SPs11.
( Changed at 10.06.2007 )

EP-PIN-NAV

Release with restrictions
WorkProtect for “Window Close”
The write-protect feature for closing a window is only supported for the main portal window.
This restriction is no longer valid.
Handled for SPS05.
( Changed at 05.12.2005 )

EP-PIN-OBN

Release with restrictions
OBN & FPN Remote Delta Link – OBN is not working with 04s producer and SP14 consumer
OBN with RDL is not working with 04s producer and SP14 consumer . Scenrio: In design-time of OBN in FPN environment, in RDL scenario, a Remote Delta-Link to the Target iView/Page is created on the Consumer but the implemented Operation is not copied from the Producer to the Consumer,hence OBN mechanism on the Consumer does not find this Target.
This restriction is no longer valid.
The limitation is fixed on SP15
( Changed at 25.02.2008 )
OBN: Passed parameters are corrupted when the OBN Source and Target are from different technologies
Problem description: OBN Source or Target that is a WD iView handles OBN parameters using the “DynemicParameter” key (e.g. DynemicParameter=key%3Dvalue) while HTML iView that is an OBN Source or Target uses the “objValue” Key. An OBN configuration that involves both types of iViews (e.g. HTML Source + WD Target) might not support parameters passing because of the protocol differences.
This restriction is no longer valid.
The limitation is fixed on SP15
( Changed at 25.02.2008 )

EP-PIN-WD-PB

Release with restrictions
Refresh of a Web Dynpro iView cause a runtime exception
Trying to refresh a Web Dynpro iView results in a runtime exception
This restriction is no longer valid.
Handled for SPS05.
( Changed at 05.12.2005 )

EP-SYS

Release with restrictions
System Copy workaround for SP Stack 05
The general note for the SAP NetWeaver 2004s Java System Copy is 870863. The workaround is needed because of the substitution variables ${com.sap.portal*} as described in SAP note 888718.
This restriction is no longer valid.
successful EP SystemCopy with NW04s SP05
( Changed at 15.02.2006 )
Errors during SDA Deployment on UNIX due to missing directory
SDAs of type file system cannot be deployed on UNIX if they contain a path relative to a non existing directory like <not_existing_directory>/ ../<other_path>. Therefore, some SDAs of EP/KMC are effected. The problem is independent whether it’s an initial installation or a system copy. Workaround: Create the directory <not_existing_directory> manually.
This restriction is no longer valid.
Fix was done for SPS06
( Changed at 15.02.2006 )

EP-VC

Release with restrictions
Adobe Flex compilation error – 32k error
Symptom: In some cases, when compiling and deploying a Visual Composer model to the Flex runtime, a compilation error appears indicating a 32K problem. The error you receive may be similar to the following: “Branch between 7824 and 40595 around line 0 exceeds 32K span.” This is a known Adobe limitation. More information can be found on the Macromedia web site: http://www.macromedia.com Solution: Alternatively, you could do the following: 1. Break the iView into several nested iViews. 2.Remove chart animation effects. 3. Add an empty layer.
This restriction is no longer valid.
fixed with SP14
( Changed at 19.01.2009 )
Navigation using the “navigate to” connector
Symptom You are using Visual Composer 7.00 SPS07: Navigation from one iView to a target iView defined by a Navigate connector is limited to iViews residing in the same PCD path. For instance, it is not possible to navigate from an iView on one page to an iView on another page. Other terms Navigation; PCD; navigate; target iView Reason and Prerequisites This is a limitation Solution Visual Composer 7.00 SPS07: Ensure that when deploying an iView, the target of the Navigate is in the same PCD path. Furthermore, portal administrators must be aware that moving iViews from one location to another in the PCD can disrupt the link between an iView and another target iView. The iView and its target must be in the same path, on the same page, or in the same folder. Visual Composer 7.00 SPS08 and above Resolved in SP8
This restriction is no longer valid.
Refer to SAP Note 0000936547
( Changed at 27.07.2006 )
Visual Composer – Display error for lower/upper values in the area chart
Symptom: If you are trying to display data in a “Area Chart” view using Macromedia Flex run time, low values (e.g. 0 – 10) and / or high values (e.g. 1000 and above) are not displayed in the chart.
This restriction is no longer valid.
fixed according to Adi Neeman (7.10.2008)
( Changed at 07.10.2008 )

XX-INT-UR

Release with restrictions
WD Wizard – JavaScript Errors are popped up while working in the portal new WD wizard
The iframe in which the webdynpro application is running is being terminated but an additional webdynpro javascript code is still running. The whole scenario is executed through EPCM call cycle (between webdynpro application and the appdesigner).
This restriction is no longer valid.
Handled for SPS05.
( Changed at 14.03.2006 )