pre processing a deployment

Johnny

We are looking at options for approving, submitting and versioning content but postponing the deployment based on a certain date.
With this we would be using batch deployment of the content ,so a scheduled area comparison would run each day.

This is basically timed deployment, without using workflows to hold on to assets for the duration of the time delay and without individual deployments for each workflow (we would have the possibility of numerous deployments per day that way which we want to avoid)


One option was to have an EA with a publish date field set on the assets.
To take advantage of this we would need some sort of open deploy pre processing that is able to manipulate the manifest of files that open deploy determines are candidates for deployment and filter that manifest based on some criteria (this scenario would be EA fields)

DnR scripts and the Delivery Adapter Framework both provide file manifests though you are unable to alter them in anyway before deployment.

Is there anyway to interact & extend opendeploy as described?

I haven't seemed to have found a way to do this. I also had a look at the OD 6.0 webcast and am not sure if it would be a feature of that product.

Is this a valid feature or would there be a more obvious solution?
I would have thought a method like this would be quite powerful and well integrated.

Perhaps someone can see another option based on our requirements aside from the workflow method described above?

Any insight would be great!

John Cuiuli

Migrateduser

OpenDeploy 6.0 introduces the ability to publish and expire content based on EAs. The out-of-box approach involves indexing EAs into a database (using DAS, for example), and configuring a payload adapter-based deployment (new OD6 feature).

The deployment criteria is a metadata query expressed in the deployment config file. So all files matching the query are returned in a manifest, which OD then compares with the target to deploy the updated files. Or deletes the files if you specify to expire content matching the query.

The out-of-box payload adapter that does the metadata query against a database is part of the new Intelligent Delivery module, which also provides content syndication (offer-subscription management) on top of OD. (This is a separately licensed module that installs on top of the OD base server.)

If you prefer to use a different metadata repository or don't want to use the supplied payload adapter, you can write your own using the payload adapter framework. This is similar to the delivery adapter framework, except that the Java class you write is spun up at the beginning of the deployment in the source-side base server (as opposed to the end of the deployment on the target). The class you implement is responsible for determining which files to deploy and passing the manifest back up to OD for processing.

Input from the deployment config to the payload adapter can be a query structure (as described earlier) or a character data string. Either way, the adapter would parse the input and proceed accordingly.

Hope that helps clarify.

Todd Scallan
Director of Product Management
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com