nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Deploy Task

auli

Hi,
We are using WFM 1010 with TS672 on Windows environment.
I have read in some threads that with new WFM deploy task, there is no need to call a ipl instead some java class should be used. I am having a confusion here as earlier iwodcmd was used to initiate the deployments which was in turn called inside some ipl. Now is that logic written in the java file? And what about the filelists, are they created automatically? If not, where we can call a IPL in deploy task for that?Can we still pass those 3 variables(jobID, taskID, Area) to the ipl from the deploy task? I was also not able to find the default java file for deployment i.e. DeployURLExternalTask.

Can somebody explain how exactly deploy task works.

TIA
-Auli

Find more posts tagged with

Comments

Faizi

Hi,
We are using WFM 1010 with TS672 on Windows environment.
I have read in some threads that with new WFM deploy task, there is no need to call a ipl instead some java class should be used. I am having a confusion here as earlier iwodcmd was used to initiate the deployments which was in turn called inside some ipl. Now is that logic written in the java file? And what about the filelists, are they created automatically? If not, where we can call a IPL in deploy task for that?Can we still pass those 3 variables(jobID, taskID, Area) to the ipl from the deploy task? I was also not able to find the default java file for deployment i.e. DeployURLExternalTask.

Can somebody explain how exactly deploy task works.

TIA
- Auli

Hi Auli,

You can perform deployment in different ways. I am giving brief idea of using deployment:

In new version of WFM lots of task perform through URL Task. So you can perform deploymen using URL Task but it little sticky. For this you have to pass Bean Id, Target Node, ClassName. For more detail you can dig into OOTB workflow of LiveSite "Publish LiveSite Content". This workflow performs deployment for Livesite content on different node either Development or Production server.
For deploying in earlier way (teamsite), you can use Deploy Task, in this task you have to just pass the DeploymentConfig file only in variable deployment file. By default it calls the teamsite deployment class. All the process it will perform automatically on the basis of deployment config file. If you have written own class then you can use it too. But for that you must follow the process of customizing the teamsite.
If you still want to use .ipl file for deployment you can use by External Task. You have to pass the Command for executing the .ipl and the .ipl file.

So hope this helps in understanding the different way of deployments.

Thanks,

auli

For deploying in earlier way (teamsite), you can use Deploy Task, in this task you have to just pass the DeploymentConfig file only in variable deployment file. By default it calls the teamsite deployment class. All the process it will perform automatically on the basis of deployment config file. If you have written own class then you can use it too. But for that you must follow the process of customizing the teamsite.So hope this helps in understanding the different way of deployments. Thanks,

You can perform deployment in different ways. I am giving brief idea of using deployment:

Thanks for the reply Faizi.
I have done deployment using WFM external task but while using deploy task what values should be given for filelist parameter(under source) in the deployment configuration? Is the path known, where these filelists are being automatically created? Also, what is the path of the default deployment class file?

santosh013

The examples of a simple deployment configuration are clearly given on page 84 of the PDF(OD.610.admin.pdf).
Hope it will clear all your doubts.

Thanks,

Faizi

Thanks for the reply Faizi.
I have done deployment using WFM external task but while using deploy task what values should be given for filelist parameter(under source) in the deployment configuration? Is the path known, where these filelists are being automatically created? Also, what is the path of the default deployment class file?

Welcome Auli,

In Deploy Task, You can specify values for the following variables:

odDeploymentName (required). A valid deployment name in the OpenDeploy server. Do NOT include the file extension. For example, the deployment name should be test, not test.xml.
ClassName (optional). Fully qualified class that contains custom implementation. If you do not specify a class, the following default class is used: com.interwoven.ui.teamsite.workflow.task.urltask.DeployURLExternalTask
odHost (optional). Name of the server where OpenDeploy is running. It is optional if OpenDeploy and TeamSite are running on the same server.
odPort (optional). Port where OpenDeploy is running. The default value is 9173. If left blank, the default value is used. It is optional if OpenDeploy and TeamSite are running on the same server.

You can also pass the OD Variables that used as Key-value pairs that are dded to the task as task variables.

All the variables you have defined in deployment file can be passed by OD Variables.

Hope this helps.

auli

Thanks Faizi, it helped a lot.
One more question - how can we access the global variable in our external task script and then can we change its value in the script itself?
I tried it the same way $workflow->GetVariable but it didnt work. Is there some other way to access the global variables in WFM?

Faizi

Thanks Faizi, it helped a lot.
One more question - how can we access the global variable in our external task script and then can we change its value in the script itself?
I tried it the same way $workflow->GetVariable but it didnt work. Is there some other way to access the global variables in WFM?

Welcome Auli,

Accessing the global variable in external task using ipl is little bit sticky. There are many people who faced this issue with WFM. There is no any direct solution of this.
You have to follow some tricky things to achieve this.
Hope this thread will give some pointer.

Thanks,

auli

Thanks a lot for the replies. Got everything to work as suggested Smiley Happy

CRB

i have an issue that is related to the deploy task so i thought i expand this thread.

my workflow is similar to this :

editor -> submit task -> deploy task -> deploy success -> end
OR -> deploy failure -> notify to editor -> resolve deploy error task -> waits for user action to cancel or retry deploy task.

we have a situation where different editors will invoke the same workflow at the same time and get deployment failure, so i enabled the deployment to get queued when the same deployment is already running.

the issue here is that even if a deployment is just queued (not failed) the deploy task always transitions with deploy failure which invokes notification of failure to the editor and waits for the editor to take action.

my question:
is there a way to distinguish between when the deployment fails and when the deployment is queued on the fly ( in the workflow). or do i just have to abandon the deploy task and use an external task to handle deployments.

please advice with you think is best practice for this case.

Adam Stoller

i have an issue that is related to the deploy task so i thought i expand this thread.

my workflow is similar to this :

editor -> submit task -> deploy task -> deploy success -> end
OR -> deploy failure -> notify to editor -> resolve deploy error task -> waits for user action to cancel or retry deploy task.

we have a situation where different editors will invoke the same workflow at the same time and get deployment failure, so i enabled the deployment to get queued when the same deployment is already running.

the issue here is that even if a deployment is just queued (not failed) the deploy task always transitions with deploy failure which invokes notification of failure to the editor and waits for the editor to take action.

my question:
is there a way to distinguish between when the deployment fails and when the deployment is queued on the fly ( in the workflow). or do i just have to abandon the deploy task and use an external task to handle deployments.

please advice with you think is best practice for this case.

Not knowing how the Deploy Task actually performs its operation makes it difficult to figure out how to refine it - I think you either need to see if the source is available (I doubt it) or replace it with your own code, in which you can control the -inst parameter and/or examine the output from the command to determine if it is a real, or temporary error.

That being said, you should probably open a case with IWOV Support and explain the scenario to them - while I'd classify it as a "bug", they'll probably want to classify it as an FR to "enhance" the Deploy Task to handle concurrent deployments [better]

CRB

Not knowing how the Deploy Task actually performs its operation makes it difficult to figure out how to refine it - I think you either need to see if the source is available (I doubt it) or replace it with your own code, in which you can control the -inst parameter and/or examine the output from the command to determine if it is a real, or temporary error.

i ended following your 1st suggestion... I digged in teamsite code, found the source code for the deploy task. i added some code to handle queued deployements. so now my deploy task can return 3 different status ( success, queued, failed). my custom deploy task lives in its own package so anybody can use it. i dont think i can post it online, but feel free to email me if anybody wants it.
i am sure IWOV doesnt like us playing with their source code but i dont see the point of waiting for them to resolve it in the next release or they might not even consider resolving it.