SAP Basis Tech Supports

Symptom
This note contains information on release restrictions in SAP Web Application Server 6.40.
Other terms
NetWeaver 04, Web AS, Web AS 640, Web AS 6.40, RampUp, Ramp-up, SAP Web Application Server 6.40, Release restriction,
Reason and Prerequisites
At the time of the release of SAP SAP Web Application Server 6.40 restrictions existed concerning the productive usage of certain functions on which SAP provides customer information in this note.
Dear customer,
the following restrictions concerning the productive usage of SAP Web Application Server 6.40 are described in particular in this note. The status of the following explanation corresponds to the date of the last change of this note.
If you have questions, suggestions or comments on the productive usage of SAP Web Application Server 6.40 or the individual functions, SAP appreciates your feedback.
In case of the usage of functions which require the consultation with SAP, consult the contact person specified for the respective component in square brackets directly via email. Keep on entering problem messages via Service Marketplace or SAPNet – R/3 Frontend.
The statements made here, especially those referring to availability dates, reflect current planning and can be changed without prior notice.
Solution

Open Limitation(s)

BC-FES-ITS

Release with restrictions
SAP integrated ITS: Released for productive usage only on 64Bit platforms
If you would like to use a large number of sessions on the SAP integrated ITS you have to take into account the following limitation: If you want to configure many sessions, bottlenecks occur in the process address space (2 GB) of the SAP work process. You can only avoid this problem by configuring multiple application servers with fewer sessions on each server or by changing to 64-bit hardware because on this hardware the address space is not limited to 2GB. Since many live SAP System instances are already at the 2 GB limit even if you do not use SAP integrated ITS, you must use 64-bit hardware for productive use of the SAP integrated ITS. Test and demo systems with relatively few users needing the SAP integrated ITS can be set up on 32-bit hardware. Of course you can use an integrated ITS 6.40 on 32-bit hardware for administrative purposes as well as long as no productive load is put on the integrated ITS. This limitation cannot be overcome.
( Changed at 08.12.2008 )

BC-WD-JAV-ADB

Release with restrictions
Web Dynpro Interactive Forms and Office Apps will not work with other Browser than Internet Explorer
In NetWeaver 04 there are no plans to support other browsers than Internet Explorer for scenarios with interactive forms. In NetWeaver 04 there are no plans to support other browsers than Internet Explorer on Windows for scenarios with office integration.
( Changed at 08.12.2008 )

BC-WD-UR

Release with restrictions
Active Components for Web Dynpro can not be used in certain containers
In NetWeaver 04 it will not be possible to use Web Dynpro Active Components in popups and in scrollable containers. This is independent of the client (i.e. browser) used.
( Changed at 27.01.2009 )
Upgrade of custom themes might lead to visual design issues
Upgrade of custom themes might lead to visual design issues With new releases and Service Packs, some issues can occur with the visual design of your custom themes (created with the Theme Editor). SAP cannot guarantee that the visual design of UI elements remains unchanged. If an SAP theme is changed, this can have an impact to the custom themes. In most cases you can fix these issues by using the updated version of the Theme Editor. But in rare cases these issues cannot be fixed anyway.
( Changed at 21.06.2007 )

KM-KW

Release with restrictions
SAP KW 7.0: Localization of Asian languages
Finalization of some translation and editing functions for Korean and Chinese (Simplified and traditional) pending.
This restriction will probably no longer be valid with SAP KW 7.0 Support Package 04.
( Changed at 19.01.2009 )
SAP KW 7.0: UNICODE enabling
SAP KW 7.0 supports UNICODE backend systems only with non-UNICODE frontend tools (KWB, SAP KW Viewer).
This restriction will probably no longer be valid with SAP KW 7.0 Support Package 04.
( Changed at 19.01.2009 )

Fixed Limitation(s)

BC-DWB-JAV

