Created by: Melissa Smith on 12-01-2011 11:44:08 PM <!--StartFragment--> I¿m currently working with a customer and we have been using the Web Service Element in Studio successfully in the lab environment, now we are deploying the apps to production. We are changing the WSDL¿s in the app to reflect production environment instead of the lab environment. But when we deploy the new app to the production VXML servers and make a test call, we are getting a web service failure, when looking into this deeper it shows in the logs that WSDL info has defaulted back to the lab environment information.
We can see this by looking into the Application¿s web service folder on the vxml and looking at the WSDL file via notepad and see that it¿s pointing back to the lab environment instead of production even though we had made the change in studio, saved it, and deployed again.
Has anyone else encountered any issues like this before? I don't believe this would be "working as designed". Any information or workaround would greatly be appreciated.
<!--EndFragment-->
Subject: RE: Re: New Message from Melissa Smith in Customer Voice Portal (CVP) - CVP Replied by: Melissa Smith on 13-01-2011 01:06:32 AM So we brought in a new web service element and loaded the new WSDL, then deployed. I think I mentioned before ..we found a work around but it's ugly and the customer isn't very happy or excited about the workaround, especially since there are several apps and numerous production servers that we will have to push this to. This is what we did: We released the previous app and deleted it from the vxml server before deploying the "new" app. Then we looked in the Web Service's folder and looked at the WSDL file (for lack of a better term) and saw that it was pointing to the lab environment (even after loading a new web service element with the new wsdl.) We then modified it there and saved, then we were able to get it work. Please tell me this isn't a "working as designed" thing.
When you say that 'We are changing the WSDL in the app to reflect production environment' - what exactly do you mean?
Once you load a wsdl into a Web Services element, there's no way to change the wsdl that the element has loaded (other than using a new web services element, or going into the location where studio stores the wsdl information).
I suspect that you might think you're changing the wsdl, but you're probably not changing the one that Studio has loaded and deploys with. Studio stores a copy of the wsdl into the directory C:\Cisco\CallStudio\eclipse\workspace\AppName\callflow\.wsdl_repository - it'll have a strange name on the file (usually a negative sign and a lot of digits).
You could back up your application (make a copy of it) and then quit studio; replace this local copy of the wsdl file with the modified one that points to a production server; and then start studio; then deploy from studio and you should be good to go.
Janine
On 1/12/2011 6:44 PM, Cisco Developer Community Forums wrote: > We are changing the WSDLâ¿¿s in the app to reflect production environment
-- Janine Graves
Subject: Re: New Message from Melissa Smith in Customer Voice Portal (CVP) - CVP - A Replied by: Janine Graves on 13-01-2011 12:41:01 AM When you say that 'We are changing the WSDL in the app to reflect production environment' - what exactly do you mean?
Once you load a wsdl into a Web Services element, there's no way to change the wsdl that the element has loaded (other than using a new web services element, or going into the location where studio stores the wsdl information).
I suspect that you might think you're changing the wsdl, but you're probably not changing the one that Studio has loaded and deploys with. Studio stores a copy of the wsdl into the directory C:\Cisco\CallStudio\eclipse\workspace\AppName\callflow\.wsdl_repository - it'll have a strange name on the file (usually a negative sign and a lot of digits).
You could back up your application (make a copy of it) and then quit studio; replace this local copy of the wsdl file with the modified one that points to a production server; and then start studio; then deploy from studio and you should be good to go.
Janine
On 1/12/2011 6:44 PM, Cisco Developer Community Forums wrote: > We are changing the WSDLâ¿¿s in the app to reflect production environment
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: