Web Service Configuration

 

 

This article describes how to set up the web services runtime and common issues.

 

The Varo(FLM) Developer Guide has additional details on implementing web services.

 

How to setup the Web Service Runtime

  • Run SRT_ADMIN in SE38 ticking box ‘Run Technical setup’ in client 000
  • Run SRT_ADMIN in SE38 ticking box ‘Run Technical setup’ in client (XXX runtime client)
  •  In SICF activate node /sap/bc/webdynpro/ and everything underneath it
  • You may also need to activate a number of  other services inside SICF , when you activate select the yes to Activate all children services as well.
    • /sap/public/bc/pictograms
    • /sap/public/bc/webdynpro
    • /sap/public/bc/webicons
    • /sap/public/myssocntl        
  • If system is slow,
    • in RZ10 add parameter to the Instance Profile under Extended Maint. icm/keep_alive_timeout, set value to 300 (5 minutes) copy and activate the new instance profile.
    • Go to SMICM, then on menu /Administration/ICM/Exit Hard/Local
  • Hit refresh a few times until Green icon is showing again.  Check new parameter is set by menu /Goto/Parameters/Display
  • For more details please see the SDN article below.

  • SAP Note 1043195 - Configuration of the Web service runtime

 

Some Common Issues

  • Symptom: Access Denied IE Popup for Web Service Call
    • Check SOAMANGER that the SSL flag is set.
    • If SSO is used from Ent Portal integration also check in SOAMANGER that the SSO option is set.
  • Symptom: Call to SAP system is SSL but URL switches to HTTP.
    • Check SMICM that HTTPS is configured. See example below.
    • Check the RZ10 parameter login/ticket_only_by_https is set 1.
  • If you have a password rule: "Password must be max 8 characters and must not contain lower case letters." the SRT_ADMIN report won't be able to autogenerate the service user password. Turn this rule off and rerun report.

 

Setting up logs and traces for trouble shooting.

  • How to setup Logs and Traces in SOAMANAGER
    • In SOAMANGER open Logs and Traces Tab
    • Open the SOA Runtime Trace Configuration
    • Set Trace level to Payload or Full
  • When trouble shooting check each level of analysis and work back to identify where the issue is.
    • If there is an issue in IE then there will be no trace in SOAMANGER so review fiddler or protocol analysis in browser developer logs. 
    • If there is an issue in SOAMANGER then there will be no authentication trace details in ST01.
    • Check in SE37 and SE80 test that the web service function module is returning results.
      • In SE80 -> Repository Information System
      • Enterprise Services
      • Search on function module.
      • Double Click, then F8 to test.
      • Unless search value is set there will probably be undefined abort error.

 

Check WSDL settings are correct for SSL in SOAMANAGER.

  • Open Service Administration -> Web Service Configuration
  • Search for the webservice: for example Z_FLM_ACL_INVOKE_WS
  • In the Configuration tab for the web service open Edit Binding icon
    • Ensure Transport Security is set to SSL (https) and Save.
    • If you are using SSO you may get additional authorization errors and need SSO settings correct.

 

How to check the server name and port are correct In SOAMANAGER.

  • Open Service Administration -> Web Service Configuration
  • Search for the webservice: for example Z_FLM_ACL_INVOKE_WS
  • In the Configuration tab for the web service Open Binding WSDL Generation icon
  • At the bottom under WSDL Generation select the Execute Icon
    • The URL shown here is to open the WSDL in IE and might look wrong
    • If so once launched in IE adjust the URL so the server:port is correct and you can open the WSDL file.
    • Scroll to the bottom of the WSDL file and you will see the server:port, this must be https not http and you should also see the proxy server name.
    • If it is correct please send me a screen shot like the example below.
    • Here is an example of what you are looking for.
    • If the protocol or server:port are NOT correct then a Web Service Reverse Proxy must be setup.

 

Setting up a Web Service Reverse Proxy

  • In SOAMANAGER open Technical Administration -> SAP Client Settings -> Reverse Proxy Settings
  • Append Row and add the settings (make sure its set to Active) and save.
  • The server:port in the WSDL should now be correct.
  • You may need to restart the SOAMANAGER transaction.
  • If changes don’t appear to be taking effect restart the SOAMANAGER transaction and restart the ICM server in SMICM.

 

Additional Documentation