Configuration of Web service runtime

2017-08-31 Page 1/10 1043195 - Configuration of Web service runtime Version 7 Type SAP Note Language Inglés Master Language Alemán Priority Recommendations / Additional Info Category Customizing Release Status Released for Customer Released On 05.10.2016 Component BC-ESI-WS-ABA ( Web Service and SOAP - ABAP ) Please find the original document at https://launchpad.support.sap.com/#/notes/ 1043195 Symptom You want to set up the technical configuration of the Web service runtime environment. You also want to check the technical configuration of the Web service runtime environment. Other Terms SOAP Web service runtime exception CX_SOAP_SEQ_SCD_ERROR Plain SOAP Reason and Prerequisites You use the ABAP Web Service runtime. As of SAP Basis 7.00 SP14, a technical configuration of the Web Service runtime is required. This SAP Note is valid up to SAP Basis 7.40. As of SAP Basis 7.50, SAP Note 2347013 applies. Solution You want to set up and check the technical configuration of the Web service runtime environment. You use the Web service runtime with the SAP products "Netweaver" and "Business By Design". You do not require the technical configuration of the Web service runtime when you use the Web services in Release NetWeaver 7.00 as of Support Package 14 if you do not want to use asynchronous Web services. It is not important whether the asynchronous Web services are transferred with WS-RM or SAP RM. The Web service runtime to send asynchronous messages is first delivered in SAP NetWeaver 7.00 Support Package 14. You may not want to activate the new Web service runtime process, and you should only do so if you want to use the process. Introduction and overview Executing asynchronous Web services requires settings to ensure trouble-free processing. For this task, you must configure such system components as AUTOABAP, RFC, bgrfc and ICF that were set by the Web service runtime. Remote-enabled function modules (SRT_TECHNICAL_SETUP, SRT_TECHNICAL_SETUP_RESET) are provided to operate a central configuration. Programs for technical configuration You can call transaction SRT_TOOLS (SOA Runtime Tools) to access the services for the technical configuration: "Technical Configuration of SOAP Runtime" or "Check Administration Environment of SOAP Runtime". When you double-click the selected row, the programs for the technical configuration start.

2017-08-31 Page 2/10 Program for making and withdrawing the technical settings: SRT_ADMIN Program for checking the technical settings: SRT_ADMIN_CHECK Different availabilities for the specified programs and their operation are specified in the different versions. As a result, automatic setup and activation of ICF nodes for the Web service runtime is not available in Releases 700 and 710 (for example). The configuration of a Netweaver system can be performed manually or automatically using the configuration program (report SRT_ADMIN). Caution: Not all releases of "NetWeaver" and "Business By Design" have the aforementioned programs and their functions. There are differences in the program functions and their display (message display). For example, the technical configuration in Netweaver Release 7.10 Support Package 2 is performed by the function module SRT_TECHNICAL_SETUP and not by the program SRT_ADMIN. The function SRT_TECHNICAL_SETUP_RESET will only be available as of Netweaver Release 7.10 Support Package 5. Automatic setup of ICF nodes for the Web service runtime is not yet available in Releases 700 and 710. Automated execution of configuration Call transaction SRT_TOOLS and double-click the "Technical Configuration of SOAP Runtime" function. We recommend that you begin the configuration of a system in client 000. The users that are used there should have a range of administrative authorizations. The required authorization objects for these users are: S_TCODE with SA38 S_PROGRAM with the action SUBMIT S_SRT_ADM with activity 70 and WS_NAME "*" S_USER_GRP with the class * and activities 01, 03, and 06 S_USER_SAS with activities 01, 06, and 22, as well as the activity group SAP_BC_WEBSERVICE_SERVICE_USER S_USER_AGR with activity 64 and the activity group SAP_BC_WEBSERVICE_SERVICE_USER S_RFC_ADM with activities 01, 02, and 06 and RFC type "3" S_BGRFC with activity 02, bgrfc type 07 The options in the technical configuration are as follows: Automatic setup. Perform technical setup The steps described in the following section are performed by the automated setup process; they are listed in case a manual setup is required and to document the activities. Create a user for the service destination. The service destination is used for background activities in a concrete client with specific authorization requirements and must therefore be assigned to a user. For security reasons, this user must have the type "System" or "Service". Since users that have the type "Service" are permitted to perform a logon, we also do not recommend this type. During automatic setup, the system creates and uses a user that has the type

2017-08-31 Page 3/10 "System". In addition to the data, this user receives an alias and is activated for an unlimited validity period (December 31, 9999). The name of the user is SAP_WSRT. In certain versions or maintenance levels, the name is also created randomly and consists of hexadecimal characters. The password of the user is created via a system routine. After the user is created, the role SAP_BC_WEBSERVICE_SERVICE_USER is assigned to it and a user comparison of the role takes place. The role is part of the delivery and can be enhanced only to include corrections and enhancements. If customer-defined rules are ignored when generating the password, you must perform setup for the service destination (user and RFC destination) manually. Create the service destination as an RFC destination with the type "3". The service destination is created as an RFC destination. The administration attributes are as follows: Connection type "3" (=ABAP) Name WS_SERVICE_<service_user_name><client> Technical Settings: Default values Logon & security Client = <client>, user: <service_user_name>, password status: secured MDMP - Unicode: Communication type with the target system: Transfer the Unicode settings from the system settings. All other settings for MDMP remain at their defaults. Special options: qrfc version selection: 0 classic qrfc All other settings remain at their defaults. Register the service destination in the SOAP runtime. The name of the RFC destination is saved in the global properties of the SOAP runtime. Create a background RFC (bgrfc) inbound destination. The registry of an inbound is required to use the scheduler in the inbound scenario. The inbound destination is required only once for each system and is set up in client 000 of the system. Together with this destination, prefixes are entered to divide the messages into different processing queues. The names of the prefixes of the inbound destinations are: SRTQC_ SRTQP_ SRTQS_ PERSP_ PERSC_ Register the inbound destination in the SOAP runtime. The name of the inbound destination is saved in the global properties of the SOAP runtime. The name of the inbound destination is WS_BGRFC_INBOUND. Depending on the release and the time when the configuration was first performed, the names WS_SRV_INBOUND, WS_SRV_INBOUND000, and WS_SERVICE_<key>_IN are also possible, whereby <key> represents hexadecimal encryption (for example, WS_SERVICE_1DEFA1887AA3_IN). An inbound destination name that is granted once and used in the bgrfc must always be used. Even after you reset the settings, it is important that you use this name because no changes to the assignment of the prefixes to an inbound destination name as described above are permitted. You can use the "Define Inbound Dest." area of transaction SBGRFCCONF to determine the name that was first used for the bgrfc and that is valid. If the overview that is located there contains several names of inbound destinations, you can double-click each listed name one after the other to determine the name that is registered for the Web Service runtime. If the list of the five constant prefixes is displayed in the "Queue Prefixes" overview, the correct inbound destination name that is currently valid is determined for the Web Service runtime. After a repeated switch between the setup and the reset in the "Name of Inbound Destination" field of the report SRT_ADMIN, the system should also display this name in the "Web Service-Specific bgrfc Settings" block. An automatically performed setup automatically always attempts to determine the name registered for the bgrfc. The name is assigned only when setup is performed for the first time.

2017-08-31 Page 4/10 Assignment of check class to inbound destination The use of the bgrfc scheduler by the Web service runtime makes it necessary to suppress deletion of units in the monitor of the bgrfc because this may result in inconsistencies between the Web service runtime and queues occurring. This is achieved by a registry of an technical ABAP class to a scheduler destination of the bgrfc. The name of this scheduler destination corresponds with the inbound destination of the Web service runtime on the bgrfc. This means that after an inbound destination registry on the bgrfc, a scheduler destination is set up (see the "Scheduler: Destination" tab within the configuration using transaction SBGRFCCONF) and the name of an ABAP class in the Web service runtime is assigned to this. In addition, you must activate this registry. This action is also performed by the automatic setup process. The name of the ABAP class that regulates deletion of units from the Web service runtime is: CL_SOAP_QUEUE_BGRFC_MON_CB. If required, you can also make this setting manually. If you do this, note that you have to do it only in client 000 and that the name of the scheduler destination must be identical to the name of the inbound destination (constant prefixes). Note that if you use the technical reset, the check class on the scheduler destination is not reset. Start the task watcher. The final task of the automated technical configuration is to start the task watcher as long as setup has taken place in client 000. The task watcher performs the following activities in the background: 1. Monitoring the logical units of work (LUWs) that execute a Web service that contains a TUCC pattern in all clients. 2. Monitoring the transactional registries of the Web service in the COMMIT or ROLLBACK phase. 3. Synchronizing the design, time, runtime, and configuration changes in the various clients. Perform the technical reset The technical reset is the reversal of the technical setup. All settings are undone with the exception of the registration of the inbound destination to the bgrfc and the check class to the scheduler destination. If the reset takes place in client 000, the task watcher and the event handler are canceled. o Manual setup. Manual setup is provided for repairs. Depending on the version, release, and maintenance level, it provides three functions. - ABAP connections An ABAP connection that serves as a service destination is registered. This field (activated by the existing radio button and given the name of an existing RFC destination) overwrites the existing entry in the global properties of the SOAP runtime when you subsequently execute the report. You use this function for the manual configuration or for repair purposes. - Web-service-specific bgrfc settings An inbound destination is registered for the bgrfc. By activating the existing radio button and given the name of an inbound destination, this name overwrites an existing name in the configuration database. You must have registered the name of the inbound destination in advance on bgrfc together with the prefixes PERSC_, PERSP_, SRTQC_, SRTQP_ and SRTQS_ using transaction SBGRFCCONF. You use this function for the manual configuration or for repair purposes. The system makes the settings automatically when you use the automatic setup. - Web-service-specific ICF settings Set up the nodes required for the WS runtime operation for the current client on the Internet Communication Framework(ICF). This function must be performed once and it is not performed by the automatic setup. It can be performed again. Pay particular attention to Note 1124553 regarding the activation of ICF services of the Web service runtime or Web Dynpro tools.

