Metatagger Migration

Hi All

We currently have 2 solaris 8 servers. Both have Teamsite 6.5 sp3 installed. One of them is a production server and the other is the development server. The Metatagger is installed on the Development box and is used in the Production server. We are planning to migrate the Metatagger installation from the development box to the production box so that we can use the development box for 6.7.1 upgrade test.

I am very new to metatagger. I tried going through some documentation but could not find straight forward information. This is the information I have gathered.
1. Install Metatagger on Production server.
2. Configure metatagger users???????
3. update the iwmetatagger section in the iw.cfg
4. Copy all the configuration files from the development server to production server (Dont know which files to copy)
5. iwreset -ui
6. Test the installation.

Can anyone tell me what would be the basic steps involved in the migration process? What all files do we need to migrate from the Development server to the Production server to enable proper functioning of Metatagger.

I would appreciate your help.

Thanks in advance.

Find more posts tagged with

Comments

Migrateduser

(1) Install MT on production server (put the new license.cfg in $MT_HOME/conf)
(2) Migrate users (use CIAdmin and recreate the users from development box one by one)
(2.1) Replacing $MT_HOME/conf in production-server with $MT_HOME/conf from development server minus license.cfg and admin.cfg should also work.
(3) Change the [iwmetatagger] section is iw.cfg to point to the production server instead of the development server.
(4) iwreset
(5) test, use iwmtbatch or use Content Center to tag a file.

4. Copy all the configuration files from the development server to production server (Dont know which files to copy)

The files under $DB_HOME/conf, which has the summarizers, extractors, classifiers, recognizers, processors ... depending on your license.

If you are planning to keep MT only on the production server, send out a mail to all MT Studio users to use the production server Smiley Happy

syal123

Thanks snkmoorthy

I do have few more questions.
1. Does the info in the admin.cfg file get filled automatically upon installation or is that entered manually?
2. From 2.1 do you mean that after installing the MT on Production if we just copy all the files except the 2 files you mentioned, the installation would work properly? When are all those files created? (Sorry might look like a silly question but I have never worked with MT)
3. By reply 2 I concur that MT does have its own users right?

Thanks again.

Migrateduser

Answers:
(1) It is written by the installer with the host and port number of MT and Studio server port number, logging level ... on the host on which you ran the installer, so over writing it, will lose this info mainly host name.

(2) The MT_HOME/conf a.k.a $DB_HOME is where MT stores all the taxonomies, summarizers, extractors, pre/post processors ... so by copying over these files is ok as along as the source and destination installations have the same MT version. The files found here are created when you create projects via MT Studio or iwmtbuild and MetaTagger Administrator using CIAdmin or MTAdmin publishes them(makes them available for use by MetaTagger clients, like TagUI)

(3) Out-of-the-box MT comes with one user who is the administrator with login name admin. Users are managed locally by MT(no LDAP, ADS...). By copying over $DB_HOME you are skipping the steps of actually creating any of the users you had in the development server(somebody, already added them when MT was in the development box) and dumping the end product(a user database) in to your production server.

syal123

Thanks a lot for your reply. I appreciate your help.

Migrateduser

Some additional ideas:

1) You can use OD+TS or CAP to manage the versioning and deployment of MT configurations from development to production. Easiest way is to create a branch on your production TS server for the MT configuration, then use OD to deploy from MT-dev to TS to MT-prod via a workflow. That way you can always rollback if there is an issue.

2) Consider not overwriting the MetaTaggerAdmin*.db as it keeps the user database. By limiting who can log in to the production instance, you can enforce proper update methodology for the configurations (update dev; test; version; deploy).