Deployment Task

Workflow Details

Custom workflow to convert .pages to .html and convert them to XML feed and deploy them to AppServer. I have this workflow created and working fine.

Now my new requirement is i should provide user to provide the list of servers that he want to deploy to.. Its a multi-select option and i need to deploy it to all the servers that user has selected.

Currently i am using OOTB deployment task in my workflow for deployments.

Is there a way to send the selected servers as parameters to this OOTB deployment task to that it will deploy to those servers ?

Do i have to create a new external task by copying the existing class and make modifications to accept params and do the deployment ?

Suggestions plzz..

TS 7.2.1 sp2
Win 2008

Find more posts tagged with

Comments

mart2001

Yes, you will need to modify or create another external task to use the deploy feature. The OOTB deploy task doesn't have that many options as using multi select servers to pass in as parameter substitution.

Rick Poulin

Yes, you will need to modify or create another external task to use the deploy feature. The OOTB deploy task doesn't have that many options as using multi select servers to pass in as parameter substitution.

I'd agree in earlier versions, but TS7.2.1 SP2 should have all the fixes needed to define multiple target nodes in the PLC, meaning the OOTB deployment task could quite possibly achieve what you need. You'd have to define your target environments in customer-teamsite-resource-config.xml and then make the deployment task's TargetNodes variable a configurable variable. Then, on a custom instantiation screen, build something to load the available targets into a multiselect box.

nipper

I do not remember a SP2 for 721. There was a single large patch and that must be applied to TS as well as LS

I would double check

Rick Poulin

I do not remember a SP2 for 721. There was a single large patch and that must be applied to TS as well as LS

Right, I meant to comment on that. I'm assuming that by 'SP2' you mean to have received some kind of special patch that brings you in line with the functionality available in 7.3. I do not believe that LSCS in 7.2.1 SP1 properly recognizes custom target nodes.

nipper

... I do not believe that LSCS in 7.2.1 SP1 properly recognizes custom target nodes.

I think it does, we loaded it up recently and it seems to be working for LSCS and LSDS

scott_field

I am using simple deployment task not the plc version.
I dont have LSDS or LSCS. my deployment descriptors are in od-home one for UAT and one for PROD.
Now before UAT deployment i need to provide multi-server (UAT servers) selection.
when i check the deployment task(which is external task) i couldnot find the class that it is referring to as there is no class variable.
So i want to know the class path sothat i can look at it and modify accordingly.

TS 7.2.1
Sitepublisher
NO LSCS
No LSDS

My workflow converts .pages to .xmls and send them to weblogic app server.

Rick Poulin

when i check the deployment task(which is external task) i couldnot find the class that it is referring to as there is no class variable.

By default, the DeploymentTask uses this class. I don't believe the source code is published anywhere though, so you might need to roll your own if you need any changes.

com.interwoven.ui.teamsite.workflow.task.urltask.DeployURLExternalTask

What would be easiest though, is to either use a configurable variable as the odDeploymentName value (or any of your odSubst_ variables, depending on how you've built it), or to create an external task that modifies that variable prior to arriving at your deployment task.

Migrateduser

By default, the DeploymentTask uses this class. I don't believe the source code is published anywhere though, so you might need to roll your own if you need any changes.

com.interwoven.ui.teamsite.workflow.task.urltask.DeployURLExternalTask

What would be easiest though, is to either use a configurable variable as the odDeploymentName value (or any of your odSubst_ variables, depending on how you've built it), or to create an external task that modifies that variable prior to arriving at your deployment task.

odDeplymentName would still remain a single deployment config file right? it can have multiple execDeploymentTask nodes and all of them will get executed. We cannot control which one....what is needed is a mechanism to choose if a deployment is required to a single target env or more depending on input by user. Having more than one deploy tasks might me an option here which would get triggered conditionally....