SOAP Header Tag

Hi All,
Is there any way out to eliminate the tag <SOAP:Header/> while sending the message to a legacy system using a receiver SOAP adapter.
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelop
e/'>
<SOAP:Header/>
<SOAP:Body>
Need to eliminate the SOAP:Header tag while sending...Is this possible in any way..
Thanks
Amit

Hi All
We have a empty SOAP Header tag which needs to be suppressed so that the target system receives the data...
Any way we can achieve this without going in for adapter module..
I have tried with Do not use SOAP envelope, Encoded headers...All options dont yield the desired result..
It is an empty <SOAP Header/> tag which we want to eliminate..

Similar Messages

Read SOAP Header tag

Hi,
I'm using with great success JDEV9.0.3prod for create and deploy web services. I maked all with wizard.
All work, but now I would read and manage SOAP header tag.
This is the question: how is possible to read the header tag of the SOAP Message, using jdev wizard?
Any help would be very appreciated.
Thank in advanced.
massimo

Unfortunately, the JDev wizards don't help access the header characteristics, yet.
It is further complicated in that the Oracle9iAS Web Services implementation right now does not have a good way to get the header information, however, the Apache SOAP implementation that also ships with Oracle9iAS does.
As we go forward to JAX-RPC the API's for the header will be exposed. If absolutely necessary now, you can use the Apache SOAP implementation (we are actually at 2.3.1) so the doc at xml.apache.org on Apache SOAP and pointers to headers should give you an idea of how to approach it.
Sorry I don't have any code samples to point you at.
Mike.

XI APIs to access SOAP Header Tags

Hi Forum,
The way we use DynamicConfiguration class from com.sap.aii.mapping.api.* API, to access file names etc,
is there classes available for accessing other tags in the SOAP Header, for example ReliableMessaging, PerformanceHeader, etc

U can look into Adapter Specific attributes for soap adapter also. If you want to transfer header fields, set the relevant indicator for Variable Header in the SOAP communication channel. This is generic for header fields. Not sure about the particual fields
Regards,
Prateek

Remove Soap Header while calling a WS from BPEL 11g

Hi
My requirement is to remove the entire SOAP Header tag in the invoke activity. How this can be achieved? Please help
thanks
Sesha

Note sure if this possible.. but just wondering if you can try using <bpelx:remove> extention to delete the soap header variables..
Other viable option is to write SOAP Message handlers on your outbound webservices...

Remove XI-part of SOAP Header in Axis Adapter

Hi folks!
We are running a PI 7.11 and use the SOAP Axis Sender Adapter in a synchronous SOAP Web Service scenario. Our challenge is that in our response we definitely need a SOAP Header tag, but it should be empty like this <soapenv:Header/> or this <soapenv:Header></soapenv:Header>
We tried to achieve this with the Axis Handler com.sap.aii.axis.soap.HeaderRemovalHandler. But regardless of the parameters we provide to this handler it always removes the complete SOAP Header. On sample is to remove the PI-specific Main header tag from SOAP Header:
name.1=Main
namespace.1=http://sap.com/xi/XI/Message/30
We also tried it only with namespace. But always the same sh... happens: The SOAP Header is removed completely.
Any ideas?
Thanx very much in advance!
Regards,
Volker

Hi Stefan!
Thanx for your reply. We found that Axis handler mentionedby me in SAP Note 1039369 "FAQ XI Axis Adapter" .
But please tell me how to parameterize the java:com.sap.aii.axis.xi.XI30InboundHandler to ensure that the XI part of SOAP header is removed, but not the complete SOAP header.
Thanx in advance!
Regards,
Volker

Query reg adding custom tags in SOAP Header - AXIS Receiver Adapter

Hi All,
I need to send custom tags as mentioned below to my traget webservice application. I think I can do this with Receiver AXIS adapter but not sure how it can be done. Can any of you suggest?
                                              <WSContext>
               <FromAppId>ABC</FromAppId>
               <ToAppId>XYZ</ToAppId>
          </WSContext>
Thanks,

