Hi,
We want to upgrade from R/3 4.6C to 4.7 (R/3 Enterprise).
As we are planning to develop new apps mostly on the web side, we want to use web dynpro.
As far as I have understood the articles about web dynpro and the versions of WAS and R/3, we need the WAS 6.40 to use web dynpro technology. The R/3 4.7 only shipps with WAS 6.20, so we can't use the web dynpro 'out of the box'.
Now my question:
Is there a chance to use the WAS 6.40 (only the Java stack I suppose) for the web dynpro stuff and communicate to the WAS 6.20 running the R/3 system or communicate directly with the 4.7 R/3 system?
Can I use the benefits of the web dynpro technology or is only the half of the technology available/running with this architecture?
Has anyone experience with this or is my whole idea too adventurously?
Has anyone better ideas how to use web dynpro with a R/3 4.7 backend?
Any comments, hints or ideas are welcome...
TIA
Ralph
Hi,
The answer is yes. You can use WAS 6.40 as a standalone Java Web application server and conect it to you busness functionality on r/3 4.7 system using JCO. Moreover, this is one of the most common scenarios of work with WAS 6.40 (at least for projects I am familiar with). This scanario gives you most of the power and functionality of Web Dynpro approach. All WAS and Web Dynpro APIs are available for use, the only think you can't use is API dedicated for portal enviroment (portal eventing for exampele).
Add a comment