SAP Technologies

• Infolytics Mobile DB-Monitor
• Teradata Foundation for SAP
• DB-Migration
• SAP Internet Transaction Server (ITS)
• (Web)SAPConsole
• Business Server Pages (BSP)
• MaxDB Services

Database Systems

Data Warehousing

Migrations

Software Development

Products

SAP Internet Transaction Server (ITS) is the interface between SAP R/3 Versions and the Internet. ITS enables executing browser-based applications, transactions function components and reports in the WebGUI or starting so-called Internet application components (IACs).

In the past ITS was an independent product component (“stand-alone”) but as of version 6.4 of SAP Base or SAP Web Application Server has been completely integrated into the Web Application Server (with the exception of a few components that are no longer supported). Thus with an upgrade to version 6.40 or above web applications that had used the stand-alone ITS (external) must be modified or migrated. With the use of a field-tested procedural model Infolytics supports ITS users in migration from “external” to “internal”.

ITS Migration from external → internal

For some it is a stroll, for others it can turn into an obstacle course: The ITS conversion from “external” to “internal”. Because with the upgrade to SAP Enterprise Suite 6.0 the SAP Internet Transaction Server (ITS) is now only available integrated into SAP Web Application Server.

Users who until now have only used SAP’s own Internet application components are in good shape since with the new release they are delivered ready to run in an „internal“ version. But those who implemented their own web applications with IACs must now migrate them internally.

In migration of Internet Application Components (IACs) there is a distinction between two types. For IACs based on web transactions the conversion is relatively simple: since this technology was retained in the integrated ITS existing business HTML templates can be directly taken over with minor adjustments.

On the other hand IACs based on Flow File do not use Dynpros and the execution logic is not within the SAP system rather in the Flow-Files themselves. An HTML layout was generated based on the return value of an SAP RFC by means of business HTML and JavaScript.
 This IAC type is no longer supported by the internal ITS. However, since the current business HTML templates continue to be understandable by ITS, it nonetheless remains possible to convert customer-written IACs for the integrated ITS.

Based on experience in diverse conversion projects Infolytics AG has put together a conversion guideline that documents a practice-proven approach prototype in five steps.

• Create an ABAP program later to contain the Dynpro control according to the flow logic.
• Create/load Internet Service and Templates and adapt them if the corresponding service is not yet available in the system.
• Create ICF service if not yet available.
• Migration of execution logic: transfer the Flow-File execution logic to the Dynpro execution logic.
• Test of transformed IACs and integration into the customer environment.

Several SAP customers were able to migrate their IACs quickly and economically based on this conversion guide. The greatest advantage:

• The customary browser applications can be retained and the users do not need to be re-trained.