SOAP Authentication with URL Parameters

SOAP Authentication with URL Parameters

In one of my latest project we set up a SOAP communication with a partner. Unfortunately, the partner was not able to include basic authentication header when sending a SOAP message. As we did not want to expose our SOAP Sender communication channel to the web, but could not wait for the partner to find a way to use basic authentication, we looked for another solution.

Message in status Message recorded (commit missing)

Message in status Message recorded (commit missing)

After creating a test message with the “Test service” tool in transaction “SPROXY “to test an asynchronous interface out of your ERP system, the transaction “SXMB_MONI” or “SXI_MONITOR” has a white flag on your message and shows the following error:

Message in status Message recorded (commit missing)

Peer certificate rejected by ChainVerifier

Peer certificate rejected by ChainVerifier

In a scenario with a SSL encrypted (HTTPS) SOAP target URL in SOAP receiver channel, the following error message is shown in message log:

SOAP: Call failed: java.io.IOException: Failed to get the input stream from socket: iaik.security.ssl.SSLCertificateException: Peer certificate rejected by ChainVerifier

Find complete BPMN error traces

Find complete BPMN error traces

During the development of a BPMN on SAP Process Orchestration you will probably arrive at a point where your BPMN does not work as expected. One way to find the issue is to check the traces in the Log Viewer, to find out more about the error.

“Start Process” in Process Repository is disabled

“Start Process” in Process Repository is disabled

If you develop a BPMN, you probably have to manually trigger the process multiple times to check that everything works as expected. One way to trigger a BPMN is the usage of the “Start Process” function in the Process Repository.
But, the “Start Process…” button in the Process Repository is disabled.

Error during BPMN deployment

Error during BPMN deployment

When redeploying a BPMN with SAP NetWeaver Developer Studio, the following error message was shown in the deployment log:

Description: Description: 1. Adapter com.sap.glx.adapter.internal.Transformer has refused deploy unit e5853c8198e860817e261ae672f4bfc4 using configuration mode DEPLOYMENT
-> Transformer could not get lock within 60 seconds
IDOC_ERROR_PARSE_FAILURE: Namespace in IDOCs

IDOC_ERROR_PARSE_FAILURE: Namespace in IDOCs

In a SOAP to IDOC scenario with a XSLT mapping, the receiving IDOC Communication Channel produced the following error message:

Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: Invalid XML 1.0 character encountered within IDoc-XML for type :
state=EXPECTING_IMMEDIATE_TAG_END, charPosition=64, lineNumber=1, columnNumber=65, invalidChar=U+0078,
sourceSnippet=...UTF-8" standalone="no"?>