Charmed Quark Systems, Ltd. - Support Forums and Community

Full Version: Porting a developed App to a different PC
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I've currently been developing my application on the Main CQC server box as it's been the easiest for me to get started and understand. However long term, there are bits and pieces that I want to migrate to a different machine. Is there a tutorial or FAQ that would help me accomplish the following:

A) Right now I have Zoomplayer and JRMC on the main server. Everythings configured so that it plays music fine and browses coverart. However, longterm, I want Zoomplayer to send the audio stream out a different PC that's attached to my whole house audio system (the Main CQC server is not). Is it as simple as deleting the existing ZP and JRMC drivers, recreating with the same name, but pointing it to a different PC that ZP will reside on? Will the JRMC XML need to be moved to the same PC or can it continue to reside on the main CQC Server.

B) Misc Stuff like weather and Horoscopes. Is there any advantage to moving these drivers to the actual CQC client machine where the main interface viewer will be running? Or should stuff like that always reside on the CQC server.

C) Right now all the templates are designed/defined on the main CQC server. However, long term, my touchscreens will be communicating via CAT5 extenders to a client CQC box. What's required to 'move' the templates to the client box (I figure there's a How-to somewhere on this, but I'm not sure where to look).

Basically, my architecture as it exists now is ONE CQC Server PC called Theater and all the drivers and templates are defined on it. Long term, I want to keep the CQC server on the Theater PC, but have the audio and interface viewer run from another PC.

PS.....Big thanks to Ripper and IVB for providing starting point templates...In less than a day, I've got a fair amount of stuff configured and running to where it's almost usable and will pass WAF.
A) Just remove the drivers and create them with the same names on the new box. It would be optimial to omve the XML and images to the machien where the JR driver is. You can just do a copy. That's what I do. I do the actual JR/DVDP on my bedroom machine, then export the XML and copy the images to the theater box and then force it to rescan.

B) No particular advantages having it on the client machine, and if the client machine isn't on all the time, that would be a good reaso for leaving it on the server.

C) You don't have to move the templates. They stay on the master server machine, and can be accessed from anywhere on the network that you've installed the client tools.
I would like to migrate CQC to another hardware and I would like to do it a driver at a time, while both systems run (the new in trial mode for now).

I concern about a collision on the LAN (two CQC Master servers). Is there a problem to do it? If there is, will subneting solver the problem.

I'm sure there is a solution that developers or Professional Installers are using. They need to have a base development system and need to build and test a few variations of CQC configuration (while their demo/test system is still running) before they deploy it to their customers.
Subnetting should take care of the issues. The only network related stuff that's not done via direct connections are the broadcasts for events. As long as those don't cross subnet boundaries, they shouldn't interfere with each other.
1) I know it's not CQC specific question, but I've never subneted a LAN

Any good tutorials?


2) How do I make sure Events don't cross subnet boundaries?

Thanks
I don't think that routers will pass broadcasts over subnet boundaries, right? So if you use a router, and set that router to a different sub-net address, any machines connected to that router should be in a different sub-net. Not sure how Windows workgroup/domain type stuff reacts to that.
I would say that your best best is to just move it wholesale to the new machine. Stop CQC on the main server and set it for manual startup, and bring it up on the new machine and get it running. If anything goes wrong and you need to step back and punt, remove it from the new machine and bring it back up on the old one. Keep it around on the old machine for a few weeks until you are sure the new one works, then just remove it on the old one.