Tadm10 2 en Col99 Fv Part a4

TADM10_2SAP NetWeaver AS

Implementation & OperationI

SAP NetWeaver

Date

Training Center

Instructors

Education Website

Participant HandbookCourse Version: 99Course Duration: 10 Day(s)Material Number: 50118031

An SAP course - use it to learn, reference it for work

Copyright

Copyright 2013 SAP AG or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may be changedwithout prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.

Trademarks

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks ofAdobe Systems Incorporated in the United States and other countries.

Apple, App Store, FaceTime, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C,Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.

Bluetooth is a registered trademark of Bluetooth SIG Inc.

Citrix, ICA, Program Neighborhood, MetaFrame now XenApp, WinFrame, VideoFrame, andMultiWin are trademarks or registered trademarks of Citrix Systems Inc.

Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.

Edgar Online is a registered trademark of EDGAR Online Inc., an R.R. Donnelley & Sons Company.

Facebook, the Facebook and F logo, FB, Face, Poke, Wall, and 32665 are trademarks of Facebook.

Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, GoogleMobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater,Google Voice, Google Mail, Gmail, YouTube, Dalvik, and Android are trademarks or registeredtrademarks of Google Inc.

HP is a registered trademark of the Hewlett-Packard Development Company L.P.

HTML, XML, XHTML, and W3C are trademarks, registered trademarks, or claimed as genericterms by the Massachusetts Institute of Technology (MIT), European Research Consortium forInformatics and Mathematics (ERCIM), or Keio University.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, Systemz, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, PowerSystems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter,System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks,OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarksor registered trademarks of IBM Corporation.

Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registeredtrademarks of Microsoft Corporation.

INTERMEC is a registered trademark of Intermec Technologies Corporation.

IOS is a registered trademark of Cisco Systems Inc.

The Klout name and logos are trademarks of Klout Inc.

Linux is the registered trademark of Linus Torvalds in the United States and other countries.

Motorola is a registered trademark of Motorola Trademark Holdings LLC.

Mozilla and Firefox and their logos are registered trademarks of the Mozilla Foundation.

Novell and SUSE Linux Enterprise Server are registered trademarks of Novell Inc.

g201332495638

OpenText is a registered trademark of OpenText Corporation.

Oracle and Java are registered trademarks of Oracle and its affiliates.

QR Code is a registered trademark of Denso Wave Incorporated.

RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch,BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry AppWorld aretrademarks or registered trademarks of Research in Motion Limited.

SAVO is a registered trademark of The Savo Group Ltd.

The Skype name is a trademark of Skype or related entities.

Twitter and Tweet are trademarks or registered trademarks of Twitter.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Wi-Fi is a registered trademark of Wi-Fi Alliance.

SAP, R/3, ABAP, BAPI, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjectsExplorer, StreamWork, SAP HANA, the Business Objects logo, BusinessObjects, Crystal Reports,Crystal Decisions, Web Intelligence, Xcelsius, Sybase, Adaptive Server, Adaptive Server Enterprise,iAnywhere, Sybase 365, SQL Anywhere, Crossgate, B2B 360 and B2B 360 Services, m@gicEDDY, Ariba, the Ariba logo, Quadrem, b-process, Ariba Discovery, SuccessFactors, Executionis the Difference, BizX Mobile Touchbase, It's time to love work again, SuccessFactors Jam andBadAss SaaS, and other SAP products and services mentioned herein as well as their respectivelogos are trademarks or registered trademarks of SAP AG in Germany or an SAP affiliate company.

All other product and service names mentioned are the trademarks of their respective companies.Data contained in this document serves informational purposes only. National product specificationsmay vary.

Disclaimer

These materials are subject to change without notice. These materials are provided by SAP AG andits affiliated companies (SAP Group) for informational purposes only, without representation orwarranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to thematerials. The only warranties for SAP Group products and services are those that are set forth inthe express warranty statements accompanying such products and services, if any. Nothing hereinshould be construed as constituting an additional warranty.

g201332495638

g201332495638

About This HandbookThis handbook is intended to complement the instructor-led presentation of thiscourse, and serve as a source of reference. It is not suitable for self-study.

Typographic ConventionsAmerican English is the standard used in this handbook. The followingtypographic conventions are also used.

Type Style Description

Example text Words or characters that appear on the screen. Theseinclude field names, screen titles, pushbuttons as wellas menu names, paths, and options.

Also used for cross-references to other documentationboth internal and external.

Example text Emphasized words or phrases in body text, titles ofgraphics, and tables

EXAMPLE TEXT Names of elements in the system. These includereport names, program names, transaction codes, tablenames, and individual key words of a programminglanguage, when surrounded by body text, for exampleSELECT and INCLUDE.

Example text Screen output. This includes file and directory namesand their paths, messages, names of variables andparameters, and passages of the source text of aprogram.

Example text Exact user entry. These are words and characters thatyou enter in the system exactly as they appear in thedocumentation.

Variable user entry. Pointed brackets indicate that youreplace these words and characters with appropriateentries.

2013/Q1 2013 SAP AG or an SAP affiliate company. All rights reserved. v

About This Handbook TADM10_2

Icons in Body TextThe following icons are used in this handbook.

Icon Meaning

For more information, tips, or background

Note or further explanation of previous point

Exception or caution

Procedures

Indicates that the item is displayed in the instructor'spresentation.

vi 2013 SAP AG or an SAP affiliate company.

All rights reserved. 2013/Q1

Contents

Course Overview .......................................................... ix

Course Goals .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixCourse Objectives ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Unit 1: Technology Components for Browser-Based UserDialogs........................................................................ 1

Internet Scenarios with SAP Systems... . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3The Internet Communication Manager (ICM) ... . . . . . . . . . . . . . . . . . . 10Internet Communication Framework ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28The SAP Web Dispatcher.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Load Balancing in the SAP NetWeaver AS Java Environment . 93

Unit 2: AS ABAP Fundamentals of User Administration ....109

User Administration Concept .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Authorization Concept.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121Login Parameters and User Info .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139Appendix: Advanced User Administration Topics .. . . . . . . . . . . . . .149

Unit 3: Setting up SSL for AS Java ................................. 159

Network Security .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160Setting Up SSL ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168

Unit 4: AS Java User and Authorization Concept............. 193

Structure and Configuration of the User Management Engine(UME) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195

User and Group Administration ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .222The Java Authorization Concept .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .235Special Principles .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253Logon Procedure of the AS Java ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .264

Unit 5: RFC Connections, Communication and IntegrationTechnologies ............................................................. 285

Fundamentals and Variants for Using RFC... . . . . . . . . . . . . . . . . . . . .286Setting Up RFC Connections... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .298

Unit 6: Java Connector and Destinations ......................... 315

Connections to other Systems ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .316Appendix: Connections to other Systems with the Java Connector

Architecture .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .332

2013/Q1 2013 SAP AG or an SAP affiliate company. All rights reserved. vii

Contents TADM10_2

Unit 7: AS ABAP System Monitoring and Troubleshooting 345

Monitoring Architecture.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .347Configuring System Monitoring in CCMS.... . . . . . . . . . . . . . . . . . . . . .361Introduction to Monitoring using SAP Solution Manager .. . . . . .383Traces and Logs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .398Troubleshooting Procedure... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411

Unit 8: AS Java Monitoring......................................... 419

Monitoring SAP NetWeaver AS Java ... . . . . . . . . . . . . . . . . . . . . . . . . . .420Connecting to a Central Monitoring System... . . . . . . . . . . . . . . . . . . .432Availability Monitoring ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .451Log Viewer and Log Configuration ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . .464

Unit 9: Software Lifecycle Management ........................... 489

Glossary................................................................... 493

Index ....................................................................... 497

viii 2013 SAP AG or an SAP affiliate company.


Course OverviewCourse TADM10 is the foundation for various, further training courses forconsultants. After TADM10, you can continue your training to become a(Technical) PI or Portal Consultant. Alternatively, you can proceed to courseTADM12 where you will further expand your knowledge of SAP NetWeaver AS.

This training content is largely independent of the type of operating system anddatabase technology.

