SAP Knowledge Base Article - Public

2985067 - Integration Center: Queue Name should be double-encoded when using SCP Enterprise Messaging

Symptom

  • When adding the SCP Enterprise Messaging REST API URL in integration center there is an issue adding a queue name that uses the reserved forward slash character 
  • Integration center generates the following error: Http Error response code 400 with response state text: Bad Request

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."

        

Environment

SAP SuccessFactors HXM Suite

Integration Center

Reproducing the Issue

1. Create an outbound REST job in integration center

2. REST API URL: Add the SCP Enterprise Messaging API URL with QueueName: queue/msg:

3. Run the job the following error is generated: Http Error response code 400 with response state text: Bad Request

Cause

  • The forward slash character “/” , is a delimiter for passing URLs for REST API and because the queue name also contained a “/”, this issue emerged

Resolution

  • In cases where SCP Enterprise Messaging “QueueName” contains “/”, the “/” in the QueueName should be double-encoded:

Keywords

Integration center, Bad request, encoding, escape character, REST, API,Http Error response code 400 with response state text: Bad Request , KBA , LOD-SF-INT-INC , Integration Center , LOD-SF-INT , Integrations , Problem

Product

SAP SuccessFactors HCM suite all versions