Updating Logon Data for Web Service in SICF not possible

Hello, hopefully someone can help me with my problem.
I have created a custom Web Service based on a custom Z Function Module.
This all works fine in our Development environemnt. I was able to go into SOAMANAGER and generate the end point. This created the web service in SICF. I was then able to go into SICF and change the logon data to use our service ID.
All tested and functionaing great.
We then transported everything to QAS. I again went into SOAMANAGER to generate the End Point, and this worked fine, we have the web service now visible in SICF.
The problem now occurs when I go into SICF and try go into change mode to enter the service user in the logon data tab. I get a popup message stating :
"You cannot use this transaction to change the service."
When I click on the long text explanation I get:
"Message SHTTP824
You cannot use transaction SICF to modify this service.
This means that only the application has the authorization to use the defined interface to modify this service."
Does anyone know how to get around this ? Or how to define our logon data using SOAMANAGER ?
thanks
Adrian

the right way to transport logon info along with SICF service is to create an external alias for your BSP and maintain the logon info in the external alias.
other wise you have to open the production system for changes and change it , which may not be allowed.
Regards
Raja

Similar Messages

About XML Parameter for Web Service invoking

I would like to use the XML parameter as the Web Service's input(Attachment is
the XML schema) in WebLogic Server 8 sp1. When I generated the Web Service and
use the WebLogic Server generate test web page to test it, I got Exception. The
WebLogic Server can't constructe the input XML.
The correct XML should look like this:
<ids>
<desc>Description</desc>
<id>1</id>
<id>2</id>
<id>3</id>
</ids>
Is there any one can tell me whether this kind of XML was permitted for Web Service
invoking or not?
[sample.xsd]

Hi Andy,
On the test page, before the invoke of the operation, did it say
something like:

if so, the service itself may be working OK, the deficiency is that the
test page tries its best to determine sample values for the invoke,
however it does not know in this case.
Did you try with a client?
Your XML should be fine.
Regards,
Bruce
Andy wrote:
>
I would like to use the XML parameter as the Web Service's input(Attachment is
the XML schema) in WebLogic Server 8 sp1. When I generated the Web Service and
use the WebLogic Server generate test web page to test it, I got Exception. The
WebLogic Server can't constructe the input XML.
The correct XML should look like this:
<ids>
<desc>Description</desc>
<id>1</id>
<id>2</id>
<id>3</id>
</ids>
Is there any one can tell me whether this kind of XML was permitted for Web Service
invoking or not?
Name: sample.xsd
sample.xsd Type: ACT Project (text/xml)
Encoding: base64

Need help in design the scenario sending data to web service

Hello All,
I need to send data to web service and get the response back.
i want to use HTTP to soap Scenario.Please let me know the necessary steps in the scenario.
Thanks and Regards,
Chinna

Hi Chinna,
> i want to use HTTP to soap Scenario.Please let me know the necessary steps in the scenario.
Split this into 2 scenarios
1. HTTP to SOAP (Request) treated as Asynchronous.
2. SOAP to HTTP (Responce) treated as Asynchronous.
For HTTP to SOAP synchronous scenario
Here the receiver side request and responce structures no need to create, the receiver client will provide you the XSD file, on that XSD file having the request and responce message structures, so you have to import that to XI server as External definition.
For sender HTTP you have to create 2 data types, 2 message types as well as 2 message interfaces, 2 message mappings for request and responce messages and 2 service/Message interfaces (HTTP is outbound and SOAP is inbound).
Configuration objects are same.
Regards
Ramesh

Want to find out how much data a Web Service is sending to client (JWSDP)

Well, the subject line didn't fit what I was intended to say, so if you don't get what I am saying in the subject line, I am sorry.
My question is... I have a Web Service client that uses stub classes generated by wscompile in JWSDP. I am wondering, it there a way to find out how much data the Web Service is sending back to my client.
The reason I asked is this, I used WebLogic 7.0 workshop to create a Web Service and also used JWSDP to create the same Web Service which deploys to Tomcat. The generated WSDL files from WebLogic workshop and JWSDP that expose the same functionalities have differences. The WSDL from WebLogic workshop is 1.5 times the size of the WSDL from JWSDP. When I tested both with client programs, calling the Web Service in Tomcat (which uses JWSDP to built) is much quicker than calling the Web Service in WebLogic.
For this reason, I would liked find out if the Web Service from WebLogic is sending more data than the one created with JWSDP.
Thanks.

