sync files/data with OpenDeploy dbLoader

I am intending to use OpenDeploy's dbLoader config to sync deployment of files and EAs to a database.

After reading the documentation I am not sure which OpenDeploy node the datadeploy connection is made from. If the config deploys files from base node A to receiver node B is the dbLoader datadeploy JDBC connection made from base node A or receiver node B ?

The version of OpenDeploy is v6.1.0

If someone could clarify that would be great.

Thanks.

Find more posts tagged with

Comments

Adam Stoller

I am intending to use OpenDeploy's dbLoader config to sync deployment of files and EAs to a database.

After reading the documentation I am not sure which OpenDeploy node the datadeploy connection is made from. If the config deploys files from base node A to receiver node B is the dbLoader datadeploy JDBC connection made from base node A or receiver node B ?

The version of OpenDeploy is v6.1.0

If someone could clarify that would be great.

Thanks.

I believe that (at least by default) the dbLoader connection is made from the source-side (base node A).

(As I've never used dbLoader - I'll defer to the most likely more experienced reply below)

jed

I am intending to use OpenDeploy's dbLoader config to sync deployment of files and EAs to a database.

After reading the documentation I am not sure which OpenDeploy node the datadeploy connection is made from. If the config deploys files from base node A to receiver node B is the dbLoader datadeploy JDBC connection made from base node A or receiver node B ?

The version of OpenDeploy is v6.1.0

If someone could clarify that would be great.

Thanks.

The connection is made on the receiver. Some light reading that might be helpful:
http://devnet.interwoven.com/site.fcgi/techlib/docs/GearUp06/presentations/gear-up-jed-michnowicz.pdf

Specifically, look at slide 16.

Bill Klish

I think the answer is, it depends on the target for the OD definition in which you are deploying to the database.

If you are moving files and data inside the same definition, then yes it will connect on the receiver. If you are deploying files in one definition and running dbLoader in another, you technically could have the connection made from the source side.

jed

If you are deploying files in one definition and running dbLoader in another, you technically could have the connection made from the source side.

Not sure what you mean by that. dbLoader is always invoked on the target. If this is not the case, can you provide a sample config file?

In theory, you can perform a loopback deploy back to the base server (content and all), but technically the dbLoader is still part of the "receiver" leg. I have a FR open to perform a dbLoader with content supression, but last I checked it had not been fulfilled.

Example:
we have three deploys right now:
o datadeploy for preview
o datadeploy/opendeploy for staging
o datadeploy/opendeploy for production

Our "preview" deploy does not need content deployed since our preview server does a NFS mount of the teamsite server. For consistency, all three deploys use dbLoader. For the preview deploy, we do a loopback to a temp directory and rm -rf the temp docroot after deployment.

Clear as mud?

~jed

debus

If it is an area directory comparison deployment (ie: not filelist) does that not mean your loopback deployment redeploys the entire site every time since you delete what was deployed ?

jed

If it is an area directory comparison deployment (ie: not filelist) does that not mean your loopback deployment redeploys the entire site every time since you delete what was deployed ?

We only do filelist deployments.

Bill Klish

Jed,

Following back up to my previous post. Sorry for the delay.

We currently have the following deployment that runs dbLoader on our source server.

OD Def #1:

File list deployment to target web server (images, flash, etc.)

OD Def #2:

dbLoader deploys to localhost (TeamSite server) and inserts into MySQL database on another server.

So, yes, dbLoader is invoked on the target, but in this case, our target is the source server (TeamSite server). We are deploying back to ourselves for the database leg of the deployment, and to the web server for the images, etc. all within the same OpenDeploy script.

Hope that makes sense.
-Bill