If you want to add custom tags in the soap header, one possible solution is use XSLT mapping or Java mapping to create header first then do message mapping for mapping the payload structure between your source and target as usual.
So in operation mapping you sequence mapping like this... first XSLT mapping for custom tags for the SOAP Header followed by payload mapping.
Hope that helps.
Search SDN for XSLT Mapping for soap header. Already we have handled these issues.

header tag in soap

i just read through Axis user doc, but all sample app it mention doesn't show how to use the <HEADER> tag inside soap request / response.
1 -- is <HEADER> tag not much a use when doing 1 - 1 host to host request /response?
2 -- <HEADER> is only useful when soap massage need to pass multiple endpoints / hosts ?
3 -- Why most of the web services at www.xmethods.net don't use <HEADER> tag on request / response xml?
4 -- Is that in most cases, BODY tag in soap is enough? no HEADER needed?
5 -- Hosts in between web service client + provider process <HEADER> elements but not the content of BODY element? and the Ultimate SOAP receiver will process the BODY elements?

Note sure if this possible.. but just wondering if you can try using <bpelx:remove> extention to delete the soap header variables..
Other viable option is to write SOAP Message handlers on your outbound webservices...

How do I access the DCJMS* variables in my response SOAP:Header ?

Hi all,
I have set up a sync / async Integration Process in XI
This is initiated by a SAP R/3 transaction that calls a synchronous function to enter XI
Once in the Bridge, a JMS receiver adapter sends out an asynchronous request message from XI to MQ
A correlation allows the JMS sender adapter to return an asynchronous response message from MQ to XI back into my the Integration Process
I have set up the JMS sender adapter configuration to return the DC (dynamic configuration) variables in the <SOAP:Header> of the XI response message along with the payload
You can see that the DCJMS* variables are returned below
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
+ <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
+ <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
+ <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
+ <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
+ <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:DynamicConfiguration xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Record namespace="http://sap.com/xi/XI/System/JMS" name="DCJMSCorreleationID">40D982A0-B19D-11DB-9508-0002A5D5916B</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/JMS" name="DCJMSTimestamp">1170297456940</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/JMS" name="DCJMSMessageID">ID:414d5120514d4430312020202020202045c12b962001dd02</SAP:Record>
</SAP:DynamicConfiguration>
- <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:TraceLevel>Information
<b>Question</b>
I want to access the DCJMS* variables but am not sure how to go about it as the
variables exist in the <SOAP:Header>?
I followed the SAP documentation to access adapter-specific attributes (refer to link http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm )
I have used the following code to create a user-defined function for the accessing adapter specific attributes (similar to the link)
public String Get_Msgid(Container container){
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get
(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create
("http://sap.com/xi/XI/System/JMS","DCJMSMessageID");
String jmsMsgID = conf.get(key);
return jmsMsgID;
<b>Question</b>
Do I use message mapping to extract the DCJMS* variables?
<b>Question</b>
If so then which message is used for the source message so that I can access the <SOAP:Header>? Eg do I use the response message type or is there a trick to accessing the SOAP:Header?
<b>Question</b>
Do I use the user-defined function (like above)?
I performed the following steps
     Opened the message mapping in edit mode
     Created the user-defined function using the graphical editor
     Saved the message mapping
     I have not connected the user-defined function to any of the xml tags in either the source or target messages
When I go to test the message mapping I am getting the following error
Compilation process error : CreateProcess: null\bin\javac -J-Xmx256m @E:/usr/sap/XID/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Mapd79a7bf0b65611dbaf390002a5d5916b/O1170817003886.txt @E:/usr/sap/XID/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Mapd79a7bf0b65611dbaf390002a5d5916b/S1170817003886.txt error=2
STACKTRACE:
com.sap.aii.ib.core.mapping.exec.ExecuteException: Compilation process error : CreateProcess: null\bin\javac -J-Xmx256m @E:/usr/sap/XID/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Mapd79a7bf0b65611dbaf390002a5d5916b/O1170817003886.txt @E:/usr/sap/XID/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Mapd79a7bf0b65611dbaf390002a5d5916b/S1170817003886.txt error=2
at com.sap.aii.ib.server.mapping.exec.ServiceUtil.compileSourceCode(ServiceUtil.java:207)
at com.sap.aii.ib.server.mapping.exec.ServiceUtil.compile(ServiceUtil.java:156)
at com.sap.aii.ibrep.server.mapping.ServerMapService.compileSourceCode(ServerMapService.java:361)
at com.sap.aii.ibrep.server.mapping.ServerMapService.compileSourceCodeWithoutAndWithArchives(ServerMapService.java:301)
at com.sap.aii.ibrep.server.mapping.ServerMapService.execute(ServerMapService.java:153)
at com.sap.aii.ibrep.sbeans.mapping.MapServiceBean.execute(MapServiceBean.java:52)
at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0.execute(MapServiceRemoteObjectImpl0.java:259)
at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0p4_Skel.dispatch(MapServiceRemoteObjectImpl0p4_Skel.java:146)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
A thread in the SDN (Error while Activating Message Mapping, Posted: Jan 9, 2007 3:32 PM) suggests checking the java path on the XI machine
This is JAVA_HOME=C:\j2sdk1.4.2_08 and seems ok
<b>Question</b>
Do you know why I would get the compilation error?
Any assistance would be appreciated
Regards,
Mike

Jin,
My compilation issue has gone via a SAP recommendation to specify the JDK home directory in the instance profile
Back to the mapping - I can now run my scenario
<b>Source message</b>
The response message has the following <SOAP:Header> from which I want to extract the DCJMSCorreleationID (note that it's misspelt)
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:DynamicConfiguration xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Record namespace="http://sap.com/xi/XI/System/JMS" name="DCJMSCorreleationID">40D982A0-B19D-11DB-9508-0002A5D5916B</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/JMS" name="DCJMSTimestamp">1170297456940</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/JMS" name="DCJMSMessageID">ID:414d5120514d4430312020202020202045c12b962001dd02</SAP:Record>
</SAP:DynamicConfiguration>
<b>Grahpical mapping</b>
LHS - Response message with occurrance 0..1 so it is not connected to my UDF
UDF Get_Corrid with no inputs
RHS - The UDF output is connected to the Acknowledgement msg tag <ACK>
<b>UDF</b>
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get
(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create
("http://sap.com/xi/XI/System/JMS","DCJMSCorreleationID");
String Corrid = conf.get(key);
return Corrid;
<b>Target message</b>
The idea is to copy the correlation id of the response message into the acknowledgement message. But as you can see the result is NULL
<?xml version="1.0" encoding="utf-8" ?>
- <ns2:AWB0020_MARKET_DATA_RESPONSE_ACK xmlns:ns2="http://awb.com.au/mq/tx/MarketData">
<ACK>null</ACK>
</ns2:AWB0020_MARKET_DATA_RESPONSE_ACK>
Please advise
Thanks Mike

Calling A Secured webservice using Username and password in the Soap header

I want to call a secured webservice.
The Username and password should be sent with the payload in the SOAP Header
as
<wsse:Security S:mustunderstand="0" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:UsernameToken wsu:Id="SecurityToken-XXXXXXXXXXXXXXXXXXXXXXXXX" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<wsse:Username>uname</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">pwd</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
Can you please send me the steps?
I tried with giving the username and password under Service Account.
I tried to create a wspolicy under business service. But nothing works...
Please help me at the earliest.
Also please give me steps in sequence.

Now i made sure that the endpoint is available!
Now am getting this error:
<soapenv:Fault>
<faultcode>soapenv:Server</faultcode>
<faultstring>BEA-380002: localhost1</faultstring>
<detail>
<con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>BEA-380002</con:errorCode>
<con:reason>localhost1</con:reason>
<con:location>
<con:node>RouteNode1</con:node>
<con:path>request-pipeline</con:path>
</con:location>
</con:fault>
</detail>
</soapenv:Fault>
Also in the invocation trace i can observe the following things:
Under Invocation Trace:-
========================
     Receiving request =====> Initial Message context
     ===============================================
     under added header:-
     ==================
     <soap:Header xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
     </soap:Header>
     under RouteNode1
================
     Route to "TargetMyService_BS"
$header (request):-
<soap:Header xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
</soap:Header>
Under Message Context changes:-
*===============================*
I can find this element also:-
con:security>
*<con:doOutboundWss>false</con:doOutboundWss>*
*</con:security>*
eventhough we enabled ws security, how the above tag can be false?
I think its getting failed to populate the header with the required login credentials.
The other doubt i have is:-
=================
I have chosen the service account type is static...is this right?

Add field inside SOAP header PI 7.1

Hello,
by proyect needs we need to add into SOAP header some dynamic information
(Web Services calls to target systems from PI 7.1). This information is
needed in target application for validating permissions of the web
services calls.
The tags are
<soap:Header>
<CarHeader xmlns="http://xxxxx.xxxxxxxx.xxx.org/">
<TicketCar>xxxxxxxxxxxxxxxxxxxxxx......</TicketCar>
</CarHeader>
</soap:Header>
TicketCar's value (xxxxxx....) will be different in each call.
We think that this is not possible with standar or Axis PI SOAP receiverchannel and a solution could be making a Abap mapping for composing the
SOAP call with this tags and values, and in the comunication channel
check the parameter "Do not use SOAP Envelope".
It's rigth? Is there any other solution for doing it?
An example of a call will be:
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Header>
<CarHeader xmlns="http://xxxxx.xxxxxxxx.xxx.org/">
<TicketCar>C4A8A61D86C56DC27......</TicketCar>
</CarHeader>
</soap:Header>
<soap:Body>
<E000xx xmlns="http://xxxxx.xxxxxxxx.xxx.org/">
<_request>
<NumeroExpedienteAdministrativo>xxx</NumeroExpedienteAdministrativo>
<CodigoDocumentoInterno>xxx</CodigoDocumentoInterno>
<Status>xx</Status>
<NumeroExpedienteContable>xxx</NumeroExpedienteContable>
</_request>
</E000xx>
</soap:Body>
</soap:Envelope>
Any idea will be welcome
Edited by: Ramon Coma Alcantara on Feb 2, 2010 4:15 PM

Hi Ramon,
The axis adapter comes with a convenient header insertion handler where you can insert an arbitrary header using a template.
For example, you can define a template like this in the module configuration.
<x:header xmlns:x="urn:x"><me>i say </me><you>you say </you></x:header>
where , , ... are variable place holders.
and you associate these variables with any context value available in the message.
For example, when you pass Hello and Bye for these variables, you soap message will get the header:
<x:header xmlns:x="urn:x"><me>i say Hello</me><you>you say Bye</you></x:header>
You can look at the examples described in Note 1039369 Axis Adapter FAQ.
As I said before, the mileage you can go with the do-not-use-envelope mode is very limited. But if you are happy with it, why not.
Best regards, Yza

HTTP response code 500 : Error during parsing of SOAP header

Hi Experts,
I have a MAIL to IDOC scenario. An external third party emails invoices to our inbox - which we pick up and process the attachment. All is well when I test the scenario internally, but when the third party emails it fails with (see ERROR MESSAGE below).
When I look at the SOAP header of the failed message I see the values from the dump in this field:
<sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderTHREAD-INDEX">AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1pEZAF500SsAYW46lgBgX2bGALyieMQAXw2oKgBYXf0WAGeueD0AAAHnhwBamTSaAGIUE0kAYZSYTQBgY5OTADunN0gAE3t/sQAWScBXADTQvvEAD4yNhQATdkKiAFr7DBMAGIXTZQAP2xJFABZ0YfoAGHYAuAAKlaeaACJ9xtUAEjcvQAAV4L06ABZuwsAAK/f9vgAAF/GSAAAYmRYARIKwtQAV5R9SABMo5bsAGQQyvAAVqsjyABOh9uMAFXTa2QAWEjsfABaEvp4AFaL1NQAV5MnUABXiVbIAGc7LsQAYVN9SABLfYQIAEwF3nQAWSL2lABn5ZgIAEf/k8gAWeVgrAAJaSZIAAElM4gATZR0GA=</sap:Record>
Can anyone tell me what SHeaderTHREAD-INDEX does? Or what my problem is (Our email is Outlook)
ERROR MESSAGE.........
SOAPFault received from Integration Server. ErrorCode/Category: XIProtocol/WRONG_VALUE; Params: SOAP:Envelope(1)SOAP:Header(1)sap:DynamicConfiguration(3)sap:Record(14), AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1pEZAF500SsAYW46lgBgX2bGALyieMQAXw2oKgBYXf0WAGeueD0AAAHnhwBamTSaAGIUE0kAYZSYTQBgY5OTADunN0gAE3t/sQAWScBXADTQvvEAD4yNhQATdkKiAFr7DBMAGIXTZQAP2xJFABZ0YfoAGHYAuAAKlaeaACJ9xtUAEjcvQAAV4L06ABZuwsAAK/f9vgAAF/GSAAAYmRYARIKwtQAV5R9SABMo5bsAGQQyvAAVqsjyABOh9uMAFXTa2QAWEjsfABaEvp4AFaL1NQAV5MnUABXiVbIAGc7LsQAYVN9SABLfYQIAEwF3nQAWSL2lABn5ZgIAEf/k8gAWeVgrAAJaSZIAAElM4gATZR0GA=協彎䅍䔾ਉ़䥎噏䥃䕟乏㸸㌱ㄵㄹ㰯䥎噏䥃䕟乏㸊उ㱁䵏啎呟䕘䍌彖䅔㸷⸵〼⽁䵏啎呟䕘䍌彖䅔㸊उ㱃啒剅乃失㹅啒㰯䍕剒䕎䍙ㄾਉ़䅍何乔彖䅔㸱⸴㜼⽁ꯃ䅢坡汫, ST: ST_XM; AdditionalText: An error occurred when deserializing in the simple transformation program ST_XMS_MSGHDR30_DYNAMIC; ApplicationFaultMessage: ; ErrorStack: XML tag SOAP:Envelope(1)SOAP:Header(1)sap:DynamicConfiguration(3)sap:Record(14) (or one of the attributes) has the incorrect value AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1pEZAF500SsAYW46lgBgX2bGALyieMQAXw2oKgBYXf0WAGeueD0AAAHnhwBamTSaAGIUE0kAYZSYTQBgY5OTADunN0gAE3t/sQAWScBXADTQvvEAD4yNhQATdkKiAFr7DBMAGIXTZQAP2xJFABZ0YfoAGHYAuAAKlaeaACJ9xtUAEjcvQ An error occurred when deserializing in the simple transformation program ST_XMS_MSGHDR30_DYNAMIC Data loss occurred when converting AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1p
Transmitting the message to endpoint http://sdcxp1-ci.na.fmo.com:8000/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Error during parsing of SOAP header.

We work with Microsoft Outlook, but I'm sure this could work with any email system.
This error only came from external emails - what we did in the end is to get the third party to email a particular email (email1) in our company. This is set up as a regular email account. On this email put a forward rule to email2 for a particular sender/subject. email2 is set up as POP3 so that XD1 can poll it - we also block any emails except from email1.
Doing this accomplishes a couple of things:
1) We get around the error because XI polls email2 (which has adapter settings of IMAP4 so we can see MAIL adapter attributes ie. sender, subject etc...When we originally had as POP3 we were not able to see these - but setting as IMAP4 causes the error for external emailers)
2) We have a SPAM filter - the XI email is clean from SPAM and the adapter will not have errors, as it only receives valid emails to process
3) We have a central email (email1) which is used to archive all XI emails - we use this for all email scenarios (as we also save to folder and forward in the rule)
Hope this helps your situation.

How to modify the soap header of ebxml control?

I need to change the soap header information of the ebxml control
from
<eb:CPAId>http://www.openuri.org/cpa</eb:CPAId>
to
<eb:CPAId>MyString</eb:CPAId>
and I want to add some additional information to the header such as the wsse feature
<wsse:Security xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/12/secext" xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/12/utility">
<wsse:UsernameToken>
<wsse:Username>1234</wsse:Username>
<wsse:Password>5678</wsse:Password>
<Organization>abc</Organization>
<Domain>DEFAULT</Domain>
</wsse:UsernameToken>
</wsse:Security>
Does anyone know where I can change the type value?
Thanks, Kun

Your code works. But if I place the TextInput in the formItem
and form tags, the Y value becomes 0. You can try this one:
<?xml version="1.0"?>
<mx:Application xmlns:mx="
http://www.adobe.com/2006/mxml">
<mx:Form paddingBottom="0" paddingTop="0"
paddingRight="0">
<mx:FormItem label="Title:">
<mx:TextInput width="275" id="newSongTitle"/>
</mx:FormItem>
<mx:FormItem>
<mx:Button id="submitSongData" label="Add Song"
width="150"/>
</mx:FormItem>
</mx:Form>
<mx:Text text="{newSongTitle.x}" width="322"/>
<mx:Text text="{newSongTitle.y}" width="322"/>
<mx:Button label="set Y" click="{newSongTitle.y =
newY.value}"/>
<mx:NumericStepper id="newY" value="50" minimum="0"
maximum="400"/>
</mx:Application>

