Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
10 replies
Subscribers
5 subscribers
Views
2864 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Integrations
Has anyone used Appian 7.2 to integrate with SharePoint2010 using WSDL and the &
ianc236
over 10 years ago
Has anyone used Appian 7.2 to integrate with SharePoint2010 using WSDL and the "Call Web Service" nodes; if so how did you achieve it; if so did you encounter any memory issues and how did you resolve them?
Thanks...
OriginalPostID-88969
OriginalPostID-88969
Discussion posts and replies are publicly visible
0
shelzle
over 10 years ago
Please search for SharePoint in forum. There are several posts regarding this. The webservices provided by MS are not compatible with Appian. The lists.asmx webservice can be called using the HTTP request plugin. We are doing this. Works quite well.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
ianc236
over 10 years ago
Thanks for this
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
ianc236
over 10 years ago
Have now searched the Forum as suggested and it appears there are lots of questions and not a lot of answers that match my question. Not so sure about the MS non compatibility; in what way are they not compatible when Appian's own documentation talks about albeit briefly using them. Plus I have process models that currently work using them but it appears they use an unnecessary amount of resource which doesn't appear to get cleared down once the process model has completed. What I would like to know is how can I from the PM ensure the resource used by the Call Web Service node(s) is cleared down once the PM task has completed.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
shelzle
over 10 years ago
To clean up any used resources you can put the nodes in a sub process and delete it as soon as it completed. See tab "Data Management" on process model properties dialog.
Regarding SharePoint: Do you already have implemented any functionality you need? AFAIK there are at least 4 types of webservices to access SharePoint. (1) SOAP webservices provided by MS, (2) SOAP webservices provided by the Appian SharePoint addon, (3) XML-RPC (lists.asmx) provided by MS and I think SharePoint 2010 already provides some form of (4) REST interface.
(1) does not work because of crappy data definitions in the WSDLs
(2) works but does not provide much functionality and are rather old
(3) works using the HTTP request plugin. We use that way
(4) should work using HTTP request and JSON plugins. Will be our way to go
@ Appian PS: Could you please create a wiki page to document this topic.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
sreenivasaraoa
over 10 years ago
(3) works using the HTTP request plugin. We use that way --- Could you please provide any documentaion on this
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
ianc236
over 10 years ago
Thank you for the post however, our issue seems to have gone away and our processes using WSDL connectivity to SP2010 are stable
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
sreenivasaraoa
over 10 years ago
We are facing problem with WSDL connectivity to SP2010 by "call webservices" by both https and https. Could you please suggest
Thanks
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
ianc236
over 10 years ago
I'm assuming you are now trying to use the Call Web-Service Smart Service nodes. At this moment in time I haven't created any documentation due to work load on other projects. What type of authentication are you using to connect to your SP2010 environment?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
sreenivasaraoa
over 10 years ago
I am trying to coneect using Call Web-Service Smart Service with HTTP Authentication only. The sharePoint url is SSL (https). Getting error with this approach.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
ianc236
over 10 years ago
We had to enable http authentication on the SP environment.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel