Activation of SAP WebGui

To be able to benefit from SAP WebGui, you have to execute some initial configuration steps. These steps ensure that the services and the ICF nodes are correctly configured and mime files like JS, CSS, images are available and accessible by WebGui. More information about the necessary ICF configuration steps for WebGui can be found at SAP Help.

The services listed there for WebGui are:

  • /default_host/sap/public/bc/its/mimes
  • /default_host/sap/bc/gui/sap/its/

The URL to access SAP WebGui is: http(s)://<server>:<port>/sap/bc/gui/sap/its/webgui

For some reason the above linked SAP Help page is not listing all ICF nodes and steps needed to execute successfully WebGui. Especially when you have to set up a fresh installed NetWeaver system, several additional steps have to be executed to be able to use WebGui. In total, the steps involved in having a working WebGui are:

  • Base ICF nodes
  • Icons
  • Mime
  • Webgui
  • Publish services


The base ICF nodes must have been activated before.

Activate ICONS

  • Tx: SICF
  • Virtual host: DEFAULT_HOST
  • Service Patch: /sap/public/bc/icons



Activate MIMES

  • Tx: SICF
  • Virtual host: DEFAULT_HOST
  • Service Patch: /sap/public/bc/its/mime



Activate Service


Activate WebGui

  • Tx: SICF
  • Virtual host: DEFAULT_HOST
  • Service Patch: /sap/bc/gui/sap/its/webgui



Activate Service webgui

Publish services

The ICF nodes are activated, but that does not mean they are also executable in a fresh installed NetWeaver ABAP system. This is caused by that services are not automatically published to ITS after a system is newly installed. You have to do this manually. See
SAP Note 790727
for more on this. Luckily, SAP delivers a transaction that publishes all ITS services: SIAC_PUBLISH_ALL_INT


Run it, nothing else to than to wait until the report finishes. You will get an overview presented.

Too much information? No worry, the most important part is the summary of number of messages in each category.

411 times no problems reported!

Test service

Let the world know

Initial setup of ICF

To be able to use of SAP NetWeaver ABAP ICF, for instance, to be able to log on via ICF, you need to activate some nodes. Check SAP Note 517484 for more details. Without these nodes activated, you cannot access SAP WebGui. For instance, accessing it via gives an error message.

Note: /sap/public/bc should already be active. It was at least in my fresh NW 7.5 installation.

  • Tx: SICF
  • Virtual Host: DEFAULT_HOST
  • Service Path /sap/public/bc/ur


Activate service

Let the world know

Initial setup of SAP NetWeaver ABAP ICM for HTTP

SAPGui is just one way to access an SAP system. A more and more common way to interact and work with SAP is through a browser. As with all web sites, a web server must handle the browser requests. For SAP NetWeaver ABAP, the web server is ICM. ICM is integrated with NW ABAP, no need to install it as an additional package. The only task to be execute by BASIS is to configure ICM. First step is to validate that ICM is working and no errors are occurring. For a browser to be able to access NW ABAP through HTTP, ICM must be up and running and listening on a HTTP port. Without this port, no communication from a browser to NW ABAP is possible. To see the configured HTTP port of ICM, you can either look at the profile parameter or use SMICM to see the service information.

Check ICM HTTP Port configuration

  • Tx: SMICM

Goto -> Services

This shows the active services handled by ICM. As you can see, HTTP is just one of several possible services. SMTP is available, as can be telnet too! For each service you can see additional information like host name, and port. Port is given a 0. Check the ICM parameters to find out why. Also, take a look at SAP Help about this.

“Default Values AS ABAP

icm/server_port_0 = PROT=HTTP , PORT=0 , TIMEOUT=30 , PROCTIMEOUT=60

Outbound connections across HTTP and SMTP are possible with default values, but no ports for inbound connections are open.”

Configure ICM HTTP Port

Security first. That`s how SAP rolls. To allow someone accessing your SAP ABAP system via HTTP, you must explicitly activate this. Gives you also a hint if or if not SAP sees HTTP based access in ABAP as an equal citizen compared to SAPGui. To see the (default) parameter used by ICM, select:

Goto -> Parameters -> Display.

This will show you the parameters used by ICM. The ICM server parameters are given by icm/server_port_X.

Default parameter for HTTP is icm/server_port_0. Value for port is PORT=0. 0 meaning no incoming communication possible. A browser won`t be able to connect to NW ABAP. You have two options to change this: temporarily or permanent.

Change the HTTP port temporarily

  • Tx: SMICM

Goto -> Services

Select the service: Service -> Change.

In the dialog, enter the new parameters. For port, you can use 8080. Confirm the data to start the service.

This _should_ start the HTTP service using the informed port. In my case – obviously – this did not work.

Change the HTTP port permanently

As the above solution is only a temporary workaround, the error message can be ignored (well, not sure if it is an error message, looks green, OK, and so). To change the profile parameter of ICM, RZ10 is used. This makes the HTTP port change permanent.

  • Tx: RZ10
  • Profile: Default
  • Type: extended maintenance

