Symptom

Problems with the SAP Integrated ITS (in SAP Web Application Server 7.00)
Other Terms
preclarification, basic analysis, WebGUI, SAP GUI for HTML, HTMLGUI, HTML GUI, I
TS, internal ITS, Internet Transaction Server, 7.00, SAP NetWeaver 2004s
Reason and Prerequisites
Solution
1. Determine the Web Application Server's Kernel Patch Level and SAP_BASIS Suppo
rt Package Level:
System > Status, buttons "Other kernel info. (Shift+F5)" and "Comp
onent information" respectively
Kernel Patch Level can also be checked using report RSMONREL_ALV (
through transaction SE38); this will display a list of all Application Servers a
nd their respective Kernel Patch Level.
Make sure they are reasonably current. The Support Package Schedul
e can be found at http://service.sap.com/ocs-schedule. To check for the latest a
vailable Kernel Patch, go to http://service.sap.com/support and navigate to Down
loads > SAP Support Packages > Browse our Download Catalog > SAP NetWeaver > SAP
NETWEAVER > SAP NetWeaver 2004s > Entry by Component > Application Server ABAP
and then further according to operating system and database.
A list of corrections for the SAP Integrated ITS in both Support P
ackage and Kernel Patches can be found in note 890601, which is updated regularl
y.
2. Check whether the SAP Integrated ITS is enabled:
Transaction RZ11, Parameter Name: itsp/enable; this has to be set
to "1".
3. Make sure the service you want to use is activated:
Transaction SICF, Hierarchy Type SERVICE, navigate to default_host
> sap > bc > gui > sap > its > [servicename]; if the name is gray, activate it
first.
If the service also makes use of (static) mime files, default_host
> sap > public > bc > its > mimes has to be activated, too.
4. Check the GUI Link:
Following the same path as in the previous point, double click on
the service name and check the settings for "GUI Link". For sap > public > bc >
its > mimes, this has to be blank. All other services (under sap > bc > gui > sa
p > its) that use SAP Integrated ITS (e.g. webgui, it00, bwsp, bbpstart) require
this parameter to be set to "Y".
5. Test the general ICF/ICM functionality:
http://<server>:<port> /sap/public/ping
http://<server>:<port> /sap/bc/echo

If these, too, do not work, check note 634006 for further assistan
ce.
6. Make sure the service has been published:
Go to transaction SE80, select "InternetService" in the Repository
Browser's drop down box and enter the name of the service. Then, double click t
he service's name in the tree below. On the right side at the top, find the serv
ice name followed by its status ("Saved/part-published", "Published", ...). Doub
le click this status text to see detailed information on the date and time the s
ervice was last published to the (possibly various) ITS sites (these might also
include standalone ITS 6.20 installations if the landscape has any). The publish
ing site for SAP Integrated ITS is INTERNAL - check if the date of last publishi
ng is newer than the date of the last change
In order to publish the service, choose "Utilities > Settings" fro
m the menu, go to tab "Internet Transaction Server", subtab "Publish" and select
"Integrated ITS". Leave the popup, right click on the service name in the tree
on the left side and select "Publish > Complete Service" from the context menu.
Do NOT use the "Publish" button in the main toolbar or the "Publis
h" entry in the "Utilities" menu. Both will only publish the single file current
ly displayed instead of the complete service!

Please note that there are two special services: SYSTEM and IAC. S
ervice SYSTEM should always be published correctly - it is required by all servi
ces that make use of SAP Integrated ITS. Service IAC needs to be published if yo
u want to use services other than WEBGUI (= SAP GUI for HTML).
7. Check the System Log:
Use transaction SM21 to check if there are any System Log messages
for the user you encountered the problem with at (or around) the corresponding
time.
If these steps do not resolve the problem, prepare both an R/3 Service Connectio
n (note 31515) to the backend system and an HTTP Connection (note 592085) to the
URL you use to call the service using the SAP Integrated ITS. (Please note that
you probably will also have to allow access to .../sap/public/bc/its/mimes.) Pr
ovide logon data for a user that will allow us to replicate the problem (if poss
ible, give a detailed step by step description how to do this) as well as a user
with the necessary authorization to check both the SAP Integrated ITS configura
tion and the system's traces and log files. See note 508140 for information on h
ow to provide logon data in a secure way.

Header Data
Released On 13.12.2010 13:19:36 By Frank Krause (D031909)
Release Status Released for Customer
Component BC-FES-ITS SAP Internet Transaction Server
Other Components

BC-FES-WGU SAP GUI for HTML

Priority Recommendations / Additional Info

Responsible Jan Pluntke ( D034977 )
Processor Frank Krause ( D031909 )
Category Help for error analysis
Relevant for Translation Yes
Validity

Software Component
From Rel.
To Rel.
And Subsequent

SAP_BASIS
700
700

References
This document refers to:
SAP Notes
808347
ITS 6.40 - preclarification and basic problem analysis
634006
Note on the preclarification of ICM messages
592085
Installing HTTP Connect service
31515
Service connections

This document is referenced by:

SAP Notes (5)
31515
Service connections
808347
ITS 6.40 - preclarification and basic problem analysis
592085
Installing HTTP Connect service
1494398
LTX - SAP GUI for HTML has rendering errors
634006
Note on the preclarification of ICM messages