Configuring the Web Service Runtime

Technical Setup

1. In each productive client and in client 000, execute the Technical Setup in transaction SRT_ADMIN. You can choose between the automatic and the manual setup.

   Using this report, you create a service destination for communication through RFC and you perform the settings for the bgRFC (Background Remote Function Call).

   SOAP requests are processed using the Internet Communication Framework (ICF). The SAP NetWeaver Application Server uses the HTTP protocol of the ICF for communication between the Web service consumer and the Web service provider. The ICF provides the infrastructure for handling HTTP requests in work processes in an SAP system. An HTTP request calls a service in the ICF server. This service contains one or more HTTP request handlers that are responsible for running the ABAP functions.

   Using report SRT_ADMIN, all the following ICF services required for standard functions of the Web service runtime are created:

   • /sap/bc/srt/

   • /sap/bc/srt/wsil

   • /sap/bc/srt/wsdl

   • /sap/bc/srt/esf_in

   • /sap/bc/srt/xip

   • /sap/bc/srt/rfc

   • /sap/bc/srt/pm

   • /sap/bc/srt/xip/sap

   • /sap/bc/srt/lsc

   • /sap/bc/srt/scs

   The log and trace levels can be selected using the report SRT_ADMIN or directly in SOA Manager under Logs and Traces.

   If there are any problems, you can also perform the configuration in single steps.

   • Create a service destination

   • Performing Settings for bgRFC

   Afterwards you should check the configuration.

2. Start the background request SAP_SOAP_RUNTIME_MANAGEMENT for component BC. Call transaction SM36, and choose Standard Jobs - Standard Scheduling and Schedule Standard Job. You must schedule the job hourly as default scheduling.

3. If bgRFC has not been used before, set up the bgRFC supervisor destination in transaction SBGRFCCONF under Define Supervisor Destination. Specify a name and a user and assign it to role SAP_BC_BGRFC_SUPERVISOR.

Configure Message Persistency

From SAP NetWeaver 7.4 Service Package 0, Web services are stored in a Web service-specific persistency (WS persistency). Messages that were created in an older release are stored in the persistency of the SAP Process Integration engine (PI persistency). You can see all messages in the message monitor (transaction code SRT_MONI) and the column Persistency shows where a message is stored.

1. Start Web Service Utilities (transaction code SRT_UTIL).

2. In the menu bar, choose Tools and then Global Configuration.

   Under Message Persistency, you see where your messages are stored.

   If WS Persistency is displayed, all of your messages are stored in Web service persistency.

   If PI Persistency is displayed, all of your messages are stored in PI Persistency.

   If WS and PI Persistency is displayed, both persistencies are in use. This is the case if you have just upgraded your system and still have some older messages in PI Persistency and new ones in the WS Persistency.

3. Specify the retention period for messages in Web service Persistency. The default value is 40 days.