The Portal Info Center talks about deploying xmlaccess generated export scri
pts from a DEV server, then importing this to a STG server while preserving 
object id's..

What does preserving object id's mean? Is preserving object id's synonymous 
to modifying the xml script file and adding the create-oids="true" in the re
quest element?

G

[ Post a follow-up to this message ]

Every object in Portal (Page, Portlet, Skin, Theme, ...) has an Unique
Object ID. This Unique Object ID can be used to identify an object over
several Portal installations (like Development, Staging, Production).

So, that means, you can make changes to an object in your Development
installation. These changes will be applied to the object with the
Object ID in the Staging Environment. Dito for Production Environment.

To use this feature, you have to preserve the Object ID:
1) Export all object from your DEV installation to full-export.xml
2) Import full-export.xml into your Staging environment without creating
new Object IDs (create-oids="false")

If you set create-oids="true", new Object IDs will be created during XML
import. So, you could not map objects from DEV and StG server.

Maik


gdaswani@esri.com wrote:
> The Portal Info Center talks about deploying xmlaccess generated export sc
ripts from a DEV server, then importing this to a STG server while preservin
g object id's..
>
> What does preserving object id's mean? Is preserving object id's synonymou
s to modifying the xml script file and adding the create-oids="true" in the 
request element?
>
> G

[ Post a follow-up to this message ]

Thanks Mark for the clarification, ran into the same conclusion after readin
g the InfoCenter deployment guide the third time.

I believe create-oids="false" is the default processing attribute.

[ Post a follow-up to this message ]