0% found this document useful (0 votes)
51 views5 pages

Basic Activation of Webservice SOAP Runtime

Basic activation of the web service SOAP runtime

Uploaded by

ganesh.bhadury
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
51 views5 pages

Basic Activation of Webservice SOAP Runtime

Basic activation of the web service SOAP runtime

Uploaded by

ganesh.bhadury
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Basic activation of web service SOAP

runtime

This blog will explain how to activate the SOAP runtime inside the ABAP stack. This
is a mandatory step before you can set up web services 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 tool set:


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.

In case of issues with the creation of user DELAY_LOGON, check this OSS note:

2848763 – Creation of DELAY_LOGON user using SRT_ADMIN does not work


reliably.

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:


For the background jobs check OSS note 2231932 – ESI – How to schedule the
SAP_SOAP_RUNTIME_MANAGEMENT standard background job.

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 transaction code SU01D to see if the users are created properly with the correct
roles.

Use transaction code SBGRFCCONF and check the last tab that the supervisor
destination is assigned. In systems with CUA there might be an issue with creating
the supervisor destination. In this case follow the steps of OSS note 2775490 – Error
in customizing while creating supervisor destination.

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.

SOAP consistency check: see oss note 2353589 – Consistency Check for Soamanager.

Consistency check for Business application ID: see oss note 2347852 – Consistency
check for usage of Business Application Id within Web Service Configuration.

Other notes:

 2330353 – ESI – Dump: CX_SOAP_SEQ_SCD_ERROR in CL_SOAP_QUEUE_BGRFC


 2442402 – ESI – Inbound destination service errors in SRT_ADMIN technical check
 2469988 – ESI – How to create Supervisor Destination in SBGRFCCONF
 2515926 – ESI – SRT_ADMIN_CHECK report error: Unicode flag on destination <&>
is different than on client
 2530329 – ESI – No texts are visible for report SRT_WSP_INITIALIZE_WS_CFG
 2573849 – ESI – Logon error in SM21
 2586443 – ESI – Error: No check of inbound destination:WS_BGRFC_INBOUND000
no usable service destination in client 000
 2772494 – ESI – User credentials are requested when executing a Local Shortcut
Web Service call
 2799685 – ESI – Update hung while creating user via SRT_ADMIN
 3057262 – Deletion of error message in SBGRFCMON by report SRT_SEQ_TOOLS
 3128006 – ESI – Configuration not successful: No default co. address has been maint.
in the system. Create an address.
 3214850 – ESI – How to utilize the setup from SRT_ADMIN effectively

SOAMANAGER and issue solving

In SICF activate the services /sap/bc/srt and


/sap/bc/webdynpro/sap/appl_soap_managements.

After the steps above and the general activation, the transaction SOAMANAGER
should start up properly.

You might also like