Submit Task Stuck on Resolve conflict

TS: 7.3.2

Windows Server 2008 R2 64 Bit

I have an issue with Workflow Submit Task. Im not using file list deployment. I have a DEploy task that compares 2 TS instances and deploy from one to another. Once it get deployed I want to submit those files. The Submit task says 'Resolve Conflicts' but there is no file attached.

Am I missing anything? Attached is the .ipm file and the default config

Find more posts tagged with

Comments

Adam Stoller

vend2804 wrote:

I have an issue with Workflow Submit Task. Im not using file list deployment. I have a DEploy task that compares 2 TS instances and deploy from one to another. Once it get deployed I want to submit those files. The Submit task says 'Resolve Conflicts' but there is no file attached.
Am I missing anything? Attached is the .ipm file and the default config

I'm a bit confused by the above.

You have a workflow that runs on server-A
It performs a comparison deployment between [the same area] on server-B
You are somehow extracting the list of files that were deployed (presumably getting it from the data on STDOUT in a DNR)
You want to take that list of files and have the workflow submit them

Is the above a reasonable summary of the scenario?

If so:

Regarding #2: Are you deploying from server-A to server-B or performing a reverse deployment from server-B back to server-A?

The former does not make sense in this scenario since the workflow is running on server-A there would not be any changes to those files on server-A and a workflow running on server-A cannot [in itself] submit files on server-B (that could be done with a target-side DNR in the deployment though)

Regarding #3-#4: Once you get the list of files that were deployed (you are getting that - right?) do you explicitly add those files to the task / job that is running on server-A?

If not, then what are you expecing the submittask to operate on?

I imagine the conflict issue is because there are no files associated with the task and the submittask doesn't know how to deal with that situation - just a guess - but until you can clarify the above items I wouldn't worry about that.

Vendim Birbili

your Assumption are correct.

Yes I am performing the Reverse DEployment so I have the files in the server.

The DNR generate a file list for purpose of LSCS so its formatted specifically to that since After sync Server A with SErver B I also do deploy the files to the runtime servers(Doing compare TS-LS)

You are correct that the submit task seem like not finding the files.

I am not attaching the file list that is generated to the task as I use it only for the LSCS deployment only.

1. Do I need to generate a specific file list for this since Im not doing file list deployment?

2. Attaching file list to the task is that something you can point me to? All I know for my past WF is that it happens internally in PLC but since this workflow runs as a job not sure how that would happen.

thanks

Adam Stoller

The submittask operates on files associated with the task, so you basically have two choices:

Take the list of files retrieved from server-B and add them (using workarea-relative-paths) to the task before transitioning to the submittask
Take the list of files retrieved from server-B and create a temporary file consisting of the area-relative paths and submit comments, and then use an externaltask (or perhaps do this as part of the DNR script) to run iwsubmit -f file and remove the submittask from the workflow

If you don't know how to add files to a task programmatically, spend some time with the manuals.

If you don't understand the format of the file to be provided to iwsubmit, spend some time with the manuals

If you still have problems with either of those, provide as much detail as you can, here, about what you tried, what results / errors you got - and/or hire someone who already knows this to do it for you.

Vendim Birbili

Fair Enough. Thanks for the direction. I think I can take it from there. I will let you know my results.

I like to make it more challenging so I will try both options.

thanks

Adam Stoller

I suggest you do one-or-the-other *not* both -- though if you want to try one, and then back that out and try the other -- that's a reasonable learning / verification path