I have constant for web services wsdl, web services node uses that constan

foussenik over 9 years ago

I have constant for web services wsdl, web services node uses that constant, however I am seeing very odd behavior in Appian 7.6., web services node is using different url from one defined in constant.
I am not sure where appian is getting the value being used to make web service calls.
I am in dev, but WS node is calling test wsdl which is not defined in my constant.

Discussion posts and replies are publicly visible

0 Tim Nguyen
Appian Employee
over 9 years ago

Has there been changes to the web service node recently? Have you tried restarting the application server?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 vineeta6579 over 9 years ago

Have you checked the "use a dynamic WSL URL option ".
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 foussenik over 9 years ago

I created a small process with node and used the wsdl directly, still same result meaning going to test server. Node can get soap operations,but at runtime it is going to test server. The soap location is correct in wsdl.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 vineeta6579 over 9 years ago

Please attach screenshot of the call webservice configuration tab
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 foussenik over 9 years ago

Here is a screen shot.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 9 years ago

Restart the application server to delete the cached WSDL then try again.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 foussenik over 9 years ago

Where to delete cached wsdl?
Is standalone\ mp\\work\\jboss.web\\default-host\\suite location are you referring?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 9 years ago

It will be automatically delete with the restart.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Mahesh Sanga over 9 years ago

We faced this issue today, JBoss restart didnt fix the issue at first time. We had to restart the JBoss thrice to make it work. Weird.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 9 years ago

You might want to consider upgrading to the latest versions of the product where the caching behavior has been improved.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel