Upgrade to ECC6-NW2004s: What can we NOT do if we don't install Java stack?

[a_heut]

We are preparing the upgrade of our 4.6c - Nw 2004 system to ECC 6 - NW2004s. Currently we only have ABAP stack installed on 4.6c and we are discussing whether to only install ABAP stack on ECC6 or to install both ABAP and Java stack. We use NWDS not really active yet but our IT strategy will probably be to use Eclipse IDE for custom web development and ABAP IDE for custom solutions/adjustments where SAP standard functionality cannot cover our requirements. We also have plans to install NW for CE and we use Visual Composer.

Does anybody know what we cannot do on ECC6 if we decide to NOT install the Java stack?

Any input would be very much appreciated!

kind regards

Angelique Heutinck

[Former Member · Accepted solution]

ECC6 does not require java stack and the list of things you can't do without it would be exhaustive and not necessary relevant to ECC6.

If you anticipate adding BI-Java, portal, PI, or other apps that require java, you would install a new java instance anyway. There's no technical requirement to ever install a java add-in to an existing ABAP (let alone an ABAP ECC6) system.

There are some solutions you can add later that may require java, like biller direct. Depending on the level of java useage you may find it more suitable to install a java stack in a standalone instance. It's becoming less common to run dual-stack ABAP+JAVA in productive environments due to the performance requirements and the need to maintain as much scalability and flexibility in architecture.