Hummingbird Migration

Migration in Hummingbird is separated into 4 main area: Database, Document, Indexes (but we can always recreate a new index after the document and database was restored to a new machine, so this is not necessarily needed), and the last is the enhance asp pages.

In Hummingbird application, all data settings was located in its database. So the only way to migrate is just backup and restoring database to a new database server.

Database Migration

I assumed you can do the backup restore database of SQL Server, so the main thing I want to teach is not about the backup or restore process but afterward the restoring.
After the database was restored to a new database server, you need to run this script:

For SQL Server 2000

update sysusers set sid = (select sid from master.dbo.sysxlogins where name='DOCSADM'),password = (select password from master.dbo.sysxlogins where name='DOCSADM') where name='DOCSADM'

update sysusers set sid = (select sid from master.dbo.sysxlogins where name='DOCSUSER'),password = (select password from master.dbo.sysxlogins where name='DOCSUSER')where name ='DOCSUSER'

update sysusers set sid = (select sid from master.dbo.sysxlogins where name='WFADM'),password = (select password from master.dbo.sysxlogins where name='WFADM')where name ='WFADM'

if it produce an error message like this:
Server: Msg 259, Level 16, State 2, Line 1
Ad hoc updates to system catalogs are not enabled. The system administrator must reconfigure SQL Server to allow this.

what you have to do is:

1. Open the SQL Server Enterprise Manager.
2. Right click on (Local)(Windows NT) node inside SQL Server Group node on the Tree, choose Properties.
3. Choose Server Settings Tab, under the Server Behaviour group box, give check to "Allow modifications to be made directly to the system catalogs" check box.
4. Then Close the window by clicking OK button.

Now, re-run the script again.

After that, Clear Cache in DM Server Manager.

For SQL Server 2005 and above

run this script:

EXEC sp_change_users_login 'Auto_Fix', 'DOCSADM', NULL, 'P@ssw0rd';

alter login DOCSADM with password='password' , CHECK_POLICY = OFF;

EXEC sp_change_users_login 'Auto_Fix', 'DOCSUSER', NULL, 'P@ssw0rd';

alter login DOCSUSER with password='password' , CHECK_POLICY = OFF;

EXEC sp_change_users_login 'Auto_Fix', 'WFADM', NULL, 'P@ssw0rd';

alter login WFADM with password='password' , CHECK_POLICY = OFF;

Then Clear Cache in DM Server Manager.

------
After the restoring script was run successfully, then change the server parameter in these tables.
Change Parameter in Remote Libraries table:

update docsadm.remote_libraries set server_location='New_Server_Name' where library_name='Library_Name'

Change Network Aliases into the current domain name:

update docsadm.network_aliases set network_id='Domain_Name\' + substring(network_id,charindex('\',network_id)+1,len(network_id)-charindex('\',network_id))

If the application server was newly installed for Hummingbird and the library name was new, then you have to find the PCDOCS.INI file, then add these line into the file:

[Library DM_TEST]

Vendor=3

Database=DM_TEST

Owner=

Location=DBSERVER_NAME

Username=DOCSUSER

Password=4a097d315857cdcb

After the restore script was done, try to login into Hummingbird web.

Document Migration

If the was already documents inside the server, then find the location of the document in DOCSADM.PROFILE table, using this query:

select distinct(docserver_loc + path) from docsadm.profile

Move the document into the exact same location, or mo to new location, then change the value of that field according to the new location of the document.

Index Migration

Only hummingbird server with millions of document that need this migration, if there is only thousands of document, I would recommended to re-create the index, it's much simpler and the newly created index would be more reliable.

Location of Index can be found in DOCSADM.FT_INDEXES table.

Enhance ASP Page

These are the pages that usualy customized:

- loginandgo.inc (in DM 5, is used to add tab in Quick Reference).
- frameset.asp (only in DM 6, is used to add more menu)
- itemdetaildsp.asp (to add tab in document detail)
- itemactionsact.asp (to insert process after the document profile was submitted)
- etc..

That is all I can share here, so many things can happen when you do the migration, not everything goes as smooth as when you simulation in your VMWare :P but at least some of them was written here, he3..

Good Luck..
-julie-