Quantcast
Channel: SCN: Message List - Service-Oriented Architecture (SOA) and SAP
Viewing all 1056 articles
Browse latest View live

Re: Calling .net SOAP web service with user/pass + certificate auth

$
0
0

The problem was related to some network errors.


no wsdl root element set

$
0
0

Hello,

 

I am trying to consume an .net web service. Using no security works. But now we activated SSL and user/pass authentification and i am not able anymore to generate the service. The Report RSSIDL_DESERIALIZE_DEMO shows the following error message:

 

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

 

-<soap:Body>

 

-<soap:Fault>
<faultcode>soap:Server</faultcode>

<faultstring>SIDL/SLIB exception</faultstring>

-<detail xmlns:slibfault="http://xml.sap.com/2005/11/esi/slib/fault/">
<slibfault:timestamp>Thu, 18 Jul 2013 12:32:50 GMT</slibfault:timestamp>
-<slibfault:exception>
<slibfault:text>Kein WSDL-Root-Element gesetzt</slibfault:text>
<slibfault:positionprogram="CL_SRT_WSP_CONFIG_SIDL========CP" include="CL_SRT_WSP_CONFIG_SIDL========CM011" line="30" />

</slibfault:exception>

</detail>

</soap:Fault>

</soap:Body>

</soap:Envelope>

 

 

But we have a root element and when I see the WSDL in the i-browser I am able to spin it up and down.

Like I told the .net WSDL changed but I cannot see which element is wrong:

 

<wsdl:definitions name="MasterDataService" targetNamespace="http://tempuri.org/">

    <wsp:Policy wsu:Id="basicHttpBindingEndpoint_policy">

      <wsp:ExactlyOne><wsp:All><http:NegotiateAuthentication/>

      <sp:TransportBinding><wsp:Policy><sp:TransportToken>

      <wsp:Policy>

<sp:HttpsToken RequireClientCertificate="false"/>

</wsp:Policy>

</sp:TransportToken>

<sp:AlgorithmSuite>

<wsp:Policy>

<sp:Basic256/>

</wsp:Policy>

</sp:AlgorithmSuite>

<sp:Layout>

<wsp:Policy>

<sp:Strict/>

</wsp:Policy>

</sp:Layout>

</wsp:Policy></sp:TransportBinding>

<wsaw:UsingAddressing/>

</wsp:All>

</wsp:ExactlyOne>

</wsp:Policy>

<wsdl:types>

 

When I download the WSDL and its XSD-files and exchange the policy-area of the wsdl with the old one without security. I am able to see the WSDL in the report without any problems.

Did someone ever has had a similar problem and knows how to fix it? Searching in google and the scn didn't bring new informations. I also could not find any sap notes that describe this problem. What is the element that is wrong?

 

Greetings, Vanessa

Re: no wsdl root element set

$
0
0

If I delete the sp:TransportBinding - Section... I can see the WSDL file with the mentioned report. Does it mean that sp:TransportBinding is microsoft specific and not supported by SAP?

Re: Incorrect path prefix in HTTP destination generated from SOAMANAGER

$
0
0

Gov, I was hoping that there was a better solution than manually editing the RFC destination. Do you know if this is the SAP recommended solution for this problem?     

Re: SOAP:1.008 SRT: Couldn't create Object

$
0
0

Hi,

 

Please refer SAP Note 510007 .

 

Thank You

Regards

Goverdhan Totawar

Re: Error while parsing wsdl while creating logical port

$
0
0

Hello Rolf,

 

I am currently facing the same problem, Did you solved it ?

 

Thanks for your help.

 

Marc

Error while creating logical port

$
0
0

Hi,

 

I have created a client proxy successfully. Now the issue is with logical port.

 

When I try to create logical port via local file system is giving below error.

 

SRT Framework exception: Initial value "consumer context table" in method IF_SRT_WSP_CONFIG_REGISTRY~CREATE_CONTEXTS_FROM_WSof class CL_SRT_WSP_CONFIG_REGISTRY.

 

Please let me know if any settings needs to be done.

 

 

Thanks,

Sarang

Re: Error while parsing wsdl while creating logical port

$
0
0

sorry Marc,

solved it somehow - but I don't remember details anymore.

Maybe changed the namespace definitions.


Re: Experiences with ES bundle 'Integration of External Warehouse Management System'

$
0
0

Hi Martin,

 

I'm looking at the same challenge. The ES bundle for managing external warehouse is all very IM based wth deliveries and good movments. I'm also looking at a ES repalcement for the external warehouse management scenario based on using the warehouse transfer orders send from SAP to external WMS and updates send back form wms system to confim, or cancel or update.

 

this scenario is normally based on the idocs wmtord,wmtoco and wmcato but in the scenarios it refers continously to is  the good movement ES

 

any suggestions or are you still waiting for answers ?

Re: Error while parsing wsdl while creating logical port

$
0
0

Hi Rolf,

 

It looks like you are using Internet Explorer 8.0, is this correct? IE8

by default switches off the supply of full file path during file upload.

This is done for security reasons. Full file path is required by our

WSDL library. You can find how to switch it on on the following link:

 

You can find the option by:

Tools=> Internet Options => Security tab => Custom level =>

"Include local directory path when uploading files"

 

2013-07-24 07-56-30 PM.png

 

Thank You

Regards

Goverdhan Totawar

Re: Error while creating logical port

$
0
0

Hi,

 

For Logical Port configuration you have four different options

 

1. WSDL Based Configuration

2. Manual Confiuration

3. Process Integration Runtime

4. Local shortcut Configuration

 

It looks like you have selected WSDL based configuration

 

This means, that the binding and service elements are missing. These are mandatory to

create LP based on the WSDL based configuration(this contains the access URL as well)

 

Please get the binding WSDL of this service and try with that.

 

Alternatively you could do a Manual configuration (Logical Port).

 

Thank you

Regards

Goverdhan Totawar

Re: Logical port creation error through SOAMANAGER

$
0
0

Hi,

 

Try creating Logical Port via Manual Configuration option.

 

Thank You

Regards

Goverdhan Totawar

Re: Web Service Creation (through Dynamic Web Project)

$
0
0

Hello,

 

I know this is horribly old, but I'm facing the same issue.

Anyone know how to solve this?

 

Thanks

Not supported fragments

$
0
0

Hello,

 

I am trying to consume an WCF-Webservice. I am able to create the consumer proxy via https. But when I try to generate the binding it fails. Using the WSDL-Analyse I get the following errors in not supported fragments:

<http:NegotiateAuthentication xmlns:http="http://schemas.microsoft.com/ws/06/2004/policy/http" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:tns="http://tempuri.org/" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract" xmlns:wsa10="http://www.w3.org/2005/08/addressing" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata"/>

 

<sp:TransportBinding xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:tns="http://tempuri.org/" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract" xmlns:wsa10="http://www.w3.org/2005/08/addressing" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata"><wsp:Policy xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xml:base="https://fqdnpath_to_service?WSDL"><wsp:ExactlyOne><wsp:All><sp:TransportToken><wsp:Policy xml:base="https://fqdnpath_to_service?WSDL"><wsp:ExactlyOne><wsp:All><sp:HttpsToken RequireClientCertificate="false"/></wsp:All></wsp:ExactlyOne></wsp:Policy></sp:TransportToken><sp:AlgorithmSuite><wsp:Policy xml:base="https://fqdnpath_to_service?WSDL"><wsp:ExactlyOne><wsp:All><sp:Basic256/></wsp:All></wsp:ExactlyOne></wsp:Policy></sp:AlgorithmSuite><sp:Layout><wsp:Policy xml:base="https://fqdnpath_to_service?WSDL"><wsp:ExactlyOne><wsp:All><sp:Strict/></wsp:All></wsp:ExactlyOne></wsp:Policy></sp:Layout></wsp:All></wsp:ExactlyOne></wsp:Policy></sp:TransportBinding>

 

Unfortunetly I have no glue what is not supported by SAP. Does someone has an idea?

 

In some discussions they say that I have to use another WSDL-file for the binding. But there is no other WSDL-file for the WCF-Webservice. Or do I need to use another file for the binding of the .net webservice?

Re: Error Troubling me Since Two days

$
0
0

Resolvd using :

Transaction SES_ADMIN by defining the index for the Business object.


Re: Message types missing in XI Content for SAP TM

$
0
0

Hi Xiang,

 

We are working on ECC to TM standard interface. I downloaded SWCV

 

SAP TM 1.0 Patch 08 and SAP TM IC 1.0 Patch 08  but i am not able to see source structure in MM and Idoc for the components. My question is what is the exact component we have to download and is there any pre-configuration we have to do before importing the coponent? We are stuck in the middle of the configuration , help will be more appreciable.

 

 

Thanks & Regards,

Ravi.

Web Service: change faultstring in response message

$
0
0

Dear Experts,

 

currently we are setting up interfaces to a third-party system. The third-party system calls SAP Web Services built with SOAMANAGER.

 

When calling an invalid request the error message in the XML faultstring is something like "Processing Error. More details in WS Error Log (transaction SRT_UTIL) by selection with UTC timestamp".

--> In SRT_UTIL error log the Error Message is more detailed such as "Value 20130101 is not a valid date in accord with the XML format for ABAP". Is there a chance to send this instead of the other within the "<faultstring xml:lang="en">" since the third party does not have access to the SAP System?

 

Any help will be greatly appreciated.

 

Kind Regards,

Dirk

Re: Change SOAP Header: Consuming Webservice

$
0
0

Ok ,but what do you do if your header will not fit into the string?  I have the following header XML given by the service.

 

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">

<SOAP-ENV:Header>

<Service>PointOfSale</Service>

<Activity>Authorization</Activity>

<SourceSystem>Connect2</SourceSystem>

<SourceID>1000</SourceID>

<ISFmsgVersion>2.0</ISFmsgVersion>

<ActivityMsgVersion>1.0</ActivityMsgVersion>

<Locale>en_US</Locale>

<TimeStamp/>

</SOAP-ENV:Header>

 

But when I concatenate it it loses the last three lines.  any ideas?

What is the best way to create Web Services?

$
0
0

Hello Experts,

 

I know that there are several ways to create (Provide) SOAP based SAP Web Services.

 

1. Using ESR (Enterprise Service Repository) and provider proxy method.

2. Using function group or function module and then creating endpoints using SOAMANAGER.

3. On any RFC FM using SICF services (RFC and WSDL11). (All services using same endpoint sap/bc/soap/rfc, generating WSDL using WSDL11 service).

 

I would like to know what is the best way to provide web service and why?

I personally prefer the ESR based proxies. But my current client doesn't have ESR installed so I would go for SOAMANAGER to create endpoints.

 

Can anyone please comment on the benefits of using SOAMANAGER based services over SICF RFC service for RFC FMs.

 

Thanks,

Anand

Query string in SOAP adapter

$
0
0

Hi

 

I have a SOAP scenario, sender and receiver is SOAP Adapter. The client wants query string at both ends. What are the advantages of using query string? Is it added to the message header in XI, if I check query string in Com channel paramters in both sender and receiver?

 

Radhika

Viewing all 1056 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>