Requirement of Java stack in system to be upgraded to SAP BW 7.31

[Former Member]

Hello Experts,

I need your inputs on system architecture while we are undergoing upgrade from BW 3.5 to BW 7.31.

Current BW 3.5 system is used for SRM reporting. WAD 3.5 is used to publish BEx reports to the reporting roles in BW, BW roles are then distributed SRM roles. Ultimately, reports are accessed through SRM web application. We are NOT using portal and do NOT have Java stack.

My questions are -

- While we are upgrading to BW 7.31 (technical upgrade), do we need to have a Java stack in addition to ABAP stack for WAD to remain accessible through SRM Web Application (it's not a portal application)?

- What will be the java stack requirement in both the cases where we decide to migrate WAD 3.5 to 7 and to let WAD templates remain in 3.5 as it is?

- What functinality of 7.3 will we miss out if we don't have the Java stack?

- What is the best practice in case Java is required - dual stack or seperate instance ?

I will appreciate you can share the some doc link along with your suggestion for me to have clarity on post upgrade landscape.

Thanks & Regards.

[Former Member · Accepted solution]

If you want to use the new BEx Web runtime introduced with BI 7.0, BI JAVA is required. SAP is discontinuing the dual-stack approach so you should look at installing separate AS JAVAs to host BI JAVA unless you alread have AS JAVAs where you can install BI JAVA without compromising maintenance lifecycles. See the attached link for a document discussing BI JAVA. See also the FAQ on BEx and portal integration, link attached. The SAP NetWeaver 7.3 EHP1 Master Guide has also some useful information on the topic.

http://scn.sap.com/docs/DOC-11603

http://scn.sap.com/docs/DOC-7640