No release
PAR Upload from the Enterprise Portals plugin in SAP NetWeaver Developer Studio
The PAR Upload from the Enterprise Portal plugin in SAP NetWeaver Developer Studio is not able to work properly on a secured portal (https://…). On attempting to upload a PAR file on a https portal the plugin gets stuck.
This restriction is no longer valid.
This limitation is no more valid
( Changed at 12.08.2004 )

BC-INS

Release with approval of SAP or after consultation with SAP
High Availability for Web AS JAVA
SAP NetWeaver 04 components are currently not released to be installed or operated in a highly available manner without prior SAP Consultation. The SAP note #803018 慍entral note for NetWeaver 04 High Availability capabilities?describes the actual state of limitations regarding NW04 components in highly available environments (per SAP component and platform), as well as the process to follow in order to accomplish High Availability operation of SAP NetWeaver 04 components on a project base.
This restriction is no longer valid.
Refer to SAP Note 0000803018
( Changed at 06.09.2005 )

Release with restrictions
Installation of heterogenous landscape
The installation of a standalone J2EE engine for the Windows platform is only supported if all application servers have the same CPU architecture (I386, IA64 or AMD64). If the central instance is installed on a I386 machine, all application servers have to be I386 machines. The reason for this is that the executables of the system are centrally located in the directory \\$(SAPGLOBALHOST)\sapmnt\$(SYSTEMNAME)\SYS\exe and this directory can only contain executables for one CPU architecture. see note 875322
This restriction is no longer valid.
fixed
( Changed at 25.11.2008 )

No release
Choosing passwords for the default users within SAPInst
During the installation of SAP WebAS Java with SAPInst, the administrator must choose passwords for the default users, which are created during the installation. For these passwords the current restriction does not allow characters, which need to be escaped in XML documents, e.g. <,> and &.
This restriction is no longer valid.
Limitation is fixed
( Changed at 31.01.2006 )

BC-INS-MIG

Release with restrictions
Java Systemcopy on IBM zLinux
The Java system copy with SAP NetWeaver SR1 is not supported with IBM zLinux
This restriction is no longer valid.
fixed with 6.40 patch collection
( Changed at 23.04.2008 )
Java Systemcopy on Solaris and HP/UX
The Java Systemcopy with SAP NetWeaver04 Service Release 1 is not supported for Solaris and HP/UX
This restriction is no longer valid.
Refer to SAP Note 0000716604
Refer to SAP Note 0000716926
( Changed at 08.03.2005 )
Java Systemcopy on HP/UX PA-Risc
The Java Systemcopy with SAP NetWeaver04 Service Release 1 is not supported for HP/UX on PA-Risc architecture
This restriction is no longer valid.
fixed with 6.40 Patch Collection and SR1 SP16
( Changed at 20.06.2008 )

BC-JAS-SEC

No release
Custom Login Modules not supported
Custom Login Modules are not supported until NW04 SPS 8. They will be supported starting with NW04 SPS 9.
This restriction is no longer valid.
limitation is fixed
( Changed at 31.01.2006 )

BC-JAS-WS

No release
WebService Navigator cannot use HTTPS URLs
The WebService Navigator cannot use HTTPS URLs for WSDL files. As a result of this, any WebService Homepage of a deployed web service can only be started via HTTP.
This restriction is no longer valid.
Is fixed in NW Stack SP3
( Changed at 20.07.2004 )

BC-SRV-FP

Release with approval of SAP or after consultation with SAP
Interactive Forms/Print Forms
Adobe Reader Version 6.0.2 necessary for usage of Interactive Forms/Print Forms, available for SAP customers on June 14th 2004
This restriction is no longer valid.
Refer to SAP Note 0000682619
This restriction will not longer be valid with SAP NetWeaver 04 Support Package Stack 03.
( Changed at 14.06.2004 )

Release with restrictions
Scalability
The current Adobe Document Services do not support a complete clustering scenario.
This restriction is no longer valid.
This restriction will probably no longer be valid with SAP NetWeaver Support Package 04.
( Changed at 13.08.2004 )

BC-WD-JAV

Release with restrictions
Restriction of Web Dynpro and reverse proxy usage
Web Dynpro supports no system landscapes with reverse proxies set-up in SP9 to SP12. If still reverse proxies are used, the URLs of static Web resources will not be dissolving properly. Pictures and icons will not be displayed correctly. It is planed to support reverse proxies with SP13.
This restriction is no longer valid.
With SP 13 Web Dynpro supports reverse proxy usage due to a change in URL generation
( Changed at 09.01.2006 )

BC-WD-JAV-RUN

Release with restrictions
Netscape restrictions for Web Dynpro Java
Starting with Stack11 Web Dynpro Java supports Mozilla 1.7.2 Some limitations however apply with respect to certain UI elements. Known issues: – Tree in ScrollContainer jumps to the top and requires re-scrolling afer navigation. The tree node opens but the focus shifts to the top. This works different in Internet Explorer. – Table in tab pane The table is not displayed fully in Mozilla. There is no (left-right) scroll bar present in the bottom for the user to scroll.
This restriction is no longer valid.
see limitation “Browser Restriction for Web Dynrpo Java”
( Changed at 06.03.2006 )
Explorer 5.5 restrictions for Web Dynpro Java
Internet Explorer 5.5 is not fully supported by Web Dynpro Java up to SP8/Stack05. Availability is granted for evaluation purposes only. This means with SP8 or lower it is not recommended for productive use. The end of this limitation is planned for SP9/Stack09.
This restriction is no longer valid.
( Changed at 17.09.2004 )

CAF-IDE

Release with restrictions
Composite Application Design Time: Limited size of composite application project
Limited size of composite application project: The size of a composite application development project should not exceed 20 entity and application services. Larger projects could lead to serious performance issues in the SAP NetWeaver Developer Studio.
This restriction is no longer valid.
FIXED
( Changed at 23.01.2009 )
Composite Application Design Time: Data volume of Entities
Data volume of entities should not exceed 1 000 000 instances. For more than 1 000 000 instances and searching by text into an attribute TREX or another full text search engine is recommended.
This restriction is no longer valid.
Solved in SP16
( Changed at 07.03.2006 )

Release with restrictions
Composite Application Design Time: Limited team development capabilities
Composite Application Designtime: Limited team development capabilities No tool support for concurrent metadata modifications. Team development can only be enabled by organizational measures.
This restriction is no longer valid.
FIXED
( Changed at 23.01.2009 )