Use of variable header XHeaderName1 in SOAP sender adapter

Hi all,
I have a doubt regarding the use of adapter-specific attributes in SOAP sender adapter. In specific:
the SOAP client should be able to pass a variable with the SOAP request (XHeaderName1 header variable) and this should be available in mapping (Dynamic configuration)
I've already checked the [help page|http://help.sap.com/saphelp_nw04/helpdata/en/fc/5ad93f130f9215e10000000a155106/frameset.htm] but it seems I'm doing something wrong.
I tried with those settings in SOAP adapter configuration:
Keep headers checked
XHeaderName1 = Test
I try to call the SOAP adapters in the following 2 ways, but none works (the value is not available in message mapping with Dynamic configuration)
1. Pass "Test" value xxxx in SOAP Header as a tag
<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">
     <SOAP-ENV:Header>
          *<Test>xxxx</Test>*
     </SOAP-ENV:Header>
     <SOAP-ENV:Body>
     </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
2. Pass "Test" value xxxx in SOAP URL
http://host:50000/XISOAPAdapter/MessageServlet?channel=p:s:c&version=3.0&Sender.Service=...&Interface=...&Test=xxxx
Could anyone give me a hint about how to pass those values in the SOAP call and eventually the correct config. of SOAP sender ?
Thanks a lot,
Manuel

Hi Manuel,
Could you give a bit more detail on how you handled the SOAP message yourself.
I have a similar issue. I am consuming a non SAP Web Service which requires a non-standard token element to be passed back. I have created a an RFC sender to SOAP reciever scenario which works fine for the inital logon and returns the token it expects in the follow up messages.
At present I'm at a loss so your help would be much appreciated. We have got round the immediate issue by creating and sending the SOAP message directly from SAP WAS.
Could we use the XI Adapter and ABAP proxy in a similar way?
Thanks,
Tim J.

Similar Messages

'Keep Header' Option in SOAP sender adapter not working

Hi all
I have exposed a webservice using a SOAP sender adapter in XI. A SOAP client is sending request to this service.
The SOAP request has some elements in the header like wssecurity and ws addressing tags.
When I remove the header elements and send the request my scenario works as expected but when I include the header fields I get a time out in my soap client application and cannot see any message, any where on XI. Can somebody help me understand why this is happening.
Thanks
Dilip

Hi Stefan
In my scenario it is ok if XI ignores the soap header tags it does not understand. I want the system to ignore the header tags and go ahead and process only the payload.
But unfortunately I keep getting a time out whenever I send a request with the header tags. When I remove the header I can sucessfully post documents.
I tried increased the time out to 5 min but still continue to get the problem. So am sure the problem is not exactly related to timeout, but due to the header tags.
What do you suggest?
Regards
Dilip

Variable Transport binding - SOAP Sender Adapter

Hi All
have a scenarion where Sender System is sending Custom SOAP Header as below into P through SOAP Sender ChannelI.
And the requirement is to access the values coming in Header fields, example within Message Mapping need to Map Headername1 value to Outgoing structure.
<soapenv:Header>
     <Header1>S1</Header1>
     <Header2>S2</Header2>
     <Header3>S3</Header3>
</soapenv:Header>
   <soapenv:Body>
     u2026..
   </soapenv:Body>
Have checked the Paramter KEEP Headers in SOAP Adapter and in Adapter Specific Message Attributes have defined the following
Variable Header (XHeaderName1) = Header1
Variable Header (XHeaderName2) = Header2
Variable Header (XHeaderName1) = Header3
Now need to know what should be mentioned in the UDF in the Message Mapping for accessing Dynamic Configuration. Will these headers mentioned will be a part of Dynamic Configuration or not ?
Using the below UDF and its failing in Message Mapping - kindly suggest the corect way of achieving the same
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key1 = DynamicConfigurationKey.create( "http://sap.com/xi/XI/System/SOAP", "XHeaderName1");
String value = conf.get(key1);
return value ;
Appreciate response in this regard
//Swetank

Hi Abhishek
Its failing at runtime at Message Mapping stage. The real problem is that I can't see the Header1 in my Dynamic Configuration header - it has all the other fields like SServerHost, SRemoteUser, but not my Header1 (S1) field. Thus either the UDF is wrong or any configuration in SOAP Sender Channel needs to be adjusted.
Further I am not sure whether Custom SOAP Header fields can be a part of Dynamic Configuration or they only show fields which are part of HTTP header.
//Swetank

SAP PI: Using Variable Header Binding in Receiver Mail Adapter

Hello,
I try to use Variable Header Bindings in the Receiver Mail Adapter. Therefore I wrote the following User-Defined-Function in a mapping:
Java Function Start -
DynamicConfiguration conf = (DynamicConfiguration) container
    .getTransformationParameters()
    .get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key1 = DynamicConfigurationKey.create(
    "http://sap.com/xi/XI/System/Mail",
    "XHeaderName1");
DynamicConfigurationKey key2 = DynamicConfigurationKey.create(
    "http://sap.com/xi/XI/System/Mail",
    "XHeaderName2");
DynamicConfigurationKey key3 = DynamicConfigurationKey.create(
    "http://sap.com/xi/XI/System/Mail",
    "XHeaderName3");
conf.put(key1, new String("Test1"));
conf.put(key2, new String("Test2"));
conf.put(key3, new String("Test3"));
Java Function End -
As expected I see the Attributes and Parameters in the Dynamic Configuration in the SAP XI Monitor:
Dynamic Configuration Informattion Start -
<?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/Mail" name="XHeaderName3">Test3</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/Mail" name="XHeaderName2">Test2</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/Mail" name="XHeaderName1">Test1</SAP:Record>
</SAP:DynamicConfiguration>
Dynamic Configuration Informattion End -
Now I configure my Receiver eMail Communication Channel and set the Variable Header Fields as follows:
   Adapter Specific Attributes: Checked
   Variable Transport Binding: Checked
   Variable Header (XHeaderName1): TSender
   Variable Header (XHeaderName2): TReceiver
   Variable Header (XHeaderName3): TOther
With this configuration I would have expected three new Header fields in the Header of the eMail, the reicever gets. But they are not there.
When I set standard attributes like THeaderTO, THeaderSubject a.s.o this works fine and the values are also set accordingly. Where it the mistake here?
The PI version we are working with is PI 7.0 SP10.
Your help will be highly appreciated.
Thank you,
Steffen

Hi Luciana,
Honestly, I cant really remember how or if it was resolved and I was just helping out on the issue, but another consultant continued with it, so unfortunately I cant be any help on this.
Good luck!
Cheers,
Brad

Using custom http headers in SOAP sender adapter

Hi,
my problem is exactly the same as reported [here|Re: SOAP Sender - Extract Header Values;] and [here|Variable Transport Binding - Soap Sender;
Basically I'd like to send through the soap sender adapter some custom http headers. I check the necessary options in the advanced tab (set adapter-specific message attributes and variable transport binding), and in the variable header one I put x-StoreCode, which is the same http header I send to PI.
But I won't see anything in the dynamic configuration section when the message is persisted in PI.
Very surprised that I've seen this issue is a common problem others have faced before without success.
Thanks!

Hi Michal,
the extra info I'm trying to send separated from the message is an http header, not part of the query string.
If I incorporate the extra info as a parameter to the query string like this, for example:
http://host:50000/XISOAPAdapter/MessageServlet?senderParty=&senderService=S1&receiverParty=&receiverService=&interface=Int&interfaceNamespace=urn:test&x-StoreCode=13&nosoap=true
Then I can see the value in the dynamic configuration section:
<SAP:Record namespace="http://sap.com/xi/XI/System/SOAP" name="SQueryString">senderParty=&senderService=S1&receiverParty=&receiverService=&interface=Int&interfaceNamespace=urn:test&x-StoreCode=13&nosoap=true</SAP:Record>
But what I'm trying to do shoould be possible, according to sap help:
http://help.sap.com/saphelp_nwpi71/helpdata/en/fc/5ad93f130f9215e10000000a155106/content.htm (section Define Adapter-Specific Message Attributes)

Invocation of SOAP Sender Adapter using Apache SOAP

Hi,
I'm trying to invoke the XI SOAP Sender Adapter using the Apache SOAP API. It seems that my message header is missing a few parameters (see exception below). Does anybody know which to set?
Regards,
Heiko
==========
Exception:
<?xml version='1.0'?>

<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>Exception</code>
          <text><![CDATA[
com.sap.aii.af.mp.module.ModuleException
     at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:502)
     at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:103)
     at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:227)
     at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java:103)
     at com.sap.aii.af.mp.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:162)
     at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:507)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:392)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
     at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged1(Native Method)
     at java.security.AccessController.doPrivileged(AccessController.java:321)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)
