This blog will explain how to activate the SOAP runtime inside the ABAP stack. This is a mandatory step before you can set up webservices in transaction SOAMANAGER.
Questions that will be answered are:
- What steps are required for the setup?
- How can I check if the setup is done properly?
- What are potential issue solving actions?
- What other tools are available?
Setting up the SOAP runtime
Setting up the SOAP runtime is extensively explained in OSS note 1043195 – Configuration of Web service runtime. The basic steps below have to be repeated twice: first you execute the actions in client 000, then in the main data client again.
Start transaction SRT_TOOLS for reaching the main toolset:
In the Technical Configuration section select the tool for Technical Web Service Configuration. This will bring you to the main activation program:
Hit Execute to start the automatic configuration. For more information see OSS note 2347013 – Configuration of the ABAP Web Service Runtime with transaction SRT_ADMIN.
Checking the configuration
To check if is ok go back to the main screen and select the Check Technical Web Service Config tool. This is the start screen:
Start the check. Result should be like screen shot below:
Issue solving during setup
During setup things might go wrong. If you run without SAP_ALL, please check the notes that you have sufficient authorization. In the process both a background user (SAP_WSRT and DELAY_LOGON) and RFC (BGRFC_SUPERVISOR) are created. If you don’t have authorization for that, issues will happen.
Use tcode SU01D to see if the users are created properly with the correct roles.
Use tcode BGRFC_SUPERVISOR and check the last tab that the supervisor destination is assigned.
Issue solving program (run in SE38): WSS_SETUP.
Issue solving transaction: WSIDPADMIN.
Issue solving after setup
If you have issues after setup, run the above check tool via SRT_TOOLS, or directly via transaction SRT_ADMIN_CHECK.
Common root causes: changes in authorization, overzealous user admin deleted SAP_WSRT or DELAY_LOGON user, or somebody deleted the supervisor RFC destination, etc.
Consistency check for Business application ID: see oss note 2347852 – Consistency check for usage of Business Application Id within Web Service Configuration.
The SRT_TOOLS transaction also lets you jump to other useful tools such as the WS message monitor and the web services utilities tool.
Webservice issues after system copy
After a system copy you might be confronted with data inconsistencies. Upon start of SOAMANAGER you might get this screen:
Follow the instructions from OSS note 2353589 – Consistency Check for Soamanager. It might mean you need to run program SRT_WSP_INITIALIZE_WS_CFG to re-initialize the complete setup and reconfigure all the webservices again.
SAP background wiki
Please follow this link to the SAP background wiki on basic SOAP runtime activation.