SAP Basis Tech Supports

Symptom
Release restrictions of SAP NetWeaver 2004s – Usage Type Application Server – Java (AS-Java)
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 AS-Java. 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)

BC-WD-ACF

Release with restrictions
Embedding of active components (Active Component Framework) is limited
Embedding of active components (Active Component Framework) is limited Due to technical restrictions of the browser active components (for example Network, Gantt, OfficeIntegration, and Interactive Forms) cannot be used in every case. We do not support the embedding of active components in modal dialog boxes (IWDWindow.createModalWindow) and in container controls, which can be scrolled (ScrollContainer, Tray, Group, TabStrip with scrollingMode “AUTO” or “BOTH”). Future support is also not planned.
( Changed at 09.09.2008 )

BC-WD-JAV

Release with restrictions
Integration of Distributed Web Dynpro Applications into the Portal
The local integration of Web Dynpro content into the portal works as expected. Web Dynpro Application can however not be run as embedded remote content in the portal. More precisely: while portal content can be distributed over servers other than the portal server a Web Dynpro IView or page marked as embedded can only refer to a local application. This restriction in turn implies limitations on running Web Dynpro in a Federated Portal scenario. Running a Web Dynpro iView as isolated iView based on the AppIntegrator (aka NW04 integration level) it is possible to run the Web Dynpro content on a different system than the portal itself.
( Changed at 04.09.2006 )

Fixed Limitation(s)

BC-CTS-CBS

No release
System Copy Usage Type NetWeaver Development Infrastructure (NWDI)
The system copy for usage type NetWeaver Development Infrastructure (NWDI) is not released yet.
This restriction is no longer valid.
solved with SR1 in JDI System Move guide
( Changed at 06.04.2006 )

BC-INS

Release with approval of SAP or after consultation with SAP
High availibility support -Installation
Installation tool (SAPinst) support for out-of-the box installation option of SAP recommended High Availability Setups for NW2004s Application server Java (see SAP’s “SAP Web Application Server in switch over environments” guide) is not released and therefore not supported.
This restriction is no longer valid.
solved with SR1
( Changed at 04.04.2006 )

No release
Java Add-In installation after ABAP upgrade and ABAP installation
Java Add-In installation after ABAP upgrade and ABAP installation is not yet released and therefore not supported until further notice. Note: Java Add-In installation comprises installation of a SAP Application Server Java stack to an existing ABAP stack utilizing the same system ID (SAP SID) and same database. Current workaround: Install your Java system as a separate/standalone SAP Application Server Java. In case of a new installation you may directly install a double-stack system to reach the same result.
This restriction is no longer valid.
solved with SR1
( Changed at 06.04.2006 )

BC-INS-MIG

Release with restrictions
Java Systemcopy with SUN JDK 1.4.2_11 (Solaris/Windows/Linux)
The Java Systemcopy with SAP NetWeaver04S is slow with SUN JDK 1.4.2_11 for Solaris, Windows and Linux. For more information on Java Systemcopy see note 716604.
This restriction is no longer valid.
solved with J2SE 1.4.2_12 SDK
( Changed at 28.07.2006 )

BC-UPG

Release with approval of SAP or after consultation with SAP
High availibility support -Upgrade-
Upgrade Process to NW2004s Application server Java has no specific support for Systems that are configured in highly available environments (see SAP’s “SAP Web Application Server in switch over environments” guide). Java support packages stacks can not be applied to SAP Application Server Java in HA environments without additional manual steps, too. (JSPM)
This restriction is no longer valid.
solved with SR1
( Changed at 07.04.2006 )

BC-WD-ACF

Release with approval of SAP or after consultation with SAP
Office and Adobe Integration on VISTA OS
The Active Component Framework installation does not work on VISTA OS. Therefore the Office Integration and the Adobe Integration scenarios do not work on VISTA OS clients.
This restriction is no longer valid.
fixed with SP16
( Changed at 07.10.2008 )

BC-WD-JAV