Like the other TADM courses, TADM10 comprises several individual courses (orparts thereof), which are arranged here in a way that will enable you to gain theknowledge you require as an SAP Technology Consultant as efficiently as possible.

Week 1 of Course TADM10 is Based On Content Taken from the FollowingCourses:

1. SAPTEC

2. ADM100

3. ADM800

Week 2 of Course TADM10 is Based On Content Taken from the FollowingCourses:

1. SAPTEC

2. ADM100

3. ADM103

4. ADM800

Target Audience

This course is intended for the following audiences:

SAP Technology Consultants (Associate Level)

Course Prerequisites

Required Knowledge

Basic knowledge of IT

Basic knowledge of operating systems and databases

2013/Q1 2013 SAP AG or an SAP affiliate company. All rights reserved. ix

Course Overview TADM10_2

Course GoalsThis course will prepare you to:

Work as a Technology Consultant

Configure and manage AS ABAP

Configure and manage AS Java

Course Objectives

After completing this course, you will be able to:

Process administrative tasks in SAP systems

x 2013 SAP AG or an SAP affiliate company.


Unit 1Technology Components forBrowser-Based User Dialogs

Unit OverviewIn this unit, you learn about a number of central technology components that areimportant if SAP systems are used for intranet or internet applications. In courseADM103, the focus is on administration of the components that are introduced,not on development.

The SAP Internet Transaction Server (ITS) is used with Web applications(IACs) and with SAP GUI for HTML. Depending on the system release andscenario in question, the functions of the SAP ITS can be implemented bymeans of a standalone ITS or using the ITS integrated in the AS ABAP.

The Internet Communication Manager (ICM) is the process that turns theconventional ABAP application server into a Web server or Web client.

The Internet Communication Framework (ICF) provides an environmentfor handling HTTP(S) requests in the ABAP work process using Webapplications such as BSPs or Web Dynpro ABAP.

With the usage type AS Java, the SAP NetWeaver Application Serverprovides a complete runtime environment for Java EE applications.

The SAP Web Dispatcher distributes HTTP(S) requests to a suitableapplication server (instance).

Unit ObjectivesAfter completing this unit, you will be able to:

Describe the options that SAP provides for intranet and internet scenarios

Describe the areas of use of SAP ITS, ICM, AS ABAP, and AS Java

Describe the implementation area of the ICM

Configure and monitor the ICM

Explain the importance of the Internet Communication Framework (ICF)for handling HTTP requests

Outline the interaction model

Describe what constitutes an ICF service

2013/Q1 2013 SAP AG or an SAP affiliate company. All rights reserved. 1

Unit 1: Technology Components for Browser-Based User Dialogs TADM10_2

Activate and use the integrated ITS

Outline the function of the SAP Web Dispatcher

Explain how you can use the SAP Web Dispatcher to distribute workloadacross the different SAP instances and/or SAP systems

Install, update and operate the SAP Web Dispatcher

Explain how load balancing can be realized in the SAP system

Unit ContentsLesson: Internet Scenarios with SAP Systems ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3Lesson: The Internet Communication Manager (ICM) ... . . . . . . . . . . . . . . . . . . . 10

Exercise 1: Administration of the ICM .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Lesson: Internet Communication Framework ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Exercise 2: Administrative Work with the ICF ... . . . . . . . . . . . . . . . . . . . . . . . . 43Lesson: The SAP Web Dispatcher .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Exercise 3: Administration of the SAP Web Dispatcher.. . . . . . . . . . . . . . . 71Lesson: Load Balancing in the SAP NetWeaver AS Java Environment.. 93

2 2013 SAP AG or an SAP affiliate company.


TADM10_2 Lesson: Internet Scenarios with SAP Systems

Lesson: Internet Scenarios with SAP Systems

Lesson OverviewSAP provides a number of ways in which applications can be created forintranet or internet users. This lesson introduces the technologies on which theseapplications are based and explains the differences between them.

Lesson ObjectivesAfter completing this lesson, you will be able to:



Business ExampleYour company wants to allow its customers browser-based access to data in theSAP system (for example, in the context of Web-based purchasing). As a memberof the system administration team, it is your task to compare and evaluate differentmethods of realizing this.

SAP Internet Transaction Server (SAP ITS)(Standalone)

Figure 1: As of SAP Basis 3.1G: Web-Enabling Using SAP ITS (Standalone)



SAP delivered the first version of the SAP Internet Transaction Server (SAP ITS)with SAP R/3 3.1G in 1996. It is a software component that acts as a gatewaybetween a Web server and an SAP system. SAP ITS switches between internetprotocols and formats (such as HTTP, HTTPS, and HTML) and those of the SAPsystem (such as DIAG, RFC, and dynpros (screens)).

First, the SAP ITS was implemented as standalone software, that was used infront of an ABAP-based SAP system. This standalone ITS existed as ofRelease 3.1G up to and including 6.20 (upwardly and downwardly compatiblewith SAP systems up to and including AS ABAP 6.40). As of AS ABAP 6.40, thenew ITS is integrated in AS ABAP on all platforms with a simplified architecture.

Web applications that were developed specifically for SAP ITS are called InternetApplication Components (IACs). These include Employee Self Services (ESS)that are based on SAP R/3 and SAP R/3 Enterprise or the SAP Online Store. TheSAP GUI for HTML also uses the SAP ITS.

SAP ITS functionality (either standalone or integrated) is therefore required forexisting Web applications (in IAC technology) and the SAP GUI for HTML,regardless of the basis release of the corresponding SAP system.

Internet Communication Manager (ICM)

Figure 2: As of SAP Web AS 6.10: Openness Using the ICM

Based on the highly-scalable infrastructure, new technologies are used as of SAPWeb AS 6.10 to process HTTP requests (and other protocols) directly from theinternet or to send HTTP client requests to the internet. To achieve this, the SAPKernel has been extended with the Internet Communication Manager (ICM)process.




The ICM process forwards requests to the Internet Communication Framework(ICF), which supports numerous programming models. This is how the SAPCRM, SAP BW, and SAP PI software components use this infrastructure. Aprogramming model for such applications (among others) are the Business ServerPages (BSPs).

AS Java

Figure 3: As of SAP Web AS 6.20: Integrated J2EE Runtime Environment

With the AS Java, SAP has a complete J2EE-compatible application server in itsproduct range. The SAP NetWeaver Application Server provides the followinginstallation options (as of Release 6.20):

SAP Netweaver Application Server ABAP (AS ABAP)

SAP Netweaver Application Server Java (AS Java)

SAP Netweaver Application Server ABAP+Java (AS ABAP+Java, dualstack)

Developers, therefore, have a mature development and runtime environment forapplications based on Java / J2EE. Examples of SAP software componentsthat use the J2EE engine include SAP NetWeaver Portal (usage type EP), SAPNetWeaver Process Integration (usage type PI), and some functions in SAPCustomer Relationship Management (SAP CRM).

Note that the J2EE standard not only describes the (browser-based) user dialog,but also specifies a complete application server.



Web DynproWeb Dynpro is the preferred programming model for business applicationWeb interfaces in SAP systems based on SAP NetWeaver. It provides a cleardistinction between the user interface (UI) and the business logic. It alsoprovides functions that are not usually available as part of the standard tools fordeveloping professional user interfaces. These include functions for checkingentries, providing input help, supporting multiple languages, and handling errorscomfortably, as well as caching mechanisms that ensure fast response times andare therefore especially useful for interactive user interfaces.

The Web Dynpro programming model is available as Web Dynpro Java (as of ASJava 6.40) and Web Dynpro ABAP (as of AS ABAP 7.00). The basic conceptsof these two flavors are very similar, and so the user cannot easily recognize thetechnology used.

Figure 4: As of SAP Web AS 6.40: Web Dynpro Java




Figure 5: As of SAP NetWeaver AS 7.00: Web Dynpro ABAP

SAPUI5 is the SAP implementation of the open HTML5 standard. Afterdeploying the plug-in UI_INFRA (available for AS ABAP 7.00 onwards), the ICFcan process Web pages based on HTML5.

OData is an open standard that can be consumed by any software or device thatcan communicate using the HTTP(S) protocol and can parse and construct anXML document. OData can also be described as ODBC for the Web. SAPNetWeaver Gateway (a new product; do not confuse with the Gateway process)is the implementation of the OData standard on an AS ABAP system (availablefor AS ABAP 7.00 onwards).



Architectural Changes

Figure 6: As of SAP NetWeaver AS 7.10: Architectural Changes

Some of the changes introduced with AS Java 7.10 are

The Java Dispatcher process was replaced by the ICM process.

The SDM process was discontinued.




Lesson Summary

You should now be able to:



Related Information

SAP Community Network, Quick Links

/community/ui-technology

/community/its

/community/gui

/community/web-dynpro-abap

/community/web-dynpro-java

/community/netweaver-business-client

/community/developer-center/front-end



Lesson: The Internet Communication Manager (ICM)

Lesson OverviewIn this lesson, you will learn about the Internet Communication Manager (ICM)process and administration options.




Business ExampleAs part of the conversion to a modern, service-oriented IT infrastructure, newSAP applications based on Web Dynpro and SOAP services are implementedin your company. As a member of the system administration team, it is yourtask to configure the AS ABAP based SAP systems in accordance with yourrequirements. You therefore require an overview of the central process of intranetand internet connection the Internet Communication Manager (ICM).

Architecture of the ICM Process

Figure 7: System Landscape with AS ABAP (Example)



TADM10_2 Lesson: The Internet Communication Manager (ICM)

The figure above shows an example of a system landscape in which Webbrowsers from the internet and intranet are connected with an AS ABAP.Important features are:

Support for standard Web protocols such as HTTP, HTTP, WebDAV, SOAP,and SMTP

Display of standard Web formats such as HTML, XML, and XSLT

Complete integration into the SAP environment (development environment,user administration, authorization concept, system monitoring, andcommunication protocols)

As of Release 6.10, the AS ABAP can function both as aWeb server (server role)and as aWeb client (client role). The server role, in which the AS ABAP canaccept and process HTTP requests from any Web client (such as a Web browser)and send back an HTTP response, is what we will discuss in this lesson.

Within a work process, the Internet Communication Framework (ICF) providesthe environment for handling HTTP requests. The ICF is the bridge between the Ckernel of the SAP system and the application program created in ABAP.

As of AS ABAP 6.10, work processes can directly generate Web-compatiblecontent in a way that can be forwarded to a browser using the ICM. One way ofcreating content of this type is to use applications with Busines Server Pages(BSPs) that were developed in the SAP system using a tool of transaction SE80,the Web Application Builder for BSPs. Starting with AS ABAP 7.00, Web DynproABAP was introduced a new programming framework for state-of-the-art Webapplications.



Figure 8: Internal Structure of the ICM Process

From a technical point of view, the ICM is a separate process (icman at operatingsystem level) that is started and monitored by the ABAP dispatcher. Its task isto ensure that the SAP system can communicate with the outside world (usingHTTP, HTTPS, and SMTP). In the server role, it can process requests from theintranet/internet that arrive with URLs with the server/port combination for which




the ICM is listening. The ICM then calls the appropriate local handler, dependingon the URL. The ICM process uses threads to process the created workload inparallel. The components of the ICM are:

Thread Control: This thread accepts the incoming TCP/IP requests andcreates (or raises) a worker thread from the threadpool to process the request.

Worker Thread: This thread handles requests and responses for aconnection. A worker thread contains an I/O handler for the network inputand output, and various plug-ins for the different supported protocols.

Watchdog: A worker thread usually waits for a response (whether it is clientor server); if a timeout occurs, the watchdog takes over the task of waitingfor the response. The worker thread can then be used for other requests.

Signal Handler: Processes signals that are sent from the operating system oranother process (such as the ABAP dispatcher).

Connection Info: Table with information for each existing networkconnection.

Memory Pipes: These memory-based communication objects allow datatransfer between the ICM and the ABAP work processes.

Hint: As of AS Java 7.10, the ICM has replaced the former Javadispatcher process so the ICM is also part of every AS Java instance(except the Java Central Services instance).

The ICM uses plug-ins to implement the following communication protocols:

HTTP

HTTPS

SMTP



Figure 9: Internet Server Cache (ISC)

A part of the ICM that is important for performance is the Internet Server Cache(ISC), which stores HTTP(S) objects before they are sent to the Web browser. Thenext request can then be made directly from the ISC, provided that the expiry timehas not elapsed. This avoids branching to the ABAP work process, which canaccelerate access considerably.

Some features of the ISC:

Two-level hierarchy: When objects are stored, the advantages of both thehigh speed of main memory (memory cache) and the storage capacity of harddisks (disk cache) are used.

Dynamic Caching: Traditional products are based on HTTP proxies andusually offer caching only of static content, such as images. The ISC canalso cache dynamic content such as JSPs or BSPs.

Active Caching: The application has full control over ensuring that theobjects in the cache are up to date.

UFO Caching: Invalid requests (UnFound Objects) that lead to errorsituations in the application server or the database are directly rejected, sothat the system is protected against invalid or malignant requests.

Browser-dependent Caching: The developer of Web objects can definewhether his or her application is dependent on browser type. If this indicatoris set, the ISC uses the data in the cache only for requests from the samebrowser type.




The ISC is configured using the profile parameter icm/HTTP/server_cache* andcan be monitored and invalidated from the SAP system.

Start Procedure and Monitoring

Figure 10: Starting the ICM

The profile parameter rdisp/start_icman controls whether an ICM process is alsostarted when an application server is started. If no value is specified, the defaultsetting true applies. You configure the ICM using profile parameters (most ofwhich begin with icm/. The settings for icm/server_port_ are of particularimportance.These settings determine the port used for each protocol, as well asother attributes of the protocol (such as timeout).

In the SAP system, you can quickly obtain an overview of which applicationservers are running with an ICM using the server overview (transaction SM51).

For more detailed information (such as the thread ID), see the ICM monitor(transaction SMICM). From this transaction, you can choose the menu pathAdministration ICM Exit ... to terminate the ICM with a soft termination(corresponds to Unix signal 2) or a hard termination (corresponds to Unixsignal 9). The ABAP dispatcher then starts a new ICM process. By choosingAdministration ICM Restart Yes/No, you can control whether the ABAPdispatcher restarts the ICM if it was terminated by an error or at the request ofan administrator.



Figure 11: Functions of the ICM Monitor




The most important tool for an administrator in the ICM environment is the ICMmonitor (transaction SMICM). Note that the data displayed is instance-dependent(in the same way as the work process overview SM50). Some administrativeactivities (all available from transaction SMICM) are:

Monitoring and restarting the ICM

Configuring the trace level (Goto Trace Level ...), values from 0 to 3.

Evaluating the trace files (Goto Trace File ...); the system reads thedev_icm file from the work directory of the current instance.

Overview of the profile parameters (GotoParametersDisplay/Change).The ICM is configured using profile parameters. The displayed values applyfor the instance to which you are currently logged on. For documentation onthe parameters, see the ICM monitor (Goto Parameters Change andchoose Documentation), transaction RZ11, and SAP online documentation.

Display the statistics (Goto Statistics Display). You can use thesestatistics to find out how many requests the ICM has processed since itwas started (or since the statistics were reset). The system also displaysinformation about processing duration.

Monitoring (Goto HTTP Plug-In Server Cache Display) andresetting (Goto HTTP Plug-In Server Cache Invalidate ...) theICM server cache. The ICM server cache stores HTTP objects before theyare sent to the client. The next time that this object is requested, the contentcan be sent directly from the cache to the client.

In maintenance mode, the ICM logs off from the ABAP message server andis not available for Web requests. The ICM processes only the remainingrequests. If an internet user accesses an ICM in this status from the browser,the system issues a message stating that the ICM is in Maintenance Mode.

You can determine some of the listed data at operating system level using theicmon program. The call icmon -h displays the possible parameters for this smallprogram, which can also, among other things, generate requests to simulatenormal system workload.



Exercise 1: Administration of the ICM

Exercise ObjectivesAfter completing this exercise, you will be able to:

Monitor the ICM process

Business ExampleAs part of SAP BI, your company uses browser-based functions such as Webreporting, interactive charts, and the Business Explorer Browser (BEx Browser).As an administrator, you are responsible for monitoring the ICM processes thatestablish the connection between the Web browser and the SAP system.

Task 1: Checking the ICM Settings

Figure 12: Complete Scenario of the Training Landscape

Number, port, and release of the ICM processes in the training environment.

1. How many ICM processes are running in your SAP ECC system?

2. Determine the port through which requests in the HTTP protocol areprocessed for the application server to which you are currently logged on.

Continued on next page



3. Which release of the ICM is used on the training system?

Result

You know the port and release for the ICM process on the training system.

Task 2: Simple HTTP RequestsStart a request in the Web browser and monitor it with the ICM monitor.

1. Launch the following URL: http://twdf-SSSS.wdf.sap.corp:80$$/sap/public/ping(example for group QCC and server twdf0042http://twd0042.wdf.sap.corp:8010/sap/public/ping).

The message Server reached successfully appears.

2. Open the ICM monitor and note how many requests from your Web browser(you may have to Refresh the URL above) have been processed by theworker threads.

Hint: The data in the ICM monitor is instance-specific.

3. Launch the following URL: http://twdf-SSSS.wdf.sap.corp:80$$/sap/public/icman/ping.

4. Launch the following URL: http://twdf-SSSS.wdf.sap.corp:80$$/sap/public/ic-man/mime/theme.jpg.

Result

You can monitor the activity of the ICM.

Task 3: Load Test with icmon ToolMonitor the ICM worker threads under a generated workload.

1. At operating system level of your server, start the icmon pf= command and enter an instance profile of your ECCsystem for instance profile name.

Launch the menu (by pressing m) and generate load (by pressing g) withthe following values:





Host Host on which your SAP system is running,such as twdfSSSS.wdf.sap.corp (defaultsetting)

Port An ICM Port valid for your system, such as 8011

'1.x'=HTTP/1.x or '9.x'HTTPS

1.1 (default setting)

Get request data fromfile

No (default setting)

Path /sap/public/icman/mime/theme.jpg

Optional Attributes No (default setting)

Expected OK-Code 0 (default setting)

Think time in millisecs 0 (default setting)

Number of requests 7500

Number of threads 10

Wait time in millisecsbetween threadcreation duringrampup

0 (default setting)

2. Observe in the ICM monitor how the requests generated by icmon areprocessed by the worker threads.

Result

You can use the icmon tool to monitor the ICM and to start workloadsimulations.

Task 4: Maintenance ModeSetting the ICM process into the maintenance mode.

1. Using the ICM monitor (transaction SMICM), active the maintenance mode.

2. Launch the following URL: http://twdf-SSSS.wdf.sap.corp:80$$/sap/public/ping (and make surethat $$ matches the instance on which you activated the maintenance mode).

3. Using the ICM monitor (transaction SMICM), deactive the maintenancemode.

Result

You can enter and leave the maintenance mode.



Solution 1: Administration of the ICM

Task 1: Checking the ICM Settings


Number, port, and release of the ICM processes in the training environment.

1. How many ICM processes are running in your SAP ECC system?

a) In the server overview (transaction SM51), count the applicationservers for which the ICM process is listed. An ICM process should beconfigured for each of your ABAP instances.





2. Determine the port through which requests in the HTTP protocol areprocessed for the application server to which you are currently logged on.

a) Check the value of the profile parameters icm/server_port_, forexample:

In the ICM monitor (transaction SMICM) by choosing Goto Parameters Display

By executing report RSPFPAR

In transaction RZ10

Hint: The determined port is instance-specific. In the trainingsystems, the parameter icm/server_port_0 has the valuePROT=HTTP,PORT=80$$ (and further timeout settings). Thevariable $$ is replaced by the instance number when the ICMis started, ensuring that ports are unique per host in all cases.

3. Which release of the ICM is used on the training system?

a) You can determine the ICM release in the ICM monitor (transactionSMICM) by choosing Release Notes or Goto Release Notes.

The information that you are looking for is at the start of the list. Atthe end of the list, all problems that are solved with the current patchlevel are listed (with associated SAP Notes).

Result

You know the port and release for the ICM process on the trainingsystem.

Task 2: Simple HTTP RequestsStart a request in the Web browser and monitor it with the ICM monitor.

1. Launch the following URL: http://twdf-SSSS.wdf.sap.corp:80$$/sap/public/ping(example for group QCC and server twdf0042http://twd0042.wdf.sap.corp:8010/sap/public/ping).




The message Server reached successfully appears.

a) Enter the specified URL in your local Web browser and choose Enter.

Hint: All services under /sap/public use a predefined user(SAPSYS); therefore, no logon is required for this request.

As of AS ABAP 6.20, services must be explicitly activated.This should already been prepared in the training system forthe services specified in this exercise.

2. Open the ICM monitor and note how many requests from your Web browser(you may have to Refresh the URL above) have been processed by theworker threads.

Hint: The data in the ICM monitor is instance-specific.

a) In the ICM monitor (transaction SMICM), choose the Refresh buttonafter you have sent a few requests to the ICM.

3. Launch the following URL: http://twdf-SSSS.wdf.sap.corp:80$$/sap/public/icman/ping.

a) See task description. The message server on host twdfSSSS systemtwdfSSSS__ (000) successfully reached appears.

4. Launch the following URL: http://twdf-SSSS.wdf.sap.corp:80$$/sap/public/ic-man/mime/theme.jpg.

a) See task description. A small image should appear.

Result

You can monitor the activity of the ICM.

Task 3: Load Test with icmon ToolMonitor the ICM worker threads under a generated workload.

1. At operating system level of your server, start the icmon pf= command and enter an instance profile of your ECCsystem for instance profile name.

Launch the menu (by pressing m) and generate load (by pressing g) withthe following values:





Host Host on which your SAP system is running,such as twdfSSSS.wdf.sap.corp (defaultsetting)

Port An ICM Port valid for your system, such as 8011

'1.x'=HTTP/1.x or '9.x'HTTPS

1.1 (default setting)

Get request data fromfile

No (default setting)

Path /sap/public/icman/mime/theme.jpg

Optional Attributes No (default setting)

Expected OK-Code 0 (default setting)

Think time in millisecs 0 (default setting)

Number of requests 7500

Number of threads 10

Wait time in millisecsbetween threadcreation duringrampup

0 (default setting)

a) If you have not already done so, log onto the Terminal Services Client(also known as the RDP Client) at operating-system level using the useradm.

b) Open Windows Explorer and navigate to the directoryD:\usr\sap\\SYS\profile. Click the profile directory(in the left pane) with the right mouse button and choose CMD PromptHere.

c) Within the command prompt, start the icmon program with an instanceprofile: icmon pf= (examplefor the dialog instances of group QCC on server twdf0042: icmonpf=QCC_D11_twdf0042).

Hint: You can drag&drop a file name from the Windowsexplorer into the command prompt window.

d) Enter the command m to switch to the Monitor-Menue and generateload by entering the command g and the parameters specified in thetask description.




2. Observe in the ICM monitor how the requests generated by icmon areprocessed by the worker threads.

a) In transaction SMICM, choose the Refresh function to observe theactivity of the worker threads. You may notice that the ICM startsfurther worker threads.

Remember that the display in transaction SMICM is not system-wide,but only applies to your instance.

Note: The default load data generates 75,000 requests (that is,number of requests multiplied by number of threads).

Result

You can use the icmon tool to monitor the ICM and to start workloadsimulations.

Task 4: Maintenance ModeSetting the ICM process into the maintenance mode.

1. Using the ICM monitor (transaction SMICM), active the maintenance mode.

a) In the ICM monitor (transaction SMICM) choose Administration ICM Maintenance Mode Activate.

b) Note that the ICM Status is Maintenance now.

2. Launch the following URL: http://twdf-SSSS.wdf.sap.corp:80$$/sap/public/ping (and make surethat $$ matches the instance on which you activated the maintenance mode).

a) 200 Maintenance Mode

b) See task description. The message 200 Maintenance Mode appears.

3. Using the ICM monitor (transaction SMICM), deactive the maintenancemode.

a) In the ICM monitor (transaction SMICM) choose Administration ICM Maintenance Mode Deactivate.

b) Note that the ICM Status is Running again.

Result

You can enter and leave the maintenance mode.




Lesson Summary

You should now be able to:



Related Information

SAP NetWeaver 7.31 online documentation, path SAP NetWeaver Library:Function-Oriented View Application Server Application ServerInfrastructure Internet Communication Manager (ICM)

SAP Note 737625: Parameter Recommendations for the ICM

SAP Note 421359: ICM: Binding


Lesson: Internet Communication Framework

Lesson OverviewThe Internet Communication Framework (ICF) provides an environment forhandling Web requests in the ABAP work process of an SAP system. This lessonintroduces the ICF and provides more information about some administrativeissues. The last section is dedicated to the integrated ITS which is available as ofas of AS ABAP 6.40.


Explain the importance of the Internet Communication Framework (ICF)for handling HTTP requests

Outline the interaction model

Describe what constitutes an ICF service

Activate and use the integrated ITS

Business ExampleYour company wants to use Web applications based on Web Dynpro ABAP, BSPs,or the integrated ITS to connect your SAP systems with the internet or intranet. Asa member of the system administration team, it is your task to create links betweencalled URLs and services and programs of the SAP system.

Classifying the ICFThe Internet Communication Framework (ICF) provides a way for differentsystems to communicate with each other over the internet/intranet using standardprotocols (such as HTTP and SMTP). No additional programming libraries (forAS ABAP) are required from SAP. However, for the HTTPS protocol, the SAPCryptographic Library (SAPCRYPTOLIB) must be installed and configured(see SAP Note 510007). Your system platform only must be configured to beinternet capable. This scenario allows for the most flexible setup of the overallcommunication requirements.

The ICF allows a response to a request to be generated using an application. AnHTTP request is sent from a client (such as a Web browser) to the server. It is thenforwarded to an application by the ICF. Here, data is collected and sent back to theclient as a response by the ICF. The response data is then displayed in the browser.

The following provides more information about using the SAP system as a Webserver (HTTP(S) server). For information about the Web client role of the SAPsystem, see the online documentation.



TADM10_2 Lesson: Internet Communication Framework

The application logic that is to be called by an HTTP request from the intranet orinternet is implemented by the HTTP request handler in each case. An HTTPrequest handler is a program (or, more precisely, an ABAP class) that is identifiedusing a URL, and which receives HTTP requests that use this URL. The taskof the HTTP request handler is to receive the data that is sent by a request (forexample, coded into the URL as query string information), to perform a numberof handler-specific processes, and to generate a response to this HTTP request.

Customers can also create these HTTP request handlers themselves, although SAPdoes provide some. Commonly used SAP HTTP request handler are the ones forBusiness Server Pages (BSP) and Web Dynpro ABAP.

If an HTTP request is received by the ICM that is to be processed in a dialog workprocess, the task handler takes control. It then starts the ICF controller. From nowon, we are in the ABAP world and in the ICF.

Figure 14: Interaction Model of an SAP System in the Server Role

An HTTP(S) request is processed in the following steps:

1. The request is sent from the user's Web browser to the ICM using theHTTP(S) protocol. The ICM uses the requested URL to determine whetherthe application called is implemented in the ABAP or Java stack of the SAPNetWeaver Application Server (in case of a dual-stack installation).

This example uses an ABAP application that must be processed by a dialogwork process.



2. The ICM stores the data received in a memory pipe (in the shared memory)and informs the ABAP dispatcher.

3. The ABAP dispatcher adds the ICM request to the dispatcher queue, createsa new context (if there is no context that is processed statefully), and selectsa dialog work process for processing.

4. The task handler in the work process reads the data from the memory pipeand transfers it to the ICF controller, which is implemented using functionmodule HTTP_DISPATCH_REQUEST.

5. The ICF controller transfers the request to the ICF manager, which isimplemented by the ABAP class CL_HTTP_SERVER. The ICF controllercreates a server control block and fills it with the HTTP request data thatit requested from the ICM.

6. The client is then authenticated, whereby several logon options are available.

7. The HTTP request handler determined previously is called (this can processthe request data, call further applications, access the response object, and soon). When the HTTP request handler is ready, it returns control to the ICFcontroller.

8. The task handler writes the response back to the memory pipe (responseserialization) and signals to the ICM that it has finished processing therequest.

9. The ICM returns the response to the Web browser.

Properties and Maintenance of ICF ServicesFrom a technical point of view, there is an ABAP class behind an HTTP requesthandler. This class implements the interface IF_HTTP_EXTENSION and themethod HANDLE_REQUEST (). SAP delivers classes of this type; customers can,of course, also create their own classes with the Class Builder (transaction SE24,integrated into the Object Builder, and transaction SE80).

Linking a particular URL with an HTTP request handler is the task of ICFservices. An ICF service therefore creates a connection between a URL to whichan HTTP request is sent and development objects that process this request.

An SAP system (with AS ABAP) already contains various services directlyafter it is installed. The exact scope depends of course on the system type (SAPECC, SAP CRM, and so on) and the release. You can obtain an overview of allavailable services using the central maintenance transaction for ICF services,transaction SICF. All available services are displayed in a hierarchical structurein transaction SICF. The complete path for a service (such as /sap/bc/icf/info)ultimately determines (together with the protocol, server name, and port) the URLunder which the service can be called. The following section explains some of theaspects that are relevant for administrators in more detail.




Activation concept

ICF services can be active or inactive, which is indicated by different colors intransaction SICF:

Status of ICF Services

Status Color in SICF Meaning

Active Black Service can be called

Gray Service is explicitly deactivatedInactive

Blue Service is implicitly deactivated

For implicitly deactivated services, there is always a higher-level service in theICF tree that has been explicitly deactivated. If you activate this service (displayedin gray), all lower-level services that were implicitly deactivated (displayed inblue) are activated. When you activate a node (by choosing Service/Host Activate or using the context menu that appears when you click the right mousebutton), you can choose whether you want to explicitly active the selected serviceonly (Yes) or all of the lower-level subservices (Yes with the tree icon).

If you try to call an inactive service, the system displays a message stating thataccess to this page is blocked. Activated ICF services are a security risk since theycan be accessed directly using HTTP(S) or SMTP from the intranet or internet(depending on your network configuration). You should therefore restrict accessusing suitable measures, such as by activating only the required ICF services andassigning the relevant authorizations to users.

Hint: At the time of delivery, all ICF services are inactive so that noICF service can initially be used.

If SAP provides changes to ICF services as part of Support Packages,these services are also inactive when you import the Support Package(regardless of the activation status before import).

Properties and Inheritance

An ICF service is characterized by properties that you maintain in transactionSICF. By double-clicking a service, you access the Create/Change a Servicescreen on which you can configure the following settings:



Service Data

An inheritance principle applies to the properties of an ICF service:In transaction SICF, you do not have to maintain properties for eachindividual service. You can do this simply for the higher service nodes(for example, /sap/bc/bsp). All lower-level services are then assignedthese properties, provided that other values have not been enteredexplicitly for them.

This inheritance process is not always required. You can use the Do NotInclude Inherited Settings indicator to control whether this inheritancelogic is interrupted. As of AS ABAP 7.00, you can choose the DisplayInheritance button to show the properties for the current service thatare inherited from higher-level ICF services.

Under Load Balancing, you can enter a logon group (from transactionSMLG) using the input help (F4). When you use the SAP WebDispatcher, requests sent to this service are forwarded only to theABAP instances of the logon group defined.

If you enter a value in the SAP Authoriz. field, the system checkswhether the user has this authorization (for authorization object S_ICF,field ICF_VALUE) at runtime.

Once the time defined in Session Timeout has expired, a statefulapplication is terminated (if the value is 0, the profile parameterrdisp/plugin_auto_logout has a default value of 30 minutes).

If you set Compression to Yes, the SAP system compresses theresponse (using the gzip technique), provided that the caller can controldecompression.

If you set GUI Link to yes, the screen images that are generated inthe application by processing conventional dynpros are converted to aformat that allows them to be displayed graphically in a browser.

This function (as well as the screen that can be accessed with GUIConfiguration) is required for the integrated ITS as of AS ABAP 6.40,and is detailed below.

The Support Accessibility indicator specifies that an accessibility modeis called if the application has one. However, it cannot be guaranteedthat this is the case.




Logon Data

There are various ways to log onto the AS ABAP via an HTTP request,and you can configure these for each individual service node. With theStandard default setting, the following check procedures are used in exactlythis sequence:

1. Logon Through HTTP Fields

2. Logon Through SSL Certificate (logon using client certificate)

3. SAP Logon/Assertion Ticket

4. SAP Assertion Ticket

5. Basic Authentication (logon using SAP user and password)

6. SAP RFC Logon

7. SAML Logon

8. Logon Through Service Data logon using the anonymous data enteredin the service)

By choosing Alternative Logon Procedure, you can select any logonprocedure (in the Logon Procedure List that appears) and change the checksequence.

With Required with Logon Data, only those entries specified in the serviceunder Logon Data (client, user, password, and language) are used for thecheck. You should enter only those users that were created in transactionSU01 as service users. If you enter a dialog user, the system issues a warningmessage.

If you select Required with SSL Certificate, logon occurs exclusively withan X.509 client certificate.

For the Standard and Alternative Logon Procedure, you can select Use AllLogon Procedures to specify whether the respective check sequence is to rununtil one of the logon procedures is successful, or whether the caller is toreceive a negative confirmation as soon as the first logon procedure fails.

Depending on the procedure selected, you can configure additional settings(for example, you can require SSL, that is, the HTTPS protocol).

Handler List

Here, you list the HTTP handlers in the sequence in which they are to beexecuted. An HTTP request handler is an ABAP class that implementsthe interface IF_HTTP_EXTENSION. This interface contains the methodHANDLE-REQUEST, which is called by the ICF.



Error Pages

On the Error Pages tab, you can specify which response pages are to be sentto the caller in the following situations:

Logon Errors (HTTP 401: logon failed)

Appl. Errors (HTTP 500: An error occurred in the application, forexample, ABAP short dump)

Logoff Page

Not Accessible (HTTP 404)

In each case, either an explicit response page can be sent to the browser orthe caller can be redirected to another URL. In the Logon Errors area, youcan also enable a direct system logon if an error occurs.

Note: Under the /sap/public node, services are defined that arerequired for system-internal services. These differ from the otherservices in the tree since no user is maintained. You therefore do nothave to log onto the SAP system. The actions are carried out underthe SAPSYS system user. Therefore, customers are not permitted tocreate their own services under the /sap/public node.

Administration

The Administration tab contains administration data such as the user whocreated and last changed a service.

Hint: If logon data is defined for an ICF service that is then transported,the logon data is deleted during transport. This is due to security reasons.Furthermore, it is not possible to guarantee that the respective user existsin the target system. The user must therefore be maintained in the targetsystems. For more information, see SAP Note 732218 ICF: Logon datafrom SICF is not transported. Also for security reasons, ICF services thathave been transported to a target system are initially inactive and must beactivate explicitly (see SAP Note 517484: Inactive services in the InternetCommunication Framework).

Aliases

In the ICF, you can link from one ICF service to another "alias". A distinction ismade between internal and external aliases:

On the Create a Service Element screen in transaction SICF, if you create aservice and choose Reference to Existing Service, you create an internal alias.Instead of defining an HTTP request handler, use the Alias Trgt tab to specify (bydouble-clicking) the page to which the alias is to refer in the HTTP service tree.This allows you, for example, to call the existing and unchanged service with




alternative settings (such as logon data and procedure). If possible, customersshould not create internal aliases to SAP services (which are always in the /sap/namespace).

To allow services to be called with any meaningful, non-technical names,customers should use external aliases. Therefore, switch to the External Aliasesview in transaction SICF. Unlike an internal alias, an external alias can containa forward slash (/) in its name; otherwise, both procedures are handled in thesame way.

Monitoring

The ICF recorder enables developers and administrators to identify and correctsources of error in failed service calls by recording HTTP requests.

You can use it to save recorded requests (without the passwords used) in thesystem database. This facilitates the evaluation process since it is usually no longernecessary to describe the error so that the problem can be reproduced. The problemcan be executed multiple times using the database entry in order to further identifythe cause of the problem by debugging or work process traces. Once the problemhas been corrected, the erroneous data can be used to check the corrections.

You can call the ICF recorder from transaction SICF by choosing Edit Recorder Activate/Deactivate/Display Recording; you can also use transactionSICFRECORDER for the evaluation process. The basic steps are:

1. Activate the recording. You have to enter:

The URL path to be recorded (if you have previously selected a path,this is used as the default value)

The duration of the recording (Record Time) and storage in the database(Lifetime)

Whether the requests of one user (recommended) or all users of thecurrent client are to be recorded

2. Call the services to be monitored (if necessary, using the selected user).

3. Deactivate the recording (to prevent performance losses).

4. Display and process the recorded requests.

In the administrator settings (available in transaction SICF under Goto Settings), you can prevent the ICF recorder from being used system-wide. Youuse authorization object S_SICFREC to control access to the request data usingthe ICF recorder.

AS ABAP with Integrated ITSSAP ITS as a standalone software component (comprising the Web server, WGate,and AGate) is also considered a standalone version and is supplied by SAP upto and including ITS Release 6.20. With Release 6.40 of the AS ABAP, the SAP



ITS was integrated in the ABAP kernel (under the name SAP Integrated ITS).This means that as of AS ABAP 6.40, it is not necessary to install separate ITScomponents or servers.

Hint:

For AS ABAP 6.20 and earlier, only the SAP ITS standalone 6.20can be used (and is supported).

For AS ABAP 6.40, both the integrated ITS and an SAP ITS 6.20standalone is released.

As of AS ABAP 7.00, only the integrated ITS can be used (and issupported).

Architecture

The integrated ITS is completely integrated in the familiar infrastructure of theAS ABAP: It is accessed via the ICM process, implemented as an ICF service,and uses the database as an object storage location.

Figure 15: Comparison: Architecture of SAP ITS (Standalone) and SAPIntegrated ITS




This setup has the following advantages:

A separate Web server and ITS server is no longer required. By reducingthe administration and maintenance expenses, the total cost of ownership(TCO) is also reduced.

The ITS is available on all platforms released for the AS ABAP, whichsignificantly enhances the platform matrix (see SAP Service Marketplace,Quick Link /pam).

With the standalone ITS, some customers deliberately separate the WGateand AGate to create a firewall. This security attribute is also available inthe integrated ITS by placing the firewall between the SAP Web Dispatcherand the ICM process.

Administrators do not require special administration tools for configurationand monitoring purposes.

Developers do not have to publish applications on external servers; IACsare accessed via a pseudo-publish operation from the system database tothe INTERNAL site.

Note: SAP Web Dispatcher is not part of this lesson.

It is technically possible to operate a standalone SAP ITS 6.20 in conjunctionwith an AS ABAP 6.40 (but not later releases). This may result from one of thefollowing restrictions in comparison to the standalone version:

The integrated ITS does not support the programming models Flow Logic,WebRFC, or WebReporting. Applications that use these still require SAPITS 6.20.

The integrated ITS always runs on the SAP system of which it is part. Thismeans that a standalone ITS is required for SAP systems based on AS ABAP6.20 or lower.

Only by upgrading to AS ABAP 6.40 you can not ensure that a productivestandalone ITS is transferred to an integrated ITS. Depending on the initialscenario, further steps may be required (transfer of programming objectsand settings).



Configuration

The integrated ITS is automatically installed with the SAP kernel as part of ASABAP 6.40 and higher. To use the integrated ITS, the following prerequisitesmust be met:

The ICM process is operational and configured for HTTP(S).

Profile parameter itsp/enable is set to 1.

The required ITS service is published to the INTERNAL site.

The required ITS service is active in the ICF and the property GUI Linkis set to Yes.

The ICF service /sap/public/bc/its/mimes is active in the ICF and the propertyGUI Link is set to Not specified.

