Triggering Fan Deployment

Hi All,

I'm quite new to TeamSite workflow and have been asked to make a change to our primary workflow that we use to deploy from TS to our production web server. What I need to know is how to trigger a fan deployment from the workflow? I have created a deployment inside OpenDeploy that pushes content to our new UNIX cluster of webservers. I'm thinking the change I need to make is pretty simple and is in wft_opendeploy.cfg. Any help would be appreciated.

Thanks

TS: 6.1.0 SP 1
OpenDeploy Base Server: 6.0
OD Recievers: 6.1

Scott Newsome
Chiron Corporation

Find more posts tagged with

Comments

jbonifaci

Just add an external task that invokes OpenDeploy. If you want to a filelist deploy, you'll need to have the external task build the filelist first and then invoke it.

thr_mezzaz

Not looking to create anything new. Just want to change what we have to deploy to 3 servers instead of the one it currently does.

Scott Newsome
Chiron Corporation

jbonifaci

Well, if it already exists, then you should only have to add two nodeRef's to the replicationFarm of the OpenDeploy config file that your workflow is using.

thr_mezzaz

Inside the wft_openndeploy.cfg is:

branchName=/default/main/chiron_global/ , dst=/usr/local/xxxx/xxxx/. useNode=dmz-****

can there be multiple of these?

branchName=/default/main/chiron_global/ , dst=/usr/local/xxxx/xxxx/. useNode=web1
branchName=/default/main/chiron_global/ , dst=/usr/local/xxxx/xxxx/. useNode=web2
branchName=/default/main/chiron_global/ , dst=/usr/local/xxxx/xxxx/. useNode=web3

etc

Scott Newsome
Chiron Corporation

jbonifaci

I have no idea what wft_opendeploy.cfg is, sounds like something custom coded for your wft. Unless it's coded to handle multiple, it won't work without code modifications.

thr_mezzaz

wft_opendeploy.cfg

#=====================================================================
# Copyright 2002 Interwoven Inc.
# All Rights Reserved.
#=====================================================================
# This is an configuration file for OOTB deployments. This file is
# in iw-home/local/config/wft/solutions/wft_opendeploy.cfg
#
# Each deployment mapping contains three required items delimited
# by commas. This file provides a mapping between the branch name
# and the corresponding deployment attributes required for deployment.
# The deployment attributes of importance are node name
# and the target directory.
#
# BRANCH NAME:
# This is the name of the source branch.
#
# *NOTE*: the branchName= string *MUST* be provided. Do not change
# the key value 'branchName' to anything else.
#
# DESTINATION NODE NAME:
# The logical node name of the OpenDeploy receiver that is
# configured in the Base OpenDeploy Server's
# <iwodhome>/etc/odnodes.xml.
#
# *NOTE*: the usenode= string *MUST* be provided. Do not change the
# key value 'usenode' to anything else.
#
# DESTINATION PATH:
# Path on the destination server where the content will be
# deployed. This path must be included as an allowed directory in
# the OpenDeploy receiver's <iwodhome>/etc/odbase.xml or
# <iwodhome>/etc/odrcvr.xml configuration file.
#
# *NOTE*: the dst= string *MUST* be provided. Do not change the key
# value 'dst' to anything else.
#=====================================================================
# Example:
#
#BRANCH NAME,DESTINATION PATH,DEPLOYMENT NODE
#---------------------------------------------------------------------
# A UNIX receiver deployment example
#branchName=/default/main/br3/,dst=/wwwroot/target,useNode=INTERNET
#---------------------------------------------------------------------
# A Windows receiver deployment example
#branchName=/default/main/br3/,dst=c:\wwwroot\target,useNode=INTERNET
#=====================================================================

branchName=/default/main/chiron_global/,dst=/usr/local/****/****,useNode=dmz-****

Scott Newsome
Chiron Corporation

jbonifaci

Well, I never use OOTB workflow, so that might explain it. Well, have you tried adding 3 deployment lines? what hapens? Have you looked at the code that reference this to see if it appears that it can handle multiple?

Adam Stoller

I don't know anything about this config file either - you'd need to figure out how the script that uses this configuration file invokes OpenDeploy - and also find out the OpenDeploy configuration file that is being used.

The configuration file *seems* to specify:
- the source branch path
- the target area path
- the target replicationFarm[node?]

If the last argument is the name of the replicationFarm and not the name of an individual node - then all you need to do is modify the deployment configuration file and add the other node references to that replicationFarm.

If it's not - then you'll either have to do a bit of digging and re-coding of the existing script - or write your own to do what you want.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

james1

Inside the wft_openndeploy.cfg is:

branchName=/default/main/chiron_global/ , dst=/usr/local/xxxx/xxxx/. useNode=dmz-****

can there be multiple of these?

branchName=/default/main/chiron_global/ , dst=/usr/local/xxxx/xxxx/. useNode=web1
branchName=/default/main/chiron_global/ , dst=/usr/local/xxxx/xxxx/. useNode=web2
branchName=/default/main/chiron_global/ , dst=/usr/local/xxxx/xxxx/. useNode=web3

No, you cannot do that. You need to modify the deployment config file located at od-home/conf/wft_opendeploy.xml to deploy to your extra 2 nodes.

-- James

--
James H Koh
Interwoven Engineering