2017-08-31 Page 5/10 o Runtime trace - Configuring the trace The settings for recording a trace (recording internal data and contents of the Web service programs as well as performance measurements of the programs involved in the WS runtime) can be made with the parameters "User name", "Trace level" and "Validity period". Use the documentation for these settings or the existing input help (F4 key) for further explanations. The recording of a trace serves as a diagnosis tool for examining incorrect behavior and performance. - Configuring logging You can make the settings for recording a log with messages of the programs involved in the Web service runtime using the parameters "User name" and "Log level". Use the documentation for these settings or the existing input help (F4 key) for further explanations. The recording of messages of the Web service runtime programs serves as a diagnosis tool for examining incorrect behavior and performance. Using the program SRT_ADMIN Execute the program SRT_ADMIN with the function "Perform technical setup" in client 000 if you want to use the asynchronous Web services in it. You must repeat the process in every client in which you want to use the Web services live. In general, client 066 is to be ignored. When you start the program, the system reads any existing settings and inserts them in the initial screen: This is the name of the service destination in the current client and the cross-client name of the bgrfc inbound destination. If there are already values in the fields "Name of ABAP Connection" and "Name of Inbound Destination" for the aforementioned reason, you are not required to make any changes to the settings in this client. However, you must manually reset certain settings if a check of the settings (using the report SRT_ADMIN_CHECK) has resulted in errors. To execute the function, choose "Start" (F8 key). The output of messages indicates the result of the execution in each case. If you want to deactivate the service destination, for example, select the check button in front of the "Name of ABAP Connection" field in the "ABAP connections" block, delete the field with the name of the service destination, and execute the report (F8 key). Note that when the automatic technical configuration (service destination) is performed, system programs that are required for the background processing of Web Services are started approximately five minutes later. These programs only exert a negligible load on the application server. The configuration should then only be performed if you want to actually use the new Web service runtime. The technical configuration does not include the background programs of the Web service runtime that are managed via a job. The job is contained in the list of the "Standard Jobs" function in job management and is started and monitored using this. o Standard job of SOAP runtime (only in some releases) - This job is scheduled as a standard job (activated manually using transaction SM36 -> Standard jobs or automatically by the installation (like for the product "A1S")). The job SAP_SOAP_RUNTIME_MANAGEMENT manages several tasks of the SOAP runtime by starting other jobs. For more information, see SAP Knowledge Base Article 2231932. Check of technical configuration (report SRT_ADMIN_CHECK) o Service destination in all productive clients