For the integrated ITS, various profile parameters are relevant, which all beginwith itsp/. Administrations can use the usual methods to call documentationfor individual parameters (transaction RZ11) and change the assigned valuespermanently (transaction RZ10).

Two profile parameters are particularly significant in relation to the integrated ITS:

itsp/enable: You use this to deactivate (0) and activate (1) the integrated ITS.Even if the integrated ITS is active, it uses the system resources only whenit is actually used. However, it can be useful to deactivate it for selectedinstances so that no users can access the SAP system via the SAP GUI forHTML with these instances (for example, batch or update instances). Sincethe conversion of SAP screen images to HTML pages also requires CPUtime, it is useful to reserve a number of dedicated application servers foruse with SAP GUI for HTML and to use a special logon group for loadbalancing between them.

em/global_area_MB: This parameter determines the memory commonlyused by all ABAP work processes of the SAP kernel. The integrated ITSuses it for session information and the runtime version of the HTML businesstemplates. The required memory space depends on the number of sessionscurrently in use, as well as the number and size of the templates used whenusers want to call and display services. If your users log onto the ITS indifferent languages or with different browsers (for example, MicrosoftInternet Explorer and Mozilla Firefox), or if you require additional servicesnot included in SAP GUI for HTML, the number of templates used increasesand you will have to modify em/global_area_MB (see SAP Note 742048).

Alongside these profile parameters, which are evaluated by the kernel and affectthe entire integrated ITS, there are also service parameters, which affect theindividual ITS services. You maintain these settings in transaction SICF.

The basic behavior (such as logon, anonymous logon data, service options,security requirements, basic authorizations, and customized error pages) resultsfrom the properties of the ITS services in the ICF, as is also the case with




normal ICF services. You maintain other, ITS-specific service parameters(that begin with ~) in transaction SICF on the Create/Change a Service screen.Choose the Service Data tab and in the Interactive Options area, chooseGUI Configuration. For more information about these parameters, see theSAP NetWeaver 7.31 online documentation, path SAP NetWeaver Library:Function-Oriented View Application Server Application Server ABAP UI Technologies in ABAP Further UI Technologies Web UI Technology SAP ITS in SAP NetWeaver Application Server Configuration Parametersfor Administrators/Developers.

Note: The global.srvc, webgui.srvc, and .srvc files andtheir service parameters used with the standalone ITS do not exist in theintegrated ITS.

Developers create new ITS services with the Web Application Builder for ITSServices, a tool in the ABAP Development Workbench SE80. Services arepublished to the (implicitly available) INTERNAL site. The ITS service must alsobe created in the ICF, and can be accessed with the URL http(s)://://(or by choosing Test Service in transaction SICF).

SAP GUI for HTML with the Integrated ITS

In numerous installations, customers activate the integrated ITS as of AS ABAP6.40 so that they can comfortably use the SAP GUI for HTML. In addition, severalIACs use objects of the SAP GUI for HTML, which therefore have to be activated.

In addition to the general settings listed above, the following prerequisites alsoapply to the SAP GUI for HTML:

The internet services system and webgui are published to the INTERNAL site.

The ICF service /sap/bc/gui/sap/its/webgui is active in the ICF and theproperty GUI Link is set to Yes.

Hint: For detailed information about the storage structure in the integratedITS, see SAP Note 678904: ITS - New storage structures as of SAP WebAS 6.40.

You start the SAP GUI for HTML by entering the URL http(s)://:/sap/bc/gui/sap/its/webgui. Theabove comments about the properties of an ICF service (such as client, logonlanguage, and so on) also apply here.



Monitoring

The administrator can use the tools integrated in the AS ABAP (such astransactions SM21, ST22, SMICM, and SICF) to monitor the integrated ITS. Theintegrated ITS does not have special trace files, but instead uses the standarddeveloper trace files of the work processes dev_w*.trc. Developers can speciallyactivate ITS tracing (in transaction SM50 or with report RSTRC000, componentWebGui).

They can also use transaction SITSPMON and program SITSPMON, whichprovide a detailed status summary of the integrated ITS.

Figure 16: Monitor Functions for the Integrated ITS

The following list contains a number of selected monitor functions for theintegrated ITS:

Status: message text, FeatureSet version, and parameters

Memory consumption: Overview and details about memory consumed bysessions and ABAP work processes

Caches: Status and invalidation of caches for HTML templates and MIMEobjects

Mutex locks (from mutual exclusion: technology for preventingsimultaneous access to a resource by several processes)




New features of the integrated ITS have been added with AS ABAP 7.00. Theseinclude an improved use of memory, improved diagnosis functions, and anenhancement to the SAP GUI for HTML for Mozilla and Firefox. For moreinformation, see SAP Note 890606: SAP NetWeaver 2004s integrated ITS: NewFeatures.

Active Services for Web Dynpro ABAP

SAP Note 1088717 lists the services in transaction SICF which need to be activatedfor Web Dynpro ABAP applications, for the Web Dynpro ABAP developmentenvironment as well as for Web Dynpro ABAP applications for troubleshooting.



Exercise 2: Administrative Work with theICF

Exercise ObjectivesAfter completing this exercise, you will be able to:

Activate and call ICF services

Create external aliases

Use the IFC recorder

Activate and call the integrated ITS

Business ExampleYour company uses an SAP ECC 6.0 system as part of its SAP ERP solution. Yourdevelopment department has added a number of BSP-based applications to thestandard SAP system. You are to ensure that these applications can be called.



Task 1: Activating ICF Services


Activating and Calling ICF Services

1. In your ECC system, activate the ICF service /sap/bcincluding all subservices(if they are not yet active).

2. Call the following URL in a Web Browser (such as training room,VDI environment, Common Training WTS): http://twdf-SSSS.wdf.sap.corp:80$$/sap/bc/bsp/sap/it00(example for group QCC and server twdf0042:http://twdf0042.wdf.sap.corp:8010/sap/bc/bsp/sap/it00).

3. Within BSP application it00, start the function 7. MIMEs 2. AccessingSAP Icons in MIME Repository. Note the Internet Server Cache (of the ICMthat processed your request).

4. Optional: From transaction SICF, start the Web Dynpro ABAPapplication/sap/bc/webdynpro/sap/OTHELLO.

Result

All services under /sap/bc can now be called from the intranet and, if thenetwork settings allow, from the internet.





Task 2: Creating an External AliasCreate a new ICF service as an external alias to an existing service.

1. Use the wizard to create new ICF service /ADM/myInfo that links to/sap/bc/icman/test01 as an external alias.

2. Close all of your browser windows. What do you notice when you test thenew service /ADM/myInfo in transaction SICF?

3. For the /ADM/myInfo service, enter the logon data of the course user-## assigned to you by the instructor.

4. Check that you can now call the /ADM/myInfo service without having tolog on.

Result

Your SAP system provides a new /ADM/myInfo service with saved logondata.

Task 3: Optional: Creating an Internal Reference(Internal Alias)Creating a new service as an internal reference to an existing service.

1. Without using the wizard, create an independent (not: external) ICF service/ADM.

2. Without using the wizard, create an ICF service /ADM/myPing that links to/sap/public/ping as an internal reference.

Remember to activate your new service.

3. Test the new /ADM/myPing service in transaction SICF.

4. Optional: Determine all ICF services that link to the /sap/public/pingservice.

Result

Your SAP system provides a new service, /ADM/myPing.

Task 4: ICF RecorderAnalysis of HTTP requests with the ICF recorder

1. Activate the ICF recorder for service /sap/bc/bsp/sap/it00. The recordingshould contain requests, responses, and failed logons, be relevant to all users,and be stored for one day.

2. Close all open Web browser windows.




Start the /sap/bc/bsp/sap/it00 service (either by using the test function intransaction SICF or by entering the URL in the Web browser) and log onwith...

... an invalid user name.

... a valid user name but an incorrect password.

... a valid user name and password.

Once you have logged on successfully, call some of the functions.

3. Deactivate the ICF recorder

4. Display the recorded requests and responses.

