SPARs Vs Open Deploy

System

Hi Guys,

I wanted to poll this group for the best practices around deploying sitepublisher content (Components, templates, DCTs, iw-resources, sites) from one Teamsite environment to another.

I tried creating spars and was not successful with this approach, when i have components and templates it works fine but if i include the sites/pages then it never succeeded.

Before i troubleshoot anyfurther i wanted to know if spars are the only way to move sitepublisher content across environments?

I thought Opendeploy can do the same job with extended attributes set while deployment.

Please share your experience with both the approaches.

Thanks,
Arun.

Faizi

Hi Guys, I wanted to poll this group for the best practices around deploying sitepublisher content (Components, templates, DCTs, iw-resources, sites) from one Teamsite environment to another. I tried creating spars and was not successful with this approach, when i have components and templates it works fine but if i include the sites/pages then it never succeeded. Before i troubleshoot anyfurther i wanted to know if spars are the only way to move sitepublisher content across environments? I thought Opendeploy can do the same job with extended attributes set while deployment. Please share your experience with both the approaches. Thanks, Arun.

As per as my knowledge there is only way to migrate component and template to other sitepublisher environment is

SPARS

.
For Opendeploy concern, it will do same but only from the workarea section not from the iwadmin section. So it can works for .page but do not for components.
A

spar

file is like a

jar

file. You have to create folder structure for component and

.page

files. For component a put all the component in component folder. For site and

templatedata

create a

workarea_root

folder.

HTH,