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
17 replies
Subscribers
5 subscribers
Views
5383 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
Hi All, I published the process model as service & used that url
rishub356
over 8 years ago
Hi All,
I published the process model as service & used that url into SOAP UI. I am getting the following error:
org.apache.xmlbeans.XmlException: org.apache.xmlbeans.XmlException: error: Unexpected element: TAG_END
Can any one guide what is the issue?
Thanks
OriginalPostID-199964
OriginalPostID-199964
Discussion posts and replies are publicly visible
0
Eduardo Fuentes
Appian Employee
over 8 years ago
I'm thinking you need a proxy then. Go to Internet Explorer - Internet Options - Connections - LAN Settings.
Do you see a proxy configured there?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
rishub356
over 8 years ago
Here is the IE Proxy Settings
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 8 years ago
1. Those proxy settings don't look like they would be required to be applied to SoapUI.
2. Let me ask you this, when you clear your browser cookies, if you navigate to
xxxxxxxxxxxxxxxxxxx/.../syncProcess
do you have to login to see the WSDL? What do you see right after typing that URL?
3. Is your Appian site SSO enabled? (e.g. SAML, SiteMinder, Kerberos, etc)
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
rishub356
over 8 years ago
Hey Eduardo, even after I clear my browser cookies, I can see the WSD after I paste URL. Yes, our Appian site SSO is enabled.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 8 years ago
What SSO are you using? I'm thinking that when SoapUI is making the call to the WSDL, it's getting your SSO login page instead of the WSDL. I wouldn't expect that though, since the WSDLs for models are supposed to be whitelisted by default to bypass authentication.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 8 years ago
I think my theory is correct. I edited my configuration files to require authentication for URLs of type /webservice/processmodel/ (which is NOT the default behavior) and got the same error with SoapUI.
You should check with your system administrator if the SSO solution is protecting URLs of type /webservice/processmodel/, it should not, since the invocation already has protection via the required authentication parameters in the request.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 8 years ago
This URL is whitelisted by default inside ear\\suite.ear\\web.war\\WEB-INF\\conf\\security\\spring-security-02-unsecured*
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
<