SOAP prefixes required

Hi Experts,
I have an SOAP inbound interface comming to XI.
The SOAP envelop has not prefixes defined.
This message was genareted by Microsoft Bizztalk
The message is generating error in mapping.
But, when I run the interface with the same WSDL but using XMLSpy, it's working fine.
The question is, SOAP prefixes are allways required ?
The message genareted by BizzTalk shoud be wrong or XI mapping is wrong ?
Follow bellow the messages example:
MESSAGE FROM BIZZTALK - ERROR !!!
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
<MTP_Qualidade_Celulose_Seca
MESSAGE FROM XMLSPY - WORKING FINE !!!
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
<m:MTP_Qualidade_Celulose_Seca
Cheers !
Regis Ferrato

are you able to see the message in XI. If yes can you post the error message from log.

Similar Messages

Prefix required for namespace error

When I try to import an XML schema into the TopLink workbench, I'm getting the following error:
0800 - Prefix required for namespace "http://www.ACORD.org/standards/PC_Surety/ACORD1.6.1/xml/".
Has anyone seen this before? Any help would be appreciated!
Thanks,
Greg Plummer

Hi Blaise,
Thanks for the reply. The schema I was trying to import was huge and it has come to my attnetion that it has been broken down into a set of more managable schemas. Now I'm getting a different error trying to import those smaller schemas, as follows:
(Error) Can not build schema 'http://www.w3.org/XML/1998/namespace' located at 'file:/C:/Temp/Pliq XML Schemas/FromJim/xml-ns.xsd'
I copied the xml-ns.xsd file to the directory that contains the schema I'm trying to import, but that made no difference. I also tried changing the schema to use an absolute path to xml-ns.xsd, but no luck with that either. Any thoughts???
Thanks, Greg

XML Namespace Prefix required

Hello,
our partner uses Biztalk to receive our SOAP calls. They tell us that each attribute and element needs to have the namespace prefix otherwise Biztalk cannot read it.
We are sending:
SAP XI Output
<?xml version="1.0" encoding="utf-8" ?>
<ns11:Receive_SAP xmlns:ns11="http://zzz.com/it/mmpur/sem/xi">
<part>
   <xform id="SWI:PLG:Order Header - SAP">
    <model>A</model>
   </xform>
</part>
</ns11:Receive_SAP>
They want:
Biztalk Requirement:
<?xml version="1.0" encoding="utf-8" ?>
<ns11:Receive_SAP xmlns:ns11="http://zzz.com/it/mmpur/sem/xi">
<ns11:part>
   <ns11:xform id="SWI:PLG:Order Header - SAP">
    <ns11:model>A</ns11:model>
   </ns11:xform>
</ns11:part>
</ns11:Receive_SAP>
Can that be done with the XI 3.0 Graphical mapping or do I have to use JAVA Mapping or XSLT?
Did anyone come accros this before with Biztalk Server and it there an option to avoid it on the Biztalk Server side?
Thanks
Stefan

Hi Stefan,
Where did you obtain the schema (XSD) from?
Most likely, the elements you are using are local elements and do not belong to the target namespace, but to an unnamed global namespace. This is a typical characteristic of schema's defined by SAP.
The short answer/solution is probably putting elementFormDefault="true" in the header of your target schema. That should do the trick.
Kind regards, Guy Crets

SOAP Envelope Requirements

Hi,
i have a question concerning SOAP envelope.
(We run on XI30 SP19.)
A message sent to SOAP adapter with
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-SOAP-Envelope">
runs on error:
Caused by: org.apache.xmlbeans.XmlException: error: The document is not a Envelope@http://www.w3.org/2003/05/soap-SOAP-Envelope: document element namespace mismatch expected "http://www.w3.org/2003/05/soap-SOAP-Envelope" got http://schemas.xmlsoap.org/soap/envelope/
If i use
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
it works.
Can anyone point me to a ressource which describes the XI requirements to the SOAP envelope?
What is/isnt allowed for XI in special?
Thank you very much in advance.
Michael
Edited by: Michael Höcht on Oct 28, 2008 2:56 PM

Hmm, based on error it looks like service provider expecting some security headers. Are you able to test from other utility soapUI or browser?
Regards,
Chintan

WIP numbering prefix required while using ASCP