2017-08-31 Page 6/10 The aforementioned rules for client 000 apply also for all other clients that you use live. You must create a separate user for each client and assign a new RFC destination to it. Pay particular attention to the settings for the client in the section "Logon & security". The client specified there must be the current client of the logon. You must also use the report SRT_ADMIN to inform the relevant client of the technical configuration of the name of the destination. In addition, note that the modified design time objects of the Web service runtime (that is, service and proxy definitions) are also compared using the RFC destinations. This comparision is called from the maintenance transaction of the objects (SE80 + SPROXY) as well as when the objects are transported in the AFTER_IMPORT phase of the transport. o Check of service RFC destinations in the system. You can use the report SRT_ADMIN_CHECK to check the existence and the functions of the service destinations of the system. Start the report and note the messages in the output table. Execute the report according to the settings in the relevant client, and note messages that relate to the current logon client. The report always checks all clients. The output of the checks performed by the program consists of three sections. In the first section, the system outputs check results that apply for the entire system (cross-client). In section 2, the system outputs check results that relate to one client. In section 3, the system outputs check results that relate to a connection check in a certain client. Example: Section 1 Check of cross-system settings The bgrfc destination is ready for use. The bgrfc supervisor destination is registered. WSRM event handler is active. TASK monitor is active. Data collector for monitoring is active. End of the checks of the cross-system settings Section 2 Checks of the client-dependent settings Service destination is not configured in client 066. End of the checks of the client-dependent settings Section 3 Client-dependent connection checks (destinations) Connect test in client 000 was successful. Service destination is not configured in client 066. Connect test in client 105 was successful. Connect test in client 106 was successful. End of the client-dependent connection checks (destinations) No problems are reported in section 1 for the above example output. In section 2, the system documents that no service destinations were set in client 066. This may mean that you should not use client 066 live. This is still correct because client 066 serves the "Early Watch" service and is not used live by customers. In section 3, the system reports that the connection tests in clients 105 and 106 were performed successfully. This explains that the system is used live in clients 105 and 106. In Releases 730, 731, and 702, the output of the checks is newly categorized and typed. The function to check the administrative environment of the SOAP runtime calls the program SRT_ADMIN_CHECK. A selection parameter for the subsequent program run exists in the new version of this program. You can first restrict the check to one single client. In addition, you also have the option of checking only certain areas

2017-08-31 Page 7/10 [service destination, inbound destination, bgrfc configuration, ICF nodes, and IDP settings]. In each check run, the settings that are valid system-wide are checked: Supervisor destination and task watcher. The settings that were selected or that are client-dependent then follow: Supervisor destination The supervisor destination is a setting on the bgrfc that is a prerequisite for operating the Web service runtime. You cannot use the technical setup described in this note to execute this destination. The check that is performed reports only the current state of this setting (existence and status). The bgrfc supervisor destination has the following attributes from the point of view of the Web service runtime: Client, name, status, status text, name of the user on the supervisor destination, name of the user who made the last change, date of the last change, and time of the last change. Task watcher This check type reports the current status [active, inactive] of the process and the following attributes: Repeat interval, name of the user who made the last change, date and time of the last change. Inbound destination This check type reports the status of the inbound destination to the bgrfc [operational, non-operational, usability, error messages, name of the check class, activation status of the check class]. Service destination This check type reports the technical attributes of the current service destination [client, name of the RFC destination, status, technical name of the destination, and the name of the user on the service destination]. bgrfc This check type reports the current database statistics that are available (including the number of units that contains errors and the number of inbound and outbound schedulers). If the number of inbound schedulers is lower than one, the status of the bgrfc is incorrect from the point of view of the Web service runtime. ICF nodes You can use the technical setup to manually set up and activate the ICF nodes that are used for the Web service runtime. These are nodes from the following list: /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 Idempotent service This check type comprises the setting for the idempotent service. The status is determined from the existing configurations, as well as the status of the background processing programs and their job status.

