DataDeploy and Templating Question

plantronics

We've been using Templating to output static files for a long time but are seeking to migrate DCR data into a db via OD/DataDeploy for the first time and instead rendering this data dynamically via the app server (ATG). Im hoping someone can enlighten me as to what the specific procedural differences are when using Tempating to publish to a database via DataDeploy vs. using templating to generate a static file. For instance take the below cases:

Case 1: Using Templating to output data to a static file
1) User saves and clicks "generate" within the DCT form, producing a DCR.
2) Templating engine merges the DCR with the associated TPL to produce the user defined output file (in our case a JHTML file).
3) Templating engine forwards the user to the generated file.
4) User starts an approval workflow with generated file(s) attached which submits file(s) to staging on approval.

Case 2: Using Templating to output data to a DB via DataDeploy
1) User saves and clicks "generate" within the DCT form, producing a DCR.
2) Generate action kicks off a DataDeploy script (is this possible? what is a typical trigger action used within TS to kick of the DataDeploy process?)
3) ????? (This is where I am not sure what happens, since the data would go into a DB and there is presumable no output file as in the above case).

Im fairly clear on how DataDeploy GETS the data into the database with mapping files and such (the documentation is good here), but, Im having trouble getting my head around the process and end user experience expressed in Case #2.

Thanks in advance,

Mike

Edited by plantronics on 11/22/04 02:14 PM (server time).

Migrateduser

MIke,

I'm not completely clear on what you're trying to do.

Do you want to use DD's DAS mode to automatically make updates to the database when the user takes an action?

DataDeploy in DAS mode is basically jsut waiting for events to happen (such as submit a DCR). It subscribes to certain events and takes action based on the event. So TeamSite doesn't kickoff a script to invoke DD. It publishes events (via JMS) and DD is one of the subscribers. DD listens for events and then takes the appropriate action.

Mariam