Tuesday, May 20
Release Restrictions For SAP EP 6.0 on Web AS 6.40
Symptom
Information on release restrictions for SAP Enterprise Portal 6.0 on Web AS
6.40.
Reason and Prerequisites
The statements made here, especially those referring to availability dates,
reflect current planning and can be changed without prior notice
Solution
Open Limitation(s)
EP-KM
Release with restrictions
Knowledge Management and Collaboration in external facing portals
Knowledge Management (KM) and Collaboration are released in a restricted way for scenarios where the external facing portal capabilities of NW'04 SP 14 are used (i.e. reducing the network load by using the 'light framework page' concept of the portal): - KM runs within the light framework page without erros (as from NW'04 SP14). Collaboration Rooms run within the light framework page as from NW'04 SP17. However, for both KM and Collaboration, the network load will not be decreased since the navigation within the KM and Collaboration 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 NW'04 SP14 is NOT used. For more information on how to enable KM (and Collaboration) for anonymous users, please refer to the following notes. SAP NetWeaver '04 SP11 and below: Note 728106. SAP NetWeaver '04 SP12 and higher: Note 837898.
Fixed with NW'04 SP14 (KM) and SP17 (Collaboration)
( Changed at 13.10.2006 )
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-COL-DSC
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.
( Changed at 03.11.2008 )
EP-PIN-MIG
Release with approval of SAP or after consultation with SAP
Migration EP5 to NW04: Few types of URL iViews will not work after migration.
After migrating EP5 (Portal & KM) to NW04, few types of URL iviews will not work. (URL & iView catcher from EP5) iViews. Here is the list: - Delimiters supports only # (for personalization) - No support in personalization names with special characters. - - The URLIView supports only the following EP5 tags: , ,
, , - The
other EP5tags are not supported - URLIViews with declaired 'EP5 system' that
contains the following characters '<' and '>' as part of parameter will
not work properly. - EP5.0 URL IView with Post method after migration will not
work (to fix it edit the EP6 IView and change the Method to Post). -IView
Catcher rendered IViews after migration will not work. - In case of EP5 tags in
the iView (the .asp file returns html with TAGS) the tags will not get
translated. Therfore the html content might be corrupted.
( Changed at 08.12.2008 )
Fixed Limitation(s)
EP-KM
No release
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 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 20.07.2007 )
For EP server running on UNIX: Connecting Windows file systems is not possible
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 limitation is planned to be resolved with SAP NetWeaver support package stack 04.
This restriction is no longer valid.
Fixed with SP stack 4
( Changed at 10.06.2005 )
EP-KM-ADM-UPG
No release
KMC NW04 SPS10 not released on DB2 database
NW'04 SP stack 10 Knowledge Management & Collaboration (KMC) is not released on DB2 database platforms. The upgrade from NW04 SP9 (NW04 SR1) fails, sapinst returns the following error in the "Deploy patch files" phase: "SDM call of deploySDAlist ends with returncode 4 See output of logfile /tmp/install/KMC_SP10/logs/callSdmViaSapinst.log for details" Background information: There are two of KMC tables which cannot be converted. The reason is their definitions have been changed in SP10 but during the upgrade they contain some data that cannot be converted to the new structure on DB2. This problem will be fixed with NW'04 SP stack 11.
This restriction is no longer valid.
Refer to SAP Note 0000821801
( Changed at 10.06.2005 )
EP-KM-CM
No release
Upload of files > ~ 70 MB not possible on SQL Server
Upload of files larger ~ 70 MB not possible on SQL Server
This restriction is no longer valid.
Refer to SAP Note 0000739263
( Changed at 10.06.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.
This restriction is no longer valid.
Fixed with NW'04 SP15
( Changed at 23.12.2005 )
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. This limitation is fixed with SAP NetWeaver SP stack 10.
This restriction is no longer valid.
LImitation is fixed with SP stack 10
( Changed at 10.06.2005 )
EP-PCS-IVS
Release with restrictions
Limited Support for Business Packages
Business packages will not be available with the beginning of ramp-up. This restriction will probably no longer be valid with NW ’04 SP Stack 02. After release of business package, please check SAP note 642775. This note explains specific installation instructions that have to be followed.
This restriction is no longer valid.
Refer to SAP Note 0000709354
Fixed with SP Stack02
( Changed at 10.06.2005 )
EP-PIN
Release with restrictions
No Full Locking Mechanism Support for PCD Objects
With SAP Enterprise Portal 6.0 SP2 a locking mechanism was implemented to avoid that two administrators work on the same PCD objects in parallel. With SAP Enterprise Portal 6.0 on Web AS 6.40 this mechanism has not been implemented by the following editors: Rule editor , and Desktop editor. They are planned for the next NetWeaver release.
This restriction is no longer valid.
Refer to SAP Note 0000920332
( Changed at 07.10.2008 )
Release with restrictions
No Accessibility Support for the End User
SAP Enterprise Portal 6.0 on Web AS 6.40 Support Pack Stack 01 is not yet fully accessible. Accessibility support for the end user is planned to be available NetWeaver `04 Support Pack Stack 04.
This restriction is no longer valid.
Refer to SAP Note 0000709354
Fixed with SP Stack04
( Changed at 10.06.2005 )
Web Dynpro for Java and Portal: Style Sheet Support only When Running on the same SP Stack
The style sheets generated by SAP Enterprise Portal 6.0 on Web AS 6.40 are not yet downward compatible. To guarantee a consistent branding of Web Dynpro applications running in SAP Enterprise Portal, SAP Enterprise Portal 6.0 on Web AS 6.40 and Web Dynpro for Java (resp. Web AS 6.40) have to run on the same NetWeaver `04 Support Pack stack. With NetWeaver `04 Support Stack 03 and Stack 05, the portal branding does not work at all for Web Dynpro applications. This is planned for NetWeaver`04 Support Stack 09.
This restriction is no longer valid.
Fixed with SP Stack 09
( Changed at 10.06.2005 )
No release
No Cluster Support With NetWeaver '04 at begin of Ramp-Up
SAP Enterprise Portal 6.0 on Web AS 6.40 Ramp-up is to be installed as a single-node installation, only. As long as this restriction is valid, we neither recommend performance nor stress tests. SAP plans to release cluster functionality with SAP NetWeaver `04 Support Package Stack 04 (“feature pack”) Before that, a Cluster installation can be done on individual project request. In this case, please contact your SAP Ramp-Up contact.
This restriction is no longer valid.
Refer to SAP Note 0000709354
Refer to SAP Note 0000803018
Fixed with SP Stack04
( Changed at 06.09.2005 )
EP-PIN-MIG-R3
No release
No Role Upload from SAP Backend Systems Before Support Pack Stack 06
SAP Enterprise Portal 6.0 on Web AS 6.40 Support Pack Stack 01 does not support a role upload from SAP backend systems. Thus, roles have to be created manually in the portal and cannot be uploaded from the SAP system. This is planned for SAP NetWeaver'04 SP Stack04 (Feature Pack).
This restriction is no longer valid.
Refer to SAP Note 0000709354
Fixed with SP Stack04
( Changed at 10.06.2005 )
EP-PIN-USM
No release
Limitations in the User Persistence Stores (ABAP + LDAP)
SAP Enterprise Portal 6.0 uses the User Management Engine (UME 4.0) as user management system. UME supports LDAP directories, SAP systems and DB as user persistence stores. 1) Limitations when using LDAP directory as user persistence store: - Dynamic groups are not supported. - Security policies defines on the directory server are not reflected in the UME - Group assignment only read-only when using a deep hierachy. Please check note 673824 for details. 2) Limitations when using MS ADS as user persistence store: When accessing the ADS with the global catalogue, only read access is possible. Please check note 673824 for details. 3) Limitations when using SAP System as user persistence store: -As of 4.6D, UME XML-user replication to ABAP-Systems (specificially SRM) is limited to up to 3 systems and 5000 users.
This restriction is no longer valid.
Refer to SAP Note 0000673824
( Changed at 10.06.2005 )
Single Sign On Limitations
With SAP Enterprise Portal 6.0 on Web AS 6.40 Support Pack Stack 01 cross domain Single Sign-On is not supported. An official support is planned with Support Pack Stack 04. In the meantime a solution can be realized on a project base (How To Guide is under preparation; a How To Guide for SAP Enterprise Portal 6.0 SP2 is already available: http://service.sap.com/ep60howtoguides). SAP provides a Web server filter and a programming interface (ticket verification library/API) to enable non-SAP applications to work with SAP logon tickets. SAP Logon Ticket webserver plugins are available for selected platforms and web servers. For details please refer to note 723896.
This restriction is no longer valid.
Refer to SAP Note 0000709354
Fixed with SP Stack04
( Changed at 10.06.2005 )
EP-SYS
No release
No Support of Clustered Portal Database wiht NetWeaver `04
With SAP Enterprise Portal 6.0 on Web AS 6.40, DB Clustering will not be officially supported. This applies to Microsoft SQL, as well as to Oracle Database cluster implementations. The technical feasability of active/active DB-Cluster solutions (like ORACLE RAC or MS SQL in active/active cluster mode) in conjuction with SAP Enterprise Portal 6.0 on Web AS 6.40 Support Pack Stack 01 is under investigation. But there are currently no plans to release it within the NetWeaver '04 timeframe. Since some customer projects have shown that EP 6.0 SP2 (!) is able work on top of an active/passive DB-Cluster-Solution SAP is willing to help customers on a project to get DB-Cluster related problems solved (in case of Oracle this is true for Fail Over mechanisms, but not for Real Application Clustering (RAC)). If you are interested in setting up DB-clustering on your own risk and on a project base, please contact SAP NetWeaver Product Management via your SAP contact in sales or consulting. This is solved with SAP NetWeaver 2004 SP Stack13.
This restriction is no longer valid.
Refer to SAP Note 0000709354
( Changed at 22.02.2006 )
EP-SYS-UPG
No release
Migration to SAP EP 6.0 on Web AS 6.40 not yet available
The following migrations are planned: - from EP 5.0 SP6 to NW'04 SP Stack 04 (FP): Oct 2004 (NOT SUPPORTED ANYMORE!!!) - from EP 5.0 SP6 to NW'04 Support Release 1: Released on Jan 26th, 2005 - from EP 6.0 SP2 to NW'04 Support Release 1: Release in March 2005 Please check http://sercice.sap. com/~form/sapnet?_SHORTKEY=01100035870000499845&_OBJECT=0110003587000057 04272003E for details. Please note that customers can of course manually export SAP Enterprise Portal 6.0 SP2 content and import it into SAP NW04 Enterprise Portal 6.0 on Web AS 6.40 Support Pack Stack 03-09.After the import please verify that the content is running.(personalization will not work) No upgrade from SAP Enterprise Portal 5.0 to SR is possible.
This restriction is no longer valid.
Refer to SAP Note 0000732461
( Changed at 10.06.2005 )
EP-UNI
No release
Unification Support only With NetWeaver '04 Unrestricted Shipment
SAP is currently porting the C++ based 5.0 Unification to a Java based 6.0 Unification. For customers this will have the advantage that unifiers will run as portal services on the portal server. Thus, no separate unification server will be required anymore. The C++ 5.0 unifiers have not been qualified for running in a SAP Enterprise Portal 6.0 on Web AS 6.40 Ramp-up (=NetWeaver Support Stack 01) environment and are therefore not released. The new java based 6.0 unifiers are planned to be release with NetWeaver '04 Support Pack Stack 05. See note 749643 for further details.
This restriction is no longer valid.
Refer to SAP Note 0000749643
Fixed with SP Stack05
( Changed at 10.06.2005 )
EP-KM
Release with restrictions
Knowledge Management and Collaboration in external facing portals
Knowledge Management (KM) and Collaboration are released in a restricted way for scenarios where the external facing portal capabilities of NW'04 SP 14 are used (i.e. reducing the network load by using the 'light framework page' concept of the portal): - KM runs within the light framework page without erros (as from NW'04 SP14). Collaboration Rooms run within the light framework page as from NW'04 SP17. However, for both KM and Collaboration, the network load will not be decreased since the navigation within the KM and Collaboration 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 NW'04 SP14 is NOT used. For more information on how to enable KM (and Collaboration) for anonymous users, please refer to the following notes. SAP NetWeaver '04 SP11 and below: Note 728106. SAP NetWeaver '04 SP12 and higher: Note 837898.
Fixed with NW'04 SP14 (KM) and SP17 (Collaboration)
( Changed at 13.10.2006 )
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-COL-DSC
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.
( Changed at 03.11.2008 )
EP-PIN-MIG
Release with approval of SAP or after consultation with SAP
Migration EP5 to NW04: Few types of URL iViews will not work after migration.
After migrating EP5 (Portal & KM) to NW04, few types of URL iviews will not work. (URL & iView catcher from EP5) iViews. Here is the list: - Delimiters supports only # (for personalization) - No support in personalization names with special characters. - - The URLIView supports only the following EP5 tags:
( Changed at 08.12.2008 )
Fixed Limitation(s)
EP-KM
No release
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 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 20.07.2007 )
For EP server running on UNIX: Connecting Windows file systems is not possible
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 limitation is planned to be resolved with SAP NetWeaver support package stack 04.
This restriction is no longer valid.
Fixed with SP stack 4
( Changed at 10.06.2005 )
EP-KM-ADM-UPG
No release
KMC NW04 SPS10 not released on DB2 database
NW'04 SP stack 10 Knowledge Management & Collaboration (KMC) is not released on DB2 database platforms. The upgrade from NW04 SP9 (NW04 SR1) fails, sapinst returns the following error in the "Deploy patch files" phase: "SDM call of deploySDAlist ends with returncode 4 See output of logfile /tmp/install/KMC_SP10/logs/callSdmViaSapinst.log for details" Background information: There are two of KMC tables which cannot be converted. The reason is their definitions have been changed in SP10 but during the upgrade they contain some data that cannot be converted to the new structure on DB2. This problem will be fixed with NW'04 SP stack 11.
This restriction is no longer valid.
Refer to SAP Note 0000821801
( Changed at 10.06.2005 )
EP-KM-CM
No release
Upload of files > ~ 70 MB not possible on SQL Server
Upload of files larger ~ 70 MB not possible on SQL Server
This restriction is no longer valid.
Refer to SAP Note 0000739263
( Changed at 10.06.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.
This restriction is no longer valid.
Fixed with NW'04 SP15
( Changed at 23.12.2005 )
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. This limitation is fixed with SAP NetWeaver SP stack 10.
This restriction is no longer valid.
LImitation is fixed with SP stack 10
( Changed at 10.06.2005 )
EP-PCS-IVS
Release with restrictions
Limited Support for Business Packages
Business packages will not be available with the beginning of ramp-up. This restriction will probably no longer be valid with NW ’04 SP Stack 02. After release of business package, please check SAP note 642775. This note explains specific installation instructions that have to be followed.
This restriction is no longer valid.
Refer to SAP Note 0000709354
Fixed with SP Stack02
( Changed at 10.06.2005 )
EP-PIN
Release with restrictions
No Full Locking Mechanism Support for PCD Objects
With SAP Enterprise Portal 6.0 SP2 a locking mechanism was implemented to avoid that two administrators work on the same PCD objects in parallel. With SAP Enterprise Portal 6.0 on Web AS 6.40 this mechanism has not been implemented by the following editors: Rule editor , and Desktop editor. They are planned for the next NetWeaver release.
This restriction is no longer valid.
Refer to SAP Note 0000920332
( Changed at 07.10.2008 )
Release with restrictions
No Accessibility Support for the End User
SAP Enterprise Portal 6.0 on Web AS 6.40 Support Pack Stack 01 is not yet fully accessible. Accessibility support for the end user is planned to be available NetWeaver `04 Support Pack Stack 04.
This restriction is no longer valid.
Refer to SAP Note 0000709354
Fixed with SP Stack04
( Changed at 10.06.2005 )
Web Dynpro for Java and Portal: Style Sheet Support only When Running on the same SP Stack
The style sheets generated by SAP Enterprise Portal 6.0 on Web AS 6.40 are not yet downward compatible. To guarantee a consistent branding of Web Dynpro applications running in SAP Enterprise Portal, SAP Enterprise Portal 6.0 on Web AS 6.40 and Web Dynpro for Java (resp. Web AS 6.40) have to run on the same NetWeaver `04 Support Pack stack. With NetWeaver `04 Support Stack 03 and Stack 05, the portal branding does not work at all for Web Dynpro applications. This is planned for NetWeaver`04 Support Stack 09.
This restriction is no longer valid.
Fixed with SP Stack 09
( Changed at 10.06.2005 )
No release
No Cluster Support With NetWeaver '04 at begin of Ramp-Up
SAP Enterprise Portal 6.0 on Web AS 6.40 Ramp-up is to be installed as a single-node installation, only. As long as this restriction is valid, we neither recommend performance nor stress tests. SAP plans to release cluster functionality with SAP NetWeaver `04 Support Package Stack 04 (“feature pack”) Before that, a Cluster installation can be done on individual project request. In this case, please contact your SAP Ramp-Up contact.
This restriction is no longer valid.
Refer to SAP Note 0000709354
Refer to SAP Note 0000803018
Fixed with SP Stack04
( Changed at 06.09.2005 )
EP-PIN-MIG-R3
No release
No Role Upload from SAP Backend Systems Before Support Pack Stack 06
SAP Enterprise Portal 6.0 on Web AS 6.40 Support Pack Stack 01 does not support a role upload from SAP backend systems. Thus, roles have to be created manually in the portal and cannot be uploaded from the SAP system. This is planned for SAP NetWeaver'04 SP Stack04 (Feature Pack).
This restriction is no longer valid.
Refer to SAP Note 0000709354
Fixed with SP Stack04
( Changed at 10.06.2005 )
EP-PIN-USM
No release
Limitations in the User Persistence Stores (ABAP + LDAP)
SAP Enterprise Portal 6.0 uses the User Management Engine (UME 4.0) as user management system. UME supports LDAP directories, SAP systems and DB as user persistence stores. 1) Limitations when using LDAP directory as user persistence store: - Dynamic groups are not supported. - Security policies defines on the directory server are not reflected in the UME - Group assignment only read-only when using a deep hierachy. Please check note 673824 for details. 2) Limitations when using MS ADS as user persistence store: When accessing the ADS with the global catalogue, only read access is possible. Please check note 673824 for details. 3) Limitations when using SAP System as user persistence store: -As of 4.6D, UME XML-user replication to ABAP-Systems (specificially SRM) is limited to up to 3 systems and 5000 users.
This restriction is no longer valid.
Refer to SAP Note 0000673824
( Changed at 10.06.2005 )
Single Sign On Limitations
With SAP Enterprise Portal 6.0 on Web AS 6.40 Support Pack Stack 01 cross domain Single Sign-On is not supported. An official support is planned with Support Pack Stack 04. In the meantime a solution can be realized on a project base (How To Guide is under preparation; a How To Guide for SAP Enterprise Portal 6.0 SP2 is already available: http://service.sap.com/ep60howtoguides). SAP provides a Web server filter and a programming interface (ticket verification library/API) to enable non-SAP applications to work with SAP logon tickets. SAP Logon Ticket webserver plugins are available for selected platforms and web servers. For details please refer to note 723896.
This restriction is no longer valid.
Refer to SAP Note 0000709354
Fixed with SP Stack04
( Changed at 10.06.2005 )
EP-SYS
No release
No Support of Clustered Portal Database wiht NetWeaver `04
With SAP Enterprise Portal 6.0 on Web AS 6.40, DB Clustering will not be officially supported. This applies to Microsoft SQL, as well as to Oracle Database cluster implementations. The technical feasability of active/active DB-Cluster solutions (like ORACLE RAC or MS SQL in active/active cluster mode) in conjuction with SAP Enterprise Portal 6.0 on Web AS 6.40 Support Pack Stack 01 is under investigation. But there are currently no plans to release it within the NetWeaver '04 timeframe. Since some customer projects have shown that EP 6.0 SP2 (!) is able work on top of an active/passive DB-Cluster-Solution SAP is willing to help customers on a project to get DB-Cluster related problems solved (in case of Oracle this is true for Fail Over mechanisms, but not for Real Application Clustering (RAC)). If you are interested in setting up DB-clustering on your own risk and on a project base, please contact SAP NetWeaver Product Management via your SAP contact in sales or consulting. This is solved with SAP NetWeaver 2004 SP Stack13.
This restriction is no longer valid.
Refer to SAP Note 0000709354
( Changed at 22.02.2006 )
EP-SYS-UPG
No release
Migration to SAP EP 6.0 on Web AS 6.40 not yet available
The following migrations are planned: - from EP 5.0 SP6 to NW'04 SP Stack 04 (FP): Oct 2004 (NOT SUPPORTED ANYMORE!!!) - from EP 5.0 SP6 to NW'04 Support Release 1: Released on Jan 26th, 2005 - from EP 6.0 SP2 to NW'04 Support Release 1: Release in March 2005 Please check http://sercice.sap. com/~form/sapnet?_SHORTKEY=01100035870000499845&_OBJECT=0110003587000057 04272003E for details. Please note that customers can of course manually export SAP Enterprise Portal 6.0 SP2 content and import it into SAP NW04 Enterprise Portal 6.0 on Web AS 6.40 Support Pack Stack 03-09.After the import please verify that the content is running.(personalization will not work) No upgrade from SAP Enterprise Portal 5.0 to SR is possible.
This restriction is no longer valid.
Refer to SAP Note 0000732461
( Changed at 10.06.2005 )
EP-UNI
No release
Unification Support only With NetWeaver '04 Unrestricted Shipment
SAP is currently porting the C++ based 5.0 Unification to a Java based 6.0 Unification. For customers this will have the advantage that unifiers will run as portal services on the portal server. Thus, no separate unification server will be required anymore. The C++ 5.0 unifiers have not been qualified for running in a SAP Enterprise Portal 6.0 on Web AS 6.40 Ramp-up (=NetWeaver Support Stack 01) environment and are therefore not released. The new java based 6.0 unifiers are planned to be release with NetWeaver '04 Support Pack Stack 05. See note 749643 for further details.
This restriction is no longer valid.
Refer to SAP Note 0000749643
Fixed with SP Stack05
( Changed at 10.06.2005 )
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment
You are welcome to express your views here...