I've used the TcpTunnelGui utility to see the HTTP flowing up and down the wire, that might help you.

How get data from Web Service with token?

Can I get data from Web Service made with Java?
This WS has a Token.
Any ideas o reference?
Regards!
Fran Díaz | twitter: @frandiaz_ | Blog: {geeks.ms/blogs/fdiaz/} | Communities: {onobanet.es} & {secondnug.com}

We've now added this ability to Web.Contents. You can say something like
Web.Contents("http://my.web.service/1", [Headers=[#"The-Token"="0a0138ef2d"]])
and it will pass a header with the key "The-Token" and the value "0a0138ef2d" as part of the HTTP request. For security reasons, this will only work for anonymous web requests.
The December preview can be downloaded from
http://www.microsoft.com/en-us/download/details.aspx?id=39933&WT.mc_id=blog_PBI_Update_PowerQuery

Changing SOAP Namespace for Web Service

Hi Experts,
Got a requirement to modify the SOAP namespace for a BAPI program exposed as a web service on SAP.
The fieldd denoting the SOAP namespace is accessible via transaction SE80 and navigating under: Package Name>Enterprise Services>Service Definitions> and double clicking on the exposed web service and selecting "Properties".
The SAP SOAP namespace provided by default is: urn:sap-com:document:sap:rfc:functions
Is anyone aware of a means to modify this namespace on the web service? Any help would be greatly appreciated. Thanks!
Regards,
Lionel

hi tan,
Although the SOAP Runtime is generally designed for RFC-type calls, it can also be used to access Web Services that are not implemented in a Web AS. For example, the Google search engine offers some services using SOAP, which can be accessed from the SAP Web AS.
Naming Conventions
The SOAP Runtime offers three methods of representing the original ABAP names (everything in upper case and separated by underscores) as data types in XML. Each method is associated with a different XML namespace:
urn:sap-com:document:sap:rfc:functions this is the canonical representation, which means that all names in the XML document are represented as they are in ABAP on a 1:1 basis. For repeating groups (such as the rows of a table), an XML element with the tag name item is generated (in writing) and expected (in parsing).
urn:sap-com:document:sap:soap:functions:uc-style this naming convention is similar to the first one, with the difference that instead of item, the name of the structure of the table row is generated or expected.
urn:sap-com:document:sap:soap:functions:mc-style this third convention also involves conversion of the upper case ABAP names to mixed case (both upper and lower case), according to the following algorithm: All characters except the first one are implicitly in lower case, and the underscore acts as a Shift key to effect an upper case character. RFC_SYSTEM_INFO thus becomes RfcSystemInfo. The addition of an initial underscore makes the first character lower case: RFCSYSTEM_INFO thus becomes rfcSystemInfo. An underscore character is transferred by adding an additional underscore: RFC__SYSTEM_INFO thus becomes Rfc_systemInfo.
When using the SOAP Runtime caller side, note the following points regarding the naming convention:
If the called Web Service is implemented in the Web AS 6.20, always use the namespace convention urn:sap-com:document:sap:rfc:functions. The namespace for the SOAP method must also be set according to this convention. To do this, specify the importing parameter nsvalue of the method set_method in the class CSoapDocument.
Setting the namespace of the naming convention for the SOAP method does NOT automatically mean that the SOAP Runtime also sets the naming convention for serialized SOAP messages. As a developer, you must ensure that the naming conventions are followed. To do this, you can use the methodsset_tag_name_format and set_item_name_format:
The method set_tag_name_format of the class CSoapDokument can be used to control the upper case or mixed case naming convention for tags that correspond to ABAP data types. To activate the normal ABAP format (upper case), use the value CSoapConstants=>ic_tagfmt_default for the importing parameter format. To switch to the mixed format, use the value CSoapConstants=>ic_tagfmt_mixcase.
The method set_item_name_format of the class CSoapDokument is used to control the use of the tag name for repeating groups in ABAP data types (table rows). To implement the structure name of the table row, set the value CSoapConstants=>ic_itemfmt_default for the importing parameter format. To use item as a tag, set the value CSoapConstants=>ic_itemfmt_useitem.
All names passed to the API must be in a format that is expected by the server side. This affects the importing parameter name of both the methods set_method and add_parameter of the class CSoapDocument. The SOAP Runtime caller side does not perform any conversion of these names. The document class on the calling side does NOT take into account the namespace you have selected here.
You should only implement the mixed case naming convention where it is necessary. This particularly applies when calling external Web Services, over the structure of which you have no control.
Sending the SOAP Header in the Call
The SOAP Framework does not provide general support for the handling of SOAP Header elements.
However, for calling external Web services, it is sometimes sufficient to be able to send simple Header entries as part of the request. In this special case, you can use the class CSoapDocumentHeader.
An instance of the class can be filled using the methods set_header_as_string or set_header_as_dataref. Using the method add_header, it can then be added to an instance of the class CSoapDocument, and is then serialized as a part of the document instance when the call is made.
regards
karthik
dont forgrt to reward me points if it helps u

XML really that crucial for Web Services?

No doubt Web Services are here to stay. I've tried to learn about them by reading different sites on the internet. But so far, I've only been able to read positive praises of XML. Such as the buck-a-car system. However, I'm interested in some of the negatives of XML. I want to know where XML will NOT work and is discouraged. Only be considering the negatives and limitations can I understand whether XML is appropriate for my system. (e.g., is XML good for database-to-database communications?)
When I look at the average XML file, there is so much overhead such as the DTD and descriptive XML tags. If one XML file was used to store a lot of information, it would be acceptable. But if I were to say, write a chat program, it doesn't seem wise to send an XML file for each sentence/letter typed.
And if I wanted to synchronize two databases through the internet, wouldn't it be faster to just send each record as a stream of bytes and have the other database parse that? Instead of converting the record to XML and back.
Or if I was communicating between the server and an applet, should I convert all requests into XML even though I am well aware of the format of the applet?
I personally see XML being used in only a small number of applications such as an initial handshaking process before communications.
I know it must be because I have a lack of understanding. If anyone has comments or even agrees, your feedback is more than welcome.

Well of course XML is crucial for Web Services, because the messages they pass back and forth are in XML format. (Of course that's only for the current buzzword "Web Services", some of us have been producing Web Services where the messages are in e-mail format for years now.) You're right, using XML for everything is stupid. And if you control both ends of the conversation, you can talk in any language you like, and you probably should. But if you want to talk to large numbers of people, and you don't want to limit what kind of data you might send, then you need a standard framework to do that, and XML is it. That doesn't mean that XML will replace SMTP or any other existing standard format, just that it's likely to be widely used in the future for sending generalized data between systems.

XI for Web Services

Hi experts,
I want some guidance on the following:-
1) How can we implement XI with SAP SCEM(Supply Chain Event Management) and SAP Internet sales.
2)our client wants to get SAP XI involved for Web services. He wants that his customers should be able to access data through web portal . the data can be dynamic or static . How to go about it?
3)How XI can be integrated with SAP mobile applications?
Regards
Saras Jain

Hi,
1) How can we implement XI with SAP SCEM(Supply Chain Event Management) and SAP Internet sales.
You can use SAP XI contents for SAP SCEM in which you will find almost all the interfaces for implementing the integration of SCEM.
2)our client wants to get SAP XI involved for Web services. He wants that his customers should be able to access data through web portal . the data can be dynamic or static . How to go about it?
Yes, you can use SAP XI as a middleware to expose SAP functionality as a webservice. For more details about the SCEM contents and how Enterprise service works refer to the below link
https://www.sdn.sap.com/irj/sdn/explore-es
3)How XI can be integrated with SAP mobile applications?
SAP XI is a middleware so it provides the integration for any of the platform it could be SAP MAP or it could be RFID or any other third party tool
Regard
Sumit Bhutani

Update key mapping via web service

Hi ,
I have a question about edit key mapping. The problem is that we create vendors in MDM and syndicate them to different ERP systems. To decide which system a new vendor/changes must be send to, I need the Edit Key Mapping, but the users do not want to enter this information manually and I do not see how I can create key mapping automatically.
We are working on a new solution where vendors are entered in sharepoint and updated in MDM via web services. I would like to know if one of you know if key mapping can be maintained via a web service.
Kind regards
Jonna

Hello,
You may use the document,
[MDM PI via Web Service Key Mapping|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/e0812356-e62f-2c10-76aa-9a02d038ba81]
Hope this helps your scenario
Regards,
Abhishek

Error in gettnig logon data for Adapter Engine

Hi,
We have Http > XI > RFC Scenario. We are getting 401 unauthorized error in "CALL ADAPTER" section. From the trace its clear that the logon data for the adapter engine (there is no value for USER in trace) is not getting poulated. We fixed this issue last evening....i think by doing full cache refresh, but this problem propped up again today. Yesterday when this issue was fixed the USER has "PIISUSER" in the trace.
We haven't changed any config settings since yesterday so all the passwords and other config info is same. Not sure what's causing this issue. Below is the trace. Any help will be highly appreciated.
- <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
<Trace level="3" type="T">Channel for adapter engine: RFC</Trace>
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
<Trace level="2" type="T">return fresh values from cache</Trace>
<Trace level="2" type="T">Get logon data for adapter engine (SAI_AE_DETAILS_GET): af.ppi.dac-sapd1</Trace>
<Trace level="3" type="T">URL = http://dac-sapd1.actv2.com:8007/MessagingSystem/receive/AFW/XI</Trace>
<Trace level="3" type="T">User =</Trace>
<Trace level="3" type="T">Cached = X</Trace>
<Trace level="3" type="T">Creating HTTP-client</Trace>
<Trace level="3" type="T">HTTP-client: creation finished</Trace>
<Trace level="3" type="T">Security: Basic authentication</Trace>
<Trace level="3" type="T">Serializing message object...</Trace>
<Trace level="3" type="System_Error">HTTP-client: error response= <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title>Error Report</title> <style> td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;} A:link A:visited A:active </style> </head> <body marginwidth="0" marginheight="0" leftmargin="0" topmargin="0" rightmargin="0"> <table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75"> <tr bgcolor="#FFFFFF"> <td align="left" colspan="2" height="48"> 401 &nbsp Unauthorized</td> </tr> <tr bgcolor="#3F73A3"> <td height="23" width="84"><img width=1 height=1 border=0 alt=""></td> <td height="23"><img width=1 height=1 border=0 alt=""></td> <td align="right" height="23">SAP J2EE Engine/7.00 </td> </tr> <tr bgcolor="#9DCDFD"> <td height="4" colspan="3"><img width=1 height=1 border=0 alt=""></td> </tr> </table> <table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75"> <tr bgcolor="#FFFFFF"> <td align="left" colspan="2" height="48"> Authentication did not succeed.</td> </tr> <tr bgcolor="#FFFFFF"> <td align="left" valign="top" height="48"> Details:</td> <td align="left" valign="top" height="48"><pre> No details available</pre></td> </tr> </body> </html></Trace>
<Trace level="3" type="T">HTTP-client: closing...</Trace>
<Trace level="3" type="T">HTTP-client: sending http-request...</Trace>
<Trace level="3" type="T">HTTP-client: request sent</Trace>
<Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>
<Trace level="3" type="T">HTTP-client: response received</Trace>
<Trace level="3" type="T">HTTP-client: checking status code...</Trace>
<Trace level="3" type="T">HTTP-client: status code = 401</Trace>

Hi,
go to the exchange profile.
there u need to maintain the password for the XIISUSER.
I think u need to restart the J2EE Engine for the changes to take effect.
Regards
Cornelius

Re: Why doesn't WL7.0 support get/post bindings for web services ...

hi!!!
Could you pls point to any code example.
thanks
Pushpa
"Richard Berger" <[email protected]> wrote:
>
Manoj: Thanks for the answer - do you have or can you point me at any
code samples
that accomplish this? (Yes, .NET is limited to strings/ints in their
get/post
bindings).
Thanks so much!
RB
PS - Also, can you explain any apparent discrepancy between your answer
and what
the WL documentation stated (again, it may be my misunderstanding).
"manoj cheenath" <[email protected]> wrote:
WL 7.0 does allow you to access the web service through
the browser. It even allows you to invoke service methods
with complex type arguments (.Net only supports primitive
types) and also to view the request and response soap
message for the invocation.
regards,
-manoj
"Richard Berger" <[email protected]> wrote in message
news:[email protected]...
This might be a naive question, but according to the documentation,WL 7.0
does
not support http post/get bindings for web services. Thus, for meto
access a
web service, I need to write a "middle tier" of some sort (I used
the
automatically
generated Java proxy code and JSP). All works fine, but it seems
like
it
would
sure be nice to have HTML forms access web services without havingto
write a
middle tier.
NET does this and it is extremely useful - is there a reason that
BEA
chose not
to provide this feature? (e.g. is it architecturally unsound in anyway?
or is
there an easy way to simulate it?). Given some of the Web Workshoppositioning
re: ease of use and .NET comparison, this seems like an omission.
Any insights are greatly appreciated.
Enjoy,
RB
PS - Here's the info from the documentation
Web Services Description Language (WSDL) 1.1 Specification
WSDL is an XML-based language that describes Web services. WSDL definesWeb services
as a set of endpoints operating on messages; these message containeither
message-style
or RPC-style information. The operations and messages are describedabstractly
in WSDL, and then bound to a concrete network protocol and messageformat
to define
an endpoint. Related concrete endpoints are combined into abstractendpoints (services).
WSDL is extensible to allow the description of endpoints and theirassociated
messages regardless of what message formats or network protocols areused
to communicate,
however, the only bindings described in the specification describehow to
use
WSDL in conjunction with SOAP 1.1, HTTP GET/POST, and MIME.
Note: WebLogic Server supports only SOAP 1.1 bindings.
The WSDL 1.1 Specification is available at http://www.w3.org/TR/wsdl.

This isn't a straight FORM Post as in the http binding support in WSDL. It posts
a soap message.
It's apparent that Workshop supports form-post and form-get.
But I dont see how it is done with straight WebLogic webservices. Does WebLogic
server read the web-services.xml or the WSDL file? I dont see a way to put in
http-post binding in the former and in the latter it seems to be ignored.
Can someone clarify.
Thanks.
Chu-chi
"manoj cheenath" <[email protected]> wrote:
Here is a live example:
http://65.193.192.35:7001/base/SoapInteropBaseService
Here is an example that you can download:
http://manojc.com/?sample2
This is how you run it:
http://manojc.com/?tutorial/doc/howtorun.html
More info can be found from the edocs:
7.0:
http://edocs.bea.com/wls/docs70/webserv/index.html
8.1:
http://edocs.bea.com/wls/docs81/webserv/index.html
Regards,
-manoj
http://manojc.com
"pushpa krishna" <[email protected]> wrote in message
news:[email protected]...
hi!!!
Could you pls point to any code example.
thanks
Pushpa
"Richard Berger" <[email protected]> wrote:
Manoj: Thanks for the answer - do you have or can you point me at
any
code samples
that accomplish this? (Yes, .NET is limited to strings/ints in their
get/post
bindings).
Thanks so much!
RB
PS - Also, can you explain any apparent discrepancy between your answer
and what
the WL documentation stated (again, it may be my misunderstanding).
"manoj cheenath" <[email protected]> wrote:
WL 7.0 does allow you to access the web service through
the browser. It even allows you to invoke service methods
with complex type arguments (.Net only supports primitive
types) and also to view the request and response soap
message for the invocation.
regards,
-manoj
"Richard Berger" <[email protected]> wrote in message
news:[email protected]...
This might be a naive question, but according to the documentation,WL 7.0
does
not support http post/get bindings for web services. Thus, for
me
to
access a
web service, I need to write a "middle tier" of some sort (I used
the
automatically
generated Java proxy code and JSP). All works fine, but it seems
like
it
would
sure be nice to have HTML forms access web services without havingto
write a
middle tier.
NET does this and it is extremely useful - is there a reason that
BEA
chose not
to provide this feature? (e.g. is it architecturally unsound in
any
way?
or is
there an easy way to simulate it?). Given some of the Web Workshoppositioning
re: ease of use and .NET comparison, this seems like an omission.
Any insights are greatly appreciated.
Enjoy,
RB
PS - Here's the info from the documentation
Web Services Description Language (WSDL) 1.1 Specification
WSDL is an XML-based language that describes Web services. WSDL
defines
Web services
as a set of endpoints operating on messages; these message containeither
message-style
or RPC-style information. The operations and messages are describedabstractly
in WSDL, and then bound to a concrete network protocol and messageformat
to define
an endpoint. Related concrete endpoints are combined into abstractendpoints (services).
WSDL is extensible to allow the description of endpoints and theirassociated
messages regardless of what message formats or network protocols
are
used
to communicate,
however, the only bindings described in the specification describehow to
use
WSDL in conjunction with SOAP 1.1, HTTP GET/POST, and MIME.
Note: WebLogic Server supports only SOAP 1.1 bindings.
The WSDL 1.1 Specification is available at http://www.w3.org/TR/wsdl.

Why doesn't WL7.0 support get/post bindings for web services ...

This might be a naive question, but according to the documentation, WL 7.0 does
not support http post/get bindings for web services. Thus, for me to access a
web service, I need to write a "middle tier" of some sort (I used the automatically
generated Java proxy code and JSP). All works fine, but it seems like it would
sure be nice to have HTML forms access web services without having to write a
middle tier.
.NET does this and it is extremely useful - is there a reason that BEA chose not
to provide this feature? (e.g. is it architecturally unsound in any way? or is
there an easy way to simulate it?). Given some of the Web Workshop positioning
re: ease of use and .NET comparison, this seems like an omission.
Any insights are greatly appreciated.
Enjoy,
RB
PS - Here's the info from the documentation
Web Services Description Language (WSDL) 1.1 Specification
WSDL is an XML-based language that describes Web services. WSDL defines Web services
as a set of endpoints operating on messages; these message contain either message-style
or RPC-style information. The operations and messages are described abstractly
in WSDL, and then bound to a concrete network protocol and message format to define
an endpoint. Related concrete endpoints are combined into abstract endpoints (services).
WSDL is extensible to allow the description of endpoints and their associated
messages regardless of what message formats or network protocols are used to communicate,
however, the only bindings described in the specification describe how to use
WSDL in conjunction with SOAP 1.1, HTTP GET/POST, and MIME.
Note: WebLogic Server supports only SOAP 1.1 bindings.
The WSDL 1.1 Specification is available at http://www.w3.org/TR/wsdl.

Manoj: Thanks for the answer - do you have or can you point me at any code samples
that accomplish this? (Yes, .NET is limited to strings/ints in their get/post
bindings).
Thanks so much!
RB
PS - Also, can you explain any apparent discrepancy between your answer and what
the WL documentation stated (again, it may be my misunderstanding).
"manoj cheenath" <[email protected]> wrote:
WL 7.0 does allow you to access the web service through
the browser. It even allows you to invoke service methods
with complex type arguments (.Net only supports primitive
types) and also to view the request and response soap
message for the invocation.
regards,
-manoj
"Richard Berger" <[email protected]> wrote in message
news:[email protected]...
This might be a naive question, but according to the documentation,WL 7.0
does
not support http post/get bindings for web services. Thus, for meto
access a
web service, I need to write a "middle tier" of some sort (I used theautomatically
generated Java proxy code and JSP). All works fine, but it seems likeit
would
sure be nice to have HTML forms access web services without havingto
write a
middle tier.
NET does this and it is extremely useful - is there a reason that BEAchose not
to provide this feature? (e.g. is it architecturally unsound in anyway?
or is
there an easy way to simulate it?). Given some of the Web Workshoppositioning
re: ease of use and .NET comparison, this seems like an omission.
Any insights are greatly appreciated.
Enjoy,
RB
PS - Here's the info from the documentation
Web Services Description Language (WSDL) 1.1 Specification
WSDL is an XML-based language that describes Web services. WSDL definesWeb services
as a set of endpoints operating on messages; these message containeither
message-style
or RPC-style information. The operations and messages are describedabstractly
in WSDL, and then bound to a concrete network protocol and messageformat
to define
an endpoint. Related concrete endpoints are combined into abstractendpoints (services).
WSDL is extensible to allow the description of endpoints and theirassociated
messages regardless of what message formats or network protocols areused
to communicate,
however, the only bindings described in the specification describehow to
use
WSDL in conjunction with SOAP 1.1, HTTP GET/POST, and MIME.
Note: WebLogic Server supports only SOAP 1.1 bindings.
The WSDL 1.1 Specification is available at http://www.w3.org/TR/wsdl.

WSDL error during generation of ABAP proxy for web service

Hi friends,
I am getting error during the generation of ABAP proxy object for web service developed in .NET .
Error : Proxy generation terminated: WSDL error (<extension> not supported).
How to make this WSDL file compatible for ABAP proxy.
I have tried to edit WSDL file in XML Spy but did not get any option to replace/remove the tag <extention>.
If any one worked on this. Please help me its urgent.
Thanks and regards,
Shivanand.

HI ,
I am having the same issue!!!
Does ABAP Proxy Generation support <extension> ?
Is there a list available of what is supported and what not (please consider I do not have access to sap notes)?
Thanks

Best book for Web Services

Can you suggest me what's best book for Web Services and XML to study? I'm planning to buy..
Thanks in advance..

Why does it need to be the best one? What would that even mean? Just buy something reputable, like an O'Reilly book, it's not going to be so horrifically poor that you can't learn from it

How to activate trace for web services

Hi Experts,
How to activate trace for web services in SOAMANAGER.
We are not able to view the Payload trace of the error logs.
Can anyone please let me know how to go about this???
Regards,
Ashwini

Hi Ashwini,
The thread below might be useful to you:
[SOAMANAGER - Get the XML generated;
Regards, Trevor

Updating Logon Data for Web Service in SICF not possible

Similar Messages

Maybe you are looking for