Variable Transport Binding - Soap Sender

Hello all,
I'm trying to retrieve a parameter from the HTTP header of a SOAP request.
I have created a SOAP sender communication channel, checked "Set Adapter-Specific Message Attributes" and "Variable Transport Binding", and entered the name of the parameter in Variable Header (XHeaderName1).
When I send the SOAP request, DynamicConfiguration exists with all standard parameters, but there is no XHeaderName1...
If I try the same with sender HTTP adapter, it works fine.
In the other way, if the dynamic configuration parameter XHeaderName1 already exists, and I try to add it in a HTTP header parameter in a receiver SOAP CC, that works.
Does somebody know why this doesn't work in the sender one?
Thanks,
Greg
PS: I'm using PI7.0 SP14

Hello,
I can see in dynamic configuration, with the namespace http://sap.com/xi/XI/System/SOAP, the standard HTTP parameters like SServerHost, SRemoteUser, etc...
But if I add a HTTP header parameter in the SOAP request, and I try to retrieve it with the SOAP sender CC, the parameter is not added in the dynamic configuration. If the name of the added HTTP header parameter is "TestParam", I put "TestParam" in the XHeaderName1 field of the sender CC, but the value is not added in the dynamic configuration. This is my problem.
Thanks,
Greg

Similar Messages

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

Error when using Variable Transport Binding in Sender Mail Adapter

Hi,
I am using the Sender Mail Adapter to receive an email, convert the attached tab delimited text file into xml and map it to an IDOC.
I am using PayloadSwapBean and MessageTransformBean in order to do this, and this all works perfectly.
I am now trying to access the Adapter Specific Message Attributes to retrieve the SHeaderFROM attribute from the message and map it to a field in the idoc.
However when I check the "Variable Transport Binding" option in the Advanced tab of the mail adapter, the message no longer goes through to SXMB_MONI and I get the following error in the Java logs.
Transmitting the message to endpoint http://sapserver:53500/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Received HTTP response code 500 : Error during parsing of SOAP header.
Any ideas why this is happening?
Thanks,
Brad

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

SOAP Use Adapter-Specific Message Properties and Variable Transport Binding

Hi Friends,
   I am new to use to Soap Adapter. Please help me out bellow doubts.
   1.When you use Use Adapter-Specific Message Properties and Variable Transport Binding .
   2. Where exactly we r using below parameters.
Remote User : (technical name: SRemoteUser )
Remote Host : (technical name: SRemoteHost )
SOAP Action (technical name: SHeaderSOAPACTION )
To transfer further header fields, set the relevant indicator. You can then store the following attributes and their values in the XI message header:
Variable Header : (technical name: XHeaderName1 )
Variable Header : (technical name: XHeaderName2 )
Variable Header : (technical name: XHeaderName3 )
Thanks&Regards
G.Bhanuprakash

Hi,
   1.When you use Use Adapter-Specific Message Properties and Variable Transport Binding .
SAP Help says both are needed to be checked when you want to process adapter attributes
Configuring the Receiver SOAP Adapter - SAP NetWeaver Exchange Infrastructure - SAP Library
These attributes can be get/set using dynamic configuration and their technical names are what you have pasted:
Remote User : (technical name: SRemoteUser )
Remote Host : (technical name: SRemoteHost )
SOAP Action (technical name: SHeaderSOAPACTION )
To transfer further header fields, set the relevant indicator. You can then store the following attributes and their values in the XI message header:
Variable Header : (technical name: XHeaderName1 )
Variable Header : (technical name: XHeaderName2 )
Variable Header : (technical name: XHeaderName3 )
Remote User - the username used to send a message to the adapter engine using SOAP
Remote Host - hostname which the remote user used
SOAP Action - SOAP Action of the XI webservice (sender) / SOAP Action of the receiver webservice
Variable Headers are additional key-value pairs in the HTTP Header that could be accessed in the XI Header using dynamic configuration. The limit is only three though.
Regards,
Mark

Mail sender adapter with Variable Transport Binding doesn't work

Hi,
we have PI/700 SP7.
An external partner sends an email with one attachment (a simple csv file).
I take "PayloadSwapBean" (with swap.keyName = payload-name) to get the attachment.
Both, the Adapter-Specific Message Attributes indicator and the Variable Transport Binding indicator are set.
I set the mail package format indicator too.
What I need is the sender, receiver and subject of the mail plus the attachment.
Unfortunately it is not possible to read in the email with this configuration - I get an error.
If I unset the Variable Transport Binding indicator - I get the email but without "sender, receiver and subject" in "SHeaderFROM, SHeaderTO, SHeaderSubject". The "mail package" is overwritten by the attachment.
Is it a problem of the namespace "http://sap.com/xi/XI/System/Mail"?
Do I have to define this namespace or do I have to import a content (SAP BASE 700, SP7 is imported)?
Please help...
Regards
Wolfgang

Hi Wolfgang,
I hope it is not due to the namespace.
This might help you.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9e6c7911-0d01-0010-1aa3-8e1bb1551f05
Need some Guide regarding Configuration of Sender Mail Adapters....
Regards
Agasthuri Doss
Message was edited by: Agasthuri Doss Baladandapani

Usage of Variable Transport Binding(Receiver SOAP adapter) in multimapping

Hi All,
Mentioned below is the flow of the scenario that I am facing issues with:
ECC -> PI (A) -> PI (B) - Receivers(1,2,3..n)
I am working on PI(A).
An Idoc containing multiple Plants is triggered which is mapped to an XML in PI(A).
Depending on the number of Plants in the Idocs, that many XMLs are created in PI(A) using multimapping.
These XMLs are then sent to PI(B) which would route it to different receivers.
But PI(A) should send the party name to PI(B) for routing.
For this I am using dynamic configuration. If there are 'N' party names based on 'N' plants, always the last part name is being sent to PI(B).
Is it possible to send all the party names associated with each XML(/plant) without overriding?
As mentioned in the below table, an Idoc is triggered with 3 Plants. 3 XMLs are generated each for a different party. But only the last party i.e. C is being sent to PI(B) using dynamic configuration overriding A and B.
Plant
Party Name
Output
1
A
2
B
3
C
C
Please help me to resolve this issue.
Regards,
Vishal

Hello,
DC is not supported in multimapping.
But, where exactly u want to send the party name? In the xml file u want that party name to be there?
If yes, then there are 2 options either use AM as shown below or u can use variable substitution (search SDN u will find quite a few blogs/wiki on the same)
A new approach: Multi-mapping Dynamic Configuration using a generic custom module
Thanks
Amit Srivastava

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)

SOAP Sender Web Service Authenication

Dear Experts,
Is there a way to authenticate a web service call from a third party system to local (to the company) De-central adapter. I would like to embed the required username and password in the SOAP call. I know it can be done in the URL of a HTTP request but can it be done by customising the SOAP header ?
Many thanks
Mark

Hi,
If user name is passed in header within standard field 'sap-user' in case of sender SOAP adapter, it can be read using DynamicConfiguration.
Remote User SRemoteUser
Remote Host SRemoteHost
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/SOAP","SRemoteUser");
String userName = conf.get(key);
Further you can map this retrieved value to required field from target structure.
Hope this explanation helps.
To store adapter attributes in the message header of the XI message, set the Set Adapter-Specific Message Attributes indicator.
The following attributes are added to the XI message header if the sender makes them available, and if the Variable Transport Binding indicator is set. SRemoteUser and SRemoteHost .
You can check the originating user and Host in mapping and you may decide not to answer to the soap call .Means fails the mappings
http://help.sap.com/saphelp_nw04/helpdata/en/fc/5ad93f130f9215e10000000a155106/content.htm
Also see
Security Settings for the Sender SOAP Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/1f/7e2441509fa831e10000000a1550b0/content.htm

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

Variable Transport Parameters in Mail Sender

Did anyone ever successfully use the "Variable Header XHeaderName1" in the mail sender adapter (IMAP4)?
We have two mail sender channels which require a slightly different mapping. My idea was to define a value for the field "Variable Header XHeaderName1" and evaluate that in the mapping. But the value is not passed into the SOAP header, I can configure what I want. I turned on "Adapter spec.attributes" and "Variable Transport...".
So I cannot access the field value in the mapping.
Now I evaluate the dynamic configuration field "SUser", that works, but that's only a workaround.
So either this is a bug in the system (XI 3.0 SP 21) or the documentation is wrong.
We are using an attachment, is that the problem ? "Use Mail package" off/on does not change anything.
Any ideas ? No general links to the documentation please.
CSY
Edited by: Christian Sy on Aug 15, 2008 8:48 AM

I think the DynamicConfigurationBean would help in this scenario.
You can assign a constant value in sender channel and use that constant for the determination of the mapping.
Regards
Stefan

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.

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

Axis SOAP sender failed PI7.11

Send :
<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:Body>
          <m:add xmlns:m="http://DefaultNamespace" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
               <i1 xsi:type="xsd:int">1</i1>
               <i2 xsi:type="xsd:int">2</i2>
          </m:add>
     </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
to   Axis SOAP
http://netwavetest:8080/axis/services/Calculator
get
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
     <soapenv:Body>
          <ns1:addResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://DefaultNamespace">
               <addReturn xsi:type="xsd:int">3</addReturn>
          </ns1:addResponse>
     </soapenv:Body>
</soapenv:Envelope>
But send to XI
http://netwavetest:50000/XIAxisAdapter/MessageServlet?senderParty=&senderService=DEMO&receiverParty=&receiverService=&interface=add1&interfaceNamespace=http://soap/axis
get error in cc:
message not processed: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Application:EXCEPTION_DURING_EXECUTE:
I tried Axis(http) and SOAP(http), none works.
I used XMLspy, and I did login when I post SOAP to XI.
When I try this scenario in PI 7.0 system, I got the same error.
I have no idea now.
Thanks for your time.

It makes sense.
When I used Axis SOAP sender adapter, got the first error.
When I used SOAP sender adapter, got the second error.
WSDL from PI ID.
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions name="add1" targetNamespace="http://soap/axis" xmlns:p2="http://netwavetest:8080/axis/services/Calculator" xmlns:p1="http://soap/axis" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<wsdl:documentation/><wsp:UsingPolicy wsdl:required="true"/><wsp:Policy wsu:Id="OP_add1"/>
<wsdl:types><xsd:schema targetNamespace="http://netwavetest:8080/axis/services/Calculator" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://netwavetest:8080/axis/services/Calculator">
<xsd:element name="addRequest" type="addRequest" xmlns=""/>
<xsd:element name="addReturn" type="xsd:int"/></xsd:schema>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:complexType name="addRequest"><xsd:sequence>
<xsd:element name="i1" type="xsd:int"/><xsd:element name="i2" type="xsd:int"/></xsd:sequence></xsd:complexType></xsd:schema></wsdl:types>
<wsdl:message name="p2.addRequest"><wsdl:documentation/>
<wsdl:part name="addRequest" type="addRequest" xmlns=""/></wsdl:message>
<wsdl:message name="p2.addResponse"><wsdl:documentation/>
<wsdl:part name="addReturn" type="xs:int" xmlns:xs="http://www.w3.org/2001/XMLSchema"/></wsdl:message>
<wsdl:portType name="add1"><wsdl:documentation/><wsdl:operation name="add1">
<wsdl:documentation/><wsp:Policy><wsp:PolicyReference URI="#OP_add1"/></wsp:Policy>
<wsdl:input message="p1:p2.addRequest"/><wsdl:output message="p1:p2.addResponse"/>
</wsdl:operation></wsdl:portType><wsdl:binding name="add1Binding" type="p1:add1">
<wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"/><wsdl:operation name="add1">
<wsdlsoap:operation soapAction="http://sap.com/xi/WebService/soap1.1" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"/>
<wsdl:input><wsdlsoap:body use="literal" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"/></wsdl:input>
<wsdl:output><wsdlsoap:body use="literal" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"/></wsdl:output></wsdl:operation>
</wsdl:binding><wsdl:service name="XI_6ef9141ba9383daf91ba52b9fdfd85e9_Service"><wsdl:port name="HTTP_Port" binding="p1:add1Binding">
<wsdlsoap:address location="http://netwavetest:50000/XISOAPAdapter/MessageServlet?senderParty=&senderService=DEMO&receiverParty=&receiverService=&interface=add1&interfaceNamespace=http%3A%2F%2Fsoap%2Faxis" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"/></wsdl:port>
<wsdl:port name="HTTPS_Port" binding="p1:add1Binding">
<wsdlsoap:address location="https://netwavetest:50001/XISOAPAdapter/MessageServlet?senderParty=&senderService=DEMO&receiverParty=&receiverService=&interface=add1&interfaceNamespace=http%3A%2F%2Fsoap%2Faxis" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"/></wsdl:port></wsdl:service></wsdl:definitions>
And how to set rpc-styled or document-styled, in PI adapter or Axis runtime?

Change webservice client transport/binding

I am migrating web service client generated by clientgen from 7.0 to 8.1. 7.0 client uses weblogic.webservice.binding.soap.HttpClientBinding which works directly with sockets and is fine for me. But 8.1 uses weblogic.webservice.binding.http11.Http11ClientBinding which works with java.net.HttpUrlConnection that requires proxy being set in java system property which is system wide and I cannot use that. HttpClientBinding uses system wide setting as well but it is webservice client specific at least.
So I want use HttpClientBinding in 8.1 as well. I am able to change it by calling
BindingFactory.getInstance().register("http11", weblogic.webservice.binding.soap.HttpClientBinding.class);
but this is again system wide setting which I am afraid of because of influencing other WS clients not using proxy. Is it possible to do it somehow in per client basis?
Injecting custom Binding info with getTransport returning "http" or in some other way.
Alternatively any way allowing me to set proxy on per WS client is solution for me

Hi Dahran,
SCC7 is for post import.
first you have to import the transports generated during the export into your client.
STMS. Go to your import queue and choose in the menu
Extras ->Other requests add
Fill in the transport number of one of the generated transports during the export. (something like <SID>KX0000x)
<b>After</b> the import you have to perform the SCC7

XI3 SOAP sender and Receiver

Hi
I am stuck with a connecting to scenarios using SOAP channel. In short there is one business scenario that based on some conditions must start other scenarios (each one built around one business process). I am trying to send asynchronous SOAP message within the same XI and treat it as a External XI system to start another Business Scenario (using XI adapter does not work as the system discovers the message as being in a loop).
Everything would be fine if there would be 1 target scenarios but I have 1:n. For asyncronous transport I have defined different Message Interfaces to be used for on each case. So XI should determine the right business process based on the message interface that uses the communication channel.
So I have configured a SOAP sender and a receiver channel. As I understood from SOAP adapter FAQ I checked "Use Encoded Headers" and "Use Query String" for both - sender and receiver channel. And ofcourse receiver channel is pointed to http://:/XISOAPAdapter/MessageServlet?channel=:{system name}:{receiver channel name} but when I start the initiating scenario the asyncronous message is sent of but nobody is catching it.
In RWB Message monitoring / adapter engine I found the the message receives an exeception:
SOAP: response message contains an error XIServer/UNKNOWN/ModuleUnknownException -
com.sap.aii.af.mp.module.ModuleException: either no channelID
specified or no channel found for the specified party, service, and channel name,
MessageServlet(Version $Id: //tc/aii/30_REL/src/_adapters
/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#15 $) at
com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:427) 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:401) at
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl....
handleRequest(HttpHandlerImpl.java:266) at
com.sap.engine.services.httpserver.server.RequestAnalizer....
startServlet(RequestAnalizer.java:387) at
com.sap.engine.services.httpserver.server.RequestAnalizer....
startServlet(RequestAnalizer.java:365) at
com.sap.engine.services.httpserver.server.RequestAnalizer....
invokeWebContainer(RequestAnalizer.java:944) at
com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266) at
com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at
com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160) 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)
Any ideas... how to make XI to send SOAP messages so that the same XI system would be able to pick them up?
Or what have I done wrong?
Best wishes,
Heiko

hi,
What is the format that u are using for the sender URL....The error message you are getting either because the names that you have mentioned in the sender URL are wrong or the URl format itslef is wrong.....if the format is the one that you have mentioned in the first post then it is not the desired format.
Use the following format to create the URL to send the request:
http://<servernameORserverIPaddress>:<portNumber>/XISOAPAdapter/MessageServlet?channel=:<senderservice>:<snederCCname>&version=3.0&Sender.Service=<senderservice>&Interface=<IRnamespace>%5E<senderMI>
Replace
with
& amp;
(no space inbetween the two words) in the above URL.
How to configure SOAP communication channels (sender and receiver) so that two XI instances could communicate and (more important) use different message interfaces on the same channel?
While creating a Receiver communication channel there is no need to specify the interface name and hence it can be used in different scenarios....however a sender communication needs the sender interface to be specified (as in SAP XI.....not in SAP PI).....so a sender channel can be used in different scenarios but with only the same interface.....
Regards,
Abhishek
Edited by: abhishek salvi on Feb 17, 2009 2:50 PM

Variable Transport Binding - Soap Sender

Similar Messages

Maybe you are looking for