Hi All,
We have 2 organizations and each organization needs different numbering prefix so we have defined 2 different responsibility for Work in process and assigned prefix for WIP numbering prefix profile for these 2 responsibilities at responsibility levels and controlled org access using organization acess.
But when we run ASCP this numbering format is not used and discrete jobs are getting created with some default numbering when we release the jobs from ASCP.
Can ayone please let me know the setup required for having defined prefix for discrete job numbering with ASCP.
Thanks
Vasudha.
Thanks
Vasudha

which responsibility is launching the ASCP process? Is your profile working for one of the orgs?

SOAP URL requires authentication even after enclosing user and pw

Hi,
Currently i have generated a SOAP url and had provided it to the source system owners. All they say is that when they enter the URL in the Internet Explorer, it asked for the username and password again even after adding it to the URL. Also when they integrated it to their application, it throwed an error "Transport error: 401 Error: Unauthorized"
The URL i shared is in the below format,
https://<HostName>:<Port>/XISOAPAdapter/MessageServlet?channel=:<BusinessSystem>:<CommunicationChannel>&nosoap=true&sap-user=<username>&sap-password=<password>
Please help me if i am missing something in this.

Hi,
In fact, what Mark mentioned is true. Let me throw some more light to it. You can only include the username and password in the SOAP call to PI if you post the SOAP message directly to the Integration Engine, without using sender SOAP adapter. This approach was described by Stefan Grube in his blog here:
Using the SOAP inbound channel of the Integration Engine
As a result, you would have to use a different URL to post your calls:
http://hostname:port/sap/xi/engine?type=entry&version=3.0&Sender.Service=<service>&Interface=<namespace>^<service_interface>&sap-user=<>user&sap-password=<password>
Alternatively (and this is how I would personally do it), you can include the username and password in the HTTP header attributes, as I described here:
A closer look at SOAP Sender authentication
Thanks to that, you do use the sender SOAP adapter, and achieve some more security thanks to not providing the user name and password in the URL.
Hope this helps,
Greg

Prefix namespace OSB, SOAP response

Hi!
I'm doing a web service in OSB 11g.
An application is parsing the SOAP response after calling my WS, and they are expecting that my SOAP response have hardcode prefixes.
My SOAP response is like this:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
XXXX
</soapenv:Body>
</soapenv:Envelope>
They want another prefix (soap instead of env or other prefix). Something like this:
<soap:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
XXXX
</soap:Body>
</soap:Envelope>
Do you know how can I fix it? I know this is a problem of the application who is calling my WS, but if I can do this, I can solve them a problem.
Thanks!!

mybe the valid one is something like this,...please refer to the namespace,it sould be "xmlns:soap" than "xmlns:env" because you trying to use soap prefix .
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
XXXX
</soap:Body>
</soap:Envelope>
you can change the soap message in many way...for example you can use message processing actions such as 'replace action':
you can replace xpath . on variable $body with expression fn-bea:inlinedXML('<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
</soap:Body>
</soap:Envelope>')
hope it will helping you

Compiling PHP with SOAP/Iconv/OpenSSL support

Hi,
I'm not sure if this is the best place for this but the other topics seem even less related.
I'm trying to compile PHP with SOAP and SSL on a Mac for use with Salesforce.com (it works without any issues on Gentoo and RedHat). Anytime I try to connect I get an invalid SOAP header error. It seems to be happening because the Salesforce SOAP server requires SSL connections and I don't have SSL enabled, but it's hard to backtrace. Regardless, I can't get SSL or iconv support working.
I've installed OpenSSL both from Macports and from source using the default ./config options, neither method worked. It may be related to some issues I'm having getting iconv working as well (which I also can't seem to get right, it's installed via Macports).
Here's my PHP configure, if anyone can let me in on what I'm doing wrong that would be great!!! Thanks in advance!
root# MACOSXDEPLOYMENTTARGET=10.5 \
CFLAGS="-arch ppc -arch ppc64 -arch i386 -arch x86_64 -g -Os -pipe -no-cpp-precomp" \
CCFLAGS="-arch ppc -arch ppc64 -arch i386 -arch x86_64 -g -Os -pipe" \
CXXFLAGS="-arch ppc -arch ppc64 -arch i386 -arch x86_64 -g -Os -pipe" \
LDFLAGS="-arch ppc -arch ppc64 -arch i386 -arch x86_64 -bindatload"
root# ./configure \
--prefix=/usr \
--mandir=/usr/share/man \
--infodir=/usr/share/info \
--with-apxs2=/usr/sbin/apxs \
--with-config-file-path=/etc \
--sysconfdir=/private/etc \
--enable-cli \
--with-curl=/opt/local \
--enable-ftp \
--enable-mbstring \
--enable-mbregex \
--enable-sockets \
--with-ldap=/usr \
--with-kerberos=/usr \
--with-mime-magic=/etc/apache2/magic \
--with-zlib-dir=/usr \
--with-xmlrpc \
--with-xsl=/usr \
--with-iconv=shared,/opt/local \
--with-openssl=shared,/opt/local \
--with-gd \
--with-png-dir=/usr/X11R6 \
--with-xpm-dir=/usr/X11R6 \
--with-jpeg-dir=/opt/local \
--enable-exif \
--with-freetype-dir=/opt/local \
--with-t1lib=/opt/local \
--enable-pdo \
--with-pdo-mysql \
--with-mysql-sock=/var/mysql \
--with-mysqli=/usr/bin/mysql_config \
--with-mysql=/usr/local/mysql \
--with-iodbc=/usr \
--with-curl \
--with-config-file-path=/etc \
--sysconfdir=/private/etc \
--enable-soap
Message was edited by: mkenney - bad grammar

mkenney wrote:
Hi,
I'm not sure if this is the best place for this but the other topics seem even less related.
Welcome to Apple Discussions:
Use our Unix forum here:
http://discussions.apple.com/forum.jspa?forumID=735
(yes, it's a tad hidden )
Message was edited by: nerowolfe

More information regarding 'Don't Use SOAP Envelope' in SOAP sender Adapter

Hi,
maybe this document could help you:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d23cbe11-0d01-0010-5287-873a22024f79
It says about selecting Do Not Use SOAP Envelope.
> In this case the sender SOAP adapter requires an additional
parameter nosoap=true in the URL.
Regards
Patrick

Answered

Mapping SOAP Fault during synchronous SOAP call

We are building a mediated service scenario where PI is brokering a synchronous SOAP call, without changing any of the information being sent or received (the mappings use the same source and target data types with no transformations). When the service is successfully executed everything works as expected, but when the target service returns a SOAP fault, PI appears to be wrapping the fault in a separate fault before returning it to the client. Why is this happening? Is there a way to simply return the SOAP fault to the client without adding the additional wrapper?
Here is the fault received from the target service when called directly:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <soapenv:Header/>
   <soapenv:Body>
      <soapenv:Fault>
         <faultcode>Missing_Required_Data</faultcode>
         <faultstring>**Required data is invalid : Dealer Country**</faultstring>
      </soapenv:Fault>
   </soapenv:Body>
</soapenv:Envelope>
Here is the fault received from the mediated PI service call:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP:Body>
      <SOAP:Fault>
         <faultcode>SOAP:Server</faultcode>
         <faultstring>Server Error</faultstring>
         <detail>
            <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
               <context>XIAdapter</context>
               <code>ADAPTER.JAVA_EXCEPTION</code>
               <text>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIAdapterFramework:GENERAL:com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: **Required data is invalid : Dealer Country**
     at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1161)
     at sun.reflect.GeneratedMethodAccessor948.invoke(Unknown Source)
            </s:SystemError>
         </detail>
      </SOAP:Fault>
   </SOAP:Body>
</SOAP:Envelope>
Why aren't they the same?

are diferents coz the first is a fault message and the second is a exception message.
to send back the fault message define a fault message for both structure and map them in a new message mapping. later in the operation mapping or interface mapping (depends of the pi version) under fault message or fault mappinng (i dont remember) tab assisg the fault message mapping.
thats all you need.

Net.SOAP.request error

I'm trying to invoke a web service after pressing a button in a PDF file.
Unfortunately I get the following error:
NotAllowedError: Security settings prevent access to this property or method.
Net.SOAP.request:22:Field fire_action_btn:Mouse Up
Adobe Acrobat SDK documentation at page 664 says that request method of Net.SOAP object requires forms rights.
The document has the following security permissions:
                                  Printing: Allowed
                Document Assembly: Not Allowed
                  Content Copying: Allowed
Content Copying for Accessibility: Allowed
                  Page Extraction: Allowed
                       Commenting: Not Allowed
           Filling of Form Fields: Allowed
                          Signing: Not Allowed
       Creation of Template Pages: Not Allowed
I've thought that "Filling of form fields" is the right permission required by this method, but clearly I was wrong. Which is the permission that the document should have in order to invoke Net.SOAP.request? How can I set it?
I've done the tests using Acrobat Reader 9.4.2
Thanks and regards,
Alessandro

With the Adobe LiveCycle Reader Extensions ES2 module you can add the form rights:
http://www.adobe.com/products/livecycle/readerextensions/

SOAP Envelope element descriptions

Does anybody have a link to a document that explains the semantic meaning of all of the elements that exist within the PI message SOAP Header?
BR,
Tony.
Edited by: Anthony Bateman on Apr 14, 2008 12:42 PM

Hi ,
This is from some document ...check it.
<i>The SOAP adapter creates the SOAP envelope. You cannot influence this procedure. If
you need to apply special tags inside the SOAP header, the only option is to create the
whole SOAP envelope during mapping, and in the case of a synchronous call, to remove
the SOAP envelope in the mapping.
In the SOAP adapter channel, select Do Not Use SOAP Envelope.
By using this parameter, you can use the SOAP adapter to send or receive non-
SOAP messages. In this case the sender SOAP adapter requires an additional
parameter nosoap=true in the URL. For example:
http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet?
channel=<party>:<service>:<channel>&nosoap=true</i>
Sekhar

[NOTE] Adding xsi type to SOAP messages

Here is a quick 2.0.10 note.
Some older SOAP stack require xsi type information embedded in the SOAP message to unmarshall the XML message into the appropriate object representation.
Most customers do no want the overhead of xsi type definition into the SOAP message given that most modern SOAP stack perform the unmarshalling based on the WSDL/XML Schema.
To address both requirements, we now by default do not add the xsi:type information to the SOAP traffic that the BPEL PM server generates.
But we have added a new configuration property to the partnerLinkBinding element of the bpel.xml deployment descriptor so that you can ask the BPEL PM server to selectively decorate the SOAP messages targeted at a specific partnerLink. Here is how this looks like:
<partnerLinkBinding name="XXXXX">
<property name="sendXSIType">true</property>
</partnerLinkBinding>
Note: the challenge here is that if you invoke a service that requires XSI type information and you forget to set that flag in the deployment descriptor you will get a BindingFault with no detail :-( We are very aware of this limitation and are working very diligently towards addressing this problem with a much nicer error message in the 2.1 (aka end of September release).
Edwin

Hi,
thanks for the quick answers.
The Werbservice is MS CRM Dynamics. The "GUI" is still working. so the webservice is active and alive.
I want to query the CRM, so i sent a fetch statement to file, which is being picked up and sent as SOAP message to the webservice.
With point 6 in the mentioned blog the error message in the rwb is gone now, but the message in SXMB_MONI is flagged red and i'm struggling to finfd out what the next error is....may be someone can point out where to look at

SOAP Adapter Startup

Hi All,
I have observed one thing that when we restart J2ee engine, all file, jdbc and jms adapters auto start however SOAP adapter needs a manual start in RWB.
Could someone put some light on this, and is there a way that the adapter auto starts like others.
Regards,
XIer

Hi Xier,
There very rare references avaialble about this problem. Even I wil say this not the exact problem as the adapters like SOAP , Mail required 1st message to process. Once you had message processing the Adapter status get activated to either green, red based on the successful processing of that message. Unless the 1st message is activated you will find the status with gray color. I don't think you will require to do it manually each time. Have you tried to process a message even if the SOAP adapter status is gray after restarting the J2EE Engine. Please confirm if you are getting same results for Mail adapter also.
Let me know if still you have any doubts about it.
Thanks
Swarup

How to resolve error "No SOAP Envelope but 1 {} PARAMETERS"

Hi,
I have configured an interface where the sender (SAP system) sends out a message via proxy on the Local Integration Engine, which is after XI processing supposed to be posted via HTTP (using the SOAP Adapter).
The message is processed correctly by XI, but fails to pass the SOAP Comm Channel. The error message in the Communication Channel Monitoring reads:
SOAP: call failed: java.io.IOException:No SOAP Envelope but 1 {} PARAMETERS; HTTP 200 OK
Can anyone help me understand what this means and how I can resolve this? Thanks!

Dear Johannes,
Is the SOAP call taking place synchronously ? It looks like at the end of your SOAP channel, system is not responding as expected by XI (you seem to receive the regular HTTP 200 OK code, but it does not match SOAP protocol requirements) ...
I've had such issues when web services were down due to web server issue (in this case, you just get, for instance, HTTP 500 response body, which not really SOAP compliant)
Rgds
Chris

SOAP prefixes required

Similar Messages

Maybe you are looking for