Caused by: java.lang.Exception: Bubble configuration error: parameter 'XI.InterfaceNamespace' is missing
     at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.getParaRequired(XISOAPAdapterBean.java:895)
     at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.createDefaultMessageHeader(XISOAPAdapterBean.java:942)
     at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.setup(XISOAPAdapterBean.java:214)
     at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:496)
     ... 22 more
          ]]></text>
        </s:SystemError>
      </detail>
    </SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>

Hi Heiko,
You are missing the Namespace Parameter in the sender soap adapter configuration in XI3.0
Thanks
Prasad

Reading Header data in a SOAP Envelope for SOAP Sender Adapter

Hello All,
Am using a SOAP sender adapter and want to use the data inside the SOAP Header for some routing purpose(extended receiver determination). Any SOAP message coming into XI will look something like below. But XI will pass the contents of <SOAP-ENV:Body> to Payload and <SOAP-ENV:Header> to the SOAP Header category you can see that in SXMB_MONI.
Is there a way to read the data in my SOAP Header to be later used in my extended receiver determination.
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:Q-ENV="/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
     <SOAP-ENV:Header>
          <Q-ENV:Header>
               <Q-ENV:Sender-Id>1</Q-ENV:Sender-Id>
               <Q-ENV:Receiver-Id></Q-ENV:Receiver-Id>
               <Q-ENV:Correlation-Id></Q-ENV:Correlation-Id>
               <Q-ENV:Message-Id></Q-ENV:Message-Id>
               <Q-ENV:Date-Sent></Q-ENV:Date-Sent>
               <Q-ENV:Document-Type></Q-ENV:Document-Type>
               <Q-ENV:Message-Format></Q-ENV:Message-Format>
          </Q-ENV:Header>
     </SOAP-ENV:Header>
     <SOAP-ENV:Body>
          <Q-ENV:Body>
               <Q-ENV:Content-Type>text/xml</Q-ENV:Content-Type>
               <Q-ENV:Message-Type></Q-ENV:Message-Type>
               <Q-ENV:Encoding>UTF-8</Q-ENV:Encoding>
               <Q-ENV:Message-Body>
     </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Thanks for your replies in advance.
Regards,
Prashanth

Hello,
but they were not getting any response back from XI and the sending system kept resending the message.. may be it was acting like a HTTP post.
The method that is used by the native SOAP Adapter is always HTTP Post. Not sure why you are not getting a response, have you checked the outbound firewall of the sending party or the inbound firewall of XI? To which SOAP URL are you sending to?
Hope this helps,
Mark

Soap Sender Adapter Preserve And Access Soap Header

Hi,
I would like to preserve the Soap Header created by a client and access it in a mapping using the the Soap Sender Adapter (SP16). Does anybody know how to do this?
Kind regards,
Heiko

Hello Udo,
I have found a solution to this problem. It is possible to add header entries to the DynamicConfiguration which is available by an API:
soapMsg.append("<SOAP-ENV:Header>");
soapMsg.append("<SAP:DynamicConfiguration xmlns:SAP=\"http://sap.com/xi/XI/Message/30\" xmlns:SOAP=\"http://schemas.xmlsoap.org/soap/envelope/\" SOAP:mustUnderstand=\"1\">");
soapMsg.append("<SAP:Record namespace=\"http://sap.com/xi/XI/System/SOAP\" name=\"SRmsUser\">test</SAP:Record>");
This code snip shows Java client code to add an element to the SOAP header which corresponds to the DynamicConfiguration. In XI it will be accessable using the respective API.
Cheers,
Heiko

Using SOAP Sender adapter in PI 7.1

Hi Guys,
I've created a sync scenario with SOAP sender adapter, but I have troubles with calling it.
I use following URL: http://<host>:50000/XISOAPAdapter/MessageServlet?channel=:BS_Bus_Sys:CC_SOAP_Test as I did in XI 3.0, but I'm getting error HTTP 400 Bad Request. I'm using the request generated from the IR Configuration.
Has something changed in 7.1 for this type of scenario?
Thanks guys,
Olian

Hi! Olian,
I think u r going in a wrong way. The above given URL is wrong and incomplete one.
The above url comes only after generating the WSDL. You ill gives that URL to ur source team to post their data at which this URL itselfs acts as an Gateway to enter into SAP XI/PI.
The generated WSDL contains URL like this>>
"http:// Host:Port/XISOAPAdapter/MessageServlet?senderParty=&senderService=Business Service&receiverParty=&receiverService=&interface=SenderInterfaceI&interfaceNamespace=http://XXXXXXXX" />
Also follow the below procedure for generating the WSDL.
Except generating WSDL remaining all development steps are same as creating File to Proxy Scenario.
CREATING THE WEBSERVICE IN XI :
1) In Integration Directory, go to Tools tab --> Define Web Services.
2) Now one Wizard window will opens and follow the below steps:
Here donu2019t go for the u2018 Proposed URLu2019, instead specify the URL as::
http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet?channel=:<service>:<channel>
If there is party then ::
http://host:port/XISOAPAdapter/MessageServlet?channel=<party>:<service>:<channel>.
3) Specify the Source Messageu2019s Message Interface.and remaining other input parameters.
4) Specify the Sender Business Serviceu2019s details:
5) Here, Cross check the details displayed and then click on u2018Finishu2019 button to create the Web Service
document(WSDL)
6) Now Save the WSDL code to the local system. At the bottom u ill get URL based on the above input
URl:
Note: Here in XI there is no XML Testing tool or SOAP client tool to test SOAP messages. That is why most of the people prefer either ALTOVA XML SPY Tool or SOAP CLIENT TOOL or INFO PATH.
If your working on PI 7.1 means::
1) Simply after creating Sender Agreement go to options above to that sender agreement instead of tools menu... and there you can observe 2 options at the bottom side.
a) PUBLISH in SR
b) Generate WSDL.
2) Once after activating your ID componenets just Press or go for option Publish in SR. Then automatically it will generate WSDL and publish that WSDL in the SERVICE REGISTRY. which is latest concept in PI 7.1.
3) Now by entering authentification details you can able to enter into service registry.
There are 4 tabs::
a) Service definitions
b) Publish
c) classifications
d) Manage.
Go for Service definitions::
4) Enter your sender SOAP interface and press GO or enter.
5) Select your interface and then at the bottom u can observe again 4 tabs:
a) General b) End Points c) classifications d) System Details.
6) In the general you can able to see your WSDL URL by again entering Authentification details.
7) Now Click End Points>Test Button>Enter Authentification details-->Seelct your Interface
Note:: Now you can test your scenario in this WEB SERVICE NAVIGATOR.
8) There you can enter you can pass your Input data parameters in your SOAP interface and execute or test your scenario here itself without any using of external tool like Altova XML or SOAP client tool.
I hope the above information will give you a detailed information in generating and testing webservice right.
Regards::
Amar Srinivas Eli

How to use SOAP sender adapter

Hi all
i have configured the SOAP sender adapter. Now my 3rd party needs to send me a soap message.
I have checked that the status at the following URL is OK:
http://host:port/XISOAPAdapter/MessageServlet?channel=:MXII_Web_Service:SOAP_MXII_Sender.
This is fine, however
I am unsure of the following:
1. Does XI make a wsdl available to the 3rd party?
2. Where does my 3rd party send the soap message to?
3. Is the SOAP message sent via a query string?
4. Do I need to create a web service?
Thanks for all your help in advance
Clinton

Hi Moorthy
Thanks for your answer.
The problem was solved, we used .Net to write a webservice to our wsdl.
I have now another problem.... When the message comes into XI it shows that no receiver found(RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC). If I just test the scenario with a file adpter as Sender, and Receiver it is fine, but when using the SOAP adapter as Sender, it gives me the no receiver found message.
Any help with this issue will be appreciated.
Thanks again
Clinton

Use Moduls with SOAP Sender Adapter

Hi Experts,
I have a question regarding the use of modules in the soap sender adapter / communication channel. Is it correct that the use of modules in the soap sender adapter is not possible?
the background of my question is that we use modules from SEEBURGER in our Communication channels for archiving incoming and outgoing documents. the use of modules in the soap receiver adapter is possible. why not in the soap sender???
according to the sap help it is possible to use the axis framwork in the soap adapter. then it should be possible to use modules. Is that correct? I tested it but it is not working. If I send a soap message (with the soap reveicer adapter) to the axis soap sender adapter there occure internal server errors. it is only working if I write my own modules for the axis soap sender adapter? is it not possible to use external modules like in other channels (File/FTP, soap receiver etc.)???
thanks and best regards!
Christopher

we have moduls from SEEBURGER. so I have to test it. but before I need a scenario with which I can test it.
We have a customer who sends xml-files per soap to us. these files we receive succussfully with the soap sender adapter. now we want to use some modules. so we have to use the axis soap sender adapter. I tried to send an xml file with the soap receiver adapter to the axis soap sender adapter, but this was not working. http 500 internal server errors occurred. is it possible that this scenario (soap-to-axis-soap) is not working? need I a specific configuration for this?
thanks and regards
Christopher

ASMA in SOAP Sender adapter.

Hi All,
Using ASMA under SOAP sender adapter I am trying to get the username of the user . I am referring below links for the same:
/people/michal.krawczyk2/blog/2009/05/26/pixi-pseudo-principal-propagation (referring this only for getting username)
getting user name from sopa header
But while testing through XML SPY , i am getting error :
Com.sap.engine.interfaces.messaging.api.exception.MessagingException: Received HTTP response code 500 : Error during parsing of SOAP header.
Please help??.
Thanks
Amit

Hi.
I have created WSDL file using below URL:
http://ISVSAPPIDEV:50100/XISOAPAdapter/MessageServlet?channel=:BS:CC_SOAP_Sender
Actually its a synchronous SOAP -PI - RFC scenario. When i am pinging the PI through XML spy(ASMA AND Transport Binding is UNCHECKED in soap sender channel) i am getting the response back from RFC, but when i am pinging after chking the ASMA and Transport Binding in SOAP sender adapter i am getting this error(the message is itself not reaching the PI):
Com.sap.engine.interfaces.messaging.api.exception.MessagingException: Received HTTP response code 500 : Error during parsing of SOAP header.
Thanks
Amit

Remove XML Prefix in SOAP Sender Adapter

Hi
I am using a SOAP sender adapter and testing it from SOAP UI. The format that is generated from the web service is
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
   <soapenv:Body>
      <sap:SALES_ORDER xmlns:sap="http://XYZ.org/">
         <sap:HEADER>
            <sap:BATCH_ID>XYZ</sap:BATCH_ID>
            <sap:CREATE_DT>XYZ</sap:CREATE_DT>
This format when processed in SOAP UI gave error which its not giving for other files. Clearly I need to remove this sap: tag, I can't use XML anonymizer as it is SOAP adapter and I can't select do not use soap env...Could anyone provide me Java/xslt code for the same..I tried all the codes on sdn but none of them worked.
Regards,

SImple Java mapping, that should help
import java.io.InputStream;
import java.io.OutputStream;
import com.sap.aii.mapping.api.*;
import org.w3c.dom.*;
public class DeleteCDATA_DOM_mapping extends AbstractTransformation {
     public void traceXML(Node n,int i)
     {   AbstractTrace trace = getTrace();
          trace.addInfo(i+"$"+n.getNodeName());
          trace.addInfo(i+"$"+n.getNodeValue());
          trace.addInfo(i+"$"+n.getNodeType()+"");
     public void traceNL(NodeList nl)
          {      for (int i=0 ; i<nl.getLength();i++)
                    traceXML(nl.item(i),i);
     public void transform(TransformationInput in, TransformationOutput out)
               throws StreamTransformationException {
                    AbstractTrace trace = getTrace();
                         try {
                              InputStream is0=in.getInputPayload().getInputStream();
                              StringBuffer out1 = new StringBuffer();
                              byte[] b = new byte[4096];
                              for (int n; (n = is0.read(b)) != -1;) {
                                   out1.append(new String(b, 0, n,"UTF-8"));
                              String sss=out1.toString();
                              sss=sss.replaceAll("<sap:", "<");
                              sss=sss.replaceAll("</sap:", "<");
                              OutputStream os = out.getOutputPayload().getOutputStream();
                              os.write(sss.getBytes("UTF-8"));
                         } catch (Exception e) {
                              throw new StreamTransformationException(
                                   "Exception in DeleteCDATA_DOM_mapping JAVA mapping ): "
                                        + e.getMessage());

HTTPS-based SOAP Sender Adapter

Dear all,
We're using NetWeaver 2004s SP12. I need to enable an HTTPS based SOAP sender adapter. According to online-help document at http://help.sap.com/saphelp_nw2004s/helpdata/en/fc/5ad93f130f9215e10000000a155106/content.htm, there should be a field "HTTP security level" to specify whether HTTPS is used. But I cannot find it in the communication channel configuration UI. Does anybody have any idea?
Thanks + Best Regards
Jerome

Hi
Just a try with this link am not sure ...
<i>If you want to specify security checks in the message header for the plain HTTP inbound channel, create a communication channel <b>for the party and service</b> in the Integration Directory.</i>
http://help.sap.com/saphelp_nw04/helpdata/en/43/64db4daf9f30b4e10000000a11466f/content.htm

Error while posting messages to SOAP sender adapter SP 13

Hi Friends,
I have configured a SOAP sender adapter in XI 3.0 and is using the URL
http://host:port/XISOAPAdapter/MessageServlet?channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP to post the messages. When I open the URL in the browser I am getting the error.
Message Servlet is in Status ERROR
Status information:
Servlet com.sap.aii.af.mp.soap.web.MessageServlet (Version $Id: //tc/aii/30_VAL_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#5 $) bound to /MessageServlet
Classname ModuleProcessor: null
Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean
Lookupname for remoteModuleProcessorLookupName: null
ModuleProcessorClass not instantiated
ModuleProcessorLocal not instantiated
ModuleProcessorRemote not instantiated
But when I test the URL http://host:port/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP to check the communication channel I am getting the right response as below.
<?xml version="1.0" ?>
<http://host:port/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:BS_EBTR_WEBSERVICE:CC_EBTR_WEBSERVICE_SOAP> <s:ChannelInfo xmlns:s="http://sap.com/xi/WebService/xi30">
<channelID>e7ac884596ea3d088cbfd8b434f942f2</channelID>
<name>CC_WEBSERVICE_SOAP</name>
<type xmlns:st="http://sap.com/xi/XI/System">st:SOAP</type>
<direction>INBOUND</direction>
<party />
<service>BS_WEBSERVICE</service>
</s:ChannelInfo
I used the http capture to debug, In the 1st case though I am getting "Message Servlet in status error" I am seeing a 200 OK code in the http capture tool. When the message is posted from .net client proxy we are getting a 500 internal server error.
Am not sure what causes the error ? I saw two notes in SDN related to SOAP - J2EE SP13. We are in SP13. Is this the issue ? Wanted to know your opinion before applying the notes.
Thanks & Regards,
Mathew

ABAP & Java stack was on different SP levels.

Use of variable header XHeaderName1 in SOAP sender adapter

Similar Messages

Maybe you are looking for