Internet Transaction Server OR ITS
Posted:
Hi friends a very useful info on ITServer
The SAP Internet Transaction Server (ITS) is the essential link between the SAP R/3 system and the Internet. It enables Internet (and Intranet) users to communicate directly between R/3 system to run R/e transactions, remote enabled function modules and reports as Internet applications components. The ITS is one of the cornerstones of SAP's mySAP.com offerings and strategy and integrated into the SAP 6.10 Web Application Server release. The ITS is the key technology behind the following products: Workplace, Employee Self-Service (ESS), Enterprise Buyer Professional (EBP), BW 2.0 Interface, Online Store and Retail Store, and the APO Interface. There are many other SAP products and applications that are based on ITS technology to interface from the Web to SAP R/3.
SAP ITS can handle complementary Web technologies to access data from SAP R/3:
- SAP GUI for Html: SAP transaction screens are dynamically converted to HTML pages
- Web transactions: SAP transactions that can be called from an HTML page (template based mode)
- Web remote function call (RFC): SAP R/3 function module that can be called from an HTML page
- Web reporting: Mechanism for linking to SAP reports and regenerated lists from an HTML page. Web reporting is implemented as a special-case RFC.
- ITS Flow Logic: Events, statuses, and modes used to model the dialog logic of a Web application in "flow files" on the SAP ITS.
SAP R/3 data is accessed via BAPI or RFC. Access to external data providers is also possible.
SAP's Internet applications are known as Internet Application Components (IAC) or Easy Web Transactions (EWT). Both are complete business solutions that allow Internet and Intranet users to access business information in the SAP R/3 system by starting transactions, function modules, and reports from a Web browser. All IACs or EWTs are based on a common infrastructure consisting of two essential components.
SAP Internet Transaction Server (ITS) - The ITS is the interface between the Internet and R/3 and is the runtime engine that links Web server to the R/3 Application server.
ABAP workbench tool - Web Application Builder and/or SAP@Web Studio - WAB is an R/3 ABAP workbench tool and SAP@Web Studio is a PC tool for creating, modifying and managing all ITS objects on which IACs or EWTs are based. These objects include service files, HTML Templates and HTRC language resource files.
The ITS solution to developing Internet applications is based on the premise that there is already a suitable business application solution, which has a stock of transactions, function modules and reports, as well as its own integrated development environment. All that is needed to enable Internet users to access and run these applications is an interface to the Internet. Apart from the general advantages derived from making SAP R/3 business information available over the internet, the ITS solution has many benefits.
These include:
• Ease of development - Programmers can develop IACsEWTs using a business application system (R/3), development environment (ABAP Workbench) and a programming language (ABAP), with which they are already familiar. There is also integrated data dictionary support from the ABAP Dictionary and appropriate transaction handling.
• Ease of deployment - The ITS solution supports internationalization of applications.
• Ease of use - ITS based IACs and EWTs have the same look and feel as any other Web site.
The separation of programming tasks from the visual design aspects is desirable, because both require different skills. In the ITS scenario, the ABAP programmer develops the application in ABAP using the ABAP Workbench in the SAP R/3 system and the user interface specialist handles the design and navigation aspects of the application with design languages like HTML and SAP's HTML Business in either the SAP@Web studio or ABAP Workbench tool, Web Application Builder.
The aim is to create applications that send documents back to the Web browser client in plain HTML format, since this format can be handled by all major browsers. This is important in an environment like the Internet where there is often little control you can exert over client software such as Web browsers. Fit can be controlled; you can also use Dynamic HTML, Java applets, JavaScript, and VBScript in you HTML templates, because the script language is transparent to the ITS.
How does the SAP ITS work?
When an Internet user requests an ITS service by clicking on a URL hyperlink or keying in a URL address in a Web browser to run a IACEWT, the request is processed as follows:
1. The Web browser passes the request to the Web server.
2. The Web server calls the server-specific ITS extension WGate - WGate is the link between the ITS and the Web server. WGate is a Web server extension that encapsulates the various supported HTTP server interfaces such as: CGI (Common Gateway Interface), NSAPI (Netscape Server Application Programming Interface), ISAPI (Internet Server Application Programming Interface) in a transparent manner that passes the requested data to the ITS AGate component.
3. WGate forwards the request to the ITS server process called AGate (which may or may not reside on the same machine.)
4. AGate is the link between the ITS and the SAP R3 application server. AGate is the core processing component of the ITS. It receives Web browser request from WGate and communicates with the SAP R3 application server via the DIAG or RFC protocol.
5. AGate then processes the requests, and sends all relevant details (including logon information) to the SAP R3 system, which either starts the first dialog step of a new transaction of submits further data for the next dialog step of a transaction already started.
6. SAP R3 starts the transaction for the service requested and sends the screen output to AGate.
7. When the dialog step has finished, AGate retrieves the result from SAP R3, and is responsible for session management, including mapping of SAP R3 screen or function modules to HTML, web session timeout handling, SAP R3 connection management and generation of HTML documents that are sent back to the Web browser client.
8. AGate forwards the formatted HTML page to WGate.
9. WGate forwards the formatted HTML page to the Web server.
10. The Web server sends the formatted HTML page to the Web browser, where it can be viewed by the user.
The ITS is downward compatible, therefore the ITS release must be the same or higher than the SAP R/3 kernel release.
There are three restrictions to this approach:
1. The SAP R3 release must be at least version 3.1I or higher.
2. You can only use those Internet Application Components that were shipped with the SAP R3 release you are using.
3. ITS 6.10 should only be installed in front of an SAP E3 kernel release 6.10 (e.g. CRM 3.0)
*** ITS 4.6D Server Platforms ***
>>Wgate
Microsoft NT 4.0 Server
Microsoft Web Server (ISAPI)
Netscape Web Server (NASPI)
Apache HTTP Server (Apache Module)
Any CGI Web Server (CGI)
Microsoft windows 2000 Server
Microsoft Web Server (ISAPI)
Linux/Intel
Apache HTTP Server (Apache Module)
>>Agate
Microsoft NT4.0 Server
Microsoft Windows 2000 Server
SAP@Web Studio
Microsoft NT 4.0 Workstation
Microsoft Windows 2000 Workstation
*** ITS 6.10 Server Platforms ***
>>Wgate
Microsoft NT 4.0 Server
Microsoft Web Server (ISAPI)
Netscape Web Server (NASPI)
Apache HTTP Server (Apache Module)
Any CGI Web Server (CGI)
Microsoft windows 2000 Server
Microsoft Web Server (ISAPI)
Microsoft XP Server
Linux/Intel
Apache HTTP Server (Apache Module)
>>Agate
Microsoft NT4.0 Server
Microsoft Windows 2000 Server
Microsoft XP Server
SAP@Web Studio
Microsoft NT 4.0 Workstation
Microsoft Windows 2000 Workstation
Microsoft XP Server
Evaluate ITS Server Speed issues
You have 10 users accessing sap via an ITS server (6.20) and it is soooo slow !!! access via sapgui is fast - any ideas what to look for ??
We tested several options for deploying the SAPGUI :-
Tivoli packages
ITS
Citrix MF XP
Tivoli was already built and in house so all we had to do was create a SAPGUI package and deploy it to the field (3000+ users) - pain in the butt because we had to find out all the users workstation id's for the users in 900+ locations. So far we have deployed 35% and our Go-live is 10/01!
ITS - We had an ITS consultant come in and review our setup. We were able to enhance the performance to some extent (20%). But, that was still unacceptable in comparison to the WINGUI that the users are now accustomed to. In short, we scraped the ITS project because of the problems with latency/performance. Our connection between our test locations and the Data Center was 100MB. The other locations were 10MB.
ITS Tuning in relating to performance of the ITS Server
1. HKEY_LOCAL_MACHINE\Software\SAP\ITS\2.0\<ITS instance>\Programs\SAPjulep\StaticTemplats
To simulate the test, the parameter for Static Templates was changed from 0 to 1
Recommendation : Development system = 0 ; Production System = 1
2. ITS Parameters / Recommended / Ours
a) Worktreads and Sessions
MaxSessions 400 400
MaxWorkThreads 64 40 (can be reduced)
MinWorkThreads 64 40 (can be reduced)
b) Caching
Caching 1 1
CacheSize 16384 16384
FileSize 1048576 1048576
TimeToLive 31 31
StaticTemplates 1 0
CacheInvalidateHour
CacheInvalidateMinute
Staticflows 1
ProductionMode 1 0
StaticBor 1 0
c) Timeout Parameters
TimeoutPercentage 75 75
d) Debugging Parameters
~rfcDebuggingOn 0 0
~rfcTraceOn 0 0
AdminEnabled 0 0
localTraceLevel 0 0
SAPDebuggerDelay
e) Miscellaneous
MinRespSize 32768 32768
MaxRespSize 2097152 2097152
MaxServiceContextSize 20480 20480
~http_compress_level 7 7
~http_use_compression 1 1
2. Load Balancing and Multiple Agates
IncAGates 1 (Do not modify this value.)
MinAGates (Do not modify this value.)
MaxAgates (Do not modify this value.)
IncWorkThreads 1
3. Windows Environment Settings
4. SAP R/3 Parameters
rdisp/gui_auto_logout >= ~userTimeout
3. Check the following internet option settings.
Under "Advanced", make sure both HTTP 1.1 settings are on
Under "Security", "Custom Level" under the point "micellaneous" make sure these are ENABLE:
a) access the data sources across domains
b) Launch programs and files in IFRAME
c) Migrate sub-frames across different domains
4 Verify Compression. These values were changed in the global.srvc file
~http_use_compression 1
To increase the transmission speed and reduce the overall network load we reduce the size of the data sent from the server to the web browser by using compression. The values are 0 to disable compression and 1 to enable compression.
~http_compress_level 7
The compress level can be set between 1- 9 where 1 is the lowest compression level and 9 is the highest. The higher the value set for ~http_compress_level, the better the compression achieved.
The Level 1 achieves the lowest compression level/ fastest procession speed and Level 9 achieves the highest compression level/slowest procession speed
5 ~navigationenabled : Enables / Disables Drag & Relate functionality in the SAP GUI for HTML.
Using Drag & Relate in the SAP GUI for HTML requires a callback from the R/3 System for nearly every request / response cycle. This is an unnecessary overhead for many applications. Hence we disable Drag&Relate by setting this parameter to 0 in the webgui.srvc file on the Agate.
Citrix proved to be just too expensive an option for right now. The SAP 4.6d protocol proved to be quite thin, with the bandwidth requirements tracking only slightly greater than ICA. However, on a number of occasions over the test period, it was observed that SAP could demand a considerable amount of bandwidth for short bursts. This traffic was primarily outbound, targeted at port 4803. However, even with the thin nature of SAP, ICA still provided a bandwidth advantage.
To better understand this and develop conservative figures, a trend analysis of the data was performed. This analysis allowed for a weighted smoothing of the statistics, lessening the impact of the burst type activities. Based on the trend figures, the following observations where made:
SAP showed an overall Kbps trend average of 2.5 Kbps
ICA showed an overall Kbps trend average of 1.7 Kbps
Overall, ICA showed a 30% improvement in bandwidth utilization when compared to SAP, based on the trend analysis of the data. This margin jumps to almost 70% when averages are analyzed.
The maximum SAP burst activity exceeded the maximum ICA burst activity by 70%.
Both SAP and ICA displayed extremely limited network utilization. Over extended periods, ICA displayed consistently low inbound traffic, trending towards .8
If all you have is 10 users, what's wrong with deploying the SAPGUI?
The ITS environment was initially created with very minimal customized configurations (2 servers Dell 2650's). Most ITS performance parameters were accepted as default. We tested over dual T1's (1.5MB) as well as Ethernet 10/100MB max.
For each request by the webserver, a separate request is made to the backend - so what you get is a constant request/send, even though each one is milliseconds adding hundreds of requests through the WGate to AGate to R/3 you can see there just isn't much you can do to improve the speed.
To help diagnose the network or measure network metrics, we used a program from SAP called “NIPING”. Niping is a test program for the network interfaces (NI) layer. It provides connection and performance test with the same mechanisms that the SAPGUI uses. To test the network, the niping tool runs a continuous test. It generate and evaluate a network trace simultaneously from the ITS server and the front end. We ran several niping tests and the following results were produced.
Since the communication between the client and the Web servers is over the HTTP protocol, SAP-ITS also makes the SAP transactions accessible to distant locations via the Internet, enterprise networks, and virtual private networks. These networks are typically very complex and have many users. As the distance between the nodes and the complexity of the network increase, application performance becomes an important issue. The performance of a network depends mainly on two
different factors - the bandwidth (throughput) and the latency (delay).
Bandwidth is the most commonly known factor affecting performance of a network. Network bandwidth defines the amount of data that can be transferred at a given time. Networks with higher bandwidth provide better performance.
The second factor relating to performance of a network is latency. Latency can be defined as the delay in processing data within the network. A network with lower latency performs better than a network with high latency.
In addition to the individual effects on bandwidth and latency within the network, their combination can also affect the quality of communication, hence determining the overall network performance (network speed).
best regards
MOHAMMED ABDUL MUQEET
9985683706
The SAP Internet Transaction Server (ITS) is the essential link between the SAP R/3 system and the Internet. It enables Internet (and Intranet) users to communicate directly between R/3 system to run R/e transactions, remote enabled function modules and reports as Internet applications components. The ITS is one of the cornerstones of SAP's mySAP.com offerings and strategy and integrated into the SAP 6.10 Web Application Server release. The ITS is the key technology behind the following products: Workplace, Employee Self-Service (ESS), Enterprise Buyer Professional (EBP), BW 2.0 Interface, Online Store and Retail Store, and the APO Interface. There are many other SAP products and applications that are based on ITS technology to interface from the Web to SAP R/3.
SAP ITS can handle complementary Web technologies to access data from SAP R/3:
- SAP GUI for Html: SAP transaction screens are dynamically converted to HTML pages
- Web transactions: SAP transactions that can be called from an HTML page (template based mode)
- Web remote function call (RFC): SAP R/3 function module that can be called from an HTML page
- Web reporting: Mechanism for linking to SAP reports and regenerated lists from an HTML page. Web reporting is implemented as a special-case RFC.
- ITS Flow Logic: Events, statuses, and modes used to model the dialog logic of a Web application in "flow files" on the SAP ITS.
SAP R/3 data is accessed via BAPI or RFC. Access to external data providers is also possible.
SAP's Internet applications are known as Internet Application Components (IAC) or Easy Web Transactions (EWT). Both are complete business solutions that allow Internet and Intranet users to access business information in the SAP R/3 system by starting transactions, function modules, and reports from a Web browser. All IACs or EWTs are based on a common infrastructure consisting of two essential components.
SAP Internet Transaction Server (ITS) - The ITS is the interface between the Internet and R/3 and is the runtime engine that links Web server to the R/3 Application server.
ABAP workbench tool - Web Application Builder and/or SAP@Web Studio - WAB is an R/3 ABAP workbench tool and SAP@Web Studio is a PC tool for creating, modifying and managing all ITS objects on which IACs or EWTs are based. These objects include service files, HTML Templates and HTRC language resource files.
The ITS solution to developing Internet applications is based on the premise that there is already a suitable business application solution, which has a stock of transactions, function modules and reports, as well as its own integrated development environment. All that is needed to enable Internet users to access and run these applications is an interface to the Internet. Apart from the general advantages derived from making SAP R/3 business information available over the internet, the ITS solution has many benefits.
These include:
• Ease of development - Programmers can develop IACsEWTs using a business application system (R/3), development environment (ABAP Workbench) and a programming language (ABAP), with which they are already familiar. There is also integrated data dictionary support from the ABAP Dictionary and appropriate transaction handling.
• Ease of deployment - The ITS solution supports internationalization of applications.
• Ease of use - ITS based IACs and EWTs have the same look and feel as any other Web site.
The separation of programming tasks from the visual design aspects is desirable, because both require different skills. In the ITS scenario, the ABAP programmer develops the application in ABAP using the ABAP Workbench in the SAP R/3 system and the user interface specialist handles the design and navigation aspects of the application with design languages like HTML and SAP's HTML Business in either the SAP@Web studio or ABAP Workbench tool, Web Application Builder.
The aim is to create applications that send documents back to the Web browser client in plain HTML format, since this format can be handled by all major browsers. This is important in an environment like the Internet where there is often little control you can exert over client software such as Web browsers. Fit can be controlled; you can also use Dynamic HTML, Java applets, JavaScript, and VBScript in you HTML templates, because the script language is transparent to the ITS.
How does the SAP ITS work?
When an Internet user requests an ITS service by clicking on a URL hyperlink or keying in a URL address in a Web browser to run a IACEWT, the request is processed as follows:
1. The Web browser passes the request to the Web server.
2. The Web server calls the server-specific ITS extension WGate - WGate is the link between the ITS and the Web server. WGate is a Web server extension that encapsulates the various supported HTTP server interfaces such as: CGI (Common Gateway Interface), NSAPI (Netscape Server Application Programming Interface), ISAPI (Internet Server Application Programming Interface) in a transparent manner that passes the requested data to the ITS AGate component.
3. WGate forwards the request to the ITS server process called AGate (which may or may not reside on the same machine.)
4. AGate is the link between the ITS and the SAP R3 application server. AGate is the core processing component of the ITS. It receives Web browser request from WGate and communicates with the SAP R3 application server via the DIAG or RFC protocol.
5. AGate then processes the requests, and sends all relevant details (including logon information) to the SAP R3 system, which either starts the first dialog step of a new transaction of submits further data for the next dialog step of a transaction already started.
6. SAP R3 starts the transaction for the service requested and sends the screen output to AGate.
7. When the dialog step has finished, AGate retrieves the result from SAP R3, and is responsible for session management, including mapping of SAP R3 screen or function modules to HTML, web session timeout handling, SAP R3 connection management and generation of HTML documents that are sent back to the Web browser client.
8. AGate forwards the formatted HTML page to WGate.
9. WGate forwards the formatted HTML page to the Web server.
10. The Web server sends the formatted HTML page to the Web browser, where it can be viewed by the user.
The ITS is downward compatible, therefore the ITS release must be the same or higher than the SAP R/3 kernel release.
There are three restrictions to this approach:
1. The SAP R3 release must be at least version 3.1I or higher.
2. You can only use those Internet Application Components that were shipped with the SAP R3 release you are using.
3. ITS 6.10 should only be installed in front of an SAP E3 kernel release 6.10 (e.g. CRM 3.0)
*** ITS 4.6D Server Platforms ***
>>Wgate
Microsoft NT 4.0 Server
Microsoft Web Server (ISAPI)
Netscape Web Server (NASPI)
Apache HTTP Server (Apache Module)
Any CGI Web Server (CGI)
Microsoft windows 2000 Server
Microsoft Web Server (ISAPI)
Linux/Intel
Apache HTTP Server (Apache Module)
>>Agate
Microsoft NT4.0 Server
Microsoft Windows 2000 Server
SAP@Web Studio
Microsoft NT 4.0 Workstation
Microsoft Windows 2000 Workstation
*** ITS 6.10 Server Platforms ***
>>Wgate
Microsoft NT 4.0 Server
Microsoft Web Server (ISAPI)
Netscape Web Server (NASPI)
Apache HTTP Server (Apache Module)
Any CGI Web Server (CGI)
Microsoft windows 2000 Server
Microsoft Web Server (ISAPI)
Microsoft XP Server
Linux/Intel
Apache HTTP Server (Apache Module)
>>Agate
Microsoft NT4.0 Server
Microsoft Windows 2000 Server
Microsoft XP Server
SAP@Web Studio
Microsoft NT 4.0 Workstation
Microsoft Windows 2000 Workstation
Microsoft XP Server
Evaluate ITS Server Speed issues
You have 10 users accessing sap via an ITS server (6.20) and it is soooo slow !!! access via sapgui is fast - any ideas what to look for ??
We tested several options for deploying the SAPGUI :-
Tivoli packages
ITS
Citrix MF XP
Tivoli was already built and in house so all we had to do was create a SAPGUI package and deploy it to the field (3000+ users) - pain in the butt because we had to find out all the users workstation id's for the users in 900+ locations. So far we have deployed 35% and our Go-live is 10/01!
ITS - We had an ITS consultant come in and review our setup. We were able to enhance the performance to some extent (20%). But, that was still unacceptable in comparison to the WINGUI that the users are now accustomed to. In short, we scraped the ITS project because of the problems with latency/performance. Our connection between our test locations and the Data Center was 100MB. The other locations were 10MB.
ITS Tuning in relating to performance of the ITS Server
1. HKEY_LOCAL_MACHINE\Software\SAP\ITS\2.0\<ITS instance>\Programs\SAPjulep\StaticTemplats
To simulate the test, the parameter for Static Templates was changed from 0 to 1
Recommendation : Development system = 0 ; Production System = 1
2. ITS Parameters / Recommended / Ours
a) Worktreads and Sessions
MaxSessions 400 400
MaxWorkThreads 64 40 (can be reduced)
MinWorkThreads 64 40 (can be reduced)
b) Caching
Caching 1 1
CacheSize 16384 16384
FileSize 1048576 1048576
TimeToLive 31 31
StaticTemplates 1 0
CacheInvalidateHour
CacheInvalidateMinute
Staticflows 1
ProductionMode 1 0
StaticBor 1 0
c) Timeout Parameters
TimeoutPercentage 75 75
d) Debugging Parameters
~rfcDebuggingOn 0 0
~rfcTraceOn 0 0
AdminEnabled 0 0
localTraceLevel 0 0
SAPDebuggerDelay
e) Miscellaneous
MinRespSize 32768 32768
MaxRespSize 2097152 2097152
MaxServiceContextSize 20480 20480
~http_compress_level 7 7
~http_use_compression 1 1
2. Load Balancing and Multiple Agates
IncAGates 1 (Do not modify this value.)
MinAGates (Do not modify this value.)
MaxAgates (Do not modify this value.)
IncWorkThreads 1
3. Windows Environment Settings
4. SAP R/3 Parameters
rdisp/gui_auto_logout >= ~userTimeout
3. Check the following internet option settings.
Under "Advanced", make sure both HTTP 1.1 settings are on
Under "Security", "Custom Level" under the point "micellaneous" make sure these are ENABLE:
a) access the data sources across domains
b) Launch programs and files in IFRAME
c) Migrate sub-frames across different domains
4 Verify Compression. These values were changed in the global.srvc file
~http_use_compression 1
To increase the transmission speed and reduce the overall network load we reduce the size of the data sent from the server to the web browser by using compression. The values are 0 to disable compression and 1 to enable compression.
~http_compress_level 7
The compress level can be set between 1- 9 where 1 is the lowest compression level and 9 is the highest. The higher the value set for ~http_compress_level, the better the compression achieved.
The Level 1 achieves the lowest compression level/ fastest procession speed and Level 9 achieves the highest compression level/slowest procession speed
5 ~navigationenabled : Enables / Disables Drag & Relate functionality in the SAP GUI for HTML.
Using Drag & Relate in the SAP GUI for HTML requires a callback from the R/3 System for nearly every request / response cycle. This is an unnecessary overhead for many applications. Hence we disable Drag&Relate by setting this parameter to 0 in the webgui.srvc file on the Agate.
Citrix proved to be just too expensive an option for right now. The SAP 4.6d protocol proved to be quite thin, with the bandwidth requirements tracking only slightly greater than ICA. However, on a number of occasions over the test period, it was observed that SAP could demand a considerable amount of bandwidth for short bursts. This traffic was primarily outbound, targeted at port 4803. However, even with the thin nature of SAP, ICA still provided a bandwidth advantage.
To better understand this and develop conservative figures, a trend analysis of the data was performed. This analysis allowed for a weighted smoothing of the statistics, lessening the impact of the burst type activities. Based on the trend figures, the following observations where made:
SAP showed an overall Kbps trend average of 2.5 Kbps
ICA showed an overall Kbps trend average of 1.7 Kbps
Overall, ICA showed a 30% improvement in bandwidth utilization when compared to SAP, based on the trend analysis of the data. This margin jumps to almost 70% when averages are analyzed.
The maximum SAP burst activity exceeded the maximum ICA burst activity by 70%.
Both SAP and ICA displayed extremely limited network utilization. Over extended periods, ICA displayed consistently low inbound traffic, trending towards .8
If all you have is 10 users, what's wrong with deploying the SAPGUI?
The ITS environment was initially created with very minimal customized configurations (2 servers Dell 2650's). Most ITS performance parameters were accepted as default. We tested over dual T1's (1.5MB) as well as Ethernet 10/100MB max.
For each request by the webserver, a separate request is made to the backend - so what you get is a constant request/send, even though each one is milliseconds adding hundreds of requests through the WGate to AGate to R/3 you can see there just isn't much you can do to improve the speed.
To help diagnose the network or measure network metrics, we used a program from SAP called “NIPING”. Niping is a test program for the network interfaces (NI) layer. It provides connection and performance test with the same mechanisms that the SAPGUI uses. To test the network, the niping tool runs a continuous test. It generate and evaluate a network trace simultaneously from the ITS server and the front end. We ran several niping tests and the following results were produced.
Since the communication between the client and the Web servers is over the HTTP protocol, SAP-ITS also makes the SAP transactions accessible to distant locations via the Internet, enterprise networks, and virtual private networks. These networks are typically very complex and have many users. As the distance between the nodes and the complexity of the network increase, application performance becomes an important issue. The performance of a network depends mainly on two
different factors - the bandwidth (throughput) and the latency (delay).
Bandwidth is the most commonly known factor affecting performance of a network. Network bandwidth defines the amount of data that can be transferred at a given time. Networks with higher bandwidth provide better performance.
The second factor relating to performance of a network is latency. Latency can be defined as the delay in processing data within the network. A network with lower latency performs better than a network with high latency.
In addition to the individual effects on bandwidth and latency within the network, their combination can also affect the quality of communication, hence determining the overall network performance (network speed).
best regards
MOHAMMED ABDUL MUQEET
9985683706