Why Net.SOAP.request leads to NotAllowedError?

Hi Everyone,
I have defined Documen-level script which makes a web service call to locally (on the same machine) hosted web service. When I try to call it I get:
NotAllowedError: Security settings prevent access to this property or method.
Net.SOAP.request:13:Document-Level:Scripts
In Acrobat Pro version I can then select "Trust this document always" from drop-down and script will execute fine next time.
How do I make this work normally? Do I have to sign PDF with some certificate or what? Or URL to the web service must be HTTPS?
Thank you in advance.

With the Adobe LiveCycle Reader Extensions ES2 module you can add the form rights:
http://www.adobe.com/products/livecycle/readerextensions/

Similar Messages

Net.SOAP.request error

I'm trying to invoke a web service after pressing a button in a PDF file.
Unfortunately I get the following error:
NotAllowedError: Security settings prevent access to this property or method.
Net.SOAP.request:22:Field fire_action_btn:Mouse Up
Adobe Acrobat SDK documentation at page 664 says that request method of Net.SOAP object requires forms rights.
The document has the following security permissions:
                                  Printing: Allowed
                Document Assembly: Not Allowed
                  Content Copying: Allowed
Content Copying for Accessibility: Allowed
                  Page Extraction: Allowed
                       Commenting: Not Allowed
           Filling of Form Fields: Allowed
                          Signing: Not Allowed
       Creation of Template Pages: Not Allowed
I've thought that "Filling of form fields" is the right permission required by this method, but clearly I was wrong. Which is the permission that the document should have in order to invoke Net.SOAP.request? How can I set it?
I've done the tests using Acrobat Reader 9.4.2
Thanks and regards,
Alessandro

With the Adobe LiveCycle Reader Extensions ES2 module you can add the form rights:
http://www.adobe.com/products/livecycle/readerextensions/

Why SOAP Request as Impersonator account fails?

Hi everyone,
I have created an Impersonator account and accessing item of another account using SOAP Request. I am unable to query the account. The request is as follows:
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types">
<soap:Header>
<t:RequestServerVersion Version="Exchange2013"/>
</soap:Header>
<soap:Body>
<GetItem
xmlns="http://schemas.microsoft.com/exchange/services/2006/messages"
xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types">
<ItemShape>
<t:BaseShape>Default</t:BaseShape>
<t:IncludeMimeContent>true</t:IncludeMimeContent>
</ItemShape>
<ItemIds>
<t:ItemId Id="AAMkADhiYjY0NGIxLTMyZTYtNDA2YS04ZmM1LTBiZjRmZGJjMDY0NABGAAAAAAABEJy6UddET6O8EWfW99taBwABc/Z+U4EQRZ7tUFT0S/bsAAA76u/+AAABc/Z+U4EQRZ7tUFT0S/bsAAA9Cn6iAAA=" />
</ItemIds>
</GetItem>
</soap:Body>
</soap:Envelope>
And the response is as follows:
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<s:Header>
<h:ServerVersionInfo MajorVersion="15" MinorVersion="0" MajorBuildNumber="516" MinorBuildNumber="29" Version="Exchange2013" xmlns:h="http://schemas.microsoft.com/exchange/services/2006/types" xmlns="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
</s:Header>
<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<m:GetItemResponse xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types">
<m:ResponseMessages>
<m:GetItemResponseMessage ResponseClass="Error">
<m:MessageText>Access is denied. Check credentials and try again.</m:MessageText>
<m:ResponseCode>ErrorAccessDenied</m:ResponseCode>
<m:DescriptiveLinkKey>0</m:DescriptiveLinkKey>
<m:Items/>
</m:GetItemResponseMessage>
</m:ResponseMessages>
</m:GetItemResponse>
</s:Body>
</s:Envelope>
When I query using that account, then it is successful. Kindly help me?
Thanks & regards,
Talib Hussain

I don't see any of the elements that would indicate you're doing impersonation in your request. See
https://msdn.microsoft.com/EN-US/library/office/dn722378(v=exchg.150).aspx. So your request would be acting against the mailbox owned by the account that you've authenticated as, which doesn't sound like what you want. Make sure you're authenticated
as your impersonation account, and you include an ExchangeImpersonation element to indicate the account you want to impersonate.

Safri browser 3.1.2 SOAP Request HTTP 400 Error

Hi,
I have a simple html making ajax calls (XMLHttpRequest) to our webservice on a button click. The code works fine with major browsers like FireFox, IE and Opera. But if i load the html in Safari and send the SOAP request to the webservice using XMLHttpRequest, i get an HTTP 400 - Bad Request Error from the server.
Why is it failing just for the safari browser? Do i need to set any extra HTTP headers? When i see the WireShark captured packets for Firefox and Safari, i see the content length is different. And also Safari is missing a lot of headers.
Could you please help troubleshoot the issue?
PS: The webserver is running IIS 6.0 on windows server 2003.
regards
srividhya

I'm not sure how to help you. No link found.
Try this to see how Safari performs XMLHttpRequests:
http://www.mnot.net/javascript/xmlhttprequest/
Every browser is different...

Error while sending a soap request from XML SPY to a webservice in XI

Hi ,
I published a webservice om the XI end and testing it with consuming the WSDL file in XML SPY and sending a soap request from there.
I am getting the following error .
<b>com.sap.aii.af.mp.module.ModuleException: either no channelID specified or no channel found for the specified party, service, and channel name</b>, MessageServlet(Version $Id: //tc/xi/645_VAL_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#4 $)
     at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:380)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Is this error due to the user authentication or due to some other issue .
Please do let me know soon .
Thanks a lot
Nikhil

Hi Ricardo ,
I have the correct port now.
the url looks like
http://<host>:50000/XISOAPAdapter/MessageServlet?channel=:SIEBEL_DEV:SOAP_CUST
when I am testing it in the XML spy. and send a soap server request. I am getting the popup for user authentication . once i put my user id it gives me a error saying
<b>HTTP operation 'POST' could not be performed on URL
'/XISOAPAdapter/MessageServlet?channel=:SIEBEL_DEV:SOAP_CUST&version=3.0&Sender.Service=SIEBEL_DEV&Interface=http%3A%2F%2FOFCOM%2FUNIFY%2FCustomerMaster%5EMI_CUST' due to an error :
The connection to the server was terminated abnormally</b>
Any Idea as to why is such a error is coming
Thanks for the help
Nikhil

Web Service posting via SOAP.request - Security settings prevent access...

I'm trying to call a web service via the SOAP.request object in javascript embedded into my Interactive Form. I've successfully done this with SAP NetWeaver 7.0 trial version however now I'm having this issue on a production setup. The PDF generates fine and I can fill out the form and everything. I checked the properties of both PDF documents (one that works from the trial and one that doesn't from the prod box) and they are the same, expect the one that works is PDF Version 1.6, and the one that doesn't is PDF Version 1.7.
Here's the client-side error:
Acrobat EScript Built-in Functions Version 8.0
Acrobat Annotations / Collaboration Built-in Functions Version 8.0
Acrobat Annotations / Collaboration Built-in Wizard Functions Version 8.0
Acrobat Multimedia Version 8.0
Acrobat SOAP 8.0
NotAllowedError: Security settings prevent access to this property or method.
SOAP.request:31:XFA:data[0]:mainform[0]:btnRelease[0]:click
Here's the snippet of JavaScript code:
var response = SOAP.request();
Here are the security properties of the malfunctioning PDF:
Security Method: No Security
Can be Opened By: All versions of Acrobat
Printing: Allowed
Document Assembly: Not Allowed
Content Copying: Allowed
Content Copying for Accessibility: Allowed
Page Extraction: Not Allowed
Commenting: Allowed
Filling of form fields: Allowed
Signing: Allowed
Creation of Template Pages: Allowed
How do I determine what the culprit is?

Michael,
PDF Version 1.6 means Adobe Reader 7.0.x family and PDF version 1.7 means Adobe Reader 8.0.x or 9.0.x if I am not wrong.
Also if you check LiveCycle Designer Help (Using LiveCycle Designer ES > Working with Data Sources > About data sources > Working with data connections) it clearly says that with LiveCycle Designer 8.0 secured web services are not supported and there are additional security settings for Reader 8.0 onwards, that may be causing the issue.
Chintan

How to create a standard SOAP request message from a given WSDL file?

Hello,
If I have a WSDL file (either from a .net web service or from the famous Amazon web services), what is the best way to generate a SOAP compliant request message?
I am having trouble understanding the role of WSDL file in a given web service.
Question 1:
If I have a web service that is implemented using jaxm, how do I create/publish a WSDL file that describes the web service?
Assuming I can generate a wsdl file, can I recreate the SOAP request message from the WSDL file automatically (that matches the original request, which is hand build by me?)
Question 2:
If I have a web service that is implemented using JAX-RPC, based on the WSDL file, can I simply generate a valid SOAP message (by some JAVA api) and get the response message directly?
thanks...

I have the same question ("Assuming I can generate a wsdl file, can I recreate the SOAP request message from the WSDL file automatically (that matches the original request, which is hand build by me?)")
Have you already found an answer to this?

Soap request with attachment --problem in deploye to jboss useing Jdevelope

using Jdeveloper and oc4j application server i made two application.
In application one i exposed a web service method.In this application their is a handler class which able to handle soap request and response with attachment.
In application two a client is sends a soap request with attachment.
If i deploye it in oc4j it is working fine. But if i Deploye to JBoss server [i made a jboss application server connection] and then trying to send the soap request with attachment from the client application i gets the following errors--
Exception in thread "main" javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: Connection refused
     at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:152)
     at etrans.TripBean.a.ClientGateWay.msgEnvelope(ClientGateWay.java:50)
     at etrans.TripBean.a.ClientGateWay.main(ClientGateWay.java:60)
Caused by: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: Connection refused
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:148)
     ... 2 more
Caused by: javax.xml.soap.SOAPException: Message send failed: Connection refused
     at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:458)
     at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.run(HttpSOAPConnection.java:865)
     ... 4 more
Caused by: java.net.ConnectException: Connection refused
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
     at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
     at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
     at java.net.Socket.connect(Socket.java:516)
     at java.net.Socket.connect(Socket.java:466)
     at java.net.Socket.<init>(Socket.java:366)
     at java.net.Socket.<init>(Socket.java:208)
     at javax.net.DefaultSocketFactory.createSocket(SocketFactory.java:202)
     at HTTPClient.HTTPConnection.getSocket(HTTPConnection.java:3115)
     at HTTPClient.HTTPConnection.doConnect(HTTPConnection.java:3858)
     at HTTPClient.HTTPConnection.sendRequest(HTTPConnection.java:2921)
     at HTTPClient.HttpOutputStream.close(HttpOutputStream.java:421)
     at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection.sendMessage(HttpSOAPConnection.java:724)
     at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:373)
     ... 5 more
Am i made any mistake to deploye to jboss or it is not possiable to access the web service in such way?
please suggest me what is the procedure to recover from this.

Hello,
How do you package you WS client application to be deployed in JBoss?
The JAX-RPC clients are not that portable you may need to recompile the client with JBoss WebService implementation/tools, and check that you do have the different deployment descriptors for the client too.
Regards
Tugdual Grall

SOAP Request to "XISOAPAdapter/MessageServlet" or"sap/xi/engine?type=entry"

Hi,
I created a webservice whichs creates an idoc from an orders05 xml file.
I created a wsdl file and try it out with xml spy. It works fine.
However I have a question.
If I send the SOAP Request to:
http://host:port/XISOAPAdapter/MessageServlet?channel=PARTY:PARTY_Application:CC_PARTY_Application_SOAP_SND
its working fine.
If I send the SOAP Request to:
http://host:port/sap/xi/engine?type=entry?channel=PARTY:PARTY_Application:CC_PARTY_Application_SOAP_SND
it is not working.
In the second case I can see my message in the monitor and I found my orders05 xml in the payload. However the message has no information about the sender, the application and the communication channel. So I got a lot of errors.
I thought that both are url are doing the same with soap requests, the first is the adapter engine j2ee port and the other the abap stack http port.
Could someone explain the differences to me and why the information is lost when using the abap port?
Many thanks,
Nils Kloth

Hi,
In the 2. case I think there shoudnt be two question marks.
"http://host:port/sap/xi/engine?type=entry?"
Shouldnt it be like this:
"http://host:port/sap/xi/engine?type=entry:"
Hope it helps (Please inform if it works)
Regards,
Arman

PO 7.4: NW BPM: HTTP Error response for SOAP request or invalid content-type.HTTP 200 OK

Hi Experts
I am trying to call NW BPM scenario(File to BPM) from PI, and using below adapter config.
I am getting below error.
Failed to call the endpoint: Error in call over HTTP: HTTP 200 OK
SOAP: Call failed: java.io.IOException: HTTP Error response for SOAP request or invalid content-type.; HTTP 200 OK
SOAP: Error occurred: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: HTTP Error response for SOAP request or invalid content-type.; HTTP 200 OK
MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: HTTP Error response for SOAP request or invalid content-type.; HTTP 200 OK
Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: HTTP Error response for SOAP request or invalid content-type.; HTTP 200 OK
Any idea how to fix this issue?
Thanks,
Sandeep Maurya.

Hi Sandeep,
Test the URL from your browser and check the proxy settings as well.
Refer the below links
SOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT
SOAP: Call failed: java.io.IOException: Failed to get the input stream from socket: java.net.SocketException: Connection…
Regards
Bhargava Krishna

SOAP RECEIVER and WSDL-what specifies how my SOAP REQUEST should look like?

Hi
I am sending a request to a webservice (SOAP RECEIVER) but the webservice in question does not have a wsdl. I have created my own wsdl based on another example but when mapping to the REQUEST part of this and routing it through my SOAP RECEIVER channel it appears that it has NO SOAP-ENV only the pure XML in the request sent to the webservice.
I have UNTICKED the "No SOAP envelope.." so all is pretty basic.
What specifies how the REQUEST sent to the webservice through the SOAP RECEIVER comm channel should look like?
I thought that the SOAP RECEIVER ADAPTER did this automatically, but in my scenariao, it looks as if it something else as well? Is it the XSD or WSDL that dictates how the SOAP REQUEST should look like?
Cheers

> I thought that the SOAP RECEIVER ADAPTER did this automatically, but in my scenariao, it looks as if it something else as well? Is it the XSD or WSDL that dictates how the SOAP REQUEST should look like?
No. The SOAP adapter adds the SOAP enveloped, no matter how the WSDL looks like.
I have no idea why this does not work for you. Check whether the channel is active and the cache is refreshed.
Regards
Stefan

SOAP Request Error in OSB Console

Hi,
I'm just learning OSB, and I tried to test out a web service project that I'd built. I deployed the project onto Weblogic, created the WSDL file for the business service in OSB and mounted that as well, but when I try to test it, the SOAP response gives the following error: Cannot find dispatch method for {http://calculatorservice}doAdd
I'm using JDeveloper 11.1.1.4, WebLogic 10.3.4 and OSB 11gR1.
The complete source code is as follows:
Calculator.java
package calculatorservice;
import javax.jws.WebService;
@WebService(targetNamespace="http://calculatorservice")
public class Calculator implements CalculatorIF{
@Override
public int doAdd(int a, int b){
return a + b;
@Override
public int doSub(int a, int b){
return a - b;
CalculatorBusinessService.wsdl
<?xml version="1.0" encoding="UTF-8" ?>
<definitions name="CalculatorBusinessService"
targetNamespace="http://calculatorservice"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://calculatorservice"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:types="http://calculatorservice">
<types>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:tns="http://calculatorservice"
targetNamespace="http://calculatorservice"
elementFormDefault="qualified">
<xsd:complexType name="AddInput">
<xsd:sequence>
<xsd:element name="arg0" type="xsd:int"/>
<xsd:element name="arg1" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="AddOutput">
<xsd:sequence>
<xsd:element name="result" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="SubInput">
<xsd:sequence>
<xsd:element name="arg0" type="xsd:int"/>
<xsd:element name="arg1" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="SubOutput">
<xsd:sequence>
<xsd:element name="result" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="doAddRequest" type="tns:AddInput"/>
<xsd:element name="doAddResponse" type="tns:AddOutput"/>
<xsd:element name="doSubRequest" type="tns:SubInput"/>
<xsd:element name="doSubResponse" type="tns:SubOutput"/>
</xsd:schema>
</types>
<message name="doAddInput">
<part name="parameters" element="tns:doAddRequest"/>
</message>
<message name="doAddOutput">
<part name="parameters" element="tns:doAddResponse"/>
</message>
<message name="doSubInput">
<part name="parameters" element="tns:doSubRequest"/>
</message>
<message name="doSubOutput">
<part name="parameters" element="tns:doSubResponse"/>
</message>
<portType name="Calculator">
<operation name="doAdd">
<input message="tns:doAddInput"/>
<output message="tns:doAddOutput"/>
</operation>
<operation name="doSub">
<input message="tns:doSubInput"/>
<output message="tns:doSubOutput"/>
</operation>
</portType>
<binding name="CalculatorBinding" type="tns:Calculator">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/http"/>
<operation name="doAdd">
          <soap:operation style="document"/>
          <input>
               <soap:body use="literal"/>
          </input>
          <output>
               <soap:body use="literal"/>
          </output>
</operation>
<operation name="doSub">
          <soap:operation style="document"/>
          <input>
               <soap:body use="literal"/>
          </input>
          <output>
               <soap:body use="literal"/>
          </output>
</operation>
</binding>
<service name="CalculatorSerivce">
     <port name="CalculatorPort" binding="tns:CalculatorBinding">
          <soap:address location="http://localhost:7001/Calculator-CalculatorService-context-root/CalculatorPort" />
     </port>
</service>
</definitions>
Now, here are the SOAP messages auto-generated by OSB console:
SOAP Request:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
</soap:Header>
<soapenv:Body>
<cal:doAdd xmlns:cal="http://calculatorservice">
<cal:arg0>3</cal:arg0>
<cal:arg1>3</cal:arg1>
</cal:doAdd>
</soapenv:Body>
</soapenv:Envelope>
SOAP Response:
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body>
<S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope">
<faultcode>S:Client</faultcode>
<faultstring>
Cannot find dispatch method for {http://calculatorservice}doAdd
</faultstring>
</S:Fault>
</S:Body>
</S:Envelope>
I'd be really grateful if anyone could point out my mistakes.
Thank You
Edited by: Debojit Sinha on Feb 4, 2011 7:35 PM

Hi Palak,
If you are talking about the weblogic test client for the web service, then yes I was. Also, since my last post, I tried to run the business service by copy-pasting the WSDL generated by the server and using it to create the Business service, and it works fine. The results are wrong, but the error is gone. So, I think that I can safely conclude that the problems lies i the WSDL. I haven't been able to pinpoint the source, unfortunately. Comparing the two also turned up nothing. As far as I can tell, they are both semantically identical. But to let you judge for yourself, here's the server-generate WSDL:
<?xml version='1.0' encoding='UTF-8'?><definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://calculatorservice" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://calculatorservice" name="CalculatorService">
<types>
<xsd:schema>
<xsd:import namespace="http://calculatorservice" schemaLocation="http://localhost:7001/Calculator-CalculatorService-context-root/CalculatorPort?xsd=1"/>
</xsd:schema>
</types>
<message name="doAdd">
<part name="parameters" element="tns:doAdd"/>
</message>
<message name="doAddResponse">
<part name="parameters" element="tns:doAddResponse"/>
</message>
<message name="doSub">
<part name="parameters" element="tns:doSub"/>
</message>
<message name="doSubResponse">
<part name="parameters" element="tns:doSubResponse"/>
</message>
<portType name="Calculator">
<operation name="doAdd">
<input message="tns:doAdd"/>
<output message="tns:doAddResponse"/>
</operation>
<operation name="doSub">
<input message="tns:doSub"/>
<output message="tns:doSubResponse"/>
</operation>
</portType>
<binding name="CalculatorPortBinding" type="tns:Calculator">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
<operation name="doAdd">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
<operation name="doSub">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
</binding>
<service name="CalculatorService">
<port name="CalculatorPort" binding="tns:CalculatorPortBinding">
<soap:address location="http://localhost:7001/Calculator-CalculatorService-context-root/CalculatorPort"/>
</port>
</service>
</definitions>

What is needed on non-weblogic client to make soap request

Hi, I am trying to make a soap request from a client that is not weblogic to a
weblogic6.1 server. I was under the impression that all I needed was the client.jar
created by wsgen. But when I try to access the service through the client I get
the below exception. It appears to be trying to access a weblogic class that is
not contained in the client.jar. Does this mean I also need to include the weblogic.jar
on the client(I'm hoping not to). Thanks
java.lang.NoClassDefFoundError: weblogic/net/http/HttpsURLConnection
     at weblogic.soap.http.SoapContext.lookup(SoapContext.java:87)
     at javax.naming.InitialContext.lookup(InitialContext.java:350)
     at index_1._jspService(index_1.java:68)
     at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java)
     at org.apache.tomcat.facade.ServletHandler.doService(ServletHandler.java:574)
     at org.apache.tomcat.core.Handler.invoke(Handler.java:322)
     at org.apache.tomcat.core.Handler.service(Handler.java:235)
     at org.apache.tomcat.facade.ServletHandler.service(ServletHandler.java:485)
     at org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:917)
     at org.apache.tomcat.core.ContextManager.service(ContextManager.java:833)
     at org.apache.tomcat.modules.server.Http10Interceptor.processConnection(Http10Interceptor.java:176)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:494)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:516)
     at java.lang.Thread.run(Thread.java:484)

Hi Jane,
Looks like you have run smack dab into one of the first "myths" about web services
- "SOAP client software is not vendor- dependent" :-) This is in fact, exactly
the opposite! And it's not just WebLogic's SOAP client API that has this "vendor-dependent"
code. Apache SOAP, Apache AXIS, Systinet WASP, GLUE, etc. exhibit the same behavior.
The difference is that WebLogic's client.jar, is not really a "standalone, SOAP
client package". It's a "web service-specific" client package.
JAX-RPC (and the other APIs in the Java Web Services Developer's Pack) is attempting
to reduce a fair amount of this "vendor-dependency", but there will always be
some :-) WLS 6.1 doesn't use JAX-RPC, so...
Anyway, how many "vendor classes" you need, depends on what you are attempting
to do in the client. If you are just consuming a web service that uses "SOAP encoding",
then you'll need less. If you are consuming a web service that uses "literal encoding",
you'll need more. An easy (albeit time consuming) way to figure out which classes
you need from the weblogic.jar file, to use WebLogic's Web Service client package
inside Tomcat, is to use the "-verbose:class" option, on the Java command used
to start Tomcat. This will produce a lot of output, so I suggest you capture it
to a log, instead of sending it to stdout :-) But, as I said, this is a very,
very, very time consuming way to determine all the classes you need from the weblogic.jar
file. Trust me, I've done this before and it took me about 3 hours to find every
class that's needed! It's simpler just to include the weblogic.jar file in the
CLASSPATH you start Tomcat with :-)
Another option is to just use the Apache SOAP package to create the web service
client. This works wonderfully, if you don't want to use WSDL (Apache SOAP doesn't
support WSDL). If you want to use WSDL, go with the Apache AXIS package. It has
an implementation of JAX-RPC, and is pretty close to the Web Services implementation
in WLS 7.0 (which I'm assuming you'll eventually upgrade to anyway, right?).
Regards,
Mike Wooten
"Jane" <[email protected]> wrote:
>
Hi, I am trying to make a soap request from a client that is not weblogic
to a
weblogic6.1 server. I was under the impression that all I needed was
the client.jar
created by wsgen. But when I try to access the service through the client
I get
the below exception. It appears to be trying to access a weblogic class
that is
not contained in the client.jar. Does this mean I also need to include
the weblogic.jar
on the client(I'm hoping not to). Thanks
java.lang.NoClassDefFoundError: weblogic/net/http/HttpsURLConnection
     at weblogic.soap.http.SoapContext.lookup(SoapContext.java:87)
     at javax.naming.InitialContext.lookup(InitialContext.java:350)
     at index_1._jspService(index_1.java:68)
     at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java)
     at org.apache.tomcat.facade.ServletHandler.doService(ServletHandler.java:574)
     at org.apache.tomcat.core.Handler.invoke(Handler.java:322)
     at org.apache.tomcat.core.Handler.service(Handler.java:235)
     at org.apache.tomcat.facade.ServletHandler.service(ServletHandler.java:485)
     at org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:917)
     at org.apache.tomcat.core.ContextManager.service(ContextManager.java:833)
     at org.apache.tomcat.modules.server.Http10Interceptor.processConnection(Http10Interceptor.java:176)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:494)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:516)
     at java.lang.Thread.run(Thread.java:484)

Intercepting SOAP Requests at HTTP Level

We have a WLS Web Service in which we want to compress the body of the HTTP
message containing the SOAP request (envelope). The compression will be done
using gzip and including a standard
Content-Encoding: gzip
HTTP request header.
This makes it necessary to intercept the HTTP/SOAP request on the server
side to decompress the body of the HTTP message before WLS SOAP processing
begins.
Doing this in the SOAP Handler Chain is too late; by this time, WLS will
have already attempted to parse the HTTP message and create (bind) the
appropriate Java SOAP object structure (SOAPMessage, SOAPPart, etc.).
Question: Is there a way to intercept the HTTP POST request containing the
SOAP message early enough (e.g., as it comes off the wire) so that the body
of the HTTP message can be decompressed before WLS parses it and creates
the SOAP objects to pass to the Handler Chain?
Thanks for any help and insight you can provide.
John

I've been dealing with a similar problem and it actually doesn't appear that WLS has bound everything by the SOAP Handler level. I have been working on inserting encryption into the WLS's SOAP handlers. I was getting nasty error messages when I was trying to encrypt the contents of the message body. At first I thought this was due to WLS trying to bind passed variables. This was mostly because of the invalid schema representation of a variable type x combined with a java.lang.NumberFormatException. However, if I encrypt 1 level lower i.e. the contents of the operations WLS becomes happy so I don't know what to think anymore. If you have any insites into why it would give me the error message it is giving me I would like to know. I hope my post has furthered the understanding of your problem in some way.
more information on what I did is below:
complete client request
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<env:Header>
</env:Header>
<env:Body env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<m:getBalance xmlns:m="http://example.com" Id="encryptMyContents">
<intVal xsi:type="xsd:int">1</intVal>
<string xsi:type="xsd:string">blah blah blah</string>
</m:getBalance>
</env:Body>
</env:Envelope>
general form of encrypted client request
<env:Body env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<m:getBalance xmlns:m="http://example.com" Id="encryptMyContents">
<EncryptedData xmlns="http://www.w3.org/2001/04/xmlenc#"
Id="encryptedDataID"
Type="http://www.w3.org/2001/04/xmlenc#Content">
<EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#tripledes-cbc"/>
<CipherData>
<CipherValue>long encrypted stuff</CipherValue>
</CipherData>
</EncryptedData>
</m:getBalance>
</env:Body>
The above encrypting the contents of the operation
works with WLS
The below encrypting the contents of the body
does NOT work with WLS
The target of the encrytion is moved
<env:Body Id="encryptMyContents" ...
general form of encrypted server response (I suppose I should have copied server response above but you can get the picture without it)
<env:Body env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<m:getBalance xmlns:m="http://example.com" Id="encryptMyContents">
<EncryptedData xmlns="http://www.w3.org/2001/04/xmlenc#"
Id="encryptedDataID"
Type="http://www.w3.org/2001/04/xmlenc#Content">
<EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#tripledes-cbc"/>
<CipherData>
<CipherValue>long encrypted stuff</CipherValue>
</CipherData>
</EncryptedData>
</m:getBalance>
</env:Body>
I get my nasty error message...
Note this error message is if I simply use the invoke button that weblogic creates for me
In this case the what happens is
- the request handler recieves an unencrypted client request does nothing to the request
- the web service generates its response
- the response handler encrypts body contents of the response
- the handler finishes
- WLS throws the exception below
NOTE: after this point there is nothing but the error message.
Failed to invoke service:
weblogic.xml.schema.types.IllegalLexicalValueException: "9HhL2AdpL5d4B2KOWrTCtJ2Q6Ybu+6..." is not a valid lexical representation of {http://www.w3.org/2001/XMLSchema}double - java.lang.NumberFormatException: For input string: "9HhL2AdpL5d4B2KOWrTCtJ2Q6Ybu+6/AftWxi/Kv752g4P9r30FhOXGgrCimrkd6 v09FsLsPdQagJQiETnMSVwVw1Kfw34fITv/S36Et+4SQ1t5+TpZwypuVz8bkyBFy KdSzrAD9ONxYERR1y6fy3m1XPZD5IUECmAKI/QaymtZjAyzQkA3U33sB+V3n5ZqS QcYcCj/9JwheIlBPkKL/JIPn6yqg6VBMp15a8CHYY5W/+aRpSMaDeDFkXOgBIelX wQumJ47tKXbHrhHio+MmeoMrlf0A1oU71j8ZPOBkvvfg3ty56OV9HBULOr+FtpnP dIlgJA3CxyX6L3W6ElP82biZwJumqL6ABDKNvyTJn8kfCkYUPjIynv8iiOHPUPEE ssHqVy+PI1tqoXHL6llVcb2a9gL4WNPXEC8EQnIlOay1t+nVrCRAG8PbzqIFApzd" at weblogic.xml.schema.types.XSDDouble.naiveConvertXml(XSDDouble.java:182) at weblogic.xml.schema.types.XSDDouble.convertXml(XSDDouble.java:153) at weblogic.xml.schema.binding.internal.builtin.XSDDoubleDeserializer.getObjectFromContent(XSDDoubleDeserializer.java:15) at weblogic.xml.schema.binding.internal.builtin.XSDSimpleTypeDeserializer.processContent(XSDSimpleTypeDeserializer.java:173) at weblogic.xml.schema.binding.internal.builtin.XSDSimpleTypeDeserializer.processContent(XSDSimpleTypeDeserializer.java:161) at weblogic.xml.schema.binding.internal.builtin.XSDSimpleTypeDeserializer.deserialize(XSDSimpleTypeDeserializer.java:101) at weblogic.xml.schema.binding.RuntimeUtils.invoke_deserializer(RuntimeUtils.java:428) at weblogic.xml.schema.binding.RuntimeUtils.invoke_deserializer(RuntimeUtils.java:328) at weblogic.webservice.core.DefaultPart.toJava(DefaultPart.java:387) at weblogic.webservice.core.DefaultMessage.toJava(DefaultMessage.java:487) at weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.java:329) at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:147) at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:473) at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:439) at weblogic.webservice.server.servlet.ServletBase.invokeMultiOutput(ServletBase.java:359) at weblogic.webservice.server.servlet.ServletBase.invokeOperation(ServletBase.java:314) at weblogic.webservice.server.servlet.WebServiceServlet.invokeOperation(WebServiceServlet.java:361) at weblogic.webservice.server.servlet.ServletBase.handleGet(ServletBase.java:280) at weblogic.webservice.server.servlet.ServletBase.doGet(ServletBase.java:157) at weblogic.webservice.server.servlet.WebServiceServlet.doGet(WebServiceServlet.java:280) at javax.servlet.http.HttpServlet.service(HttpServlet.java:743) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:214) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:120) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:272) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:165) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3022) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1925) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1848) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1288) Caused by: java.lang.NumberFormatException: For input string: "9HhL2AdpL5d4B2KOWrTCtJ2Q6Ybu+6/AftWxi/Kv752g4P9r30FhOXGgrCimrkd6 v09FsLsPdQagJQiETnMSVwVw1Kfw34fITv/S36Et+4SQ1t5+TpZwypuVz8bkyBFy KdSzrAD9ONxYERR1y6fy3m1XPZD5IUECmAKI/QaymtZjAyzQkA3U33sB+V3n5ZqS QcYcCj/9JwheIlBPkKL/JIPn6yqg6VBMp15a8CHYY5W/+aRpSMaDeDFkXOgBIelX wQumJ47tKXbHrhHio+MmeoMrlf0A1oU71j8ZPOBkvvfg3ty56OV9HBULOr+FtpnP dIlgJA3CxyX6L3W6ElP82biZwJumqL6ABDKNvyTJn8kfCkYUPjIynv8iiOHPUPEE ssHqVy+PI1tqoXHL6llVcb2a9gL4WNPXEC8EQnIlOay1t+nVrCRAG8PbzqIFApzd" at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:1224) at java.lang.Double.parseDouble(Double.java:482) at weblogic.xml.schema.types.XSDDouble.naiveConvertXml(XSDDouble.java:173) at weblogic.xml.schema.types.XSDDouble.convertXml(XSDDouble.java:153) at weblogic.xml.schema.binding.internal.builtin.XSDDoubleDeserializer.getObjectFromContent(XSDDoubleDeserializer.java:15) at weblogic.xml.schema.binding.internal.builtin.XSDSimpleTypeDeserializer.processContent(XSDSimpleTypeDeserializer.java:173) at weblogic.xml.schema.binding.internal.builtin.XSDSimpleTypeDeserializer.processContent(XSDSimpleTypeDeserializer.java:161) at weblogic.xml.schema.binding.internal.builtin.XSDSimpleTypeDeserializer.deserialize(XSDSimpleTypeDeserializer.java:101) at weblogic.xml.schema.binding.RuntimeUtils.invoke_deserializer(RuntimeUtils.java:428) at weblogic.xml.schema.binding.RuntimeUtils.invoke_deserializer(RuntimeUtils.java:328) at weblogic.webservice.core.DefaultPart.toJava(DefaultPart.java:387) at weblogic.webservice.core.DefaultMessage.toJava(DefaultMessage.java:487) at weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.java:329) at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:147) at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:473) at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:439) at weblogic.webservice.server.servlet.ServletBase.invokeMultiOutput(ServletBase.java:359) at weblogic.webservice.server.servlet.ServletBase.invokeOperation(ServletBase.java:314) at weblogic.webservice.server.servlet.WebServiceServlet.invokeOperation(WebServiceServlet.java:361) at weblogic.webservice.server.servlet.ServletBase.handleGet(ServletBase.java:280) at weblogic.webservice.server.servlet.ServletBase.doGet(ServletBase.java:157) at weblogic.webservice.server.servlet.WebServiceServlet.doGet(WebServiceServlet.java:280) at javax.servlet.http.HttpServlet.service(HttpServlet.java:743) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:214) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:120) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:272) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:165) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3022) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1925)

How do u send the SOAP request to Siebel On Demand from Siebel on premise?

Hi,
I am trying to integrate my on premise Seibel with Siebel on Demand. The session id is generated properly after logging in. A SOAP request is generated as follows
<?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAPSDK2="urn:/crmondemand/xml/lead" xmlns:SOAPSDK1="urn:crmondemand/ws/lead/10/2004" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><SOAP-ENV:Body><SOAPSDK1:LeadWS_LeadQueryPage_Input><PageSize>10</PageSize><StartRowNum>0</StartRowNum><SOAPSDK2:ListOfLead><Lead><AccountExternalSystemId></AccountExternalSystemId><AnnualRevenues></AnnualRevenues><IntegrationId></IntegrationId><JobTitle></JobTitle><LastUpdated>LIKE '*'</LastUpdated><LeadEmail></LeadEmail><LeadFirstName></LeadFirstName><LeadId></LeadId><LeadLastName></LeadLastName><NumberEmployees></NumberEmployees></Lead></SOAPSDK2:ListOfLead></SOAPSDK1:LeadWS_LeadQueryPage_Input></SOAP-ENV:Body></SOAP-ENV:Envelope>
However when i try to send this SOAP request using HTTP transport i get the gollowing error
Error invoking service 'abc', method 'Service' at step 'EAI HTTP'.(SBL-BPR-00162)
HTTP Request error during 'Submitting Data SendHTTP request': 'Status code - 400'(SBL-EAI-04117)
Edited by: user10259353 on Nov 4, 2008 3:28 AM

Check for the pod value in the URL eg:https://secure-ausomxxxx.crmondemand.com/Services/Integration
This value changes depending on the pod value assigned to you

Why Net.SOAP.request leads to NotAllowedError?

Similar Messages

Maybe you are looking for