2017-08-31 Page 8/10 WSRM event handler Due to a significant change within the SOAP runtime, the functions of the WSRM event handler are no longer required and the process is no longer started after you implement the corrections. A restart is prevented. As a result, the meaning of the check is reversed; that is, if the WSRM event handler process is active, a configuration error exists. Troubleshooting The following messages in may indicate problems in the configuration of the system: - WSRM event handler is NOT active! - (See changes in Releases 730, 731, and 702.) After the successful configuration of a service destination in client 000, the WSRM event handler is activated by AUTOABAP. This may take up to 5 minutes after you enabled the destination. If the system displays the above message after more than 10 minutes, there may be several reasons for it: The service destination of client 000 is not maintained or is maintained incorrectly. Check whether the system outputs more precise messages in section 3. The administrator has manually deactivated the WSRM handler (number of released processes is set to zero) on the instructions of SAP Support. Ask the administrator or SAP Support about this issue. The check program SRT_ADMIN_CHECK checks incorrectly. Search in SAP notes for corrections of the program SRT_ADMIN_CHECK, implement these corrections, and check again. - Task monitor is NOT active! After the successful configuration of a service destination in client 000, the Task Watcher is activated by AUTOABAP. This may take up to 5 minutes after the first configuration of the service destination. Start the program SRT_ADMIN_CHECK again after several minutes. If the message remains, there may be several reasons for this: The service destination of client 000 is not maintained or is maintained incorrectly. Determine the name of the service destination in client 000 by calling the program SRT_ADMIN. Call transaction SM59, display the management data, and check the following circumstances: - Whether the destination is of the type "3" - Whether the destination points to client 000 ("Logon & security") - Whether the user (in "Logon & security") is of the type "S" and is assigned to the role SAP_BC_WEBSERVICE_SERVICE_USER - Whether a remote logon is possible - Whether the password of the user is set correctly - Whether the destination is set up for classic RFC ("Special Options") - Whether the user is unlocked (locking can occur due to too many error messages, for example) - Whether the user has a valid task period - The job & for the SOAP Runtime Management is NOT active! - Use transaction SM36 to check whether logs have already been written for the job SAP_SOAP_RUNTIME_MANAGEMENT, telling you that the job has already been scheduled. If the job has not been scheduled, follow the steps in SAP Knowledge Base Article 2231932. - Missing authorization & for service user & on destination &. Authorizations are missing for the user on the specified RFC destination. This could be due to any of the following reasons: a) The user was not assigned the role SAP_BC_WEBSERVICE_SERVICE_USER or, b) the role must also be upgraded after a software upgrade. Distribute the new role to all live clients. - Service user does not exist or is of type 'S' The user on the RFC destination does not exist or is of type "S". - Client on RFC destination & is & and not & In the settings "Logon & security" for the RFC destination, a different client is entered to the current client

2017-08-31 Page 9/10 (SY-MANDT). - The destination & is not suitable for background qrfc The RFC destination is not suitable for use as a bgrfc destination. - The destination & is not suitable for classic RFC The RFC destination is not suitable for use as an RFC destination. - Destination & is not the & configured on BGRFC The inbound destination on bgrfc (see transaction SBGRFC ) does not correspond with the destination that is specified as configured in the report SRT_ADMIN. - The bgrfc supervisor destination is not registered The bgrfc supervisor destination is not maintained. Start transaction SBGRFCCONF and maintain this destination. To do so, consult the documentation for bgrfc. - Error for service destination in client xyz password logon no longer possible - too many failed attempts Due to a problem with password management or with a password that was assigned incorrectly or changed, there were several failed attempts when using the service destination and the user was locked. Assign a new password to this user, enter it in the RFC service destination, and unlock the user. Changes due to new releases and corrections Releases 702, 730, and 731 make significant changes to the Web service runtime; these changes affect the configuration and its checks. As a result, the WSRM event handler is redundant; operating and starting this process is therefore no longer required. For this reason, the status of an event handler that is operating has been explained as an error. Dieses Dokument referenziert auf SAP-Hinweis/KBA Titel 2231932 How to schedule SAP_SOAP_RUNTIME_MANAGEMENT standard background job 1614334 Web Service Configuration: Track Design Time Changes 1493847 System log entries at design time for runtime comparison 1350556 Customizing for Integration of Bank Analyzer with ERP GL 1336891 Web service deleted after Design Time objects are changed 1304349 Missing settings for Web service with WSRM 1163844 Deleting the technical configuration 1124553 Inaktive ICF services of Web Service runtime Dieses Dokument wird referenziert von SAP-Hinweis/KBA Titel

2017-08-31 Page 10/10 2515926 SRT_ADMIN_CHECK report - Unicode flag on destination... is different than on client 2469988 How to create Supervisor destination in SBGRFCCONF 2330353 CX_SOAP_SEQ_SCD_ERROR dump in CL_SOAP_QUEUE_BGRFC 2469949 "ICF Error when creating HTTP client object by Config for URL" in Web Services ABAP 2479984 SAP_WSSE_TOKEN_CACHE_CLEANUP fails with authorization error 1614334 Web Service Configuration: Track Design Time Changes 1350556 Customizing for Integration of Bank Analyzer with ERP GL 1493847 System log entries at design time for runtime comparison 1163844 Deleting the technical configuration 1336891 Web service deleted after Design Time objects are changed 1304349 Missing settings for Web service with WSRM 1124553 Inaktive ICF services of Web Service runtime Terms of use Copyright Trademark Legal Disclosure Privacy