Task 5: SAP GUI for HTML Using Integrated ITSSet up and call the SAP GUI for HTML for the integrated ITS in AS ABAP.

1. Check whether the integrated ITS is active.

2. Verify that the ICF service /sap/bc/gui/sap/its/webgui is active and intendedfor calling the GUI.

3. Verify that the ICF service /sap/public/bc/its/mimes is active and that NotSpecified is entered for the GUI link.

4. Start the SAP GUI for HTML from transaction SICF.

Can you start a transaction from the command field?

5. Optional: Change the service parameter ~noHeaderOkCode for the SAPGUI for HTML to 1 and note its effects.

Result

Users can log onto the SAP system with a Web browser and call transactionswith the SAP GUI for HTML.




Solution 2: Administrative Work with theICF

Task 1: Activating ICF Services


Activating and Calling ICF Services

1. In your ECC system, activate the ICF service /sap/bcincluding all subservices(if they are not yet active).

a) You are logged on to your ECC system with a SAP GUI.

b) Call the Maintain Services transaction SICF. Accept the default valuesand choose Execute.

c) Navigate to the /sap/bc node.

d) If this service has not yet been activated, right-click this node andchoose Activate Service (or choose menu path Service/Host Activate). Choose Yes (with the tree icon) to activate node /sap/bc andall of its subservices.




2. Call the following URL in a Web Browser (such as training room,VDI environment, Common Training WTS): http://twdf-SSSS.wdf.sap.corp:80$$/sap/bc/bsp/sap/it00(example for group QCC and server twdf0042:http://twdf0042.wdf.sap.corp:8010/sap/bc/bsp/sap/it00).

a) Enter the specified URL in your Web browser again and choose Enter.

b) Log on with the course user -##.

Note: BSP application it00 is a test application for BSPdevelopers.

3. Within BSP application it00, start the function 7. MIMEs 2. AccessingSAP Icons in MIME Repository. Note the Internet Server Cache (of the ICMthat processed your request).

a) Within BSP application it00 (in the Web browser), navigate to the menuoption 7. MIMEs 2. Accessing SAP Icons in MIME Repository.

The system displays the SAP icons stored in the MIME repository(implemented in the AS ABAP database) as graphics in GIF format.

b) Start transaction SMICM on the application server whose ICMprocessed the previous request.

c) Choose Goto HTTP Plug-In Application Server Server Cache Display.

The system displays (with a preview option) the objects stored in theInternet Server Cache (ISC). If you now delete the temporary cachein your Web browser (in Internet Explorer choose Tools Internetoptions General Delete (select) Temporary Internet Files Delete) and in the BSP application it00 you call the functionMIMEs Accessing SAP Icons in MIME Repository again, you can clearly see thedifference between reading from the database and reading from the ISC.





4. Optional: From transaction SICF, start the Web Dynpro ABAPapplication/sap/bc/webdynpro/sap/OTHELLO.

a) Start the Maintain Services transaction SICF. Accept the default valuesand choose Execute.

b) Navigate to the /sap/bc/webdynpro/sap/OTHELLO node.

Alternatively, in the Filter area, as Service Name enter OTHELLO andApply this filter.

c) Right-click the node and choose Test Service. When prompted, log onwith your course user -##. Enjoy...

Result

All services under /sap/bc can now be called from the intranet and, ifthe network settings allow, from the internet.

Task 2: Creating an External AliasCreate a new ICF service as an external alias to an existing service.

1. Use the wizard to create new ICF service /ADM/myInfo that links to/sap/bc/icman/test01 as an external alias.

a) Call the Maintain Services transaction SICF. Accept the default valuesand choose Execute.

b) Choose External Aliases to switch to the Maintain axternal aliasesscreen.

c) Select default_host.

d) Choose Wizard External Alias (magic wand icon), or alternativelymenu path External Alias Wizard External Alias.

e) The wizard leads you through the following steps, whereby you accessthe following page by choosing Continue:

First, information about external aliases appears.

In the External Alias field, enter /ADM/myInfo and in theDescription 1 field, enter a description of your choice.

As the target handler, double-click the service /sap/bc/icman/test01(you may need to expand the tree structure for this).

Choose Complete.




2. Close all of your browser windows. What do you notice when you test thenew service /ADM/myInfo in transaction SICF?

a) In the hierarchy display in transaction SICF (Maintain External Aliasview), right-click your new node /ADM/myInfo and choose Test Ext.Alias.

b) Note: You must first log on (with your course user -##)before you can view the test page (including information on theinstance name).

Note: If you are not prompted to enter your user details, closeall of your browser windows.

3. For the /ADM/myInfo service, enter the logon data of the course user-## assigned to you by the instructor.

a) In the hierarchy display in transaction SICF (Maintain external aliasview), double-click your /ADM/myInfo node and switch to changemode.

b) On the Logon Data tab page, select Required with Logon Data from theProcedure dropdown box.

In the Logon Data area, enter the logon data for your course user-##. Confirm the warning If possible, do not usedialog users and save your entries.

Note: In an operational scenario, enter users of type Servicewith appropriate authorizations.

4. Check that you can now call the /ADM/myInfo service without having tolog on.

a) Close all of your browser windows.

b) In transaction SICF, right-click your external alias /ADM/myInfo andchoose Test Ext. Alias again. The system should not prompt you toenter your user details.

Result

Your SAP system provides a new /ADM/myInfo service with savedlogon data.





Task 3: Optional: Creating an Internal Reference(Internal Alias)Creating a new service as an internal reference to an existing service.

1. Without using the wizard, create an independent (not: external) ICF service/ADM.

a) Call the Maintain Services transaction SICF. Accept the default valuesand choose Execute.

b) In the hierarchy display, right-click the top node default_host. ChooseNew Sub-Element (alternatively, menu path Service/Host CreateService). Confirm the message about the namespace concept.

c) In the Create a Service Element window, enter ADM as the name andchoose Independent Service as the Type.

d) On the subsequent Create/Change a Service screen, enter a description.Leave all other fields unchanged and save your changes (for therepository request choose Local Object). Confirm the warning that thenew service cannot be accessed.

e) Go back one screen (to the hierarchy display in transaction SICF).

2. Without using the wizard, create an ICF service /ADM/myPing that links to/sap/public/ping as an internal reference.

Remember to activate your new service.

a) You are still in the Maintain Services transaction SICF.

b) In the service tree, right-click your new ADM node, and choose NewSub-Element.

c) Now create the element myPing as a Reference to Existing Service.

d) On the Create/Change a Service Call screen, enter a description text.

e) On the Alias Trgt tab page, navigate to the default_host/sap/public/pingnode and double-click this line. Save your data and go back one screen(to the hierarchy display in transaction SICF).

f) To activate your changes, select the /ADM/myPing node in the servicetree and choose Activate Link with the right mouse button. Confirmthe query by choosing Yes.




3. Test the new /ADM/myPing service in transaction SICF.

a) In the hierarchy display in transaction SICF, right-click your new/ADM/myPing node and choose Test Link. The message Serverreached successfully appears.

Hint: It may take a while for the SAP system to recognize thenew alias. If the AS ABAP does not recognize the URL as acorrect URL, try again later.

4. Optional: Determine all ICF services that link to the /sap/public/pingservice.

a) In transaction SICF, navigate to the node /sap/public/ping. With theright mouse button, choose References to Service (alternatively menupath Service/Host Alias References).

The system displays a list that contains all internal and externalreferences that link to /sap/public/ping. Your entry, /ADM/myPing,also appears here.

Result

Your SAP system provides a new service, /ADM/myPing.

Task 4: ICF RecorderAnalysis of HTTP requests with the ICF recorder

1. Activate the ICF recorder for service /sap/bc/bsp/sap/it00. The recordingshould contain requests, responses, and failed logons, be relevant to all users,and be stored for one day.

a) In the hierarchy display in transaction SICF, select the/sap/bc/bsp/sap/it00 service with the left mouse button and choosemenu path Edit Recorder Activate Recording.

b) In the Activate Recording dialog box, deselect the User-Dependentfield. In the Lifetime field, enter 1 day and 00:00:00hours:minut

Documents

Tadm10 2 en Col99 Fv Part a4