SOAP standards

Hi,
I am creating webservices based on the ESR model. I have created my service interfaces and then publishing them as webservices. My B2B vendor deals with web services in accordance to JAX-RPC
(JSR 101) and Implementing Enterprise Web Services (JSR 109) JAX-RPC 1.0 and SOAP 1.1 specifications. I want to make sure when I release my webservice to the client will it be in accordance to these standards ? Also how can I find out about the standards of SAP enterprise services? I am receiving web services based on Apache Axis. I am sure SAP can support this with the axis option in SOAP adapter. Please advise.
Teresa

Hi Teresa,
You can use the apache axis framework in PI, provided you deployed the jar files provided in this link.
http://help.sap.com/saphelp_nw04/helpdata/en/45/a4f8bbdfdc0d36e10000000a114a6b/content.htm
Also you can see Note 1028961 - How to prepare axisproviderlib.sda for Adapter Framework
Regards,
---Satish

Similar Messages

Web reference WSDL not conforming to SOAP standard

I built a web service based on the BAPI_FLIGHT_GETLIST function module using the "create web service" wizard. The generated web service endpoint is active in SOAMANAGER transaction.
When I try to generate a proxy class in Visual Studio 2005 using the "Add web reference" tool the service method is shown as expected in the preview window. However, when I click the "Add Reference" button I get the following error message:
Custom tool warning: DiscoCodeGenerator unable to initialize code generator.
No code generated.
The Solution Explorer window shows the Web Reference object generated with components Reference.map, Reference.cs and a WSDL file; however the Reference.cs proxy class has no code in it and there are no objects for the method parameters.
When running the WSDL.exe program from the command line, the following error message is generated:
Microsoft (R) Web Services Description Language Utility
[Microsoft (R) .NET Framework, Version 2.0.50727.42]
Copyright (C) Microsoft Corporation. All rights reserved.
Warning: This web reference does not conform to WS-I Basic Profile v1.1.
SOAP 1.1 binding was not found: WS-I's Basic Profile 1.1 consists of implementation guidelines that recommend how a set of core Web services specifications should be used together to develop interoperable Web services. For the 1.1 Profile, those specifications are SOAP 1.1, WSDL 1.1, UDDI 2.0, XML 1.0 and XML Schema.
For more details on the WS-I Basic Profile v1.1, see the specification at http://www.ws-i.org/Profiles/BasicProfile-1.1.html.
Warning: no classes were generated.
Warnings were encountered. Review generated source comments for more details.
I've seen several documents that step through this process that work fine. Has anyone seen this issue before and found a solution?
I'm running NW2004s with SP14 on Windows Server 2003 R2. Clients are VS2005 on both XP & Vista - same result on both client environments.
Thanks,
Dorian.

Hi,
I'm not familiar with the tools you described to create the Web Service aboved SAP BAPI's, but i have 2 ideas which you can start with.
I am part of the team developed the "ESE for .NET" and on the last step of our tool we are using VS API to "Add Web Reference".
We have noticed 2 ocaasions that might interest you:
1. Can you please verify that the WSDL contains the "wsdl:binding" part ?
   according to the error message you described you are missing the binding part.
   As you know WSDL of .NET Web Service combined of 5 major sections: "wsdl:types, "wsdl:message, "wsdl:portType, "wsdl:binding" & "wsdl:service".
   .NET proxy generation can't be executed on a WSDL based on a Service Definition only, it must have the "wsdl:binding" part which always comes only with
   the End Points WSDL from SAP services.
2. Can you send me the WSDL file by email ? [email protected]
3. Another important issue for Runtime of the Services - SAP Web Service schema is a little different than MS schema, you should look for "parameters" inside the WSDL and change it to "paramter".
Hope this information will help you,
Nadav

Weblogic throwing "null SOAP element Exception" in multi-part SOAP response

Hi All,
I'm using weblogic 10. My application is a webservice client generated using '*clientgen*', which is running on weblogic, and
is invoking a remotely hosted webservice ( Remotely hoseted webservice may not be running on weblogic).
I've the wsdl file of remotely hosted webservice.
Now the problem is with WSDL file (I suppose), have a look at this.
*<message name="m1">*
*<part name="body" element="tns:GetCompanyInfo"/>*
*</message>*
*<message name="m2">*
*<part name="body" element="tns:GetCompanyInfoResult"/>*
*<part name="docs" type="xsd:AnyComplexType"/> ------> assume all elements inside this complex type can be nil or minOccurs set to '0'*
*<part name="logo" type="xsd:AnyOtherComplexType"/> ------> assume all elements inside this complex type can be nil or minOccurs set to '0'*
*</message>*
<portType name="pt1">
<operation name="GetCompanyInfo">
<input message="m1"/>
*<output message="m2"/> -----> multi part message.*
</operation>
</portType>
Now here is sample message for the request(I've composed this message for this question):
<soap:Envelope> MESSAGE1
<soap:header/>
<soap:body>
<tns:m2>
<tns:GetCompanyInfoResult>
Blah Blah....
</tns:GetCompanyInfoResult>
<tns:docs>
Blah Blah....
</tns:docs> Assume no data for 'logo', so it's not returned. Since all its elements can be nillable.
<tns:m2>
</soap:body>
</soap:Envelope>
First of all, is this SOAP response is valid? I'm not sure about *'message' and 'parts' in SOAP*, but according to XML schema standards it's invalid.
Because, according to *'message' m2, 'logo' is missing*, eventhough all it's elements are nillable in such case there should be *<logo/>* at the end.
I mean valid message should be like below
<soap:Envelope> '*MESSAGE2*'
<soap:header/>
<soap:body>
<tns:m2>
<tns:GetCompanyInfoResult>
Blah Blah....
</tns:GetCompanyInfoResult>
<tns:docs>
Blah Blah....
</tns:docs>
*<tns:logo/> ------------------> here is the change compared to above message. empty element.*
<tns:m2>
</soap:body>
</soap:Envelope>
Now the concerns are :
(1) Which is a valid response? Message1 or Message2
(2) If message1 is valid then why is weblogic throwing an exception 'null SOAP element', I suppose this is due to missing 'logo' element.
(To confirm this I've used tcpmonitor and found message1 as response but weblogic is still throwing 'null SOAP Element' exception,
which confirms it needs 'logo' as well, I suppose <logo/> at least). Is there any workaround for this in weblogic for multi-part messages?
(3) If message1 is invalid according to SOAP standards then You've answered my question. ---> I need to talk to the webservice provider in this case.....
Thanks in advance...

Message 1 is not Basic Profile 1.1 compliant. It is specified by BP1.1 in section 4.4.1(http://www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html#Bindings_and_Parts) that when a wsdl:part element is defined using the type attribute, the serialization of that part in a message is equivalent to an implicit (XML Schema) qualification of a minOccurs attribute with the value "1", a maxOccurs attribute with the value "1" and a nillable attribute with the value "false".

SOAP error when xmlns keyword is uppercase.

I have a problem with the SOAP receiver adapter.
XI creates a soap envelope with the keyword SOAP in uppercase:
<i>SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" >
<SOAP:Body>
</SOAP:Body>
</SOAP:Envelope></i>
This gets the following response from the web service:
<i> <faultstring>The root element for the request could not be determined. When RoutingStyle is set to RequestElement, SoapExtensions configured via an attribute on the method cannot modify the request stream before it is read. The extension must be configured via the SoapExtensionTypes element in web.config, or the request must arrive at the server as clear text. --> The root element is missing.</faultstring></i>
I have finally worked out that the webservice which I am calling cannot parse this request.
It will only read the envelope and body is the soap is in lowercase.
<i><<b>soap</b>:Envelope xmlns:<b>soap</b>="http://schemas.xmlsoap.org/soap/envelope/">
<<b>soap</b>:Body>
</soap:Body>
</soap:Envelope></i>
The namespace used inside the body is fine, but uppercase SOAP fails every time.
Is there a way to change XI so it uses lowercase for the tags?
Is there a SOAP standard I can hit the webservice developers with?
Regards
Michael
(ps Thanks Bhavesh for feedback on my previous message. I have created a new message now I know what the problem is!)

The best solution is certainly for the webservice provider to follow the standard and accept any prefix for the soap envelope.
Unfortunately they are now in integration testing with other parties and cannot make any changes... This means that I have to figure out a work-around.
The soap envelope is not added at the mapping stage, so I cannot modify it there. However, I should be able to add the soap envelope in a mapping and select "No SOAP Envelope" in the soap adapter.
I have tried this but got an HTTP error, so I am obviously not getting through to the webservice - maybe the action is not sent when there is no envelope?
Also, I think I also have to cope with the response coming with a soap envelope where XI does not expect it.
Any other suggestions for modifying the output from the SOAP adapter after it gets the soap envelope and before it leaves XI?
Moorthy, I would like to see the output but SAP note 856597 is no longer available on OSS... (An SAP note with the number requested could not be found)
Smitha, I have used soapUI to test the web service, and this was how I finally worked out that the soap had to be in lower case.
Regards
Michael

SOAP Adapter And Protocol issue

Why and when we use SOAP adapter ? Does Xi uses processed XML messages using SOAP protocol ? I am new to Xi and confused over the issue. Can anyone please explain this to me. Thanks for your time.

HI KM
When you want to Send Data to XI from a Webservice and vice versa, your SOAP adapter is used.
Check these links for reference...
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d23cbe11-0d01-0010-5287-873a22024f79
/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
A SOAP adapter is used in order to post messages to a webservice or provide a web service for receiving messages.
How ToUse the XI 3.0 SOAP Adapter
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d23cbe11-0d01-0010-5287-873a22024f79
Please follow stefan's weblog
/people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
SOAP adapters are used for communicating with the WEB SERVICE. Web service is a software system designed to support interoperable Machine-to-Machine interaction over a network. Web services are frequently just Web APIs that can be accessed over a network, such as the Internet, and executed on a remote system hosting the requested services. In common usage Web Service refers to clients and servers that communicate using XML messages that follow the SOAP standard. So we communicate the WEB SERVICE using the SOAP adapters.
This is an example WEB SERVICE which follows the SOAP standards
http://www.webservicex.com/CurrencyConvertor.asmx?op=ConversionRate
A scenario using SOAP adapter..
RFC -> XI -> WebService - A Complete Walkthrough (Part 1) by Shabarish Vijayakumar
RFC -> XI -> WebService - A Complete Walkthrough (Part 2) by Shabarish Vijayakumar
SOAP , we will use for Webservices.. for sender and receiver side..also
one example from Webbrowser to XI to receiver ...system
another example is we can send it to end point URL..
Webservice
http://help.sap.com/saphelp_nw04/helpdata/en/9b/dad1ae3908ee44a5caf57e10918be9/frameset.htm
/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2
/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi - Invoke Webservices using SAPXI
/people/siva.maranani/blog/2005/03/01/testing-xi-exposed-web-services
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2131 [original link is broken] [original link is broken] [original link is broken]
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/336365d3-0401-0010-9884-a651295aeaa9
Soap adapter?
Regards
Abhishek Agrahari

XML Standard for B2B Integration

Hi B2B Gurus-
One of our client is looking at implementing a B2B solution using Oracle B2B to send and receive business documents with its Trading Partners (Suppliers and Banks).
The typical transactions as of now would be:
1. Purchase Order Outbound to Trading Partners
2. Advances Shipment Notice and Invoice Inbound from Trading Partners
3. Payment Files Outbound to the banks
The client will not be using EDI or Rosettanet standards. They are looking for XML standards ONLY.
I understand that Oracle B2B supports cXML, xCBL, ebXML, OAGIS etc
Can anybody please suggest which XML standard is the best for the above mentioned B2B transactions.
Please note that the back-end ERP system in our case is Oracle E-Business Suite R12.
Thanks in advance.
Regards,
Dibya

Hello Dibya,
RoesttaNet is a XML based standard but if I am right then your client does not want to use it.
Deciding a document protocol in B2B communication is mutual agreement based process between the trading partners, so I think your client should first check with it's TP's that which document protocol they would prefer.
Still if I have to give personal opinion, then I would go for ebMS because it has support for SOAP standard using which you may even connect with web-services of your TP (if they do not have a B2B product). Moreover, I can define my own message structure in ebMS (obviously with my TP's ack) and have CPP/CPA import functionality. There is also a PING-PONG message facility in ebMS to test connectivity between TP's. Apart from this there is also ActionName based agreement identification support for ebMS.
I would suggest you to ask your client to discuss it with their TP's and then take a decision.
Regards,
Anuj

SOAP - Why not use JMS as the transport layer?

I have been looking at the SOAP standard and can't understand
why something hasn't been done. I wondered if someone could help.
With the current Apache SOAP implementation there is a SOAP
Transport interface which is implemented for SMTP and HTTP. The
format of the messages never changes. Although it is not a
protocol it seems eminently sensible to me that there should be
a JMS implementation. Then infrastructure bridging cold be used
to give a universal message queueing standard.
Being as the current standard supports asynchronous messaging
over SMTP. It seems to be a trivial matter to add to the SOAP
implementation that Oracle supply. Does anyone have any good
reason why it shouldn't be done and is there any reason Oracle
and other standards body members couldn't have implemented it
and agreed it in the standard?

Am I missing something? I wasn't thinking of embedding JMS
messages over HTTP, but using JMS itself. This would provide an
industry standard for message queueing message formats, and
would allow interaction with any message queueing product
through bridges (i.e. OMB, with no real work). Aren't you
talking about something different?

WebLogic SOAP - newbie question

Hi all I am new to WebLogic. I did some research a while back and discovered that WebLogic did not support any SOAP definition and that if you needed to use .Net from a windows platform your only option was to write a DotTux Tuxedo and .NET integration communication layer.
Is this still the case or does WebLogic/Tuxedo support a SOAP standard?
Thanks,
-john

Here is what I read from the link
http://edocs.bea.com/tuxedo/tux81/overview/webacces.htm
Under the heading -
Exposing BEA Tuxedo Services as Web Services
Efforts are currently underway to expose existing BEA Tuxedo ATMI and CORBA services as Web services through BEA WebLogic Server. From a consumer point of view, Web services are program components—objects with encapsulated functionality—that are registered on Internet servers to be used as-is or in combination with Web-based applications. Web services may vary from simple programs to major components of a complex application.
As you can see it says efforts are currently underway...
Thanks for the link I will read it.
-john

SOAP 1.2 (final) support?

I noticed that WebLogic Server Web Services support a draft version of SOAP
1.2.. It's also recommended not to use 1.2 in production for ths reason. Is
the same true for Workshop?
Also, it wasn't clear to me whether the mapping used for method name and
parameters in doc-style was defined in the SOAP standard. If I use doc-style
is it reasonable to expect basic interoperability with the .NET world?
Many thanks
Howard

Hmmm, well, one would hope that someone in BEA knows what version of SOAP is
supported. I have thoroughly checked the Workshop docs - they say 1.2 but
don't qualify it so on that basis one would think it must be the final
version....
On Tue, 20 Jan 2004 10:23:51 +0000, Howard Hunt
<[email protected]> wrote:
I noticed that WebLogic Server Web Services support a draft version of SOAP
1.2.. It's also recommended not to use 1.2 in production for ths reason. Is
the same true for Workshop?
Also, it wasn't clear to me whether the mapping used for method name and
parameters in doc-style was defined in the SOAP standard. If I use doc-style
is it reasonable to expect basic interoperability with the .NET world?
Many thanks
Howard

SOAP interface to iFS?

Hi, I didn't see any discussion on this topic, but pls. excuse the post if this is covered elsewhere on technet.
Has anyone experimented with or otherwise developed tools (jsp's) to support SOAP based interaction with iFS?
We'd like to use iFS as the persistence tier in a document driven application network, but want to avoid building any proprietary interface mechanisms, (and we are limited to HTTP/S for communication).
SOAP encapsulated instructions for document mgmt. seems like a good solution.
Any recommendations or pointers to more info would be greatly appreciated.
Thanks -
Karl

I'm looking into the same information. In fact we built our own version of XML/HTTP communications with ASP and SQL Server pretty much doing exactly what ifs does. Its based entirely on BASE64 and raw binary data to handle binary data. The reason IFS may be slow on this fron is because the SOAP standards doesn't yet address any other content type then plain text. Once the spec moves, perhaps IFS will.
Comments from OTN mod????

Error while releasing :-Content item was not successfully checked

Hi
I have create a ucm user "john" which has auth type "Local" and roles of
          Admin
          contributor
          Sysmanager
"admin" role:- has Groups/rights such as
          Rights.Apss.RepMan
          Rights.Apss.Workflow
          Rights.Apss.ConfigMan
          Rights.Apps.Archiver
          newgroup(RWDA)
          release (RWDA)
          secure (RWDA)
"contributor" role :- has Groups/rights such as
          newgroup(RWDA)
          public(RW)
          release(RWDA)
          secure()
"sysmanager" role has groups/rights
          newgroup(RWDA)
          public(R)
          release(RWDA)
          secure(R)
When I am trying to release the documents I get error such as
Event generated by user 'john' at host '192.168.21.215'. Content item <undefined> was not successfully checked in. Security group is not defined. Unable to validate user security. [ Details ]
An error has occurred. The stack trace below shows more information.
!csUserEventMessage,john,192.168.21.215!$!csUnableToCheckIn,!csSecurityGroupNotDefined
intradoc.common.ServiceException: !csUnableToCheckIn,!csSecurityGroupNotDefined
     at intradoc.server.ServiceRequestImplementor.buildServiceException(ServiceRequestImplementor.java:1739)
     at intradoc.server.Service.buildServiceException(Service.java:1999)
     at intradoc.server.Service.createServiceExceptionEx(Service.java:1993)
     at intradoc.server.Service.createServiceException(Service.java:1988)
     at intradoc.server.ServiceSecurityImplementor.determinePrivilege(ServiceSecurityImplementor.java:795)
     at intradoc.server.DocumentAccessSecurity.checkSecurity(DocumentAccessSecurity.java:110)
     at intradoc.server.DocumentAccessSecurity.checkSecurity(DocumentAccessSecurity.java:67)
     at intradoc.server.ServiceSecurityImplementor.checkSecurity(ServiceSecurityImplementor.java:320)
     at intradoc.server.Service.checkSecurity(Service.java:2546)
     at intradoc.server.Service.checkSecurity(Service.java:2524)
As per the document I have given the user required group and role permission . What more should I do to release it ?
Guidance requested
Thanks
Joseph John

By release you mean you are unable to checkin a document?
How are you trying to checkin the document? DIS, SOAP, standard checkin form page??
It looks as if you haven`t supplied a security group or content id on the document meta data when you have checked in the document..
You can automatically assign content ids by going to admin server and enabling auto assign id check box.
John should only need the admin role, that will give the user full access.

How to use a WSDL file to call webservice? Help!

Hi Experts,
     I have exposed a SAP function module as webservice using the
     Utilities -> More Utilities -> Create Web Service -> From Function module
     What does this step actually does? Does it create some kind of web application like BSP for the function module in the background?
     After creating the web service I have released the service definition for the SOAP runtime using the transaction WSCONFIG.
    Finally I have generated the WDSL file ofr the webservice using WSADMIN transaction.
    After this how will my third party application like Java will use the WSDL? Will I need any connector software to be installed in Java side.
    How exactly will java call my webservice using WSDL?
    What actually happens or what is the message flow when java application calls by webservice?
    Kindly help.
Thanks
Gopal

Hi, Your solution should be correct and it's a quite common approach for Login authentication.Informatica's webservice provider also need 2 steps for calling its webservice1. Getting the session ID using username and password 2. Use the session ID to call any active operation 3. Use the session ID to log out if webservice do not have any time out settings for each session. SOAP standard is listed in the WSDL of saleforce webservice. It affects if you cannot find/call any operation in PowerCenter level. My lastest information is for PWC 9.1 version only, I don't know if they have enhanced this function in 9.5. If you can call the operation, you can just put it (SOAP standard) way first. Regards,Felix

REST API usign ajax

Hello
I am trying to make use of REST API using ajax, but its failing giving the error message: "NetworkError: 403 Forbidden - https://secure.eloqua.com/API/REST/1.0/data/contact/123"
Below is the javascript code I am using:
<script>
    jQuery.ajax( {
     type: 'GET',
     url : 'https://secure.eloqua.com/API/REST/1.0/data/contact/123',
     dataType : 'json',
     async: false,
     beforeSend : function(xhr) {
          xhr.setRequestHeader("Authorization", "Basic " + <base64>);
    error : function(xhr, ajaxOptions, thrownError) {
        alert("error");
     success : function(data) {
        alert("success");
</script>
Thanks and appreciate your Help !!

Yes, I am using the correct base URL for the API. The response I get is:
"urls": {
"base": "https://secure.eloqua.com",
"apis": {
"soap": {
"standard": "https://secure.eloqua.com/API/{version}/Service.svc",
"dataTransfer": "https://secure.eloqua.com/API/
"email": "https://secure.eloqua.com/API/
/DataTransferService.svc",
     /EmailService.svc",
"externalAction": "https://secure.eloqua.com/API/
"rest": {
"standard": "https://secure.eloqua.com/API/REST/
/ExternalActionService.svc"},
"data": "https://secure.eloqua.com/API/Data/
"bulk": "https://secure.eloqua.com/API/Bulk/

Sending MATMAS05 IDOC via XML-HTTP Interface (without XI)

Dear all,
I have to send the MATMAS05 IDOC via XML-SOAP-HTTP Interface to a subsystem. Sending works (the sub-system receives the SOAP-Request with the MATMAS05 as Body). So far so good. Now the SAP System is waiting for an answer (synchronous communication). How should this answer look like?
We receive the Error EA390 "Problem with SOAP Class" - execute_processing: entry result table
Can anybody give me a hint how the response should look like.
Many thanks and best regards
Roman

Hello Sven,
we find a solution. As far as I remember, there is a flag to send without waiting for answer (or technical better to not rely on SOAP standard).
Look in WE21 and the XML_HTTP Port you use. Uncheck the "SOAP Protocol" flag. Then it should work.
HTH and Best regards
Roman

PCK question

Hi folks,
Is it mandatory a communication channel type XI to connect PCK to XI-Integratio Server? Can I use the SOAP communication channel or other else available on the PCK?
Thanks in advance,
Ricardo.

Hi Satish,
Using the URL http:<hostname>:<ABAP-http-port>/sap/xi/engine?type=entry I'm using the direct access to IS trough Receiver channel type XI.
I'm asking this because between XI and PCK I have a web service that is needed. The purpose of this web service is only rooting the messages to XI PCK->WS->XI.
Full scenario: (web services) <-> XI <-> (web service rooter) <-> PCK <-> R/3.
My customer needs to know if the communication between PCK and XI uses SOAP standard. Using XI adapter, the protocol is XI messaging and is a SAP-specific implementation of the SOAP protocol. I dont know if this SOAP protocol is standard to work with all common web services.
Maybe using the SOAP channel, the SOAP protocol is 100% standard and it works for all common web services on the network I guess!
Thats the reason that I would like to know if a PCK can talk with XI via SOAP adapter, instead of XI com. Channel.
If anyone sees any impediments, please be free and tell me.
Thanks in advance,
Ricardo.

SOAP standards

Similar Messages

Maybe you are looking for