Yes Dart is setup on N7DOLST05 to push to N7DOLWEB01 02 03. But I can’t traverse (UNC) from dolpubcms01 to N7DOLSTG05 like I thought, so no easy prop file update. This is how its currently setup. Dolpubcms01 ? UNC ? dolstg05 ? dart ? dolcdnsrc ? dolimg This is how I have it setup. Dolpubcms01 ? UNC ? dolstg05 ?pull/push from?? N7DOLSTG05-> dart -> N7DOLWEB01 02 03 ?dolimg The only difference is In regards to what is currently setup in DART, I’ve added the following so N7DOLSTG05 has updated assets from DOLSTG05 to Dart to our new NAP7 cdn source servers N7DOLWEB01 02 03. \\dolstg05.starwave.com\f$\wwwroot\JupiterSite ?pull/push from?? \\n7dolstg05.starwave.com\f$\wwwroot\JupiterSite NOTE : + This is all that is currently setup in regards to DART : "JupiterCDN" (dolstg05) source = F:\\wwwroot\\JupiterSite\\imgserver\\html\\explore | |? Dolcdnsrc ( NAP7 : N7DOLWEB01 02 03) rootPath = /pool/content/dolimg/explore From: Fung, Alexander Sent: Monday, August 15, 2011 5:23 PM To: Harrington, Mark Cc: Levitan, Shlomo; #DIMG DOL Callisto; #DCAT Systems Engineering - DOL Subject: Re: \\dolstg05.starwave.com\f$\wwwroot\JupiterSite I'm confused. It looks like you're not changing the CMS properties file? It looks like you already have the DART command set up properly to push from woc dolstg05 to NAP7 cdn source servers. There's no need to sync the woc dolstg05 to the nap7 dolstg05? Ultimately what's on dolstg05 is a staging server to the cdn src servers, so replicating woc dolstg05 to nap7 dolstg05 doesn't make sense. Alex From: "Harrington, Mark" Date: Mon, 15 Aug 2011 16:15:01 -0700 To: Alexander Fung Cc: "Levitan, Shlomo" , #DIMG DOL Callisto , #DCAT Systems Engineering - DOL Subject: RE: \\dolstg05.starwave.com\f$\wwwroot\JupiterSite + This is all that is currently setup in regards to DART : "JupiterCDN" (dolstg05) source = F:\\wwwroot\\JupiterSite\\imgserver\\html\\explore | |? Dolcdnsrc ( NAP7 : N7DOLWEB01 02 03) rootPath = /pool/content/dolimg/explore ~ I setup jobs to sync the following. WOC: DOLSTG05 NAP7; N7DOLSTG05 \\dolstg05.starwave.com\f$\wwwroot\JupiterPreview -> \\n7dolstg05.starwave.com\f$\wwwroot\JupiterPreview \\dolstg05.starwave.com\f$\wwwroot\JupiterSite -> \\n7dolstg05.starwave.com\f$\wwwroot\JupiterSite + If there’s any other process else tied to (dolimg) like the image server assets let me know as were targeting next Wednesday 8/24 to cutover dolimg from WOC to NAP7. + WOC is eventually going away. Maybe a year or so from now, but I was told to migrate everything in WOC to NAP7 before the end of the year. I have built out quite a bit already in NAP7 (just not the tiers that are Jupiter specific only CMS) with the plan of retrofitting various technology stacks with BU eng when QA/BU eng are ready., Mark From: Fung, Alexander Sent: Thursday, August 11, 2011 4:39 PM To: Harrington, Mark; Demirchyan, Oganes; Koch, Jordan Cc: Levitan, Shlomo; #DIMG DOL Callisto Subject: Re: \\dolstg05.starwave.com\f$\wwwroot\JupiterSite You can just change the CMS properties to point to the new location. The listener will copy from //dolstg05/JupiterFileServer to the new location. It should work as long as there's no connectivity issues between the WOC and N7DOLSTG05. Finally, there is the DART process that copies from //dolstg05/JupiterPreview and //dolstg05/JupiterSite to the cdnsrc servers. Based on your email, it sounds like there's something similar that will do that in NAP7. Alex From: "Harrington, Mark" Date: Thu, 11 Aug 2011 14:58:31 -0700 To: Alexander Fung , "Demirchyan, Oganes" , "Koch, Jordan" Cc: "Levitan, Shlomo" , #DIMG DOL Callisto Subject: RE: \\dolstg05.starwave.com\f$\wwwroot\JupiterSite Yep I get all that. What I need to know is can I just create a scheduled task / job to move those file on dolstg05 to its NAP7 cousin N7DOLSTG05 as it is pushing to N7DOLWEB01 02 03 (NAP7 Servers : N7DOLWEB01 02 03 (consolidated dolcdnsrc01-05 & dolweb01 02 03 ). ? Or just point the current CMS ( CMSJupiter.properties ((sourceLocation siteLocation previewLocation) ) to N7DOLSTG05 ? From: Fung, Alexander Sent: Thursday, August 11, 2011 2:22 PM To: Harrington, Mark; Demirchyan, Oganes; Koch, Jordan Cc: Levitan, Shlomo; #DIMG DOL Callisto Subject: Re: \\dolstg05.starwave.com\f$\wwwroot\JupiterSite Whoa…this is not something we need to do at all. The files are on dolstg05 as a staging area. Jordan has a DART process for the imgserver assets that copies them to the CDN source servers. That's it. For Jupiter, there's no reason the DCS (and by extension the CMS) needs to be in NAP7. First, we haven't applied any of the NAP7 upgrades (config and jar file changes) to the DCS. Second, if we move the CMS and DCS, we might need to move the clients on doljupapp02 (TC-ModuleSourceServerStaticPrev, TC-ModuleSourceServerStatic, TC-PageAssemblerStaticPrev, TC-PageAssemblerStatic) to NAP7. Note that doljupapp03-10 are no longer used and should have been decommissioned right now. The only thing that is still in use is the TC-JupiterSolrSearch and TC-JupiterSolrSearchPrev on doljupapp01 and dolpreapp01 respectively. I don't know if we need to move the doladmin01 services (etftools, CMSEFServer) as well. If doladmin01 is in the WOC and the CMS is in NAP7, will there be decent connectivity. It's already slow from NoHo to the WOC. If we go from NoHo to the WOC to NAP7, that's going to really suck. The whole Jupiter system doesn't need to be in NAP7…in fact, it doesn't even need to be in the WOC. The only reason we should move it is if there are definite performance improvements or we're decommissioning the WOC. Otherwise, I'd rather have the system down in NoHo closer to the producers and under our control and you just get to deal with static files. =) Alex From: "Harrington, Mark" Date: Thu, 11 Aug 2011 13:22:51 -0700 To: Alexander Fung , "Demirchyan, Oganes" Cc: "Levitan, Shlomo" Subject: RE: \\dolstg05.starwave.com\f$\wwwroot\JupiterSite BTW…feel free to let me know if I’m way off base on this ( the Disney cutover deal sounds like it…..) and what is needed for this cutover in regards to (JupiterSite / JupiterPreview ). From: Harrington, Mark Sent: Thursday, August 11, 2011 1:17 PM To: Fung, Alexander; Demirchyan, Oganes Cc: Levitan, Shlomo Subject: RE: \\dolstg05.starwave.com\f$\wwwroot\JupiterSite They want to cutover dolimg.com / dolimg.starwave.com next week to NAP7. This (JupiterSite / JupiterPreview) seems to be included but I’m not sure how much of it I now need to have in place before hand. It looks like you would need to point to the new CMS but would also need to whole gopub stack in place, and would basically mean we would have to Cutover “Disney” etc…..? I could always setup a job to keep the assests in sync but it would be scheduled until we did cutover Disney.go.com. \\dolstg05.starwave.com\f$\wwwroot\JupiterPreview -> \\n7dolstg05.starwave.com\f$\wwwroot\JupiterPreview \\dolstg05.starwave.com\f$\wwwroot\JupiterSite -> \\n7dolstg05.starwave.com\f$\wwwroot\JupiterSite I have the CMS setup. http://n7dolpubcms01.starwave.com:7878/cms/system/tools ~ NAP7 DCS ( I HAVE NOT SETUP DCS Client hosts) …currently : doljupapp01-10 http://nap7dollogs.starwave.com/n7dolpub01_dcs_DCSJupiter/dcs/system/multicast ~ WOC PROD DCS http://doljuppub01.starwave.com:7777/dcs/system/multicast http://doljuppub02.starwave.com:7777/dcs/system/multicast http://doljuppub03.starwave.com:7777/dcs/system/multicast ~ PREVIEW http://dolpre03vm.starwave.com:7777/dcs/system/multicast ~ NAP7 siteLocations = http://n7dolpub01.starwave.com:7777/dcs,http://n7dolpub02.starwave.com:7777/dcs,http://n7dolpub03.starwave.com:7777/dcs previewLocations = http://n7dolpre03.starwave.com:7777/dcs } # The physical location where CMS stores its managed files. # For example: # sourceLocation = \\\\someserver\\cms_upload sourceLocation = \\\\n7dolstg05\\externalfiles\\CMSJupiter\\managed # The site location is where the external files # are copied upon a site publish. These values # can be overridden by their section-specific # equivalents. # For example: # siteLocation { # physical = //CMPROD/Site/Media # virtual = http://www.mysite.com/media # } siteLocation { physical = \\\\n7dolstg05\\JupiterSite\\managed virtual = http://disney.go.com/managed } # The preview location is where the external files # are copied upon a preview publish. These values # can be overridden by their section-specific # equivalents. # For example: # previewLocation { # physical = //CMPROD/Preview/Media # virtual = http://preview.mysite.com/preview/media # } previewLocation { physical = \\\\n7dolstg05\\JupiterPreview\\managed virtual = } } ~ WOC siteLocations = http://doljuppub01.starwave.com:7777/dcs,http://doljuppub02.starwave.com:7777/dcs,http://doljuppub03.starwave.com:7777/dcs previewLocations = http://dolpre03vm.starwave.com:7777/dcs } From: Fung, Alexander Sent: Thursday, August 11, 2011 12:45 PM To: Harrington, Mark; Demirchyan, Oganes Subject: Re: \\dolstg05.starwave.com\f$\wwwroot\JupiterSite That's correct. In the CMSJupiter CMS, we have a listener that copies files from \\dolstg05\JupiterFileServer\fileserver to \\dolstg05\JupiterSite\imgserver when a producer publishes a particular content object. Alex From: "Harrington, Mark" Date: Thu, 11 Aug 2011 12:43:11 -0700 To: "Demirchyan, Oganes" , Alexander Fung Subject: RE: \\dolstg05.starwave.com\f$\wwwroot\JupiterSite Alex ? From: Demirchyan, Oganes Sent: Thursday, August 11, 2011 12:42 PM To: Harrington, Mark Subject: RE: \\dolstg05.starwave.com\f$\wwwroot\JupiterSite Publisher toolkit running on doladmin01 and I think CMSJupiter Oganes ________________________________________ From: Harrington, Mark Sent: Thursday, August 11, 2011 12:40 PM To: Demirchyan, Oganes Subject: \\dolstg05.starwave.com\f$\wwwroot\JupiterSite How are files dropped here ?