IWS - ClickOnce Deployment... what gets stored on the Agent PC?

[JTL]

I have a question about IWS...

We're configured to use a ClickOnce deployment, and use 2 different versions for different agent types (just a historical thing... and a way of keeping the 2 configurations separate). I found the XML file to edit for the SIPEndpoint settings (including ports to use, codec priority etc.) - but I also checked the Agent workstation (Windows XP) where I had deployed a version of IWS using the ClickOnce page, and found nothing of IWS installed, except the shortcut icon and some files in the c:\windows\prefetch directory - so the XML file isn't pushed to the Agent workstation?

I couldn't find much (anything?) about the SIPEndpoint module in the IWS documents - other that to mention that it exists.

I did find SIPEndpoint SDK documentation, but this isn't the same thing.

So...: what actually gets deployed to the Agent PC with a ClickOnce installation, and can someone confirm that if I modify the relevant XML file and redeploy my IWS instance (I'll do a test one, I expect...) that this will take care of these settings?

[Timur Karimov]

ClickOnce it's not a Genesys invention. It's standart MS technology. SO, did you ever try to read something about it before ask the question?
I mean MSDN tech. overview for example?

[JTL]

[quote author=Timur Karimov link=topic=7791.msg33791#msg33791 date=1367190510]
ClickOnce it's not a Genesys invention. It's standart MS technology. SO, did you ever try to read something about it before ask the question?
I mean MSDN tech. overview for example?
[/quote]

Not yet - I just wondered what actually got stored on the Agent PC. I can look as MSDN tech or I guess I can Google it, but I did think this was a forum where people could ask questions... and not just be put in their place?

I'm not a Microsoft techie, and haven't come across ClickOnce before... and I'm quite certain there would be others on this forum who might be interested in what should hopefully be a simple answer.

So... when I've googled it and found out the answer, should I share it on here for anyone else who might be interested, or just keep the answer to myself and let everyone else struggle?

[Kubig]

It is not important where is located IWS files after install it via ClickOnce, all changes which you need to do on IWS via configuration files, you have to change it on server side (where ClickOnce is deployed), deploy a new version/brand of IWS and next re-distribute to agent PC, that is all.

[JTL]

[quote author=Kubig link=topic=7791.msg33801#msg33801 date=1367237304]
It is not important where is located IWS files after install it via ClickOnce, all changes which you need to do on IWS via configuration files, you have to change it on server side (where ClickOnce is deployed), deploy a new version/brand of IWS and next re-distribute to agent PC, that is all.
[/quote]

Yes, I appreciate this - but I was also expecting to see *something* on the Agent PC which would show the existing configuration. I was surprised not to be able to locate it, and didn't have the Agent PC to hand when I wrote the initial post.

I've since had a browse in hidden and system folders, and have found the files generated by the IWS deployment. There are some config files, including one for the SipEndpoint - but as part of the testing phase, I wanted to see that the SipEndPoint setting changes were deployed to config files / XML before testing them.

Not a problem, I'll just deploy and then run Wireshark and check the port ranges for some test calls. If I deploy a test version with a VERY limited port range, I should soon be able to see whether my changes were successful or not.

[Kubig]

Look at folder and subfolders C:\Users\YourUser\AppData\Local\Apps\2.0\*. In one of subfolders is saved IWS application with all DLL and etc.

[JTL]

[quote author=Kubig link=topic=7791.msg33803#msg33803 date=1367240028]
Look at folder and subfolders C:\Users\YourUser\AppData\Local\Apps\2.0\*. In one of subfolders is saved IWS application with all DLL and etc.
[/quote]

Thanks Kubig - as above, I found them... usually those folders are hidden, so I needed our IT guys to unlock an Agent PC and give me local admin over it to check, but I found them this morning