|
Home > Archive > Microsoft Content Management Server > April 2005 > Auto deployment script
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Auto deployment script
|
|
|
| Hi All,
I have two questions on auto deployment script.
1. I have a auto deployment script running between two servers [with
pCmsDeployExport.Export(strPackageFileName, 0, "")]. In site manager, I
created an export package of one template. There are several pages/postings
based on this template. When I import this package (consists of single
template) into the same server (for testing) using the site manager, the sdo
file generated from the auto deployment script is becoming very large (~188
MB). I was expecting this to be small because this should contain the
template that I just imported using the site manager. It looks like the auto
script including the all the postings and resources based on the template. Is
this normal?. Because of the large size of sdo file, the import in to the
destination server is getting hung. Is there any limit on the file imported
using the client script?.
2. Second question. I created a brand NEW template on the development
server. I created export package of this template and imported on to the
server on which auto deployment script is running. For some reason, the auto
script is not ble to detect this new template (imported using site manager).
I mean the next sdo file generated by the auto script does not include this
new template. This appears strange??.
--
Appreciate your comments,
Durga
| |
| Stefan [MSFT] 2005-04-22, 2:52 am |
| Hi Durga,
I assume you are talking about site deployment scripts, as something like an
auto deployment script does not exist.
Right?
SiteDeployment scripts cannot export a single template.
SiteDeployment scripts can only export postings and channels that have
changed or where a dependency has changed. Not single changed resources or
single changed templates.
With other words: when you modify a template then ALL postings build on this
template will be exported and not only the changed template.
You should try to export the template using SiteManager and import it on the
destination server.
Potentially this will ensure that futher incremental deployments using SDAPI
will no longer export the item.
Cheers,
Stefan
--
This posting is provided "AS IS" with no warranties, and confers no rights
New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
----------------------
"Durga" <Durga@discussions.microsoft.com> wrote in message
news:39C3FD18-2CB6-4199-9B0C-20CF4D474B51@microsoft.com...
> Hi All,
>
> I have two questions on auto deployment script.
>
> 1. I have a auto deployment script running between two servers [with
> pCmsDeployExport.Export(strPackageFileName, 0, "")]. In site manager, I
> created an export package of one template. There are several
pages/postings
> based on this template. When I import this package (consists of single
> template) into the same server (for testing) using the site manager, the
sdo
> file generated from the auto deployment script is becoming very large
(~188
> MB). I was expecting this to be small because this should contain the
> template that I just imported using the site manager. It looks like the
auto
> script including the all the postings and resources based on the template.
Is
> this normal?. Because of the large size of sdo file, the import in to the
> destination server is getting hung. Is there any limit on the file
imported
> using the client script?.
>
> 2. Second question. I created a brand NEW template on the development
> server. I created export package of this template and imported on to the
> server on which auto deployment script is running. For some reason, the
auto
> script is not ble to detect this new template (imported using site
manager).
> I mean the next sdo file generated by the auto script does not include
this
> new template. This appears strange??.
> --
> Appreciate your comments,
> Durga
| |
|
| I am talking about the site deployment script which I set up to run every 30
minutes using scheduled task. I understand what you are saying about the
deployment scripts export all the dependent objects. When I try to import the
posting/template on the destination server using site manager on which I
set-up to run deployment script, the sdo file generated from the deployment
script after import is becoming very large and it thinks all the objects
dependent on this template were changed. How do I avoid this problem?. Do I
code in my script so that when the sdo file is greater than some size skip
import?.
> You should try to export the template using SiteManager and import it on the
> destination server.
> Potentially this will ensure that futher incremental deployments using SDAPI
> will no longer export the item.
I did follow this. The problem the incremental deployment scripts are trying
to export all the dependent object after I import a posting (which also
brings its templat) using site manager.
"Stefan [MSFT]" wrote:
> Hi Durga,
>
> I assume you are talking about site deployment scripts, as something like an
> auto deployment script does not exist.
> Right?
>
> SiteDeployment scripts cannot export a single template.
> SiteDeployment scripts can only export postings and channels that have
> changed or where a dependency has changed. Not single changed resources or
> single changed templates.
>
> With other words: when you modify a template then ALL postings build on this
> template will be exported and not only the changed template.
>
> You should try to export the template using SiteManager and import it on the
> destination server.
> Potentially this will ensure that futher incremental deployments using SDAPI
> will no longer export the item.
>
> Cheers,
> Stefan
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
>
> New to MCMS?
> Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
> ----------------------
>
>
> "Durga" <Durga@discussions.microsoft.com> wrote in message
> news:39C3FD18-2CB6-4199-9B0C-20CF4D474B51@microsoft.com...
> pages/postings
> sdo
> (~188
> auto
> Is
> imported
> auto
> manager).
> this
>
>
>
| |
| Stefan [MSFT] 2005-04-22, 5:58 pm |
| Hi Durga,
all items that depend on this template - not all items the template depend
on will be exported.
The behaviour you are seeing is by design.
Cheers,
Stefan
--
This posting is provided "AS IS" with no warranties, and confers no rights
New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
----------------------
"Durga" <Durga@discussions.microsoft.com> wrote in message
news:C7FF6F89-E17E-4E57-9FA1-6E7B80BEDF02@microsoft.com...
> I am talking about the site deployment script which I set up to run every
30
> minutes using scheduled task. I understand what you are saying about the
> deployment scripts export all the dependent objects. When I try to import
the
> posting/template on the destination server using site manager on which I
> set-up to run deployment script, the sdo file generated from the
deployment
> script after import is becoming very large and it thinks all the objects
> dependent on this template were changed. How do I avoid this problem?. Do
I
> code in my script so that when the sdo file is greater than some size skip
> import?.
>
the[vbcol=seagreen]
SDAPI[vbcol=seagreen]
>
> I did follow this. The problem the incremental deployment scripts are
trying[vbcol=seagreen]
> to export all the dependent object after I import a posting (which also
> brings its templat) using site manager.
>
> "Stefan [MSFT]" wrote:
>
like an[vbcol=seagreen]
or[vbcol=seagreen]
this[vbcol=seagreen]
the[vbcol=seagreen]
SDAPI[vbcol=seagreen]
rights[vbcol=seagreen]
http://tinyurl.com/6zj44[vbcol=seagreen]
I[vbcol=seagreen]
the[vbcol=seagreen]
the[vbcol=seagreen]
template.[vbcol=seagreen]
the[vbcol=seagreen]
the[vbcol=seagreen]
the[vbcol=seagreen]
|
|
|
|
|