Locking Files While Deploying

In one of my workflows, I have a deployment leg that pushes files to another Workarea in TeamSite.

Once they have been pushed to this area, other users come in and utilize this content for their own purposes.

My problem is this. Occasionally, the deployment might be rather large (say 500 MB or a gig). Something like this can take OD a minute or so to deploy. I do not want users in my target Workarea to be able to do anything with the content until the full deployment has run.

If anyone has some advice, I'd be glad to hear it. Thanks for your time.

jt

Find more posts tagged with

Comments

ISCBorisB

In one of my workflows, I have a deployment leg that pushes files to another Workarea in TeamSite.

Once they have been pushed to this area, other users come in and utilize this content for their own purposes.

My problem is this. Occasionally, the deployment might be rather large (say 500 MB or a gig). Something like this can take OD a minute or so to deploy. I do not want users in my target Workarea to be able to do anything with the content until the full deployment has run.

If anyone has some advice, I'd be glad to hear it. Thanks for your time.

jt

I did similar things before by deploying to dedicated WA with limited access and performing Submit/Get latest
at the end (DNR, after, onSuccess, onTarget)

Regardless of the approach there are serious issues in your schema. Unless your users never *Edit* these Files
you will have to consider that target files may be already locked, conflict resolution, merging and so on.

Prashanth Shetty

Run a DNR to change the workarea permission (change group) before deployment by using iwchgrp command. Reset the permission after deployment.

jajtiii

The users cannot edit the files. They can only initiate new deployments to a variety of locations (therein, the problem...they select a directory and start deploying WHILE the directory is being populated!).

Thanks, pshetty. I will do that.

I was hoping for something easier (like a locktask or something), but will endeavor to put your suggestion in place.

appreciate it.

Adam Stoller

The users cannot edit the files. They can only initiate new deployments to a variety of locations (therein, the problem...they select a directory and start deploying WHILE the directory is being populated!).

Thanks, pshetty. I will do that.

I was hoping for something easier (like a locktask or something), but will endeavor to put your suggestion in place.

appreciate it.

If you make the deployment transactional - the file(s) should appear as filename.iwnew (and you'll see filename.iwold) up until the time the file(s) has/have been completely deployed - at which point the .iwold and .iwnew files will disappear and the file filename will be the complete new file.

This may require a bit of user training - to make sure users never try to do anything with .iwnew / .iwold files - but that shouldn't be too difficult.

JackIntheBox

I remember having this issue a few years back. I think I changed the name of the Workarea to something else and then renamed it again after the deployment was complete, using DnR's. I did have a few issues but my problems reduced dramatically ( We had over 100 users accessing the workarea as it was exclusively used to publish news articles).