Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Deploy and Run script on multiple platforms
mlevin
Hi,
I know that I can deploy content to multiple platforms by overriding the target path for one or more servers in a farm (so, for example, I can specify the default path for my windows receivers and then override for my unix receiver).
But what about doing this for a Deploy and Run script? After the deployment, I want to run a script, but obviously the script will be in different places on windows and unix (e.g., c:\myscripts\script.bat vs /etc/myscripts/script.sh). How can I override the path to the script for my unix server?
Right now the only way I can figure out how to circumvent this issue is to have the unix deployment completely separate, but that is not good for maintenance purposes, and also, I want the deployment to stay in sync with the window servers, so the unix deployment wouldn't know that the windows deployment failed and that it should roll back...
Thanks
Find more posts tagged with
Comments
Adam Stoller
[Assuming you're talking OpenDeploy 5.x - yes?]
Just thinking off the top of my head here - haven't tried it and don't really have an environment within which to try it at the moment, but ...
Suppose you create two replication farms - one for Unix one for Windows, and then create two definitions and and two execDeploymentTasks (see attached "bolierplate" as an example) - it's possible (again, I'm not sure) that you might be able to get the desired effect.
If you try this out - I recommend creating a simple script for both platforms, starting out with each of then printing out the requisite XML code to indicate failure (<response code="-2"/>) and see if it correctly triggers the uniform failure.
If that works, change one to be a no-op, and see if it still gets a uniform failure.
If that works, switch them around (no-op become failure, failure becomes no-op) and test that.
If that works - you should be fine.
If it doesn't work, I suggest working with Tech Support who can file a feature request on your behalf.
--fish
(Interwoven, Curriculum Development)