HTTP Call Service in 2013 Workflow

How can you configure a workflow (Sharepoint 2013) to call an HTTP Web Service request and evaluate the response headers to determine if the POST to an MVC Controller end-point
was a success or failure

try these links for making http web request:
http://blogs.msdn.com/b/sharepointdesigner/archive/2012/09/05/how-to-work-with-web-service-using-call-http-web-service-action.aspx
http://blog.appliedis.com/2014/10/09/sharepoint-designer-2013-workflow-working-with-web-services/
https://sergeluca.wordpress.com/2013/04/09/calling-the-sharepoint-2013-rest-api-from-a-sharepoint-designer-workflow/
https://msdn.microsoft.com/en-us/library/office/dn567558%28v=office.15%29.aspx
for second question try below links:
http://sharepoint.stackexchange.com/questions/129699/sharepoint-2013-workflow
http://www.fiechter.eu/Blog/Post/37/SharePoint-2013--HTTP-Web-Service-Action---Use-Managed-Metadata-as-Text-in-Workflow
https://social.technet.microsoft.com/Forums/sharepoint/en-US/7b889b7c-d709-4e86-a8e8-c2d0b67b4c3f/problem-in-calling-http-web-service-in-sharepoint-2013-workflow?forum=sharepointcustomization
http://www.harbar.net/articles/sp2013rm2.aspx
Please mark answer as correct if it is correct else vote for it if you find it useful Happy SharePointing

Similar Messages

Workflow 2013: Call HTTP Web Service

Is It possible to use the Call HTTP Web Service action in Workflow 2013 to make it send
a document from a document libary with meta-data to ohter system webservice that I have implemented ?

Hi,
I have seen your similar thread post
here, please check if Steve's reply is helpful.
Thanks
Best Regards
Jerry Guo
TechNet Community Support

Calling (HTTPS web service) in sharepoint 2013 workflow (SPD)

I am using SharePoint 2013. I have created a list workflow in SharePoint Designer. I know there is an action "Call HTTP Web Service". Is it possible to access some webservice with authentication (username and password)?

http://msdn.microsoft.com/en-us/library/office/dn567558%28v=office.15%29.aspx
the OData formats support communication with anonymous web services as well as with those protected by various types of authentication. In short, you have full control over the request and response for each service call. This allows you to use a series of
activities within a workflow to first authenticate using one service and obtain an OAuth token, and then include that token in future requests to services secured using the
OAuth 2.0 protocol.
http://blogs.msdn.com/b/kaevans/archive/2009/03/10/calling-sharepoint-lists-web-service-using-wcf.aspx
<?xml version="1.0" encoding="utf-8" ?>
2: <configuration>
3: <system.serviceModel>
4: <bindings>
5: <basicHttpBinding>
6: <binding name="ListsSoap">
7: <security mode="TransportCredentialOnly">
8: <transport clientCredentialType="Ntlm" />
9: </security>
10: </binding>
11: </basicHttpBinding>
12: </bindings>
13: <client>
14: <endpoint
15: address="http://sharepoint/sites/HSC/_vti_bin/lists.asmx"
16: binding="basicHttpBinding"
17: bindingConfiguration="ListsSoap"
18: contract="ServiceReference1.ListsSoap"
19: name="ListsSoap" />
20: </client>
21: </system.serviceModel>
22: </configuration>http://www.tonytestasworld.com/post/2009/06/04/How-To-Authenticate-and-Use-SharePoint-Web-Services-in-an-FBA-SharePoint-site.aspx

HTTP Web Service in SP Designer 2013 Workflow calling WCF Service - 401 403 Error

Because of the limitations of SP Designer URL's I've had to create a custom webservice to Publish, Checkin, Approve etc.... I pass the List ID and a comment as parms in the HTTP POST. The WCF lives in the /15 ISAPI directory as it should.
I setup 3 dictionaries:
POST_RequestHeader
content-type: application/json;odata=verbose, accept:application/json;odata=verbose, X-HTTP-Method: MERGE, IF-MATCH:*,Authorization:
If I don't include Authorization as null, I get a 401. With this I get a 403.
POST_Metadata
type string "name of my SP.Data category from tyhe list"
POST_Parameters
__metadata with the name of POST_Metadata
Call the webservice in SP DESIGNER 2013
Http://Mysitecollection/_vti_bin/MyWCFService/MyWCFService.svc/MyPublish/?id=123&comment='BasicTest2'
RequestHeaders set to POST_RequestHeader
RequestContent set to POST_Parameters
The Interface correctly maps and routes me to the method. The document is in Draft state ready for "Publish a Major version".
I cannot get past the security errors. My GET methods work fine. Any thoughts? How can I pass the proper credentials?
I'm running in an App Step and have granted workflows elevated privileges so no problem there.
Thanks.
                using (SPSite siteCollection = new SPSite("myservercollectionurl"))
                    using (SPWeb web = siteCollection.OpenWeb())
                        SPWeb site = siteCollection.RootWeb;
                        SPList corpPol = site.Lists["Our Policies"];
                        SPListItem spListItem = corpPol.GetItemById(id);
                        SPFile file = spListItem.File;
                        trace = "In SPsite Loop" + spListItem["Title"].ToString();
<--- Title is written OK to log
                        diagSvc.WriteTrace(0, category, TraceSeverity.Verbose, trace);
                        if (file.CheckOutType == SPFile.SPCheckOutType.None)
                            spListItem.File.Publish("done in WCF");
<-- Blows everytime with 403 Forbidden
This is in the Sharepoint logs:
System.Runtime.InteropServices.COMException (0x8102006D): The security validation for this page is invalid. Click Back in your Web browser, refresh the page, and try your operation again.     at Microsoft.SharePoint.SPFile.PublishOrUnPublish(String
comment, Boolean fPublish)
Tom

Hi Tom,
Here are two blogs for you to check:
Using SharePoint REST services from workflow with POST method
http://mysharepointinsight.blogspot.com/2013/05/using-sharepoint-rest-services-from.html
SharePoint Designer 2013 Workflow: Working with Web Services
http://blog.appliedis.com/2014/10/09/sharepoint-designer-2013-workflow-working-with-web-services/
We can use the fiddler to compose the HTTP POST method with the properly request headers and request body, then create your workflow.
http://www.fabiangwilliams.com/2013/09/03/more-on-sharepoint-2013-rest-api-with-fiddler-and-spd/
Best Regards
Dennis Guo
TechNet Community Support

SharePoint 2013 Designer Workflow Cannot find Action - Call Http web service

Hi All,
I Do not see the option in the workflow where i can add the action "Call HTTP Webservice.
Am I doing something wrong.
Thanks

Hi Nick,
Is only this action "Call HTTP Webservice" missing from SharePoint 2013 workflow?
If other actions are also missing, you can reinstall and reconfigure workflow for SharePoint 2013.
Please double check and make sure you create the SharePoint 2013 workflow platform .
http://technet.microsoft.com/en-us/library/jj658588(v=office.15).aspx
http://msdn.microsoft.com/en-us/library/office/jj164026(v=office.15).aspx
Thanks
Daniel Yang
TechNet Community Support

401 Unauthorized Error When calling a SharePoint REST web service from SharePoint 2013 Workflow

We have our Workflow Manger installed on the same server as our SharePoint 2013 WFE development environment. When creating a SharePoint 2013 Workflow all Calls to a SharePoint 2013 REST web service results in a 401 Unauthorized error.
As an example I created a simple workflow that should return a JSON result. The REST Url returns the results in the browser without error.
Set Variable:webServiceUrl to https://<hostnamedsitecollection>/_vti_bin/client.svc/web/lists/getbytitle('ISR%20Approvers')/Items?$select=Title&$filter=Title%20eq%20%27General%27
then Build{...} Dictionary (Output to Variable:requestHeaders)
then Call [%Variable:webServiceUrl%] HTTP web service with request (ResponseContent to Variable:responseContent |ResponseHeaders to responseHeaders | ResponseStatusCode to Variable:responseCode)
The RequestHeader is set to the requestHeaders variable though the web service call properties
then Log Variable:responseCode to the workflow history list
After manually running the workflow in SharePoint on a list item in the ISR Approvers list it Logs "Unauthorized" in the Workflow History Log. It does this with every SharePoint REST web service call that I have tried through the workflow.
It doesn't have anything to do with the Workflow Manger being installed on the same machine as the SharePoint WFE does it?
Thank You for any insight

Hi,
According to your post, my understanding is that you had 401 Unauthorized Error when calling a SharePoint REST web service from SharePoint 2013 Workflow.
Please make sure you use the ‘Call HTTP Web Service’ correctly.
You can enter the URL into the brower to check whether it is correctly.
You need to
create the Request header requestHeaders
using a Dictionary:
Accept : application/json;odata=verbose
Content-Type : application/json;odata=verbose
To associate the
requestHeaders variable, select the Call action
property, set the RequestHeaders property to
requestHeaders.
Please refer to the following articles:
Working with Web Services in SharePoint 2013 Workflows using SharePoint Designer 2013
Calling the SharePoint 2013 Rest API from a SharePoint Designer
Workflow
In addtion, you need to make sure you install the workflow manager correctly.
More information:
Install and configure workflow for SharePoint Server 2013
Known Issues in Workflow Manager 1.0
Troubleshooting Workflow Manager 1.0 Management and Execution
Best Regards,
Linda Li
Linda Li
TechNet Community Support

How to copy List item from one list to another using SPD workflow using HTTP call web service

Hi,
How to copy List item from one list to another using SPD workflow using HTTP call web service.
Both the Lists are in different Web applications.
Regards, Shreyas R S

Hi Shreyas,
From your post, it seems that you are using SharePoint 2013 workflow platform in SPD.
If that is the case, we can use Call HTTP web service action to get the item data, but we cannot use Call HTTP web service to create a new item in the list in another web application with these data.
As my test, we would get Unauthorized error when using Call HTTP web service action to create a new item in a list in another web application.
So I recommend to achieve this goal programmatically.
More references:
https://msdn.microsoft.com/en-us/library/office/jj164022.aspx
https://msdn.microsoft.com/en-us/library/office/dn292552.aspx?f=255&MSPPError=-2147217396
Thanks,
Victoria
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Call HTTP web service action not allowing HTTPS in SharePoint Designer 2013.

HTTP works perfectly in browser and in workflow.
HTTPS works perfectly in browser and hangs in workflow.
Others having this issue have been advised to use OAuth2. OAuth2 is not an option without HTTPS, you're passing authorization tokens around in plaintext. This is not an acceptable solution.
Please advise.

It says HTTPS web services will have an Issue with the SharePoint Designer.
Thanks, Parth

"Invalid text value" error when calling a web service from a workflow in SharePoint Online

I'm trying to create a workflow that loops through a list in SharePoint Online using a REST web service call. However, I'm having
some trouble trying to pass the authentication token as described in the following article.
http://www.fabiangwilliams.com/2013/09/03/more-on-sharepoint-2013-r...
Basically, the workflow stops right at the "Call web service" action, and the only error it tells me is the following.
Invalid text value.
A text field contains invalid data. Please check the value and try again
Has anyone had success with web service calls to SharePoint Online?
Dan Kreitz, Solutions Architect, Séafra Inc.

Hi DanPoint,
Thank you for your sharing!
Best Regards,
Wendy
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Wendy Li
TechNet Community Support

Issue with Calling Rest Web Service using Designer workflow

Hello all
I am calling a Rest web service- HTTP Post (yammer API)-
http://www.yammer.com/api/v1/messages.json?data-app-id=myappid&group_id=groupid&body=MyPost in yammer using sharepoint 2013 designer workflow.(My Requirement is to create a yammer post when I approve an item in sharepoint).
but my header parameters are creating issue while executing workflow.
Currently I have these many parameters configured in request header
Accept -application/json; odata=verbose
Content Type -application/json; odata=verbose
content length header -255
Is there anything wrong or I need to additionally pass some values in call web service action?
Any help would be highly appreciated

Hi Mahesh,
One you are missing is authentication token or credentials.
Please refer to the following articles.
http://www.cleverworkarounds.com/2014/02/05/tips-for-using-spd-workflows-to-talk-to-3rd-party-web-services/
A Series of articles related to Web Service in SPD Workflow
Trials or tribulation?
Inside SharePoint 2013 workflows–Part 1
Trials or tribulation?
Inside SharePoint 2013 workflows–Part 2
Trials or tribulation?
Inside SharePoint 2013 workflows–Part 3
Trials or tribulation?
Inside SharePoint 2013 workflows–Part 4
Trials or tribulation?
Inside SharePoint 2013 workflows–Part 5
Trials or tribulation?
Inside SharePoint 2013 workflows–Part 6
Trials or tribulation?
Inside SharePoint 2013 workflows–Part 7
Trials or tribulation?
Inside SharePoint 2013 workflows–Part 8
Trials or tribulation?
Inside SharePoint 2013 workflows–Part 9
Trials or tribulation?
Inside SharePoint 2013 workflows–Part 10
Trials or tribulation?
Inside SharePoint 2013 workflows–Part 11
Trials or tribulation?
Inside SharePoint 2013 workflows–Part 12
Please don't forget to mark it answered, if your problem resolved or helpful

Call Exchange Web Services from SP2013 Workflow

Okay... so I would love to be able to call exchange.asmx to issue an "ExpandDL" request to get the members of a particular distribution list, but I can't seem to find any documentation on how to actually make that happen or how to make any code
examples I find fit into the "Call HTTP Web Service" action format inside SPD. Ideas?

Hi ramz,
Based on the following similar post and article, SharePoint Designer 2013 platform workflow activity "Call HTTP Web Service" can't use the SOAP web service provided by Exchange(e.g. exchnage.asmx), we could only use the RESTful web service.
http://sharepoint.stackexchange.com/questions/68905/how-to-call-a-soap-webservice-with-the-call-http-service-action-in-a-workflow
https://social.technet.microsoft.com/Forums/en-US/2be5a47c-4574-4a27-a480-dabb5c0794b5/soap-webservice-using-sharepoint-designer-2013?forum=sharepointgeneral
https://msdn.microsoft.com/en-us/library/office/dn789003(v=exchg.150).aspx
Thanks
Daniel Yang
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Call HTTP Web Service Retries Every 1 Minute

I currently have a SharePoint 2013 workflow setup. This workflow calls an HTTP Web Service using the HTTP Get Method. The web service takes over a minute to execute what it needs to and respond. The workflow retries calling the web service every 1 minute
if it doesn't get a response back. This is causing issues as the process is already running and doesn't need to be run again. Is there some setting or response/request header value that I can set to prevent the workflow from retrying the web service call every
minute?
Thank You,
Jon

Hi,
As per your posting, I believe there is no direct approach in the workflow to check the web service status for every call.
Let me try to work on that and try to give you the appropriate solution.
Sekar - Our life is short, so help others to grow
Whenever you see a reply and if you think is helpful, click "Vote As Helpful"! And whenever you
see a reply being an answer to the question of the thread, click "Mark As Answer

HTTP call in a workflow using GetFolderByServerRelativeUrl returns Forbidden

This is using Office365 SPO with a 2013 workflow being created in the 2013 Designer.
We are trying to make a workflow (whose steps will later on be part of a larger) that simply does an HTTP GET call. We have a url variable set to https://xxxxx.sharepoint.com/sites/xxxx/_api/web/GetFolderByServerRelativeUrl('/sites/xxx/xxx')/files, headers
Accept and Content-Type set to "application/json;odata=verbose" and Authorization as an empty string. In the call action the RequestType is GET, RequestHeaders has those values, and the ResponseContent/Headers are set to empty dictionaries with a
ResponseStatusCode variable as an empty string. When the workflow is run the ResponseStatusCode is given a value of Forbidden. When the Authorization header part is missing it returns Unauthorized as per normal.
Navigating to the web url shows the feed page with the correct number of file entries. However, the entries all contain 0 info in the response (I'm guessing that has to do with it being a url call instead of an actual REST call).
Any ideas? This is making my and another employee's foreheads the same flatness as our desks.
Note: Both of us are still fairly new as SP was tossed on our laps w/o any warning. So if it looks like any of this is a horrible way please say so, nicely ;)

Hi Tanwedar,
Thanks for posting your issue, Kindly browse the below mentioned URL to create workflow step by step using Designer 2013
http://dinushaonline.blogspot.in/2014/07/sharepoint-2013-workflow-check-if.html
I hope this is helpful to you. If this works, Please mark it as
Answered.
Regards,
Dharmendra Singh (MCPD-EA | MCTS)
Blog :
http://sharepoint-community.net/profile/DharmendraSingh

2013 Workflow Service - Enabled for Other Site Collections

I have setup the 2013 workflow service with our SharePoint environment. This works fine with the site collection originally used to register the workflow service.
The other site collections (in the same web application - we are using host named site collections) cannot see this, and SharePoint designer gives the error: "The option for the SharePoint 2013 Workflow platform is not available because the workflow
service is not configured on the server".
Now as the other site collections are in the same web application, the have the service connection to the "Workflow Service Application Proxy".
I have also seen posts about running a "Enable-SPFeature" command on the other site collections to enable WorkflowService or WorkflowServiceStore but this only returned an error (essentially) saying the futures were already enabled.
Where else can I look to try and diagnose what is wrong or what can I do to allow the other site collections to get access to the 2013 workflow service?
Thanks,
Richard

Hi,
According to your post, my understanding is that the SharePoint 2013 workflow platform not worked in other site collection.
Did you enable the workflow service application proxy? You can enable it as below, then check whether it works.
Whenever a new workflow service application proxy is created in SP2013, by default it will not be associated(service connection) with any web application.
You can go to Central admin site->Manage web applications page -> Select the web app which was registered earlier during configuration and check " workflow service application proxy" and click OK.
Did the workflow platform work in other web application?
If they all not work, I recommend you reconfigure the workflow manager, you can also check the steps with the following articles.
http://ranaictiu-technicalblog.blogspot.com/2013/02/sharepoint-2013-workflow-manager.html
http://technet.microsoft.com/en-us/library/jj658588.aspx
Thanks & Regards,
Jason
Jason Guo
TechNet Community Support

How to call a Https Web service client (partner link)

Hi,
I am trying to call a https web service and having issues with it. I have copied the server certificate into my JDeveloper truststore as well as into OC4J truststore. I have successfully deployed the application but when I initiate the process and enter input values, it throws the following exception 'Security Requirements not met - No Security header in message'
<fault>
- <remoteFault xmlns="http://schemas.oracle.com/bpel/extension">
- <part name="code">
<code>
Server
</code>
</part>
- <part name="summary">
<summary>
Security Requirements not met - No Security header in message
</summary>
</part>
- <part name="detail">
<detail>
<detail>
<ns2:exception xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="com.sun.xml.wss.XWSSecurityException" note="To disable this feature, set com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace system property to false">
<message xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">Security Requirements not met - No Security header in message</message>
<ns2:stackTrace xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="com.sun.xml.ws.security.opt.impl.incoming.SecurityRecipient" file="SecurityRecipient.java" line="738" method="createMessage"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="com.sun.xml.ws.security.opt.impl.incoming.SecurityRecipient" file="SecurityRecipient.java" line="226" method="validateMessage"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="com.sun.xml.wss.provider.wsit.WSITServerAuthContext" file="WSITServerAuthContext.java" line="471" method="verifyInboundMessage"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="com.sun.xml.wss.provider.wsit.WSITServerAuthContext" file="WSITServerAuthContext.java" line="297" method="validateRequest"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="com.sun.xml.wss.provider.wsit.WSITServerAuthContext" file="WSITServerAuthContext.java" line="211" method="validateRequest"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="com.sun.enterprise.webservice.CommonServerSecurityPipe" file="CommonServerSecurityPipe.java" line="168" method="processRequest"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="com.sun.enterprise.webservice.CommonServerSecurityPipe" file="CommonServerSecurityPipe.java" line="129" method="process"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="com.sun.xml.ws.api.pipe.helper.PipeAdapter" file="PipeAdapter.java" line="115" method="processRequest"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="595" method="__doRun"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="554" method="_doRun"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="539" method="doRun"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="436" method="runSync"/
>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="com.sun.xml.ws.server.WSEndpointImpl$2" file="WSEndpointImpl.java" line="243" method="process"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit" file="HttpAdapter.java" line="444" method="handle"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="com.sun.xml.ws.transport.http.HttpAdapter" file="HttpAdapter.java" line="244" method="handle"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="com.sun.xml.ws.transport.http.servlet.ServletAdapter" file="ServletAdapter.java" line="135" method="handle"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="com.sun.enterprise.webservice.JAXWSServlet" file="JAXWSServlet.java" line="159" method="doPost"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="javax.servlet.http.HttpServlet" file="HttpServlet.java" line="738" method="service"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="javax.servlet.http.HttpServlet" file="HttpServlet.java" line="831" method="service"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="org.apache.catalina.core.ApplicationFilterChain" file="ApplicationFilterChain.java" line="411" method="servletService"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="org.apache.catalina.core.StandardWrapperValve" file="StandardWrapperValve.java" line="290" method="invoke"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="org.apache.catalina.core.StandardContextValve" file="StandardContextValve.java" line="271" method="invokeInternal"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="org.apache.catalina.core.StandardContextValve" file="StandardContextValve.java" line="202" method="invoke"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="org.apache.catalina.core.StandardPipeline" file="StandardPipeline.java" line="632" method="doInvoke"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="org.apache.catalina.core.StandardPipeline" file="StandardPipeline.java" line="577" method="doInvoke"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="com.sun.enterprise.web.WebPipeline" file="WebPipeline.java" line="94" method="invoke"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="org.apache.catalina.core.StandardHostValve" file="StandardHostValve.java" line="206" method="invok
e"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="org.apache.catalina.core.StandardPipeline" file="StandardPipeline.java" line="632" method="doInvoke"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="org.apache.catalina.core.StandardPipeline" file="StandardPipeline.java" line="577" method="doInvoke"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="org.apache.catalina.core.StandardPipeline" file="StandardPipeline.java" line="571" method="invoke"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="org.apache.catalina.core.ContainerBase" file="ContainerBase.java" line="1080" method="invoke"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="org.apache.catalina.core.StandardEngineValve" file="StandardEngineValve.java" line="150" method="invoke"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="org.apache.catalina.core.StandardPipeline" file="StandardPipeline.java" line="632" method="doInvoke"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="org.apache.catalina.core.StandardPipeline" file="StandardPipeline.java" line="577" method="doInvoke"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="org.apache.catalina.core.StandardPipeline" file="StandardPipeline.java" line="571" method="invoke"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="org.apache.catalina.core.ContainerBase" file="ContainerBase.java" line="1080" method="invoke"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="org.apache.coyote.tomcat5.CoyoteAdapter" file="CoyoteAdapter.java" line="272" method="service"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask" file="DefaultProcessorTask.java" line="637" method="invokeAdapter"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask" file="DefaultProcessorTask.java" line="568" method="doProcess"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask" file="DefaultProcessorTask.java" line="813" method="process"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="com.sun.enterprise.web.connector.grizzly.DefaultReadTask" file="DefaultReadTask.java" line="341" method="executeProcessorTask"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="c
om.sun.enterprise.web.connector.grizzly.ssl.SSLReadTask" file="SSLReadTask.java" line="440" method="process"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="com.sun.enterprise.web.connector.grizzly.ssl.SSLReadTask" file="SSLReadTask.java" line="228" method="doTask"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="com.sun.enterprise.web.connector.grizzly.TaskBase" file="TaskBase.java" line="265" method="run"/>
<ns2:frame xmlns:ns2="http://jax-ws.dev.java.net/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" class="com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread" file="SSLWorkerThread.java" line="106" method="run"/>
</ns2:stackTrace>
</ns2:exception>
</detail>
</detail>
</part>
</remoteFault>
</fault>
Any help will be appreciated. I am using JDeveloper 10.1.3.3.0.
Thanks

Hmm, based on error it looks like service provider expecting some security headers. Are you able to test from other utility soapUI or browser?
Regards,
Chintan

HTTP Call Service in 2013 Workflow

Similar Messages

Maybe you are looking for