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

MetaTagger 3.1 migration from one-system to two-system setup

gsundeep

Hi All,

We are about to migrate our MetaTagger 3.1 server to two-system from current one-system setup.
Currently, our MetaTagger 3.1 server is installed on same host as TeamSite 5.5.2 server.Below are the details of one-system setup

Solaris 8
TeamSite 5.5.2
MetaTagger 3.1

We will retain our TeamSite server to same as above but planning to migrate the MetaTagger server to new box .This new MetaTagger 3.1 server will be installed on Solaris 8.
( i.e OS and MetaTagger version will be retained)

I need to know the complete procedure( or Interwoven documentation if any) to help me migrate to this two-system setup.The current setup have customized vocabs/indices in $DB_HOME.

Thanks a lot,

Find more posts tagged with

Comments

psr

Hi,

Was you able to do this in the end? I have simillar situation except there is a version change also on the MT server as well as TS. It will be now 4.0 instead of previous 3.5.2 & TS 6.5 instead of 552. The rest of the scenario remains same as yours having seperate servers for the MT & TS. So the environment will be,

Solaris 9
TS 6.5 SP1
MT 4.0

Has anybody listed or is there any other thread where I can cross check steps needed to do the migration.

!Thanks

Migrateduser

Hello-

Best practice is to follow the UPGRADE document on support.interwoven.com ( https://support.interwoven.com/library/manuals/metatagger/pdf/Upgrade_to_MT40.pdf ).
It will walk you through the capture of your current system, the uninstall, then install - on
the new system. Follow the Admin Guide for integrating the two servers.

Recreate your configuration from you 3.x version of MT on the new server. Make sure
to look at the notes in the Advanced User's Guide because some the the CLT's have been
deprecated as well as some the the RACK SCRIPT processes, as well as a few Out-of-the-box
process.

Post again if you have a more specific question.

psr

Hi,

Thanks for the reply in first place.

I have just started to look into the details.
I did go thru the upgrade document. Basically there was no uninstall process involved in my case as it is a new MT server, so was just curious if it makes any difference there.

As you mentioned,
Recreate your configuration from you 3.x version of MT on the new server.

This is what I was curious about. Is it then just,
- exporting the vocabulariss as XML file & bringing over to new server through studio.
- changing the metatager.cfg (as I heard its there are changes in this version. can you refer me to the possible config changes needed)
basically we are in process of upgrading from,
- Which configs & other changes apart form the above details I need to know considering the fact that what we have here is mostly recognizers & few browse_only projects.

TS 552 -> 6.5 (already done)
3.5 -> 4.0
All new server migration. (Not really a same server upgrade.) Was curious if this makes my life easier in MT transfer as it was in TS transfer.

!Thanks

Migrateduser

The metatagger.cfg isn't compatible with 3.x, but the process is pretty basic unless you have classifiers or custom summarizer indexes. Exporting the vocabs from 3.x and loading them in 4.1 is a snap. You can recreate your configuration using your old metatagger.cfg and *.smf files as reference. It is important, however, to understand the multi-path options for different files types possible in MT 4.x.

If you have classifiers or custom summarizer indexes, the only trick is making sure you still have the document text as that will be required to rebuild.

Last note - migrate to 4.1 not that it is out. Wizard-based config and extractor support.