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)
open deploy configuration
elke
hi everyone...
inherited open deploy installed on a solaris machine, running teamsite5.5.2 i have never configured open deploy and have massive problems understanding the 350pages of material. anyone out there who can give me some advice to config it the nice'n easy way????
Find more posts tagged with
Comments
tvaughan
Hi elke,
There's no one "nice and easy way" to configure anything. The manual, while initially intimidating, really isn't all that bad.
Maybe if you could spell out what it is you're trying to do, we could steer you to the appropriate pages and/or post some examples.
Tom
elke
i have a new teamsite 5.5.2 installation on solaris, everything is working except for open deploy. my tech manager is too bussy at the moment, so i thought i give it a go and try to configure open deploy myself. i want to do deployments from the teamsite box to 2 maybe 3 different servers, nothing really complex, just file list deployment (integrated within a workflow). any help is appreciated, i am kind of stuck here..
elke
iwovGraduate
If you have not worked with OpenDeploy before, I would recommend taking one step-at a time. Instead of trying to configure a deployment from a workflow that goes to 2-3 servers simultaneously, just configure a simple deployment to one receiver.
OpenDeploy Base server ships with a default test deployment that deploys locally (to the same server).
The configuration file test.xml will be under your OD_HOME/conf directory. See if you can get this to work.
Next, change the reciever host in the test.xml to one of your receivers. (I would keep the test.xml as it is and work on a copy.) You might have to change the target directory as well. (You can use something like /tmp). Alos, you will have to change the odnodes.xml and odrcvr.xml on the receiver. Refer to the respective sections of OpenDeploy Admin guide for that. You will need to bounce the OD receiver after you make changes to the conifgurations.
That will give you a basic understanding. After that, try file list and workflow based deployment.
Filelist Deployment:
This is preety simple, in the sourceFilesystem tag use a filelist attribute. The manual has preety good examples.
Deployment from Workflow :
Look at the iw-home\local\config\wft\solutions\author_submit_with_deploy.wft
This workflow uses the external task : wft_opendeploy.ipl to do a file list deployment of the files in the submitlist of workflow. You can use the same ipl from your workflow.
Plese read the comments in the wft_opendeploy.ipl, and wft_opendeploy.cfg. The wft_opendeploy.xml file should be copied under your OD conf directory.
To deploy to more than one host, use more than one node in the replicationFarmSet tag of your deployment configuration. Again, the OD manual has some preety good examples.
Bottomline, use the 300+ pages of OD manual as a *reference*, not a text book.
Hope that helps.
Adam Stoller
If you're deploying contents from a single source area (SA) to the same target area (TA) on two different target Receivers (R1, R2) then you configure everything as if you were doing a 1:1 deployment except for the replicationFarmSet where you would define two nodes instead of one:
<replicationFarmSet>
<nodeRef useNode="R1"/>
<nodeRef useNode="R2"/>
</replicationFarmSet>
That's the real high-level response. For anything more, you'll have to supply us with what you have in the way of a configuration file to start with so we don't spend a lot of time trying to design things from scratch for parts you already have covered.
Actually maybe a better approach is to just ask whether or not you understand how to read a DTD - if so, you'll probably find it a little quicker to start with the full DTD (IWODHOME/conf/dtd/oddeployment.dtd) and then search the manual for more information about specific parts - and *then* if you have questions, post them here - with enough context that someone can respond to it as a question (as opposed to asking us to write the configuration files for you)
--fish
(Interwoven Senior Technical Consultant)