Select create parameter


  • icm/server_port_0

Copy the parameter

The comment line changes and includes a change value. Also shows who did the change (blame).

Back at the parameter list, you can now see that the added parameter is listed.

Save the changes to the profile file.

Select yes to activate the new profile.

Confirmation that everything worked.

Note that you`ll have to restart your NW ABAP server to take effect.

Restart NW ABAP.

Test ICM HTTP Port

Did it work? How to test it? Easy: take a look at ICM service and access a service using a web browser. First, let`s see if ICM is listening on port 80$$ (btw: $$ is the ID).


  • Tx: SMICM
  • Path: Goto -> Services

  • ICM is listening on port 8000 for HTTP connections!


Very easy to test. Just access a ICF node using your web browser.

Let the world know

Update SPAM


Download SPAM update from SAP market place. Navigate to: Support Packages and Patches -> Browse Download Catalog

Go to: Additional Components -> SAP SPAM/SAINT UPDATE -> SAPM/SAINT UPDATE <NW version> -> Support Packages

Select SPAM version you want to install. Try to go for the latest version.

Save the file on your hard drive. If you want, you can use sapcar to check if the file is OK. If not, sapcar will fail and you`ll have to download the archive again.


Installation procedure can be found online at SAP Help.

  • Transaction: SPAM
  • Client: 000

Upload the SAR file to the server.

To finish the upload, click on decompress. This will make the content of the SAR file available for SPAM to process. Check the version of SPAM before update. You want to be sure that the update happened J

To start the update, go to Support Package -> Import SPAM/SAINT Update.

Click on OK. The status changes and you can see that an update is running.

In the status bar you can follow the status of the update. All should work just fine.

After the update finished, you can see that the version of SPAM was updated.

Let the world know

SAPGui Maximum runtime exceeded

Systems you work with have a timeout parameter. You may be logged on or an anonymous user, in both cases the system creates a session for you and controls its lifetime. This is not to remind you to get your work done rapidly, but mostly to ensure that a long living session is not eating up too much resource (so, short, yes, it is to ensure you get your work done rapidly). The timeout period for a session depends on your system. Normal time is between 10 minutes to 30 minutes. In a SAP NetWeaver ABAP system, the time is set by default to 10 minutes, or 600 seconds. The counter is reset each time a commit is issued by the running ABAP program.

It can, however happen that you reach a timeout.

What to do? I have to say that my system was a little bit busy. I restarted my dev system and all went back into normal. As an alternative, you can change the timeout parameter. How to do this and why you should not do this is explained in SAP Note 25528.

  • Profile parameter: rdisp/max_wprun_time
  • Tx: RZ10 (permanent change)
  • Tx: RZ11 (only until next restart)
Let the world know

A place for innovations: SAP`s InnoTakeOff

SAP is a big company. As with many big companies, people think: they cannot innovate. Or: they have no culture for that. Guess what, SAP is different. HANA is the proof for that, as well as programs like startup focus, InnoJam or CodeJams. Another event you may not know about is InnoTakeOff. Set in an official style, it offers SAP employees, students and startups the possibility to innovate and turning their ideas into reality using SAP technology. This is not just a small event. Look at the sponsors: SAP BI & IT and SAP P&I. The areas at SAP that create new products. Or the executive sponsors: Ingrid-Helen Arnold, Sam Yen, Carsten Linz. Yes. The current edition started in December 2015 and will end March 23rd 2016, and is divided into 3 phases: idea evaluation, prototyping and final event. The finalists of the three areas are announced, and from what I can see, this will be a hell of a competition.

What is my role?

Being an SAP Mentor, I was kindly asked if I am interested in helping with my expertise in all three phases. For the SAP employee part, I had to act upon two phases: idea evaluation and coaching. Evaluating the ideas was easy, online only, checking viability and desirability, providing feedback. Phase two added personal aspect, as I coached two teams of SAP employees whose ideas made it through to semi finales in their prototyping phase. One of those advanced to the finale! I am little bit proud of themJ. For the startups and students, I only had to evaluate the ideas. Guess what: two ideas I evaluated were also selected as finalists!

Phase 3

Final phase, grand finale, 14 teams, on site, Silicon Valley, live systems, 2 days to finalize the idea. With support from InnoTakeOff team and my manager, I was able to get funding for the flight and will be able to join forces with the onsite coaches. The mixture of people attending looks very promising. People that already have experience with HCP, HANA, IoT, UX, others only starting to work with this. All will benefit from the power of SAP`s underlying platform. At least that what I expect J If you ever participated in an InnoJam, you know that it is somewhat magic. People are working fully concentrated, solving problems and doing things in such a short time it seems unbelievable the demoed app was developed during the event. Now, with the InnoTakeOff, participants had even more time to prepare themselves, imagine how that event will be!

Yes, I am excited. See you in the valley next week.

Let the world know

Initial configuration of TMS for a single system

To do some work with an ABAP system, you need to have TMS configured. In a single system, for demo/learning purposes, you do not have to set up a complete TMS landscape. You only do an initial configuration of TMS. This is an easy task and does not involve configuration steps. You access transaction STMS and let the system do the rest.

  • Client: 000
  • User: SAP*
  • Transaction: STMS or: SO06 -> post installation tasks -> TMS

Transaction SE06

Transaction STMS

Accessing for the first STMS will give you already a dialog confirming the transport domain. From here on, it is just clicking on save and let the system do the rest of the configuration for you.

See SAP Note 761637 what new standard password means. In case the system is new, and no default company address was yet created, you`ll have to do so now.


TMS is configured and ready to be used.

Let the world know

Initial Setup of NetWeaver ABAP System – verification

After running the initial setup task, you might want to know if your system is actually OK. Instead of checking parameters manually, you can also make use of the task wizard. A task list named SAP_BASIS_SYSTEM_CONFIG_CHECK is available that runs a set of tests against your configuration.

Transaction: STC01


Check the validation tasks you want to execute.

Execute the verification


For each warning or error, you can access the log message to understand why the task failed.

If you want, you can include this task in your daily work routine.

Let the world know

Initial Setup of NetWeaver ABAP System

After installing a SAP NetWeaver ABAP system you have to carry out several initial configuration steps to get working system. You can do these manually or simplify your life and use the “new” configuration wizard that aids you through this. Right after finishing the installation of a NW ABAP system, sapinst shows you a confirmation dialog, which includes a link to an SAP Note: 1923064. This note explains how to execute the initial configuration wizard.

Don`t be too excited about the note. It does nothing more than redirect you to Configuration Guide available on SAP Market Place. There is some documentation about his available on SCN [1] and [2]. The wizard is available with NetWeaver ABAP 7.4/7.5 and is executed via the ABAP task manager. Two transactions are important to know:

  • STC01: ABAP task manager
  • STC02: Task list monitor

Task manager contains a list of tasks you have to execute and means that you will save time and won`t miss an important configuration step. The above linked guide shows how to assign the right permissions to a user. To run the wizard, go to the ABAP task manager.

Transaction: STC01

In a base NW 7.5 system, 60 tasks are available. Enough to get you started setting up a system.

For the initial setup for a NW ABAP system, out of the 60 tasks, SAP_BASIS_SETUP_INITIAL_CONFIG needs to be selected.


Select the tasks you want to run.


The PSE file is created and configured by this task too. Default values are pretty weak/compatible. 1024 bits and SHA-1. I think it is a good idea and time to change this to somewhat more secure:





Let the world know

Install an SAP NetWeaver ABAP 7.5 system on SEL12


Download and install SUSE Enterprise Linux 12 from Suse and install it. The OS is available as 2 DVD ISOs, 7.6 GB of data. If I remember correctly, I only needed DVD1 in the end.

Download SAP NetWeaver 7.5 installation files. As DB, I am using MaxDB. Total of 5.35 GB:

  • Kernel
  • MaxDB
  • SWPM
  • Installation


Copy all files to your Linux server. Place them into a folder that everyone can access and unzip the files. I used /mnt/sapinst and gave all users read permission. This is necessary as the installer creates an SAP adm user and runs the installation under this user id. To start the installation, call the SAP Installation Wizard. Inform the basic data of the SAP system you are going to install:

  • Standalone
  • DB type: MaxDB
  • NetWeaver 7.5

The wizard will ask you to provide the sizing of the system. Of course, on a laptop, demo is enough.

A virtual IP and hostname can be configured, if you wish. Not necessary, recommended, but I opted to not use this.

With the gathered information, Yast2 is going to install additional software.

Next you have to inform the wizard where to find the installation data. That’s the files downloaded and extracted before. Do this for:

  • Software provisioning manager
  • Installation
  • Kernel
  • MaxDB

To add the medium, confirm that you want to had another one each time.

After adding all needed data medium, select no and also inform the wizard that you do not have an additional medium: No.

SUSE documentation told me that now sapinst is called and started. Did not work for me, so I had to start it manually (which, btw, means, that all the above steps were a waste of time as I had to add each medium again in sapinst). Nevertheless, in case you have more luck than me, sapinst should start and ask you some more questions like system name, SID, schema name, and so on. And then starts installation.

Takes a while. Import ABAP steps takes some time. In case anything is configured 100% and the system has all the libraries and the user premissions needed for an SAP system, the installation will just run through.

When you reach the last step of the installer, you can see that the NW ABAP system is being started and the final configuration is executed by calling some BAPIs.


After the installation is finished, you see the confirmation dialog. The dialog contains a SAP Note pointing to a note explaining how to speed up initial configuration of your new system. Read the note, or read my blog on this.

Now you can log on to the system.

In the system status, you can check the system information. Congratulations, it is a SAP NetWeaver ABAP 7.5 SP00 system!

Let the world know