1. Check if you have activated and your webgui is working for not.
First you have to know your http server port.
Call transaction SMICM
Click on services.
Check HTTP service, port number and host name.
Open internet explorer and call SAP Web GUI.
http://
Come across error message means its not yet configured.
2. Check if not acivated then need to activate:
With transaction SICF and locate the services by path
/sap/public/bc/its/mimes
/sap/bc/gui/sap/its/webgui
/sap/public/bc/ur
3. With Transaction SE80 locate from the menu, Utilities –> Settings–>Internet Transaction Server (Tab)–>Publish (Tab) and set “On Selected Site” = INTERAL.
This restricts the publication in the next step to the integrated (internal) ITS.
4. In SE80 only, Locate the Internet Services: SYSTEM and WEBGUI.
Publish these services with the Context Menu -> Publish -> Complete Service
5. Open internet explorer http://
Please enter username and password.
This will start SAP GUI for HTML.
SAPGUI get opened.
Effects on System Administration
You can administer SAP Integrated ITS using the following SAP Transactions:
1. RZ10 – definition of parameters
2. SICF – configuration of the ITS service
3. ST11 – traces
4. SITSPMON – status of integrated ITS
My integrated ITS doesn't work. What should I do?
See note 698329 in order to find out what is wrong with your integrated ITS. If you get memory errors when you start an ITS application, see also SAP note 742048
for more information.
How to prefill fields and skip first screen with webgui?
Often it is desired to prefill fields of a screen and skip this screen by triggering an okcode. The SAP kernel provides a special okcode functionality which can be used with webgui and SAP GUI. You have to create a okcode with the following syntax:
*
If you i.e. use this with the ABAP editor SE38 and enter
*se38 RS38M-PROGRAMM=rsparam;DYNP_OKCODE=SHOP
in the transaction code field of webgui or SAP GUI, the ABAP editor will be started with directly showing the ABAP code of RSPARAM. You can also make use of this in the URL with the well known ~transaction parameter.
For ITS 6.20 standalone with i.e. R/3 Enterprise 4.7 the URL would be
http://ITS_HOST:ITS_PORT/scripts/wgate/webgui/!?~transaction=*se38 RS38M-PROGRAMM=rsparam;DYNP_OKCODE=SHOP
If you use SAP Netweaver 2004 or higher with integrated ITS the URL would be
http://WAS_HOST:WAS_PORT/sap/bc/gui/sap/its/webgui?~transaction=*se38 RS38M-PROGRAMM=rsparam;DYNP_OKCODE=SHOP
After authenticating the user, the SAP system will automatically process the transaction and skip the first screen.
Parameter ~okcode is obsolete for skipping screens
Many of you may know, that the parameter ~okcode provides a similar functionality with ITS 6.20. However it is not recommended anymore to use it for skipping screens. One reason is, that the solution discussed above provides much more performance because it avoids superfluous roundtrips between the SAP kernel an ITS 6.20. The other is that with SAP Netweaver 2004 and above the ~okcode syntax no longer works in any case. Therefore just forget screen skipping with ~okcode and make use of the method described above.
How to terminate a user session with integrated ITS when the transaction ends?
This tutorial describes how to delete the user session with the parameter ~singletransaction when the transaction started with ~transaction ends.
When calling a transaction with ITS 6.20 using the parameter ~transaction, ITS takes care to delete the session when the transaction ends. With SAP Netweaver and integrated ITS this don't work because session handling is not longer done by ITS but by the SAP kernel itself. When a transaction ends the system shows the transaction selection screen with the "Start Easy Access Menu" button.
In a portal environment this is often not desired. SAP therefore enhanced the kernel to provide a similar functionality as with ITS 6.20. To activate this functionality you have to set the parameter ~singletransaction=1 in the ICF service. This parameter tells ITS to ask the SAP kernel to logoff a user session at the end of transaction. SAP note 959417 describes the kernel and support package requirements. For those who do not currently have access to the SAP service marketplace:
SAP Netweaver 2004, aka 640:
Kernelpatch: 136
ABAP Support-Package: SAPKB64018
SAP Netweaver 2004s, aka 700:
Kernelpatch: 66
ABAP Support-Package: SAPKB70009
The parameter has the limitation that it doesn't work if the transaction is terminated with LEAVE TO TRANSACTION. You should therefore not use this parameter with the standard webgui service but create an own z-service in SICF with ~transaction set to the tcode you want to provide your users.
How to customize the login screen?
Many customers would like to customize the ITS login page, so that it fits to their corporate standards. If you search information about how to customize the login page either in ITS 6.20 or with SAP Netweaver 2004/2004s/2007 with integrated ITS read this tutorial.
ITS 6.20 standalone
If you want to customize ITS system templates (and login page is one of these), ITS provides an easy way to do this. The system folder below SAP/ITS/6.20/
SAP Netweaver
With SAP Netweaver 2004 ITS is part of the SAP kernel. The login page is therefore no longer a functionality of ITS but of the Web Application Server (WAS). By default ITS Services uses the standard system login pages that WAS provides. You can customize in transaction SICF what login procedure should be used and which fields should be available on system login page. This can be done global or per service. The documentation on the SAP help portal contains information how this can be done. It is even possible to create an own login page by inheriting an own login class from CL_ICF_SYSTEM_LOGIN. You can find detailed information about how to do this on the SAP help portal System Logon. For mobile devices Netweaver provides the CL_MOBILE_SYSTEM_LOGIN class.
