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; } } }

default.sitemap migration Issue

shivgaytri

Hi,

I am unable to migrate default.sitemap()(while migrating whole site) using OD from one site publisher environment to other site publisher environment.Site map is getting corrupted.

I am using these attributes in OD config file to preserve ExtAttrs.

iwStore recordExtAttr="yes"
applyExtAttrs="yes"

Is there any way to migrate any site without corrupting sitemap?

Thanks in advance

Shiv

Find more posts tagged with

Comments

vpatel

Looked at SPAR?

shivgaytri

Looked at SPAR?

Yes I thought about that..but steps for creating spar mentioned in guide are very confusing...Do you have detailed steps for creating SPAR.

vpatel

I think I posted that info in one of the other posts about where exactly you should look. Also keep in mind that SPAR file is nothing much more than a .zip file. I have from day one followed the steps in the guide and it has worked just fine for me.

shivgaytri

I think I posted that info in one of the other posts about where exactly you should look. Also keep in mind that SPAR file is nothing much more than a .zip file. I have from day one followed the steps in the guide and it has worked just fine for me.

there is one question related to SPAR: How it is preserving EA as it's not getting/fetching EA from source environment and not applying/setting EA in target sitepublisher environment.

vpatel

Through the EA Manifest XML file. Starting at the bottom of page 278 (TS 6.7.2 SP1 SP Dev guide) it talks about this.

ccprofessional

Migrating .page and .site files from one server to another (including EAs) is a BAD idea. You will get DB conflicts when you run the .page files thru the 'publish livesite content' wfm because of uniqueness of livesite-ids. This is regardless of using SPAR tool or OD with EAs.

Why don't you use the traditional iwmigrate to migrate the default store?

IMHO Autonomy Interwoven has no clean solution for migrating content (especially Sitepublisher's .page files and other files) from one TS server to another TS server.

vpatel

ccprofessional is partially right that you do not want to migrate EAs that are set by SitePublisher. SPAR documentation makes is very clear that you should NOT carry over SP/LS specific EAs that may conflict. ArchiveManager will take care of those EAs for you automatically.

I agree that ArchiveManager will not do everything in the world for you. However if we understand what it is designed / intended to do and use it in that fashion it is pretty useful. I've used it very extensively.

Also ccpro's point to actually migrate content: just from my experience, you want to minimize migrating actual content (not components, templates, custom code, etc.) via this as much as possible -- similar to how you probably don't want to run iwmigrate every day (rather minimally run it when necessary). Just a good practice and in NO shape a limitation.

vpatel

IMHO Autonomy Interwoven has no clean solution for migrating content (especially Sitepublisher's .page files and other files) from one TS server to another TS server.

What sort of enhancements would like to see for the tool?

ccprofessional

ccprofessional is partially right that you do not want to migrate EAs that are set by SitePublisher.

WT..
can you tell me what I said is wrong? On the contrary, you were wrong when you suggested using the SPAR tool on .page files.

Stokes

can you tell me what I said is wrong? On the contrary, you were wrong when you suggested using the SPAR tool on .page files.

SPAR files CAN have .page files within them without problems. Archive Manager handles the livesite IDs when it imports the spar. Check the DevNet Tech Library for a handful of example spars that almost all include .page files.

Stokes.

shivgaytri

SPAR files CAN have .page files within them without problems. Archive Manager handles the livesite IDs when it imports the spar. Check the DevNet Tech Library for a handful of example spars that almost all include .page files.

Stokes.

Hi Stokes,

Could you provide me that article ID for DevNet Tech Library article.

vpatel

Stokes is mentioning that all of the SPARs available as part of the DevNet Tech library use this exact mechanism. I do not believe there is a specific DevNet Tech library "article" per say.

shivgaytri

Stokes is mentioning that all of the SPARs available as part of the DevNet Tech library use this exact mechanism. I do not believe there is a specific DevNet Tech library "article" per say.

Could you please let me know what steps you are following to create spar?

vpatel

Please see the SP Dev guide (TS 6.7.2 SP1) -- pages 275 to 284. It provides you step by step information on how to do this.

It is also important to keep in mind that your content/assets/code/configurations/etc. may differ completely from someone else'. Therefore it is important to understand the process.

Your SPAR file may include just components or just content or just Java code or some other configuration or some combination of these items -- depends on your what you are trying do. Include all or some of the components in the SPAR? Include all or some of the Java classes/packages in the SPAR? Reset component versions or not? Any "allowed" EAs that need to be carry forward? As you can see there are various options here. Most of these are outlined in the guide. From my past experiences, probably what will help you the most is the SPAR directory structure outlined on page 277 in Step 3.

If that does not provide a clear picture, I would recommend you inspect one of the OOTB SPARs or download one from Devnet SPAR library and check that out. Note the directory structure and how the SPAR (zip) file is laid out.

Once you have done some of this stuff listed above, please try to follow the steps to create a SPAR and post specific questions that you may have while following those steps.

ccprofessional

SPAR files CAN have .page files within them without problems. Archive Manager handles the livesite IDs when it imports the spar.

You can use the SPAR, Use OD (with EA deployment) or just use windows-copy followed by setting of EAs. That in itself is not the problem. And in my post I did mention that its not the SPAR, but the Workflow deployment task that is the problem. So - Can the SPAR have .page files in it? Sure, it can have **** for all it cares. Is it a good practise? NO.

KoenDeSmet

This is the first interesting thread and info I see about spars. I followed the official developer sitepublisher course and they staid very obscure about the usage of spar files (they just refered to the dev guide). Does anyone know what you REALLY can do while using spars ,what you can't do when using Opendeploy ?

In reply to ccprofessional :

...So - Can the SPAR have .page files in it? Sure, it can have **** for all it cares. Is it a good practise? NO...

However The dev guide contradicts itself :

In the beginning it says :

The SPAR installer does the following :
-Install Site files to the specified workarea and submits them
-Installs Pages and page assets to the specified workarea and submits them
..

Further in the doc it says :
Modifying Spar Content

The copying of .page, .site and .sitemap files is currently not supported.

Also when and when not to use the provided Ant script (ref. TS Publisher dev guid p.280) to reset template and page version numbers is unclear. Is this only to be used when using spar ,or also if you use Opendeploy when copying over components,pages and/or templates ?

Kind regards,

Koen
Belgium

current system :

# uname -a
SunOS 5.10 Generic_138888-01 sun4u sparc SUNW,Sun-Fire-V490
# iwversion
iwserver: 6.7.2 Build 69667 Interwoven 20081126
SitePublisher : 6.7.2 Build 69667 Interwoven 20081126

Environments 3 : Development,User Testing,Production

vpatel

The SPAR installer does the following :
-Install Site files to the specified workarea and submits them
-Installs Pages and page assets to the specified workarea and submits them
..

The copying of .page, .site and .sitemap files is currently not supported.

Both of these statements are correct. However, there seems to be a little confusion on the latter statement. In the dev guide, latter statement is implied for certain assets that are not to be copied.

First set of statements are correct that SPAR can install site files, .pages, components, etc. from TS server 1 to TS server 2. However once that SPAR file is installed on TS server 2, and lets say that you had a default.site file that got installed through that SPAR. You cannot just simply copy that default.site from site 1 to default.site for site 2. The reason for this is that some of these assets (i.e. .site, .pages, etc) have unique IDs assigned to them. I believe this kind of copying of SP/LS assets is not supported whether you use SPAR or no SPAR. Let's take SPAR out of the picture for a second, let's say you create site-1/default.site in your TS and you copy that into site-2/default.site -- that is not supported and that is what the document is trying to highlight.

So both statements are correct but the latter statement is considered a little out of context here. If you read the surrounding paragraphs it seems to add a bit more to it; however, I do agree that it could be clarified further in the documentation.

HTH!