SOAP Action in Logical port config

Hi,
I created a client proxy for an external web service, and developed a client application to use this proxy. I am trying to set up a logical port for it. However, in transaction LPCONFIG, it seems that the field SOAP Action is not persistent anywhere since once I leave the transaction screen and reopen it, the parameter disappears. This caused me an error when I use the proxy saying a valid action parameter needs to be set.
Anyone has any idea about this? Thanks a lot for your help!
Regards,
Hart

Hi Thomas,
Thanks a lot for your help! Actually I resolved the issue I had before and now it works well. The problem I had was I created the client proxy based on a local wsdl file, and the proxy generation somehow did not add the soap actions as operations so in LPCONFIG I could not see any operations. The SOAP Action field is open for input, but it cannot be saved.
I regenerated the proxy using wsdl directly from a URL, and now I can see all my actions/operations in LPCONFIG and of course the action field can now be saved (associated to the selected operations).
Regards,
Hart

Similar Messages

Define Logical Port and Back-End Destinations for ESOA use of this config

Hi,
Please let me know what is the use of this config I am not able to get a documentation.
Define Logical Port and Back-End Destinations for ESOA

Hi Autobots,
Even I am looking for the same information. Did u get some headstart into the matter?
Pl provide me with the inputs too.
Cheers
Nikhil

WSDL without SOAP Action (BTS.Operation?)

Hi
I got a WSDL without SOAP Action specified. I'm able to generate XSDs, set up a send port and call an operation. Since I was calling a single web operation then I set up my Action at send port WCF config to be
http://localhost/CarService/updateLocation, i.e. [service URL]/[operation name].
My problem now is that I need to call two separate operations from that web service by using BTS.Operation property; one is still
updateLocation and the other one is removeLocation. How can I specify Action in send port WCF config when SOAP Action is missing in WSDL? I tried specifying different values but none of them were successful.
Ex.
<BtsActionMapping>
<Operation Name="updateLocation" Action=""/>
<Operation Name="removeLocation" Action=""/>
</BtsActionMapping>
Kind regards
A.H.

Hi,
How are going to call these web-methods. Are your going to call these two methods from the same Orchestration. Or are you going to call these methods from two different send ports by content-based routing (send port filter).
In BizTalk, this instruction (SOAP Action) is set by assigning a value to WCF.Action context property. You can specify WCF.Action property in two ways:
Single Action Format
Action Mapping Format
The way you have been calling before "http://localhost/CarService/updateLocation" is called Single Action Format. Now you have use the Action mapping format.
In Action mapping format, you map the WCF.Action context is “mapped”/resolved from another context property BTS.Operation. So if you call from the Orchestration, set the BTS.Operation approirately to resolve the URL in the config. i.e if you have config
like this:
<BtsActionMapping>
<Operation Name="updateLocation" Action="http://localhost/CarService/updateLocation"/>
<Operation Name="removeLocation" Action="http://localhost/CarService/removeLocation"/>
</BtsActionMapping>
In your orchestration, if you set the WCF.Action to "removeLocation", WCF.Action would be resolved to "http://localhost/CarService/removeLocation". In orchestration, you set the
WCF.Action context, by setting the logical send port's operation name. Refer to this article for more info:http://www.fortuvis.com/blog/biztalk-and-wcf-soap-action/
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful.

Error in logical port while connecting to SAP CRM cloud

Dear Members,
I have created a logical port manually to connect to SAP CRM cloud system. But when I ping the web service I am getting below error. Please let me know how to solve this error.
SRT Framework exception: Service Ping ERROR: Error when calling SOAP Runtime functions: SRT: Couldn't create Object: ("ICF Error when creating HTTP client object by Config for URL <WSDL URL>

Hello Nihar,
The error message indicates the HTTP client object cannot be created by the given URL. Please check if your URL is correct.
You also need to check what protocol is used, HTTP or HTTPS, and ensure the protocol is active in your local ABAP system as well. You can check them by t-code SMICM->Goto->Services.
Regards,
Robert

How to change a Logical Port URL-Destination/Endpoint at Runtime

Hi,
i am looking for a way to change the endpoint for a webservice-call without redeploying my application. (I am using a standalone-proxy).
In the SAP-Help from NetWeaver 2004s I found the following hint:
http://help.sap.com/saphelp_nw04/helpdata/en/9f/c487d701c7214db8ca7a741ba3c9d0/frameset.htm
Configuring Logical Ports:
Logical ports (LPs) contain the configuration of the client-side SOAP runtime, such as the access URL or security settings. These are required if Web service calls are executed using proxies.
The Web service port is part of the WSDL description. This defines a URL where the service is to be called. As a rule, this URL is generated directly into the proxy object. However, this can cause problems whenever the proxy is transported into a system landscape (for example, from the test system into the productive system). In this case, the proxy would still attempt to call the Web service on the test server although the proxy should point to the productive system. The proxy could be re-generated or the coding could be changed manually. Due to the risk of errors with this method, the configuration data in the SAP Web Service Framework is separated from the implementation. After transport or re-deployment of the proxy, the URL and other important parameters can be adapted using a simple editor.
The LPs provided correspond to the Web service configurations created for the Web service.
My Question:
Where can I change the URL of the corresponding logical port at runtime?
I don't want to redeploy my application !!!
I want to change the endpoint-destination at runtime!!!
In the Visual Administrator I can see the webservice in the "Web Services Container Service Administration". I also can see the different ports from the WebService-Configuration I made.
http://help.sap.com/saphelp_nw04/helpdata/en/9f/c487d701c7214db8ca7a741ba3c9d0/frameset.htm
But it is not possible to change the "target adresses"!
Can anybody help me finding a solution concerning my question?
Regards
Steffen

You can include below method in your code and call it.
private void UpdateConfig(string key, string value, string fileName)
var cFile = ConfigurationManager.OpenExeConfiguration(fileName);
cFile.AppSettings.Settings[key].Value = value;
cFile.Save();
Here fileName is the full path + application name (eg: c:\project\WinApp.exe)
Adnan Amin MCT, SharePoint Architect | If you find this post useful kindly please mark it as an answer :)

PI 7.1 multiple operation interface and SOAP action doubt

Hi guys,
I'm trying to implement a scenario, where I have a single outbound (sender side) interface with multiple operations (as 7.1 allows). The problem is afetr the WSDL generation I have the same SOAP action for each operation. Standardly there should be unique SOAP action per operation, but how to achieve it?
And another question - is it ok to use SOAP sender adapter for this interface?
Thanks for your help,
Olian

Hi Olian,
>>The problem is afetr the WSDL generation I have the same SOAP action for each operation. Standardly there should be unique SOAP action per operation, but how to achieve it?
I dont think you need to have separate action, the Operation Name inside Service Interface differentiate the Request type. Also when you send SOAP message to PI, you are sending it to either
http://host:port /XISOAPAdapter/MessageServlet?channel=p:s:c
(where host is the host name, port is the port number, p is the optional party name, s the service name, and c is the channel name, respectively.The URL given above is valid for 3.0/7.0/7.1.)
or * http://host:port /XISOAPAdapter/MessageServlet?senderParty=FP& senderService=FS& interface=IF&receiverParty=TP&receiverService=TS&interfaceNamespace=IFNamespace *
(7. 10 onwards a new URL syntax is also valid and is recommended to be used. )
>>And another question - is it ok to use SOAP sender adapter for this interface?
Yes
Regards
Suraj
Edited by: S.R.Suraj on Sep 8, 2009 6:23 AM

Example wsdl and logical port for consumer proxy anyone ?

Hi,
Could please somebody give me an example of external WSDL file and logcial port created for the WSDL file in SOAMANAGER ?
I need to create manually logical port for my consumer proxy and I am missing something because my logical port is not active.
Any example is more than welcome.
I need to know how to populate fields manually on the following tabs based on the info in a WSDL file:
Consumer Security Additional Information Web Service Addressing Messaging Transport settings Message Attachments Operation specifi
Thanks and Regards
Agnieszka
The message, I am getting, when creating logical port is:
Operation 'SrtFmStatefulTf' not found [NS: 'urn:sap-com:document:sap:soap:functions:mc-style']
I think that maybe something is wrong with my wsdl.
Edited by: Agnieszka Domanska on Nov 17, 2010 5:41 PM

Hi Milan,
this kind of error occurs when there is no service and end point description in the WSDL of provider who's service you are trying to consume using Consumer Proxy.
Just open the provider's WSDL URL that you have given while creating Logical port for the consumer proxy and check if service and end point exists there.
Thanks
Sunil Singh

Error when generating logical port in SOAMANAGER

Hi,
When generating the logical port in SOAMANAGER transaction I get an error message 'SRT Framework exception: Uninstantiated object "subject sidl service" in method IF_SRT_WSP_CONFIG_SIDL~CREATE_CLNT_CFG_FROM_WSDL_D of class CL_SRT_WSP_CONFIG_SIDL'.
Does anyone know what the problem might be?
Thans in advance.
Kind regards,
Amel Alic

Hi,
I, by mistake, reported the same problem; however the problem is that I referenced the WSDL without endpoint (WSDL service name....). I took this URI from Servces Registry, but was wrong (altough on the SR there were a valid binding+endpoint).
I put the right IRU pointing to the compete Service COntract (with endpoint reference), and it worked.
If you did't solve the problem, try to opern on the browser the URI you are referring to, and see, at the end if it contains the endpoint like that:
<wsdl:service name="zsMy2ndCodeFirstWebService">
<wsdl:port name="zsMy2ndCodeFirstWebServiceBinding" binding="tns:zsMy2ndCodeFirstWebServiceBinding">
<soap:address location="http://xyz:8000/sap/bc/srt/rfc/sap/.....my service operation..." />
</wsdl:port>
</wsdl:service>
Hope this help.
Regards
Roberto

Point a logical Port in the backend to XI

Hi friends,
how do i point a logical port in backend to XI,how do i derive the XI url to be
pointed.
regards
kaushik

Are you asking about setting the Port in WE21?
This just points to a standard RFC ABAP Connection to the XI System.
Or are you asking about the integration engine config in SXMB_ADM? - again, it points to SM59 HTTP Connection to ABAP System (the port for this would be 80<sysno>)

Web service invocation problem on host hostname and port 8000 protocol : http logical port name : LP_WS_SMDAGENT_MONITORING

hello colleagues,
In the phase Connect Diagnostics dont show the Agent available in SLD, but when go to SLD i have the agents,
Error,
Connect Diagnostics Agent
The table does not contain any data
Agent availables in all SLD
SOAP:1.007 SRT: Unupported xstream found: ("HTTP Code 401 : Unauthorized")
Web service invocation problem on host hostname and port 8000 protocol : http logical port name : LP_WS_SMDAGENT_MONITORING
Thanks

OK, then pls follow below steps;
- Go to step 'Create Users' in solman_setup System Preparation scenario and make sure the user SM_INTERN_WS has a green status. Use the 'Test Login' button to make sure the user is not locked and has correct credentials maintained in solman_setup
- Immediately after checking the user status, navigate to Configure Connectivity->Enable Web Services and execute again the 'Create Logical Ports' automatic activity, in order to propagate the correct credentials to the Logical Port definitions.
- If the above operation is not successful, repeat the two steps above, providing a different user Id in 'Create Users' step, eg SM_INTERN_W1. This will prevent situations where the user gets locked by Logical Ports using an obsolete password.
Let me know the results.
Regards,
Vivek

Invalid SOAP action when using java ws WebService

Hi all,
this is a slightly more detailed error for a problem i posted recently. I am connecting to a web service that was generated from WSDL. It has two methods "HelloWorld" and "HelloSayFirstName". As defined in the WSDL, the methods use the SOAP action document style. I want to add a cookie to the http header, so after the port is created, I use the following to add the header to the requestContext:
 BindingProvider bindingProvider = (BindingProvider) servicePort;
 Map<String, Object> requestContext = bindingProvider.getRequestContext();
 List<String> cookies = new ArrayList<String>();
 cookies.add("mycookie=mytoken");
 HashMap<String, List<String>> httpHeaders = new HashMap<String, List<String>>();
 httpHeaders.put(HTTPConstants.HEADER_COOKIE, cookies);
 requestContext.put(MessageContext.HTTP_REQUEST_HEADERS, httpHeaders);
This works when I call the first method (HelloWorld) - the first activity message sent to the server contains the following:
<HttpRequest>
<Method>POST</Method>
<QueryString></QueryString>
<WebHeaders>
<Cache-Control>no-cache</Cache-Control>
<Connection>keep-alive</Connection>
<Pragma>no-cache</Pragma>
<Transfer-Encoding>chunked</Transfer-Encoding>
<Content-Type>text/xml; charset=UTF-8</Content-Type>
<Accept>*</Accept>
<Cookie>mycookie=mytoken</Cookie>
<Host>exampleHost</Host>
<User-Agent>Java/1.5.0_14</User-Agent>
<SOAPAction>"http://tempuri.org/IMyService/HelloWorld"</SOAPAction>
</WebHeaders>
</HttpRequest>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<s:Header xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<To s:mustUnderstand="1" xmlns="http://schemas.microsoft.com/ws/2005/05/addressing/none">http://exampleHost/WebServices/WCFService/Service.svc</To>
<Action s:mustUnderstand="1" xmlns="http://schemas.microsoft.com/ws/2005/05/addressing/none">http://tempuri.org/IMyService/HelloWorld</Action>
</s:Header>
<soap:Body>
<HelloWorld xmlns="http://tempuri.org/" xmlns:ns2="http://schemas.datacontract.org/2004/07/" xmlns:ns3="http://schemas.microsoft.com/2003/10/Serialization/">
<myValue1>world</myValue1>
</HelloWorld>
</soap:Body>
</soap:Envelope>
However, after this method, the httpHeaders in the requestContext object have been updated to include the "Accept" header and the "SOAPAction" header - which is the incorrect action! Now, when I call the method "HelloSayFirstName" I get the following:
<HttpRequest>
<Method>POST</Method>
<QueryString></QueryString>
<WebHeaders>
<Cache-Control>no-cache</Cache-Control>
<Connection>keep-alive</Connection>
<Pragma>no-cache</Pragma>
<Transfer-Encoding>chunked</Transfer-Encoding>
<Content-Type>text/xml; charset=UTF-8</Content-Type>
<Accept>*</Accept>
<Cookie>mycookie=mytoken</Cookie>
<Host>exampleHost</Host>
<User-Agent>Java/1.5.0_14</User-Agent>
<SOAPAction>"http://tempuri.org/IMyService/HelloWorld"</SOAPAction>
</WebHeaders>
</HttpRequest>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<s:Header xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<To s:mustUnderstand="1" xmlns="http://schemas.microsoft.com/ws/2005/05/addressing/none">http://exampleHost/WebServices/WCFService/Service.svc</To>
<Action s:mustUnderstand="1" xmlns="http://schemas.microsoft.com/ws/2005/05/addressing/none">http://tempuri.org/IMyService/HelloWorld</Action>
</s:Header>
<soap:Body>
<HelloSayFirstName xmlns="http://tempuri.org/" xmlns:ns2="http://schemas.datacontract.org/2004/07/" xmlns:ns3="http://schemas.microsoft.com/2003/10/Serialization/">
<dataContractValue></dataContractValue>
</HelloSayFirstName>
</soap:Body>
</soap:Envelope>
It seems that the SOAPAction in the http header and the soap header is incorrect. Is there any reason why the requestContext would keep hold of the action that was previously called, and not use the new action? I'm stumped here - any help would be greatly appreciated.
Cheers.

Does not only happen when using JAX-WS.
the following servlet code is enough to reproduce the problem :
protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
response.setContentType("text/xml;charset=\"utf-8\"");
It only occurs on 10.1.3.4.0 (works fine on 10.1.3.3.0 and 11.1.1.1.0 TP4)
Regards

SOAP ACTION IN SOAP ADAPTER and PROGRAM IF IN RFC COMMUNICATION CHANNEL

Hi Gurus,
Please Explain me what is SOAP action in soap adapter what is the use of it.
What is the Program ID in the RFC communication channel and what is the use of it.
Please tell me in Detail.
Thanks and Regards,
RAM.

Hi,
Please Explain me what is SOAP action in soap adapter what is the use of it.
As of W3C definition:
The SOAPAction HTTP request header field can be used to indicate the intent of the SOAP HTTP request. The value is a URI identifying the intent. SOAP places no restrictions on the format or specificity of the URI or that it is resolvable. An HTTP client MUST use this header field when issuing a SOAP HTTP Request.
The presence and content of the SOAPAction header field can be used by servers such as firewalls to appropriately filter SOAP request messages in HTTP. The header field value of empty string ("") means that the intent of the SOAP message is provided by the HTTP Request-URI. No value means that there is no indication of the intent of the message.
Putting things simple, this is an identifier of an operation that you want to execute in the web service (as one web service can offer multiple actions).
What is the Program ID in the RFC communication channel and what is the use of it.
Again, this is an identifier for both: RFC sender and receiver systems. It tells the receiver where to listen for connections, and the sender - where to send the data. It works a little bit like a port number in HTTP communication, but with less restrictions.
Hope this helps,
Greg

Is SOAP Adapter Action field can contain 2 or more "SOAP Actions"

Hi All,
I have following scenario:-
Step 1. Webmethod(sent price querry with material no)->R/3(search price from tables)
step 2. R/3(sent price)->Webmethod
step 3. Webmethod(sent quantity)->R/3(document created in sap)
step 4. R/3(sent confirmation doc no/error)->Webmethod
Q1 How can i implement above scenario in with one URL Webmethod????
(URL:http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel)
Q2 Is it possible with one (Receiver SOAP adapter->Conversion Parameters->SOAP Action) field can contain more than 1 SOAP Action......??????
With more than one message interfaces (inbound synchronous) in one scenario
Q3 Or I have to design two scenarios with two URL's????with different message interfaces (inbound synchronous) 
Q4 Or I use Sender(SOAP) Reciver(Rfc Adapter) in abave case??? With more than one message interfaces (inbound synchronous) in one scenario
Thanks & Regards
Message was edited by: Umesh R

When your scenario consists of sync calls, you have only to define SOAP sender channels. The best approach is to create two channels to keep the reference from interface to channel unique.
For the sync response message you do not need and communication channel (and no SOAP action).
Regards
Stefan

Calling a business service based on operation-soap action in Proxy service

Hi,
I have a requirement in which I have to call a business service based on operation-soap action defined in Proxy service wsdl.
Like in below mentioned wsdl GetPartCostDelta and GetCurrencyList operations are there.But which ever operation I select,It just goes to one business service.
Is there any way,I can route to some another business service based on the soap action
proxy service WSDL
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:ewopcd="urn:com:gm:gpd:schema:ewopartcostdelta" xmlns:gen="urn:com:gm:gpd:schema:genericfault" xmlns:tns="urn:com:gm:gpd:services:ewopartcostdeltaservice" targetNamespace="urn:com:gm:gpd:services:ewopartcostdeltaservice">
 <wsdl:types>
 <xs:schema>
 <xs:import namespace="urn:com:gm:gpd:schema:ewopartcostdelta" schemaLocation="ewocostdelta.xsd"/>
 <xs:import namespace="urn:com:gm:gpd:schema:genericfault" schemaLocation="servicefault.xsd"/>
 </xs:schema>
 </wsdl:types>
 <wsdl:message name="EWOCurrencyListRequest">
 <wsdl:part name="CurrencyListRequest" element="ewopcd:EWOCostDeltaInput"/>
 </wsdl:message>
 <wsdl:message name="EWOCurrencyListResponse">
 <wsdl:part name="CurrencyListResponse" element="ewopcd:EWOCurrencyList"/>
 </wsdl:message>
 <wsdl:message name="EWOPartCostDeltaRequest">
 <wsdl:part name="PartCostDeltaRequest" element="ewopcd:EWOCostDeltaInput"/>
 </wsdl:message>
 <wsdl:message name="EWOPartCostDeltaResponse">
 <wsdl:part name="PartCostDeltaResponse" element="ewopcd:EWOCostDeltaResult"/>
 </wsdl:message>
 <wsdl:message name="EWOPartCostDeltaServiceFault">
 <wsdl:part name="PartCostDeltaServiceFault" element="gen:ServiceFault"/>
 </wsdl:message>
 <wsdl:portType name="EWOPartCostDeltaPortType">
 <wsdl:operation name="GetCurrencyList">
 <wsdl:input name="EWOCurrencyListRequest" message="tns:EWOCurrencyListRequest"/>
 <wsdl:output name="EWOCurrencyListResponse" message="tns:EWOCurrencyListResponse"/>
 <wsdl:fault name="EWOPartCostDeltaServiceFault" message="tns:EWOPartCostDeltaServiceFault"/>
 </wsdl:operation>
 <wsdl:operation name="GetPartCostDelta">
 <wsdl:input name="EWOPartCostDeltaRequest" message="tns:EWOPartCostDeltaRequest"/>
 <wsdl:output name="EWOPartCostDeltaResponse" message="tns:EWOPartCostDeltaResponse"/>
 <wsdl:fault name="EWOPartCostDeltaServiceFault" message="tns:EWOPartCostDeltaServiceFault"/>
 </wsdl:operation>
 </wsdl:portType>
 <wsdl:binding name="EWOPartCostDeltaBinding" type="tns:EWOPartCostDeltaPortType">
 <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
 <wsdl:operation name="GetCurrencyList">
 <soap:operation soapAction="GetCurrencyList" style="document"/>
 <wsdl:input>
 <soap:body use="literal"/>
 </wsdl:input>
 <wsdl:output>
 <soap:body use="literal"/>
 </wsdl:output>
 <wsdl:fault name="EWOPartCostDeltaServiceFault">
 <soap:fault name="EWOCostDeltaServiceFault" use="literal"/>
 </wsdl:fault>
 </wsdl:operation>
 <wsdl:operation name="GetPartCostDelta">
 <soap:operation soapAction="GetPartCostDelta" style="document"/>
 <wsdl:input>
 <soap:body use="literal"/>
 </wsdl:input>
 <wsdl:output>
 <soap:body use="literal"/>
 </wsdl:output>
 <wsdl:fault name="EWOPartCostDeltaServiceFault">
 <soap:fault name="EWOCostDeltaServiceFault" use="literal"/>
 </wsdl:fault>
 </wsdl:operation>
 </wsdl:binding>
 <wsdl:service name="EWOPartCostDeltaService">
 <wsdl:port name="EWOPartCostDeltaPort" binding="tns:EWOPartCostDeltaBinding">
 <soap:address location="https://localhost/EWOPartCostDelta"/>
 </wsdl:port>
 </wsdl:service>
</wsdl:definitions>

Did you try using the Operational branching node of OSB?
You have copy the operation name from the inbound variable and populate the SOAP Header with that value into the SOAPAction tag.I think this will work.
Thanks,
Prabu

How can I check the called SOAP-action

Hi,
our scenario is IDOC - XI - SOAP (based on a wsdl). I've imported the wsdl as external definitions. The I implement all necessary interfaces, mappings, .... When I'm sending any IDOCs, I see the right interface, but I can't check the right SOAP-Action. The Receiver firm means, that the wrong function will be called.
Have you any ideas?
Thanks
Matthias

Hi Matthias,
the only way to check the SOAP Action is using an HTTP sniffer. Or you write a simple Java program that listens to a port and writes incoming data to a file.
But I have never heard about the problem, that the SOAP action is not correct. Make sure, that the correct receiver channel is used, the channel is activated and the cache refreshed.
Regards
Stefan

SOAP Action in Logical port config

Similar Messages

Maybe you are looking for