SAP Knowledge Base Article - Public

3024137 - SAP Successfactors Bizx / unapproved non-API URL(frontend login url) being used to connect to SAP SuccessFactors SFAPI is incorrect

Symptom

When running (i)Standard Successfactors Package Integrations via CPI, PI, Boomi or (ii) Third Party middleware/client or (iii)Direct Manual Query to connect to SAP Successfactors SFAPI/Soap API, The middleware/client receives below error response message along with HTTP error status codes/response codes 404 / 401 / 500

Error In PI (XI/PO) or XPI Trace result.html : 

- Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: Response message contains an errorXIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: An internal error occurred , HTTP Status Code 404
- Invalid SFAPI Session! or INVALID_SESSION , HTTP Status Code 500

Error In CPI/HCI/SCPI : 

- org.apache.cxf.interceptor.Fault: Could not send Message., cause: org.apache.cxf.transport.http.HTTPException: HTTP response '404: Not Found' when communicating with https://<BIZX_ENPDPOINT_URL>sfapi/v1/soap

Error in Boomi : (only when using HTTP Connector and not the Standard Sucessfactors Boomi Connector)

- SEVERE Connector New HTTP Client Connection: http Connector; New HTTP Client Connector Operation Error message received from Http Server, Code 404: Not Found
- SEVERE Connector New HTTP Client Connection: http Connector; New HTTP Client Connector Operation Failed to execute GET operation.
com.boomi.connector.ConnectorException: Error message received from Http Server, Code 404: Not Found

Error in Direct Query/Browser Query/3rd Party:

- {"fault":{"faultstring":"Unable to identify proxy for host: <https://<BIZX_ENPDPOINT_URL_See full list in KBA -2412791> and url: \/sfapi\/v1\/soap","detail":{"errorcode":"messaging.adaptors.http.flow.ApplicationNotFound"}}}

Status Code : 404

Environment

SAP Successfactors HXM Suite

  • Boomi (via HTTP Connector)
  • CPI
  • PI
  • Direct Query from Client

Cause

- Incorrect API endpoint url is used or maintained. For example, https://hcmxx.sapsf.com or (https://hcm17.sapsf.com/sfapi/v1/soap ) which is actually the Bizx/Frontend Login URL, instead of https://apiXX.sapsf.com (e.g. https://api17.sapsf.com/sfapi/v1/soap)

- Invalidated JSESSIONID due to improper routing / handling of the recipient server (Customer Facing Server instead of the API/SOAP Server)

For the full list of Bizx frontend login URL see 2412791 - Success Factors URL's for Production and Test on all Data Centres

Resolution

Maintain correct API endpoint URL on PI / Middleware. See below table or refer to 2215682 - Successfactors API URLs for different Data Centers

- Use correct API URL end point, So the calls will get routed through API Management Server properly so that the server is able to route the API requests and process the SESSIONID properly.

Table 1 : Correct API endpoint wrt SF Bizx URL/SF Frontend Login URL

DatacenterBizx / Frontend Login URL (not meant for SFAPI connection)Correct API Endpoint (use this for SFAPI Connection)
DC57 (old DC2 in Amsterdam, Netherlands)Production: https://performancemanager.successfactors.eu/sfapi/v1/soapProduction System url:    https://api2.successfactors.eu/sfapi/v1/soap
Preview: https://hcm2preview.sapsf.eu/sfapi/v1/soapPreview System url:         https://api2preview.sapsf.eu/sfapi/v1/soap
DC33 (old DC 5/12 in St. Leon-Rot, Germany)Production: https://performancemanager5.successfactors.eu/sfapi/v1/soapProduction System url:   https://api5.successfactors.eu/sfapi/v1/soap OR https://api012.successfactors.eu/sfapi/v1/soap
Preview:  https://hcm12preview.sapsf.eu/sfapi/v1/soapPreview System url:       https://api12preview.sapsf.eu/sfapi/v1/soap
DC68 (old DC4 in Chandler, Arizona, U.S.A.)Production: https://performancemanager4.successfactors.com/sfapi/v1/soapProduction System url:    https://api4.successfactors.com/sfapi/v1/soap
Preview: https://hcm4preview.sapsf.com/sfapi/v1/soapPreview System url:         https://api4preview.sapsf.com/sfapi/v1/soap
DC70 (old DC8 in Ashburn, Virginia, U.S.A.)Production: https://performancemanager8.successfactors.com/sfapi/v1/soapProduction System url:    https://api8.successfactors.com/sfapi/v1/soap
Preview: https://hcm8preview.sapsf.com/sfapi/v1/soapPreview System url:         https://api8preview.sapsf.com/sfapi/v1/soap
DC30 (old DC15 in Shanghai, China)Production: https://performancemanager15.sapsf.cn/sfapi/v1/soapProduction System url:  https://api15.sapsf.cn/sfapi/v1/soap
DC66 (old DC10 in  Sydney, Australia)Production: https://performancemanager10.successfactors.com/sfapi/v1/soapProduction System url:  https://api10.successfactors.com/sfapi/v1/soap
Preview: https://hcm10preview.sapsf.com/sfapi/v1/soapPreview System url:       https://api10preview.sapsf.com/sfapi/v1/soap
DC18 Moscow, RussiaProduction: https://hcm18.sapsf.com/sfapi/v1/soapProduction System url:  https://api18.sapsf.com/sfapi/v1/soap
Preview: https://hcm18preview.sapsf.com/sfapi/v1/soapPreview System url:       https://api18preview.sapsf.com/sfapi/v1/soap
DC16 Magdeburg, GermanyProduction: https://hcm16.sapsf.eu/sfapi/v1/soapProduction System url:  https://api16.sapsf.eu/sfapi/v1/soap
DC60 (old DC17 in Toronto, Canada)Production: https://hcm17.sapsf.com/sfapi/v1/soapProduction System url:   https://api17.sapsf.com/sfapi/v1/soap
Preview:   https://hcm17preview.sapsf.com/sfapi/v1/soapPreview System url:        https://api17preview.sapsf.com/sfapi/v1/soap
DC62 (old DC19 in Sao Paulo, Brazil)Production: https://hcm19.sapsf.com/sfapi/v1/soapProduction System url:  https://api19.sapsf.com/sfapi/v1/soap
Preview:   https://hcm19preview.sapsf.com/sfapi/v1/soapPreview System url:       https://api19preview.sapsf.com/sfapi/v1/soap
DC22  Dubai, UAEProduction: https://hcm22.sapsf.com/sfapi/v1/soapProduction System url:  htps://api22.sapsf.com/sfapi/v1/soap
Preview: https://hcm22preview.sapsf.com/sfapi/v1/soapPreview System url:       https://api22preview.sapsf.com/sfapi/v1/soap
DC23 Riyhad, Saudi ArabiaProduction:  https://hcm23.sapsf.com/sfapi/v1/soapProduction System url:  https://api23.sapsf.com/sfapi/v1/soap
Preview:  https://hcm23preview.sapsf.com/sfapi/v1/soapPreview System url:       https://api23preview.sapsf.com/sfapi/v1/soap
DC41 Production:  https://hcm41.sapsf.com/sfapi/v1/soapProduction System url:  https://api41.sapsf.com/sfapi/v1/soap
Preview:  https://hcm41preview.sapsf.com/sfapi/v1/soapPreview System url:       https://api41preview.sapsf.com/sfapi/v1/soap
DC42 Phoenix, USProduction:  https://hcm42.sapsf.com/sfapi/v1/soapProduction System url:  https://api42.sapsf.com/sfapi/v1/soap
Preview:  https://hcm42preview.sapsf.com/sfapi/v1/soapPreview System url:       https://api42preview.sapsf.com/sfapi/v1/soap
DC52 (old DC44 in Singapore)Production:  https://hcm44.sapsf.com/sfapi/v1/soapProduction System url:  https://api44.sapsf.com/sfapi/v1/soap
Preview:  https://hcm44preview.sapsf.com/sfapi/v1/soapPreview System url:       https://api44preview.sapsf.com/sfapi/v1/soap
DC47Production:  https://hcm47.sapsf.com/sfapi/v1/soapPreview System url:       https://api47preview.sapsf.com/sfapi/v1/soap
Preview:  https://hcm47preview.sapsf.com/sfapi/v1/soapProduction System url:  https://api47.sapsf.com/sfapi/v1/soap

See Also

Keywords

AddOn Integration, RH_SFI_SYNCHRONIZE_EMPL_DATA. Http Server, Code 404: Not Found, INVALID_SESSION, Invalid SFAPI Session! HTTP 500, HTTP 401 invalid URL , KBA , LOD-SF-INT-API , API & Adhoc API Framework , LOD-SF-INT , Integrations , LOD-SF-INT-ODATA , OData API Framework , Problem

Product

SAP SuccessFactors HCM Core all versions ; SAP SuccessFactors HCM suite all versions