Museum Help - Miscelaneous

Miscellaneous

Backups

You must backup, you must backup, you must backup.

At a minimum, you should regularly backup each repository's document directory. Even if the index is lost, the index can be recreated from the document directory.

You may also want to backup each repositories index directory and the "museum.db" database file in the server installation dir.

Keep in mind that recreating the index takes some time, depending on how many documents are in the document directory.

If you do backup the index and museum.db file, you must shut down Museum during the backup. (so the index data files are not changing during the backup)

If musuem is installed as a service, this is easily done from the command line:

    net stop museum
    ..... (do backup commands here)
    net start museum

Logging

Museum maintains 2 logs.

Standard Web Log

This is a standard text web log that can be used by any log analyser. This can be used to show usage statistics for users, searches and repositories.

127.0.0.1 - nologin [31/Jan/2005:16:39:04 -10] "GET /bh?query=emergency%7E HTTP/1.1" 200 15218

Museum Log File

This is a text file of custom format which records significant events as Museum is in operation.

It may provide useful information for fault diagnosis, as errors are logged here. Error lines have an "E" after the timestamp.

The last few lines of it can be viewed by selecting the "Logging" option in the Administrative menu.

Licensing

Select the "Licensing" option from the Administrative menu.

You will see the total number of documents currently indexed.

A list of purchased license codes are shown with the total of documents you are licensed to index.

Shutdown

The "Shutdown" option from the Administrative menu is the recommended way to shut down Museum. Using this ensures the index files are not corrupted.

You will be asked to confirm the shut down.

Restart

The "Restart" option from the Administrative menu is the recommended way to restart Museum. Using this ensures the index files are not corrupted.

You will be asked to confirm the restart.

The museum configuration file, config.xml, contains a tag called "custom_fields" for each repository. This is a comma separated list of field names. Each field must exist as a html input field in the 'docdetails.htm' page. When the 'docdetails.htm' page is saved, museum will create or update each field as required. Each field will be fully indexed.

Microsoft Exchange Integration

The Museum Client software can work with Microsoft exchange email accounts to monitor and archive email folders. This gives users maximum control on what is archived - in particular it gives them a chance to delete or move emails that do not want archived.

Another policy is to take a blanket, "archive everything" approach. Museum can work with MS Exchange to archive all emails sent and received on an MS Exchange server. This is done by enabling MS Exchange Journaling support and using Museums POP3 polling to download and archive the emails from the MS Exchange Server.

Enabling MS Exchange Journaling with Museum

* In the Exchange System Manager, expand Servers, expand , expand ¸and then right-click the mailbox store.

* On the General tab, select "Archive all messages sent or received by mailboxes on this store", and then click Browse to specify a mailbox as the journaling mailbox. All journaled messages for senders on this mailbox store are sent to the mailbox you specify.

* You will then need to enable and start "Exchange POP3 Service" from the service control panel. A shortcut way to open the services control panel is to run the command line "services.msc".

* You will then need to configure Museum to poll the Exchange POP3 server. Please click here for details .