How to get jobId in workflow model

I am using deploy Task and are passing two OD task variables. srcArea, dcrFileList. There variables are declared in my deployment descriptor.

value of dcrFileList is the file path which contains the dcr paths to be deployed.
coz at a time many deployments can be active for different DCRs, i want to appened jobId in the filePath to uniquely identify what fileList is for what Job.

For example as of now
dcrFileList=$IW_HOME/fileList/dcrFileListToBeDeployed

What i want is
dcrFileList=$IW_HOME/fileList/dcrFileListToBeDeployed_23456
where 23456 is the jobid.

Can anyone please let me know how can i get job id in the workflow model and how can it be appended to OD task variables value.

Please help.

Find more posts tagged with

Comments

nbwoven

I think to get JobID in WFs you can use iwgetwfobj. & iwqueryjobs as explained in KB#49718 (If thats what you're looking for !)
Different Methods to Obtain the JobID of Workflow

Adam Stoller

I am using deploy Task and are passing two OD task variables. srcArea, dcrFileList. There variables are declared in my deployment descriptor.

value of dcrFileList is the file path which contains the dcr paths to be deployed.
coz at a time many deployments can be active for different DCRs, i want to appened jobId in the filePath to uniquely identify what fileList is for what Job.

For example as of now
dcrFileList=$IW_HOME/fileList/dcrFileListToBeDeployed

What i want is
dcrFileList=$IW_HOME/fileList/dcrFileListToBeDeployed_23456
where 23456 is the jobid.

Can anyone please let me know how can i get job id in the workflow model and how can it be appended to OD task variables value.

Please help.

You should not need to be specifying the file list or src area for the deployment at the model level - those are things which should be determined at the program/script level when the task is activated.

Unfortunately, I have not played with the "deploy task" in WFM yet, so I don't know what it is / is not expecting in terms of parameters, nor what it is / is not designed to do as far as passing along parameters to a deployment process.

Also - you should not need to specify a jobid or taskid information at the WFM level - since at the model level those values don't exist - they only come into being after the model has been instantiated as a job.