Adding soap header in MX6.1

I have a code working on MX7, it first adds soap
header(username and password) then gets the response, but similar
code didn't work on MX6.1. Please help.
MX7 code:
<cfscript>
ru = XmlNew();
ru.AuthenticationHeader = XmlElemNew(ru, "
http://www.mytesting.com/Webservices/ProductInfo","AuthenticationHeader");
ru.AuthenticationHeader.UserName = mlElemNew(ru,"
http://www.mytesting.com/Webservices/ProductInfo","UserName");
ru.AuthenticationHeader.UserName.XmlText = "myusername";
ru.AuthenticationHeader.Password = XmlElemNew(ru,"
http://www.mytesting.com/Webservices/ProductInfo","Password");
ru.AuthenticationHeader.Password.XmlText = "mypassword";
ws = CreateObject("webservice", "
http://www.mytesting.com/Webservices/ProductInfo/Management.asmx?WSDL");
addSOAPRequestHeader(ws, "
http://www.mytesting.com/Webservices/ProductInfo",
"AuthenticationHeader", ru.AuthenticationHeader, true);
subbid = ws.GetProductInfo();
</cfscript>
MX6.1 code:

<cfinclude template="soap-udfs.cfm">
<cfscript>
ru = XmlNew();
ru.AuthenticationHeader = XmlElemNew(ru, "
http://www.mytesting.com/Webservices/ProductInfo","AuthenticationHeader");
ru.AuthenticationHeader.UserName = XmlElemNew(ru,"
http://www.mytesting.com/Webservices/ProductInfo","UserName");
ru.AuthenticationHeader.UserName.XmlText = "myusername";
ru.AuthenticationHeader.Password = XmlElemNew(ru,"
http://www.mytesting.com/Webservices/ProductInfo","Password");
ru.AuthenticationHeader.Password.XmlText = "mypassword";
ws = CreateObject("webservice", "
http://www.mytesting.com/Webservices/ProductInfo/Management.asmx?WSDL");
addRequestHeader(ws, "AuthenticationHeader",
ru.AuthenticationHeader, "
http://www.mytesting.com/Webservices/ProductInfo",
true);
subbid = ws.GetProductInfo();
</cfscript>
Error message for MX6.1:
Could not perform web service invocation "GetProductInfo"
because AxisFault faultCode: {
http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode: faultString: java.io.IOException: No serializer found
for class coldfusion.xml.XmlNodeList in registry
org.apache.axis.encoding.TypeMappingImpl@19a61ad faultActor:
faultNode: faultDetail: {
http://xml.apache.org/axis/}stackTrace:
java.io.IOException: No serializer found for class
coldfusion.xml.XmlNodeList in registry
org.apache.axis.encoding.TypeMappingImpl@19a61ad at
org.apache.axis.encoding.SerializationContextImpl.serializeActual(SerializationContextImp l.java:1281)
at
org.apache.axis.encoding.SerializationContextImpl.serialize(SerializationContextImpl.java :795)
at
org.apache.axis.message.MessageElement.outputImpl(MessageElement.java:817)
at
org.apache.axis.message.SOAPHeaderElement.outputImpl(SOAPHeaderElement.java:250)
at
org.apache.axis.message.MessageElement.output(MessageElement.java:783)
at
org.apache.axis.message.SOAPHeader.outputImpl(SOAPHeader.java:342)
at org.apache.ax...

XML snippit
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:con="urn:crmondemand/ws/contact/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
xmlns:con1="urn:/crmondemand/xml/contact">
<soapenv:Header>
<wsse:Security>
<wsse:UsernameToken>
<wsse:Username>your_site/your_login</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">your_password</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</soapenv:Header>
This isn't exactly what you are looking for but you can use this to add a header to a axis web service call.
SOAPHeaderElement header = new SOAPHeaderElement("http://your.xsd", "your tag");
SOAPHeaderElement header1 = new SOAPHeaderElement("http://your other.xsd", "your other tag");
header1.setAttribute("Id", "your value");
header.addChild(header1);
SOAPElement node = header1.addChildElement("more text");
node.addTextNode("more text");
SOAPElement nodepwd = header1.addChildElement("another tag");
nodepwd.addTextNode("more text");
nodepwd.setAttribute("Type", "http://another url");
((Stub)service2).setHeader(header);
Hope this is more helpful than confusing.

Adding soap header in java

Can anyone please tell me how to add following security header in Webservices (WS 1.0 ) client using java code? (I m using axis 1.4)
<soap:Header>
<wsse:Security soap:mustUnderstand="1">
<wsse:UsernameToken>
<wsse:Username>[email protected]</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wssusername-
token-profile-1.0#PasswordText">adminOnDemand</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</soap:Header>

XML snippit
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:con="urn:crmondemand/ws/contact/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
xmlns:con1="urn:/crmondemand/xml/contact">
<soapenv:Header>
<wsse:Security>
<wsse:UsernameToken>
<wsse:Username>your_site/your_login</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">your_password</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</soapenv:Header>
This isn't exactly what you are looking for but you can use this to add a header to a axis web service call.
SOAPHeaderElement header = new SOAPHeaderElement("http://your.xsd", "your tag");
SOAPHeaderElement header1 = new SOAPHeaderElement("http://your other.xsd", "your other tag");
header1.setAttribute("Id", "your value");
header.addChild(header1);
SOAPElement node = header1.addChildElement("more text");
node.addTextNode("more text");
SOAPElement nodepwd = header1.addChildElement("another tag");
nodepwd.addTextNode("more text");
nodepwd.setAttribute("Type", "http://another url");
((Stub)service2).setHeader(header);
Hope this is more helpful than confusing.

Access to SOAP header in synchronous SOAP response?

Hi,
Scenario: message received via synchronous SOAP adapter call.
In the response which is sent back to the sender i can influence the SOAP body but not the SOAP header.
Is there a possibility to manipulate/add/map the SOAP header in synchronous response messages?
Thank you very much in advance for your hints.
Greetings
Michael

Hi Christophe,
per default PI is sending back something like this
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
     <SOAP:Header/>
     <SOAP:Body>
          Payload, which can be accessed via mapping
     </SOAP:Body>
</SOAP:Envelope>
but required are some fields in the Header tag like:
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
     <SOAP:Header>
                               <SOAP:ABC>date</SOAP:ABC>
     </SOAP:Header>
     <SOAP:Body>
          Payload, which can be accessed via mapping
     </SOAP:Body>
</SOAP:Envelope>
Greetings
Michael

SOAP Header Tag

Similar Messages

Maybe you are looking for