Three-tier configuration and DAS

MichaelS

Hi,

We are currently running Teamiste 6.1, OpenDeploy 5.6 and DataDeploy 5.6 in a three-tier configuration. We are planning to add DAS on top of this but in the DataDeploy Admin guide on page 75 we read: "You cannot use DAS when using a three-tier configuration."
Is there any way to use DAS to deploy to one database and the three-tier configuration alongside with our current product line?

I was looking at OpenDeploy6.0 (and DataDeploy 6.0) documentation and this limitation is removed from there. Can someone confirm that we will be able to use DAS and Synchronized Transactional Deployments (in a three-tier environment) alongside when we upgrade?

Also, did anyone made the move from OpenDeploy 5.6 to OpenDeploy 6.0 (including DataDeploy move) how difficult is this?

Migrateduser

DAS must deploy directly to a database in response to TeamSite triggers. In 5.6, DAS is a daemon that can accept either iwat or event subsystem triggers from TeamSite. In 6.0, DAS is integrated into the OD Base Server and can accept only event subsystem triggers from TeamSite.

The "3-tier" data deployment model pertains to non-DAS deployments. In 5.6, that means running a DataDeploy (non-DAS) deployment, which connects to a daemon on a target system, which in turn deploys into the database. In 6.0, this is replaced by the OD Base Server deploying to an OD Receiver, which in turn deploys into the database. You must use the <dbLoader> element for this type of deployment.

Tip: Check out the "Migration Notes for DataDeploy 5.6" section of the 6.0 Database Deployment Admin Guide for a summary of how to perform tasks in 6.0 formerly done using DataDeploy 5.6.

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