cancel
Showing results for 
Search instead for 
Did you mean: 

error namespace adapter receiver uppercase

0 Kudos

We have PI 7.0

Since our system sap pi we make a request of a synchronous web service
that use ws security, signing our certificate, and sap is in charge of
making the envelope. Since the external system to ours we report the
following error.

The error occurs when parsing the request with the libxml2 library,
because the definition of Namespace.
The request two attributes one uppercase (SOAP) and one lowercase
(soap) with the same definition is used and this would violate the
restriction that two attributes have the same expanded name.

We would need to modify the request for the SOAP namespace is unified
in the document. All uppercase or all lowercase, with a single
definition.

Example:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
     <SOAP:Header>
          <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
          xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"xmlns:mustUnderstand="1">

First line second SOAP is uppercase.... Fourth line first soap is in lowercase.

We think the problems have come when we've uploaded the patch level of
the support stack or our system... stack level 28 to level 30. Both
stack abap and java stack .

In addition java stack got higher levels
sap.com/CORE-TOOLS 7.00.30.6
sap.com/SAP-JEE 7.00.30.2
sap.com/SAP-JEECOR 7.00.30.5
sap.com/SAP-XIAFC 7.00.30.3
sap.com/SAP_XIAF 7.00.30.1
sap.com/SAP_XITOOL 7.00.30.1

Kernel also passed 7200 , 401 , 0, 0 to Kernel 7200, 600 , 22, 39073
saphttp except that an additional level rose to 7200, 610 , 22, 43246
for a problem with calls icm .

Accepted Solutions (0)

Answers (2)

Answers (2)

iaki_vila
Active Contributor
0 Kudos

Hi Fernando,

If you can't use that module bean you will need to change the namespace manually with a XSL. You will need to mark Do Not Use SOAP Envelope in your SOAP adapter then you can get all the SOAP envelope in the mapping time. If you have an example with the source message and the target/desired message we can help you with the XSL.

Regards.

0 Kudos

There is no posibilty to make SOAP envelope because we can't make the develope ourselves.

We have sign digitally and into SOAP envelope have to go the sign...

The problem is to use ws_security...


iaki_vila
Active Contributor
0 Kudos

Hi Fernando,

You can work with wsse security and the SOAP AXIS adapter like this Abidemi Olatunbosun's blog point out

It is important to know that the AXIS libraries are not installed with the PI installation and you will need to install them, you can check how to install if you search in the SAP Notes. I have worked with PI 7.0 and the AXIS adapter, it's a bit weird the libraries installation but you have enough information in the SAP Notes AXIS FAQ.

Hope this helps.

Regards,

sendhil_kumar
Active Participant
0 Kudos

Hi Fernando,

U can handle the namespaces via modules. Please refer to this link.

Also in the end there are few reference links in the same blog.

Hope it will help you.

-

Sndhl

0 Kudos

I have PI 7.0 version of PI and I think this applies from 7.1...