SAP Java 堆栈架构与 ABAP 堆栈有何不同？
我的公司正在考虑将 SAP 从 46C 升级到 ECC 6.0 EHP 5，我们有以下 3 个问题：
1）ABAP Stack 和 Java Stack 之间有什么区别。我想46C是“ABAP堆栈”？
2）什么情况下绝对需要安装Java Stack？
3）安装EHP是否意味着我们应该首先安装Java Stack？
谢谢
My company is thinking to upgrade SAP from 46C to ECC 6.0 EHP 5 and we have the next 3 questions:
1) What is the difference between ABAP Stack and Java Stack. I imagine 46C is "ABAP stack"?
2) In which cases it is absolutely necessary to install the Java Stack?
3) Does the installation of the EHPs imply that we should first install the Java Stack?
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
SAP ECC（所有核心模块）在 ABAP 堆栈上运行。 SAP 的许多互操作性模块（例如 SAP PI）都在 Java Stack 上运行。如果您打算使用 SAP PI，您很可能需要安装 Java 堆栈，但您应该能够升级到 ECC6，而无需安装 Java 堆栈。
您不需要 Java 堆栈来应用增强包。
几年前，有人推动更多地转向 Java 堆栈，但我相信 SAP 已经回到了这一立场。现在，您可以使用 Web-Dynpro for ABAP 以及 Web-Dynpro for Java 进行 SAP 中的 Web 开发。
SAP ECC (all core modules) runs on the ABAP stack. Many of SAP's interoparability modules like SAP PI runs on the Java Stack. If you intend to use SAP PI you will most likely need to install the Java Stack, but you should be able to upgrade to ECC6 without having to install the Java stack.
You do not require the Java Stack to apply Enhancement Packs.
A few years back there was a push to move more toward the Java stack, but I believe SAP has gone back on that position. Nowadays you can use Web-Dynpro for ABAP for web-development in SAP as well as Web-Dynpro for Java.
仅供记录：
直到版本 4.6C 为止，只有 ABAP 实例。
此后（主要是 6.x 和 7.0x 版本），可以安装纯 Java 实例或组合的 ABAP+Java 实例。后者是所谓的双栈系统。这些堆栈共享一些内部资源（内核文件、数据库等），但在前端非常独立。不知何故，就像连体双胞胎一样。
出于稳定性考虑，不再支持双栈系统。从 Netweaver 7.3 版本开始（但也有某些例外）。甚至有一个程序可以将双栈分成两个独立的系统。
因此，如果通过增强包升级双堆栈系统，则必须将其应用于两个堆栈。
否则，根据需要安装单独的 ABAP 和 Java 系统并设置所需的连接：RFC、JCo、SOAP 等。
Just for the record:
Up until release 4.6C there were only ABAP instances.
After that (mainly releases 6.x and 7.0x) it was possible to install Java-only instances or combined ABAP+Java instances. The latter are so called double-stack systems. The stacks share some internal ressources (kernel files, database, etc) but are pretty independent on the front side. Somehow like Siamese twins joined at the hip.
Due to stability the double-stack systems are not supported any more. This from release Netweaver 7.3 onwards (but there are certain exceptions). There is even a procedure to split a double-stack into two independent systems.
So if a double-stack system is upgraded via Enhancement Package it must be applied to both stacks.
Otherwise install separate ABAP and Java systems as needed and set up the required connections: RFC, JCo, SOAP, etc.
一个是运行ABAP程序的应用服务器，另一个是运行Java程序的应用服务器。
4.6C仅提供ABAP堆栈。
每当您需要需要 Java Stack 的东西（例如 Adobe Interactive Forms 或某些 Portal 东西）时。
不。事实上，添加辅助步骤应该是与升级现有系统完全不同的项目 - 您不应该将这些组合起来以保持复杂性......
The one is an application server that runs ABAP programs, the other is an application server that runs Java programs.
4.6C only provides an ABAP stack.
Whenever you need something (like the Adobe Interactive Forms or some Portal stuff) that requires the Java Stack.
No. In fact, adding a secondary step should be an entirely different project from upgrading an existing system - you should not combine these to keep complexity at bay...