Release with approval of SAP or after consultation with SAP
Web Dynpro Temporary Firefox Restrictions
Web Dynpro integration with active components is not fully available yet: Web Dynpro integration with Adobe will not be available in Firefox for MacOS. This delay is due to missing functionality in the partner software. Web Dynpro integration with JNet and JGantt in FireFox on MacOS will be postponed to a later SP. Current target is SP9 or later. Web Dynpro integration with Star Office in Firefox on Linux and MacOS will be postponed to a later SP. Current target is SP9 or later.
This restriction is no longer valid.
fixed with SP10
( Changed at 10.11.2006 )
Applets can not be executed in the Portal environment
Portal integration with Applets is not fully available yet: Due to limitations resp. bugs in non-SAP software NetWeaver can not provide an environment such that applets can be run inside the SAP portal. In standalone mode applets can be started in Web Dynpro views. Bug reports with external software providers are filed by SAP (and accepted by the third-party) but no target dates are given so far. So in turn we can not provide a target date for ending this limitation but we expect making this integration available as soon as the issues are solved.
This restriction is no longer valid.
fixed
( Changed at 02.03.2009 )
Web Dynpro End User Personalization
In NW04s Web Dynpro is offering means to personalize views and UI elements. This is called the Web Dynpro End User Personalization. End user personalization is not available with SP5. Full functionality is expected as of SP6.
This restriction is no longer valid.
Refer to SAP Note 0000910285
( Changed at 16.03.2006 )
File Download does only work in isolated iviews
For WD applications running within the WD page builder the usage of Adobe, business graphics and file download is only possible when running as a so-called NW04 iView, i.e. the WD iView runs as isolated iView.
This restriction is no longer valid.
Part of the global portal effort in SP07
( Changed at 16.03.2006 )
Text items in Web Dynpro implicit personalization
Text constants in the implicit personalization dialogs of Web Dynpro – as delivered by SAP – will not appear translated to the appropriate login language. This is due to missing language files. Only English is available and will be displayed as fallback. This is a temporary limitiation which does not affect the general functionality of the personalization feature.
This restriction is no longer valid.
Refer to SAP Note 0000910286
( Changed at 16.03.2006 )

No release
Web Dynpro Session Management
There is a limitation with respect to committed Web Dynpro functionality. This limitation only applies in the page builder (portal) context. Session Management It is important to note that the mentioned functionality is fully available in the standalone mode of Web Dynpro. Running a WD application within the WD page builder does not support the portal session management. THe WD page builder application itself and all embedded WD Java applications are terminated correctly – all running isolated content is not terminated by the portal session management. Adobe, Business Graphics & File Download does only work in local scenario
This restriction is no longer valid.
Refer to SAP Note 0000910286
fixed with SP 6
( Changed at 16.02.2006 )
Web Dynpro Cache
There is a limitation with respect to committed Web Dynpro functionality. This limitation only applies in the page builder (portal) context. Web Dynpro Cache It is important to note that the mentioned functionality is fully available in the standalone mode of Web Dynpro. For WD applications running within the WD page builder the usage of Adobe, business graphics and file download is only possible when running without proxy server and when running on the same machine as the WD page builder itself.
This restriction is no longer valid.
Refer to SAP Note 0000910286
fixed with SP 5
( Changed at 16.02.2006 )
Web Dynpro Upload
There is a limitation with respect to committed Web Dynpro functionality. This limitation only applies in the page builder (portal) context. File Upload (WSRP topic) It is important to note that the mentioned functionality is fully available in the standalone mode of Web Dynpro. For WD applications running within the WD page builder it is not supported to use the file upload. File upload works only for WD applications running as isolated content using the NW04 portal integration.
This restriction is no longer valid.
Refer to SAP Note 0000910286
fixed with SP 5
( Changed at 16.02.2006 )

CAF-SOL

No release
Composite Application Framework: WebService Connectivity
Composite Application Framework-WebService Connectivity: Backend connectivity via WebServices is not available for productive use
This restriction is no longer valid.
Fixed in SP6
( Changed at 23.01.2009 )

No release
Composite Application Framework: WebService Connectivity
Composite Application Framework-WebService Connectivity: Backend connectivity via WebServices is not available for productive use .
This restriction is no longer valid.
FIXED BY SP6
( Changed at 06.03.2006 )