|
There has been quite a bit of confusion about SAP's new Web Application
Server and the existing Internet Transaction Server (ITS). I recommend
searching this site for a more in-depth look at each technology. In brief,
ITS requires that every program you would like to Web enable must first
have a transaction GUI within the R/3 application server. The WAS allows
you to directly call any BAPI or RFC-enabled transaction within SAP.
Moreover, WAS incorporates some of the newest Web design protocols such as
WebDav. These protocols make it fairly simple for someone with an
appropriate Web development environment (Ex. Adobe GoLive) to check out,
create/modify, and check in Web pages to the WAS rather than having to
maintain the HTML (Web pages) directly within R/3. Such is the case with
ITS, where Web designers had to manually retrieve and modify HTML source
code from SAP, then copy it back into R/3.
There are many other differences, but WAS is a fundamentally different
technology from ITS. Currently, the WAS uses pieces of ITS, but expect ITS
to be migrated out of the picture in the near future. SAP has not made the
future of ITS clear, but the WAS looks to replace it as the recommended
mechanism to Web enabling SAP.
|
