Troubleshooting in the Web Service
Runtime
In the following sections, you will find notes on how to deal with error messages that the report SRT_ADMIN_CHECK produces (refer also to the section Checking the Configuration):
Error messages can occur in the following areas:
· Event Handler
· Task Watcher
· Background Jobs
· Client-Specific Settings / Function Tests
bgRFC Settings
The name of the bgRFC destination is maintained in two different areas. One is in the general configuration of the bgRFC and the other in the configuration of the WS runtime. It is possible that two different values were set for the bgRFC destination – for example, through manually setting up an inbound destination in an area. This results in problems when scheduling sequences. If such an error occurs during execution of the report SRT_ADMIN_CHECK, the error message is: Destination <dest_1> is not the same as it is configured at the bgRFC <dest_2>” is returned.
Recommendation:
· Call transaction SBGRFCCONF. The name of the inbound destination displayed there must correspond to the name of <dest_2>. To register this name in the technical configuration, log on in client 000 and execute the report SRT_ADMIN. Enter the name of the inbound destination and execute the report.
· Create a CSN message if the inbound destination of the bgRFC setting is different from the technical configuration (output for SRT_ADMIN report) and when executing report SRT_ADMIN displays the following: Inbound destination in bgRFC is not usable
Event Handler
If the WSRM Event
Handler is active, events that occur in connection with
Web Services Reliable
Messaging are processed. Error-free functioning of the WS-RM Event Handler
is a prerequisite for being able to cancel sequences using the Sequence
Monitor. For more information on the Sequence Monitor:
Monitoring Sequences
in SOA Manager.
The WSRM Event Handler must run in client 000 and can be started manually from other clients.
Check whether the WS-RM Event Handler is running by either performing the SRT_ADMIN_CHECK report or by entering WSRM* in the Table Name field in transaction SM12. If the list is empty, the Event Handler is not active.
Recommendation:
· Check whether the service destination of client 000 is set correctly. Call the RSEHCONFIG report.
The Event Handler has been exited if the value 0 is in the field Maximum Allowed Processes. The default value is 3. You can change this value in the field Maximum Allowed Processes.
·
If no configuration
problem is discovered, the error must have other causes. Check the function of
the service destination in client 000 using the SRT_ADMIN_CHECK report. The
cause could be logon problems with the service user at the service destination
(blocked user or invalid password). For more information, refer to the section
Client-Specific Settings /
Function Tests below and
to
Monitoring
Event-Controlled Processing.
Background Jobs
A standard background job is supplied for runtime management. BC_SAP_SOAP_RUNTIME_MANAGEMENT. You start the background job using transaction SM36 (pushbutton Standard Jobs - Standard Scheduling).
Recommendation:
To check the status of the job, choose the pushbutton Standard Jobs in transaction SM36. The job list shows two entries for BC_SAP_SOAP_RUNTIME_MANAGEMENT. The first one shows that there is a job with the status Finished and one with the status Released.
If this is not the case, the job log can provide information about the reason for the problem.
Task Watcher
The Task Watcher process is started by the AUTOABAP (every 5 minutes). You can call the Task Watcher manually through the ABAP report TASK_VITAL_RUN.
The function of the Task Watcher depends on the existence and correct functioning of the service destination in client 000.
If no service destination is displayed for client 000 during execution of the report SRT_ADMIN_CHECK, this can have the following reasons:
The user of the service destination:
· is unknown
· has no (time) validity
· has no valid password
· is locked (due to too many failed login attempts)
· does not have the required authorizations
Recommendation:
Look at the output of the report SRT_ADMIN_CHECK. If there is no error message, use the name for the service destination in client 000 and call transaction SM59. Check the status of the password in the field PW Status.
Check the number of the client (000) in the settings for the destination.
Perform a Remote Logon in order to check whether this causes problems. If no error messages are displayed and the login still fails, call the User Management function (transaction SU01) and unlock the user. If this does not fix the problem, check the authorizations of the service user. Call transaction PFCG and check whether the role SAP_BC_WEBSERVICE_SERVICE_USER has been assigned to the user.
Client-Specific Settings / Function Tests
Settings
The service destination must be set in all productive clients. The problem investigation procedure is the same as described in the section Task Watcher.
Check whether:
· The user for the service destination is known in the client.
· The user is unlocked.
· The password is valid.
· The client number at the service destination is SY-MANDT.
· The Remote Logon works correctly.
· The user is assigned the role SAP_BC_WEBSERVICE_USER.
Function Test
In the third section of the configuration check using the report SRT_ADMIN_CHECK, the client-specific functions are tested. Service destinations are checked using a test (Remote Login). All problems are logged (Unlocked, Valid time range, Password status, Missing authorization).
For more information, refer to:
Monitoring
Event-Controlled Processing