Chat now with support
Chat with Support

Archive Manager 5.9.6 - Installation and Configuration Guide for GroupWise

Deployment considerations for GroupWise System requirements Hardware recommendations Pre-installation preparations Installing and configuring Archive Manager Upgrading/Uninstalling Archive Manager Post-installation tasks Appendix A: Attachment store types Appendix B: Process overview checklist

Localizing Archive Manager website (optional)

Both the Archive Manager websites for end users and Administration can be localized using JSON files stored in the Archive Manager installation directory.

To localize the website for end users into your language:
1
In the directory <ArchiveManager_Home>\WebSite\assets\language, copy the file en-US.JSON, and paste it to the same folder.
2
Rename the copy file with your language code. For example, for French (France), rename it to fr-fr.JSON.
3
Translate your language file (For each line in the file, only edit the text between the quotation marks after the colon).
4
Restart IIS.
* 
NOTE: The display language of the website for end users is determined by the user’s browser language, and English will be used if no resource file for the desired language can be found in the directory <ArchiveManager_Home>\WebSite\assets\language.
To localize the Administration website into your language:
1
Open the language file <ArchiveManager_Home>\WebSite\Resource\Languages.xml.
2
For each value code, add a new line with your language code as the culture name, and the translated text in your language.
3
Restart IIS.
* 
NOTE: The display language of Administration website is determined by the Archive Manager server language, and English will be used if no resource for the desired language can be found in the file Languages.xml.

 

Appendix A: Attachment store types

•
Attachment store types overview
•
NTFS/Windows File System
•
NetApp SnapLock
•
EMC Centera
•
Caringo CAStor/Dell DX
•
Hedvig Distributed Storage Platform
•
Common scenarios for editing the configuration

Attachment store types overview

Archive Manager supports different storage types for storing attachments and compliance messages. Details on using each of the storage types are provided below. The storage types supported by Archive Manager include:

•
NTFS / Windows File System: This is the default option, and stores files on standard disk.
•
NetApp SnapLock: SnapLock provides fast WORM (Write Once Read Many) storage on magnetic disk. It uses non-rewritable, non-erasable disk storage protects data until a specified retention date.
•
EMC Centera: This option uses an external EMC Centera server or cluster to store the attachments.
•
Caringo CAStor/Dell DX: This option uses a Caringo CAStor storage cluster or Dell DX Object Storage Platform to store attachments.
•
Hedvig Distributed Storage Platform: Works with Archive Manager as the NTFS/Windows File System.

Archive Manager allows more than one type of storage to be used on a running system. However, only one storage location can be considered the default storage location at a time.

When installing Archive Manager, you set the attachment store type on the Attachment Store Type screen. Once the product is installed, additional attachment stores can be added. This process is described below in the section Common scenarios for editing the configuration.

In all cases, Archive Manager stores each unique attachment as a single file or the equivalent unit. Archive Manager performs no compression or encryption. This is left to the underlying storage system.

Table 3. External storage type deprecation status
External Storage Type
Archive Manager Version for Deprecation

File System

Supported.

NetApp SnapLock 7.2.4

Supported.

EMC Centera 4.2.1, 4.2, 4.1, 4.0, 3.1.4, or EMC Atmos 2.0

Supported.

Caringo Castor/Dell DX

Supported.

Hedvig Distributed Storage Platform Version 3.7.1

Supported.

NTFS/Windows File System

The file system is the default storage mechanism for Archive Manager. This is a directory structure, usually in C:\ArchiveManager\Data, with each file stored represented by its database id and file type. For example: 34.gif

These files are stored in blocks of 1000 files per directory. Each database ID has up to twelve 0’s added to the front. For example, 34 becomes 000 000 000 034, and this is converted in a directory name:

c:\archivemanager\data\000\000\000\000\34.gif

By default, the entire tree, from c:\archivemanager\data down, is set to be compressed using NTFS compression. These files will not be rewritten, so any backup scheme can be used. It is recommended that you do an incremental backup.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating