<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.appian.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Issue consuming web service in Appian</title><link>https://community.appian.com/discussions/f/integrations/5002/issue-consuming-web-service-in-appian</link><description>I have &amp;quot;Oasis Web Service Security&amp;quot; in my SOAP Web Service. It has &amp;quot;username token&amp;quot; used in it. I am unable to access it from &amp;quot;Call Web Service&amp;quot; and &amp;quot;HTTP Query&amp;quot; smart services. Do I need to create a JAVA plugin for it ? If yes, any suggestions which</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Issue consuming web service in Appian</title><link>https://community.appian.com/thread/40877?ContentTypeID=1</link><pubDate>Thu, 29 Dec 2016 19:41:35 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:7989ff89-d7dc-4059-b997-64cddd5749e0</guid><dc:creator>saksheer</dc:creator><description>Hi Mayank, I have a similar requirement of calling a web service which absolutely uses OASIS UsernameToken/PasswordDigest Authentication. Would you be able to tell, what approach did you use in your case?&lt;br /&gt;&lt;br /&gt;Thanks in Advance.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Issue consuming web service in Appian</title><link>https://community.appian.com/thread/20666?ContentTypeID=1</link><pubDate>Fri, 24 Jul 2015 22:42:14 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:c5d7c20c-f58e-4cca-a283-bedb6b0b7f45</guid><dc:creator>mayankk718</dc:creator><description>I did it using Java :)&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Issue consuming web service in Appian</title><link>https://community.appian.com/thread/18414?ContentTypeID=1</link><pubDate>Fri, 29 May 2015 15:56:08 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:f2e63ab5-efd0-4e6f-8ccd-e32ecefc02b5</guid><dc:creator>akhileshn</dc:creator><description>It looks like the web service uses WS-Security and is not supported by OOTB call web service smart service. You may have to modify the wsdl to get this working as suggested here &lt;a href="https://forum.appian.com/suite/help/7.9/Advanced_Web_Service_Configuration.html"&gt;forum.appian.com/.../Advanced_Web_Service_Configuration.html&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Alternatively, generate the SOAP envelope of request with username token and use http connector to make request to service.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Issue consuming web service in Appian</title><link>https://community.appian.com/thread/18371?ContentTypeID=1</link><pubDate>Thu, 28 May 2015 18:52:34 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:8e3c49cc-1013-4dd1-8b63-7eb119f81ff4</guid><dc:creator>sayedh</dc:creator><description>I would recommend that you take the wsdl from the provider and modify it to remove &amp;quot;choice&amp;quot;. Sometimes people create/generate complicated wsdls that make it difficult to consume and you have to modify the wsdl to be able to consume it in appian. Please keep in mind that you have to keep the semantics of the wsdl intact but changing it to remove some of the xsd restrictions is okay. To give you an example, if the wsdl defines a choice to limit the values that can be passed as part of an element but the underlying type is string, you can remove the choice and replace it with xsd:string and the wsdl definition is still intact. Hope this helps.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Issue consuming web service in Appian</title><link>https://community.appian.com/thread/18348?ContentTypeID=1</link><pubDate>Thu, 28 May 2015 14:42:41 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:3185ce94-0cf9-4c92-85a6-1945fe26b259</guid><dc:creator>mayankk718</dc:creator><description>I got your point of multi level request. But, the service is unaccessible from &amp;quot;Call Web Service&amp;quot; smart service because it has &amp;quot;choice&amp;quot; of inputs. If you pass any 1 input out of n inputs (that are available), the request can move forward. Such services are not supported by &amp;quot;Call Web Service&amp;quot; smart service unfortunately.&lt;br /&gt;&lt;br /&gt;Any way to achieve this 2 level request in Java (especially the security part) ?&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Issue consuming web service in Appian</title><link>https://community.appian.com/thread/18347?ContentTypeID=1</link><pubDate>Thu, 28 May 2015 14:42:24 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:d1a0ba2d-f8a5-424a-bcf8-825286eb45db</guid><dc:creator>mayankk718</dc:creator><description>I got you point of multi level request. But, the service is unaccessible from &amp;quot;Call Web Service&amp;quot; smart service because it has &amp;quot;choice&amp;quot; of inputs. If you pass any 1 input out of n inputs (that are available), the request can move forward. Such services are not supported by &amp;quot;Call Web Service&amp;quot; smart service unfortunately.&lt;br /&gt;&lt;br /&gt;Any way to achieve this 2 level request in Java (especially the security part) ?&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Issue consuming web service in Appian</title><link>https://community.appian.com/thread/18344?ContentTypeID=1</link><pubDate>Thu, 28 May 2015 13:58:26 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:c8d47c27-b943-4143-b875-9c288a7f7374</guid><dc:creator>Stefan Helzle</dc:creator><description>This looks like you have to do two calls. First one for authentication which returns a token. Second one for the actual call which uses that token. So you would need at least two call webservice nodes in the process.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>