nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Running dbLoader from source server

sanu

Hi All,

We observed that by defaut the dbLoader is invoking a database deployment on the target server. In our case the target server is an OD receiver installation - and it is difficult to get it configured to perform database deployment. Is there a way to get dbLoader invoked from within source server itself?

Thank you,
Sanal

Find more posts tagged with

Comments

Adam Stoller

Hi All,

We observed that by defaut the dbLoader is invoking a database deployment on the target server. In our case the target server is an OD receiver installation - and it is difficult to get it configured to perform database deployment. Is there a way to get dbLoader invoked from within source server itself?

Thank you,
Sanal

I've never used dbLoader, but if memory serves correctly - it should only ever be invoked from the source-side. How you do that, unfortunately I don't remember -- this is probably one of the reasons I tend to prefer "old-school" usage of DNR scripts.

Rick Poulin

I had the same issue and got it working.

My requirements were to a) deploy files to a target and b) do a datadeployment to a DB. If one failed, both should be rolled back.

I accomplished this by creating two definitions within my OD config, one for each of the points above. The first part was a standard file deployment; the second used dbLoader. The key part is to use the targetRules on the second definition to override the target replicationFarm and point back to localhost. You can then deploy the files to a temp directory and invoke DD locally. To chain the two deployments, simply specify two execDeploymentTask elements within your deployment element.