SAP R/3 to ERP 6.0: Upgrade the network infrastructure?

SAP R/3 to ERP 6.0: Upgrade the network infrastructure?

What is the value of upgrading the network infrastructure with an SAP migration from R/3 to ERP 6.0? Moving from a client-server architecture to enterprise SOA and browser-based clients, you would think it could put more pressure on the data center LAN and WAN.

    Requires Free Membership to View

    When you register, you will start receiving targeted emails from my award-winning team of editorial writers. Our goal is to keep you informed on the hottest topics and biggest challenges faced by SAP professionals today.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSAP.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSAP.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

For the SAPGUI, the difference in network load between 4.6c and ECC is negligible.

Moving from SAPGUI to browser-based clients (SAPGUI for HTML) is something else. As of NetWeaver 6.40, SAP uses integrated ITS. Not needing separated ITS servers is an enormous improvement.

This however means that with integrated ITS memory usage increases on the server side. For an SAP GUI for HTML approximately 3 MB per session is needed. Although this is not that much, it should be taken into account. Integrated ITS and the memory requirements are discussed in more detail in OSS NOTES 742048, 890606 and 885580.

This was first published in July 2008