Netmail Archive 5.2 Installation Guide for Novell GroupWise

Transcription

Netmail Archive 5.2
Installation Guide for Novell GroupWise
Netmail Archive Installation Guide for Novell GroupWise
Netmail Archive is an enterprise-class electronic messaging solution that helps organizations address their current and future challenges of email
archiving, retention, regulatory compliance, and fast retrieval of email messages. Netmail Archive integrates seamlessly and transparently into
your corporate email system, improves server performance, lowers storage costs, and offers you the tools to individually or globally search
archived messages in aid of legal discovery, regulatory compliance, or organizational policy enforcement.
Netmail Archive adds value to your messaging collaboration system by providing secure, centralized archiving and retrieval of information. These
services are controlled by policies that allow organizations to define their rules for information retention centrally. The Netmail Archive solution
addresses an organization’s long-term archiving requirements by managing and maintaining a platform-independent external XML data repository
featuring storage management, access management, and full Information Lifecycle Management (ILM) capabilities to classify, manage, retain,
migrate, and dispose of email records—ensuring maximum uptime and enhanced performance for your email system.
Table of Contents
Introducing Netmail Archive
About Novell GroupWise
Netmail Archive Deployment Scenarios
Netmail Archive Feature Overview
Component Overview
Overall Installation Sequence
Documentation List
Netmail Archive Master Node
System Requirements
Pre-Installation Tasks for a GroupWise Deployment
Installing the Netmail Archive Master Node in a GroupWise Environment
Post-Installation Tasks for GroupWise
Indexing Node(s)
Server Requirements
Pre-Installation Tasks
Installing the Index Server
Start the Index Service
Run the Cluster Manager Tool
Configure Archive Server to Index Server Communications
Index Conversion
Using the Index Server Administration Console
Netmail Archive Worker Node(s)
Installing Worker Node(s) in a GroupWise Environment
Post-Installation Tasks for Worker Nodes
Install and Configure Optional WebViewer Component for GroupWise WebAccess
Installing the WebViewer Application to Your Web Server
Installing the WebViewer on a Linux System
Installing the GroupWise Remote Provider Component
WebViewer Post-Installation Tasks
Install and Configure Optional Stubbing Agent
Installing the Stubbing Agent
Configure Stubbing for GroupWise 8
Install and Configure the Remote Provider(s) for Netmail Search
Installing the Remote Provider(s)
Remote Provider Post-Installation Tasks
Additional Configuration for the Remote Providers
Appendix A - Rebuilding the PostgreSQL Database
Appendix B - Confirming eDirectory Schema Extensions and Objects
Appendix C - Preserving Data & System Integrity of Netmail Archive
Appendix D - Netmail Archive and Anti-virus Software
2
Copyright © 2013, Messaging Architects. Updated: 10/05/2013
Introducing Netmail Archive
This section covers the following:
Component Overview
Documentation List
Novell GroupWise is a messaging and collaboration system that supports email, calendaring, personal information management, and document
management. Netmail Archive adds value to your GroupWise system by providing secure, centralized archiving and retrieval of information.
Integrating seamlessly and transparently into the email system, Netmail Archive frees up server space, improves server performance, and
ensures fast retrieval of archived email and attachments. Netmail Archive allows administrators to enforce flexible email policies without breaching
privacy and freedom of information rights, and at the same time, to tackle an exponentially growing volume of electronic data by easily integrating
with a number of third-party storage systems.
The number of servers required for your Netmail Archive deployment will vary depending on a number of factors, such as:
Number of users
Quantity of new daily messages to process
Average size of attachments to process
Records retention policy (size of archive indexes)
Frequency of Archival access
Archiving frequency (every day or every second day)
Information Lifecycle Management jobs
Messaging Servers
Netmail Archive supports the following messaging servers:
GroupWise
In a GroupWise environment, the Netmail Archive system is responsible for extracting information from GroupWise, indexing XML content,
exporting content from the data repository to various output formats, and running grooming and deletion jobs on the archive repository. The
Netmail Archive server requires a Windows 2003 Server or a Windows 2008 Server. A single Netmail Archive server should be able to effectively
archive more than 500,000 items in less than 24 hours.
Note: Netmail Archive integrates with GroupWise via SOAP API or Object API. Stubbing functionality requires SOAP API
integration.
Exchange
In an Exchange environment, the Netmail Archive server is responsible for extracting information from Exchange, indexing XML content, exporting
3
content from the data repository, and running grooming and deletion jobs on the archive repository. The Netmail Archive server requires a
Windows 2003 Server or a Windows 2008 Server. A single Netmail Archive server should be able to effectively archive more than 500,000 items
in less than 24 hours.
Note: Netmail Archive integrates with both Exchange 2007 and Exchange 2010 via EWS.
Mixed GroupWise and Exchange Environment
With Netmail Archive, you can also use a mixed messaging and collaboration system if you are currently running both GroupWise and Exchange
in your environment or if you are planning a migration from your current email server to an alternate email server in the near future.
For additional information about deploying Netmail Archive in a mixed environment, see the “Accessing Archives in a Mixed Environment”
appendix in the Netmail Administration Guide for Novell GroupWise.
Multiple Node Deployment and Clustering
To provide organizations with a robust solution that is scalable and fault tolerant, Netmail Archive supports clustering and load-balancing to
enable multiple servers to work together. Netmail Archive is configured to automatically detect any additional nodes and cluster together for
maximum performance and uptime. Within a cluster, the Master node will automatically detect the current load of any of the Worker nodes in the
cluster and distribute the workload between the nodes accordingly to better utilize system resources.
The following figure illustrates how Netmail Archive functions in a multiple node deployment scenario:
1. Through the Netmail Archive Administration Console, archiving jobs are defined and stored in eDirectory. The Master node scans
eDirectory and executes jobs based on their schedules. When executing a job, the Master node allocates work across the available
nodes in the cluster.
2. The nodes query the messaging servers for data. Data is then sent to the nodes from the messaging server for processing through
Netmail Archive.
3. After processing, Netmail Archive converts the data to XML format and writes the data to the storage system.
4. The nodes also signal the Index Server to read the data and index the contents.
Index Server Deployment
Netmail Archive can help you respond to eDiscovery requests quickly and cost-effectively and significantly reduce your risk and liability. The
Netmail Archive solution helps organizations proactively gather, restore, search, organize, and deliver email and other records for litigation
discovery and regulatory investigations. Netmail Archive’s high performance email archiving capabilities quickly archive and index selected
electronic records that are easily transferred to a choice of media for storage. With Netmail Archive’s sophisticated new indexing and powerful
search tools, archived email and other electronic records can be located and accessed instantly from any web browser where approved users can
search, review, view, and organize these electronic assets as required.
Pre-planning is an important step to consider when planning your Index Server deployment. The number of Index Servers required for your
Netmail Archive deployment will vary depending on a number of factors. For example, as the volume of email increases, you should take into
consideration the number of messages you expect to index. Also, performance is proportional to the number of spindles available to the Index
Server. A basic Index Server should have four disks or more to store the index.
4
A single Netmail Archive Index Server should be able to index between 50 and 75 million documents. For more information on installing the Index
Server, see “Installing the Index Server”.
Netmail Archive provides a set of tools which enable the user to proactively address three key concerns: policy-based retention/deletion, full
Information Lifecycle Management, and long-term data accessibility and portability.
Policy-Based Retention
Presently, regulated industries require the retention of documents and records, including email. Best practices suggest that enforcing a corporate
email policy by extracting information and retaining it according to relevant business drivers is the best approach to tackling regulatory
compliance. Moreover, a corporate-wide email retention policy ensures reliable protection of corporate records and preparedness for legal
discovery. It also increases employee productivity by reducing the time spent managing individual mailboxes.
Netmail Archive supports enhanced SEC 17.4 compliancy for storage of data on WORM media through integration with storage solutions, such as
NetApp storage systems from Network Appliance, Inc., the Hitachi Content Archive Platform (HCAP), and hardware-agnostic Netmail Store
storage software. Messages can be tagged by Netmail Archive with retention dates that deny the capabilities of modifying or deleting these
messages until after the retention date has been reached.
Netmail Archive addresses regulatory compliance through a robust feature set and capabilities that offer:
The option of pre-defined policies for automated archiving of single or multiple accounts following industry regulations.
Transparent implementation of corporate electronic data retention policies.
The option of 100% retention of all account information, including user deleted emails.
Real-time auditing to meet even the most stringent regulatory obligations.
A set of tools for search and discovery of email messages and attachments.
Flexible storage options supporting any Windows CIFS-conformant storage solution, including magnetic, optical disks, Storage Area
Network (SAN), Network Attached Storage (NAS), and Content Addressed Storage (CAS)
Full Information Lifecycle Management
Netmail Archive provides administrators with a complete Information Lifecycle Management solution to deploy and manage more effective
retention and archiving policies to reduce current storage requirements and database sizes. It provides organizations with the ability to improve
their collaboration system performance and reliability, as well as reduce their storage costs and recovery times in the event of system failure. By
deploying Information Lifecycle Management policies, organizations can more effectively manage their archive store(s) through grooming and
deletion.
Long-Term Data Accessibility and Portability
More and more, email is becoming a source of legal documentation and this affects how industries approach long-term electronic data
management. Organizations mandated to recover email for legal discovery can no longer rely on backup tapes and personal email archives.
Netmail Archive stores corporate archives in a way that offers their easy and quick retrieval. The wide range of search functions for auditing and
record retrieval enables you to perform search and discovery of email content and records with granular control that greatly facilitates the process
of legal discovery. Netmail Archive lowers the cost of system administration and the time required to recover messages.
This feature ensures total compliance with SEC regulations in that it stores information to “Read-only” media. In other words, files are exported in
a non-modifiable and undeletable state until a specified retention date is reached.
Message discovery options include:
Global search of single or multiple mailboxes
Standard content, subject, date, and address searches
Attachment search
Refined searches
Enhanced Proximity, Wordlist, and Approximate Spelling searches
Audit trail searches
All searches are performed on email archives containing mail messages, appointments, tasks, notes, and attachments. Electronic messages are
exported to a platform-independent repository to ensure portability and ease of discovery in system-independent XML format.
Netmail Archive offers Single Instance Storage (SIS), which enables the storage of a single copy of any archived message attachment. In a
non-SIS archiving environment, every archived message attachment is stored, even if the attachments are identical. SIS reduces storage costs by
storing only a single copy of identical attachments. In Netmail Archive, SIS is implemented at the application level, so organizations benefit from
this feature regardless of their storage integration.
Component Overview
5
Netmail Archive is modular and consists of several components that can be implemented depending on your needs.
Netmail Administration Console
The Netmail Administration Console includes the main administrative interface of Netmail Archive. It is a flexible and intuitive web-based
application that allows administrators to configure Netmail Archive, create policies, and run jobs. Upon login, administrators can access system
information, view and configure Master and Worker nodes, and view, modify and/or create policies and jobs through the various available job
agents.
Policy Engine
The Policy Engine is the back-end component that creates, organizes, and manages policies within Netmail Archive. The Policy Engine facilitates
the implementation of corporate-wide email retention, storage, and compliance management by using pre-defined policies. With the policy engine,
you can create email archiving policies that truly meet your organization’s needs. Policies contain specific criteria which are then applied to
various Job Agents in the Netmail Administration Console. Polices may be as simple or as complex as your business needs dictate, and because
Netmail Archive gives you flexible control over the organization’s email policies, you can always amend existing policies or create new ones as
your business needs change.
With the Policy Engine, system administrators can:
Create policies for automated archiving and exporting of single or multiple accounts dependent on industry regulations.
Schedule archiving and/or storage tasks to run automatically at regular intervals.
Send notifications upon completion of the policy-driven archiving, exporting, indexing, and information lifecycle management processes.
Create a task process to securely copy and convert email messages and attachments from existing mailboxes and archives into ASCII
form based on the XML format.
Create policies with transparent access to GroupWise user accounts using the GroupWise Trusted Application Technology
Archive Agent
The Archive Agent is the main component of Netmail Archive. With the Archive Agent, administrators can create archiving jobs to move any
information held in your email system’s message store, such as messages, calendar information, and any attachments, to an external repository
in XML format. The Archive Agent provides more granular archiving to XML by allowing enhanced criteria searching including advanced date
selection and message property options.
With the Archive Agent, you can:
Deploy and enforce corporate-wide email retention, storage, and compliance management policies by using pre-defined archiving tasks.
Implement policies for automated archiving of single or multiple accounts according to industry regulations.
Schedule archiving tasks that are executed automatically at regular intervals.
Apply an archive process to securely copy and convert native GroupWise messages and attachments from existing mailboxes or existing
GroupWise native archives to XML format.
Perform tasks with the option of including personal address books.
Send notifications automatically upon completion of the archiving process.
Apply policies with transparent access to GroupWise user accounts using the GroupWise Trusted Application Technology.
Discovery Agent
The Discovery Agent lets system administrators create jobs to regularly analyze the state of the message store to help organizations make
informed storage management decisions. These comprehensive reports enable organizations to protect information and better manage their
electronic assets through all stages of its lifecycle. The Discovery Agent can also be used as a tool to help administrators create intelligent
Archive and ILM policies.
With the Discovery Agent, you can:
Apply policies that analyze entire domains, post offices, or individual user accounts.
Perform regularly scheduled tasks to analyze the state of the message store.
Send notifications upon completion of the discovery process.
Export Agent
The Export Agent gives organizations the ability to create specific jobs to export (or copy) the contents of their XML repositories for various
purposes (e.g., the provision of selected information to an external auditor.
With the Export Agent, you can:
Execute jobs, in conjunction with Netmail Search, to export selected items from their archive to PST, PDF, or Searchable XML format,
ready for provision to any third party.
Execute jobs to export archived content from one XML repository to another, for storage management or retention policy purposes.
Send notifications automatically upon completion of the export job.
Group Agent
6
The Group Agent allows you to schedule a series of jobs to run consecutively. The Group Agent helps you make intelligent scheduling decisions
by allowing you to configure consecutive jobs to run automatically, removing the need for constant administrator intervention.
Information Lifecycle Management (ILM) Agent
The ILM Agent provides organizations with the ability to deploy full information lifecycle management policies to address their long-term records
retention and records management needs. Using pre-defined ILM policies, organizations can better manage their XML repositories.
With the ILM Agent, you can:
Apply file grooming policies to automatically move selected data to an alternate storage location, such as a network-attached storage
(NAS) device, to maximize storage performance while minimizing costs.
Enforce ILM policies to expire messages that have reached the retention period defined by the policy.
Send notifications upon completion of ILM processes.
Index Agent
The Index Agent allows organizations to create separate Index Jobs for your XML repositories rather than having the indexing completed by the
archiving job. This can be used to improve archiving performance, as well as process more concurrent users.
With the Index Agent, you can create:
Scheduled tasks to specify the type of indexing you wish to perform, such as incremental indexing.
Tasks to recreate indexes, or convert existing indexes in XML format and re-index.
Relationships between indexing tasks and specific archiving jobs.
Notifications upon completion of indexing tasks.
Utility Agent
The Utility Agent allows you to perform various maintenance tasks on the mail system, including folder management and mailbox reduction, and
on the XML store.
With the Utility Agent, you can:
Deploy enterprise-wide management policies to create user folder structures in the corporate email system mailboxes.
Assist in implementing your retention policy by performing tasks to delete messages from your GroupWise system or from GroupWise
native archives based on specified criteria.
Delete attachments in the XML SIS store that no longer need to be saved.
Apply tools to convert legacy data into a format that is readable by the current version of Netmail Archive.
Send notifications upon completion of maintenance tasks.
Netmail Search
Netmail Search is an advanced eDiscovery tool that allows administrators to intelligently view and manage their archived data through advanced
search features and guided navigation. The tool’s search functions include the ability to search for both message and attachment attributes.
Advanced search features allow for word list usage, exact phrase matching, forbidden term searching, approximate spelling matching, and more.
Administrators may also build their own search queries, meaning they are never limited to default search criteria. Guided navigation lets users
filter search results for easy viewing and auditing, and commenting and tagging features let administrators note the relevance of specific data.
Netmail Search employs a case management organizational system. Upon logging into Netmail Search, administrators are greeted with a Case
Management Dashboard that lets them create and manage multiple cases. Through this case management system, administrators can respond
to any and all eDiscovery requests simultaneously and are spared the headache of sifting through all archived data each time an eDiscovery
request is made. Advanced search options and guided navigation, plus the logic of case management, are delivered to administrators in an
easy-to-use, intuitive web-based interface.
Netmail Archive WebViewer
The Netmail Archive WebViewer is an archive viewer integrated into the GroupWise WebAccess client interface. Once logged in to GroupWise
WebAccess, users can toggle between the standard WebAccess view of their GroupWise message store and the Netmail Archive WebAccess
view of their XML archives. Maintaining the look and feel of GroupWise WebAccess, the Netmail Archive WebViewer allows users to transparently
access their XML archives and live mailboxes for a seamless end-user experience. The Netmail Archive WebViewer displays the archive content
categorized by item types in two separate views: one for messages and another one for calendar items (tasks, appointments, and notes).
The WebViewer provides GroupWise WebAccess users with a fast, platform-independent means to access their own published GroupWise
archives via a web browser. The WebViewer interface also provides users with enhanced searching capabilities in addition to the standard
GroupWise WebAccess search interface.
Administrative Utilities
7
Netmail Archive includes a number of optional utilities to complement your Netmail Archive system. These utilities can be used to help
administrators organize and manage their archives. If you installed Netmail Archive in the default location, these utilities can be found in the C:\Pr
ogram Files\Messaging Architects\GWArchive\Deployment folder.
Indexing Server
The Indexing Server is the component that makes eDiscovery possible. This highly advanced piece of technology acts, within the platform, as the
creator of the index of all messages and attachments archived by the system. It is also responsible for processing the search queries (which are
applied against that same index) whenever users seek specific content from the archive.
This dual functionality is accessed through jobs in the Netmail Administration Console for the indexing part, and through the web-based search
interface Netmail Search. In Netmail Search, guided navigation and query creation allow administrators to search and sort search results by date,
size, or relevance, as well as to refine results by excluding irrelevant locations, dates, files, or authors.
Remote Provider
The Remote Provider is a little-known and barely visible component of the Netmail Archive solution, but an important one when it comes to user
access to the archived items. This component receives the requests for information (queries) from Netmail Search, and passes them on to the
Index Server for processing. It then re-packages the results for presentation by Netmail Search. When a user selects a specific archived item
(message or attachment or audit file) to display in Netmail Search, it is also the Remote Provider that fetches the data from the archive and
presents it in Netmail Search.
Stubbing Agent
The Stubbing Agent is a piece of software developed by Messaging Architects for Novell. It is akin to a highly specialized Remote Provider; it
receives requests for specific messages from the GroupWise client, fetches the requested items from the archive, and presents them for display
in the GroupWise client. The main difference with the Stubbing Agent is that the items are requested via the stubs, visible as special items in the
list of messages. Stubs are references to the messages, essentially pointers to archived items, but look like normal messages in the mail server.
The Stubbing Agent’s main job is to resolve those references on behalf of the GroupWise client.
For a typical deployment of the Netmail Archive solution, a number of components need to be installed and/or configured to ensure effective and
proper functionality of the archiving system. The following is an outline of the overall installation procedure for the entire Netmail Archive system:
1.
2.
3.
4.
5.
6.
7.
Verify that the system requirements are met on all servers and/or VMs
Install and configure the Netmail Archive Master node
Install and configure the Indexing node(s)
Install the Worker node(s) (if applicable)
Install and configure the optional WebViewer component
Install and configure the optional Stubbing Agent
Install and configure the Remote Provider(s) for Netmail Search
Documentation List
The Netmail Archive Installation Guide and the Netmail Archive Administration Guide combine to explain how to install and configure the Netmail
Archive Server and Web components, as well as various helpful administrative utilities. After installing and configuring Netmail Archive with the
help of this guide, refer to the Netmail Archive Administration Guide to learn how to easily use the Netmail Administration Console to create
retention and archiving policies and schedule archiving jobs. Below is a brief description of the components of Netmail Archive and the
documentation available for each. The documentation listed below can be found in the Messaging Architects Documentation folder in the Netmail
Archive package.
8
Component
Description
Available Documentation
Netmail Administration Console
A web-based administrative interface that
allows for configuration and management of
policies and jobs, as well as configuration and
monitoring of the Netmail Archive system.
Netmail Archive Installation Guide and Netmai
l Archive Administration Guide
Policies
Criteria filters used by jobs to determine which
items they will act upon.
Netmail Archive Administration Guide
Archive Agent
Allows administrators to create archiving jobs
to move any information held in your email
system’s message store to an external XML
repository.
9
Discovery Agent
Allows administrators create policies to
regularly analyze the state of the message
store to help organizations make informed
storage management decisions.
Group Agent
Allows administrators to schedule a series of
jobs to run consecutively.
ILM Agent
Allows organizations to deploy full information
lifecycle management policies to address their
long-term records retention and records
management needs.
Index Agent
Allows organizations to create separate Index
Job for their XML repositories rather than
having the indexing completed by the
archiving job.
Utility Agent
Allows administrators to perform various
maintenance tasks on the GroupWise
message store or the XML repositories.
Netmail Search for eDiscovery
A powerful web-based eDiscovery tool that
offers several advanced search capabilities to
allow administrators to find and manage
relevant information quickly and efficiently.
Netmail Search User Guide for eDiscovery
Netmail Search for End Users
allow end users to easily search and manage
their personal archives.
Netmail Search User Guide
Netmail Search for External Reviewers
allow external reviewers to search through
and review relevant information quickly and
efficiently.
Netmail Search User Guide for External
Reviewers
WebViewer for Administrators
A GroupWise WebAccess plug-in that allows
administrators to access and search the
archive data for all users in the XML
repositories to which they have access.
WebViewer User Guide for Administrators
WebViewer
A GroupWise Client plug-in that allows end
users to view their archived data.
WebViewer User Guide
Indexing Server
Creates the index of all messages and
attachments archived by the system and
processes users’ search queries.
Netmail Archive Installation Guide
Remote Provider
Receives information requests from Netmail
Search, sends them to the Index Server for
processing, and prepares the results for
viewing in Netmail Search.
Netmail Archive Installation Guide
Netmail Archive Master Node
A successful installation of Netmail Archive requires the step-by-step completion of the following steps. Once all the procedures outlined below
have been carried out in the appropriate order, you will be able to implement policy-based email retention within your organization.
Miscellaneous Prerequisites
System Requirements
Meet Hardware and Software Requirements
Install GroupWise Client (if required)
Verify the Secondary Logon Service is
running on the server
Install Novell Client (if required)
Install Outlook Client (for exporting to PST
format)
Verify .NET Framework 4.0 is installed
Verify Netmail Open Framework NOT
installed
Install Java Runtime Environment 6.0 32-bit
(on the Archive Node)
Choose your SQL-Based Logging Database
Netmail Archive Installation
Deploy Netmail Archive
Start Netmail Archive Services
Launch the Administrative Console and Log In
Post-installation Tasks
Update the Address Book Cache
Verify Netmail Archive Licensing
Configure Web Browser for Index Server
Communications
System Requirements
For a successful installation of Netmail Archive and optimum expected performance of the solution, ensure that your servers or VMs have been
built according to the minimum recommended system requirements. For the most up-to-date system information and requirements, please refer
to System Requirements for Netmail Archive or contact Messaging Architects.
Furthermore, ensure that the following miscellaneous prerequisites are met before proceeding with the pre-installation tasks:
Miscellaneous Prerequisites
10
Anti-Virus Software
Turn OFF all AV Software until the Netmail
Archive software is installed and validated
Management Software
Do not install any management software,
including Manufacturer monitoring or Backup
software
Windows Firewall
Turn OFF firewall
User Access Control
Turn off UAC
DEP Settings
Turn on for Essential Windows Services only
Windows Policies
Do NOT apply policies
Pre-Installation Tasks for a GroupWise Deployment
In order to ensure a successful Netmail Archive installation and trouble-free operation afterwards, there are certain things you must do to prepare
your system before installing Netmail Archive. The following list of requirements must be met before installing Netmail Archive in a GroupWise
environment.
GroupWise Client
If you are going to be using the GroupWise Object API (OAPI) to connect to your GroupWise system or plan to run the Netmail Archive
GroupWise to Exchange Provisioning Utility on your Netmail Archive archive server(s), then verify that the server(s) to be used as an archive
server has the appropriate GroupWise Client for your environment installed on it (minimum supported version is 6.5.6 or higher). If the server
does not have the correct version of GroupWise Client on it, install it now.
Administrator Rights and Accounts
Netmail Archive requires access to your organization’s eDirectory tree or to a new dedicated eDirectory tree. Initially, this access will be used
during installation for extending the eDirectory schema and creating the Netmail Archive configuration objects. Once operational, Netmail Archive
requires only eDirectory access for storing and reading its configuration.
Messaging Architects recommends the creation of a dedicated Netmail Archive eDirectory user account. During the installation period, this
account will need full administrative rights to the eDirectory tree (in order to extend the schema and create the initial objects). Thereafter,
however, it requires only administrative rights granted to the container where the Netmail Archive objects are stored.
Moreover, Netmail Archive requires a GroupWise account to log in to the system in order to extract information, such as the GroupWise System
Address Book content. These combined eDirectory and GroupWise account requirements are most easily achieved by creating an eDirectory
user (perhaps named "NMArchive") within a container created in eDirectory specifically for storing the Netmail Archive configuration objects. This
eDirectory user should then be given a GroupWise account on a local Post Office.
Finally, on each server that will be used as an archive server, a Windows account must be created in order to run the Netmail Archive Windows
services. To facilitate larger (or variable-size) deployments, it is usually more expedient to create a Windows domain-level account (with
membership of each archive server's local Administrators group) for this purpose. Furthermore, it may be necessary to grant this account user file
rights to any and all storage locations where GroupWise Native Archives may be located on your organization’s network.
Tip: Best practice is to use an Active Directory user account. To do so, create an Active Directory user (perhaps named
"nmarchive"), and add it to the local Administrator Group of each Archive server. Use the domain\user credentials for all the
Netmail Archive Windows Services and Share Permissions. This allows for easier management in a multi-server environment.
.NET Framework
Verify that Microsoft .NET Framework version 4.0 is installed and enabled. To verify that Microsoft .NET Framework is installed, navigate to the
Control Panel and launch the Add and Remove Programs function. In the list of currently installed programs, look for Microsoft .NET Framework
4.0. If Microsoft .NET Framework version 4.0 is not installed, the program is available for download from www.microsoft.com.
Note: If using Windows Server 2008 R2, you can verify that Microsoft .NET Framework is installed through the Server Manager.
To do so, click Start > Administrative Tools > Server Manager. In the Server Manager interface, click Features, and verify that
.NET Framework 4.0 is listed in the right-hand pane.
11
Install Java Runtime Environment 6.0 32-bit
Verify that Java Runtime Environment 6.0 32-bit is installed on your Archive server. Disable automatic updates. JDK 6.0 64-bit is required for your
Index Server.
Note: Java Runtime Environment 6.0 is sometimes referred to as Java Runtime Environment 1.6. At the time of publication, Java
Runtime Environment 6.0 was available for download at the following link: http://www.oracle.com/technetwork/java/javase/downlo
ads/index.html.
Install SQL-Based Database
During the Netmail Archive installation process, you will be prompted to install PostgreSQL to use as the logging database. However, if you do no
t want to use the PostgreSQL database, make sure that the database you are using is fully installed and accessible from the Netmail Archive
server(s). If you are using a database other than PostgreSQL, Oracle, MySQL, MSSQL (2005/Express), or MSSQL (2000/MSDE), the database
must contain a valid connection string, which you will be prompted to enter during the Netmail Archive installation process.
Note: PostgreSQL is the recommended database for Netmail Archive. For more information on logging databases, see “Netmail
Archive Logging Database”.
Installing the Netmail Archive Master Node in a GroupWise Environment
Installation sequence for Netmail Archive 5.2
Locate and run the setup.exe file located in the NetmailArchive directory. It is recommended that you right-click on the setup.exe file and select
the Run as administrator option. The Netmail Archive Setup Program will install the Netmail Archive Master node and the Corporate Archive
Viewer. The installation program will guide you through the installation process. Follow the onscreen instructions to install Netmail Archive in a
GroupWise environment.
Important: Netmail Archive does not support installing the Netmail Archive software from a USB key. Instead, you should copy
the Netmail Archive installation files to the server on which you will be installing Netmail Archive.
On the Netmail Archive Welcome screen, click Next to proceed.
On the License Agreement screen, carefully review the software license agreement, and then click I accept the terms of the license
agreement to accept the License Agreement. Click Next to continue.
12
On the Choose Destination Location screen, install Netmail Archive in the default destination folder, or browse to the location where you want to
install Netmail Archive. Click Next to continue.
The Cluster Configuration screen allows you to choose whether you are installing a Master or Worker archive node. Where workloads require,
Netmail Archive can be configured to run a cluster of archive nodes. The first server installed should always be chosen as a Master node and all
subsequent archive nodes installed as Worker nodes. Within a cluster, the Master node will automatically distribute the workload across the
available archive nodes to better utilize system resources. For smaller environments intending to use only one archive node, the Master role must
be chosen.
13
1. On the Cluster Configuration screen, select the Install Master Node option, since you are installing the first archive node of the cluster, or
you are installing only a single archive node.
Note: For more information about installing Worker nodes, see “Installing Worker Node(s) in a GroupWise Environment”.
2. Under Master Configuration, enter the IP Address of the computer where you are installing Netmail Archive.
Note: If your server has multiple IP addresses (e.g., in the case where you are using iSCSI NICS as well as LAN NICS), then
ensure that you enter the correct IP Address for Netmail Archive communication (e.g., the LAN IP address).
3. The Port field specifies the port number that will be used for Netmail Archive cluster communications by this node. By default, the port number
of the Master node is 8585. It should not have to be changed, as Netmail Archive should be installed on a dedicated server. However, you can
change the default port number based on which ports are currently in use and your network security requirements. Whichever port you choose, be
sure to verify that there are no firewalls or filters on the port that would impede communications.
4. Click Next to continue.
If you do not have an SQL database installed on your system, the PostgreSQL Installation dialog box appears, prompting you to install
PostgreSQL as your logging database. If you want to use PostgreSQL as your logging database, click Yes to proceed with the PostgreSQL
installation. Otherwise, click No to continue with the Netmail Archive installation (which continues with the Messaging Server screen).
Note: If you choose not to install PostgreSQL, you can opt to manually install a different supported database.
After clicking Yes, you are reminded to include the ODBC drivers as part of the PostgreSQL installation. Click OK to acknowledge the reminder
and continue with the PostgreSQL installation.
14
Installing PostgreSQL
Prior to the launch of the PostgreSQL installation, a command window opens (as shown below). This command window must be kept open for the
duration of the PostgreSQL installation.
The installer will also automatically install the Microsoft Visual C++ 2008 Redistributable if it is not found already installed on the server.
On the PostgreSQL Welcome screen, click Next to proceed with the installation.
15
Important: Note that the Netmail Archive Installation Wizard window remains open while you install PostgreSQL. A separate
PostgreSQL Installation Wizard opens over the window of the Netmail Archive Installation Wizard. Do not exit the Netmail
Archive Installation Wizard. Once the PostgreSQL installation is complete, you will be able to seamlessly continue with the
installation of Netmail Archive.
Note: If the installation of PostgreSQL fails, this is typically a Windows file system rights issue and/or a user rights issue.
Confirm that both have the required rights before proceeding with the install.
If, during the installation of PostgreSQL, the creation of the Postgres database fails, refer to Appendix A - Rebuilding the
PostgreSQL Database for information on how to manually rebuild your Postgres database.
On the Installation Directory screen, use the default location or specify the location in which you want to install PostgreSQL. Click Next to
continue.
16
On the Data Directory screen, use the default location or specify the location in which you want to store your data, and then click Next to
continue.
On the Password screen, enter and confirm the password for the postgres database super user and service account. If a service account already
exists, enter the corresponding password for the account. If a service account does not exist, a new one will be created when you click Next. Click
Next to continue.
17
On the Port screen, enter the number of the port on which the PostgreSQL system should listen for connections. It is recommended to use the
default value of 5432 unless you have good reason to change it. Click Next to continue.
On the Advanced Options screen, select the locale to be used by the new database cluster, and click Next.
18
On the Ready to Install screen, click Next to install PostgreSQL.
On the Completing the PostgreSQL Setup Wizard screen, you are asked if you want to launch Stack Builder upon closing the Setup wizard.
The Stack Builder utility is used to install the ODBC driver. It is very important to leave the checkbox selected to launch the Stack Builder at exit.
Click Finish.
19
On the Stack Builder Welcome screen, use the dropdown list to select the version of postgres you have just installed, and click Next to continue.
The next screen allows you to select the applications you want to install. Select Categories > Database Drivers, and then select the psqlODBC
driver. Click Next to continue.
20
On the next screen, ensure that the ODBC driver is listed in the Selected packages list. Choose a directory to which you want to download your
selected application, if required (the default download location should not need to be changed). Click Next to download the installation file.
Note: Internet connectivity is required for a successful download.
Once the installation file has been successfully downloaded, the application can be installed. Click Next to begin the installation of the ODBC
driver.
21
The Setup psqlODBC screen appears. Click Next to continue.
On the Installation Directory screen, specify the location in which you want to install psqlODBC.
22
On the Ready to Install screen, click Next to begin the installation of psqlODBC.
On the Completed the psqlODBC Setup Wizard screen, click Finish to exit the wizard.
23
On the Stack Builder Installation Completed screen, click Finish to exit the wizard.
PostgreSQL and Stack Builder have now been installed on your system, and you are ready to continue with the Netmail Archive installation.
Note: If the installation of PostgreSQL failed, this is typically due to a Windows file system rights issue and/or a user rights
issue. Confirm that both have the required rights before you proceed with the install.
If, during the installation of PostgreSQL, the creation of the Postgres database failed, refer to Appendix A - Rebuilding the
PostgreSQL Database for information on how to manually rebuild your Postgres database.
The Messaging Server screen allows you to select which type of messaging server you are using with your Netmail Archive system.
24
1. On the Messaging Server screen under Novell GroupWise, select the default connectivity method Netmail Archive should use to communicate
with GroupWise based on the version of GroupWise you are running.
Note: It is possible to switch between SOAP API and Object API after installation through the Netmail Administration Console. At
this stage, you are choosing the recommended method based on your GroupWise version.
Choose from the available options:
Version 7.02 or higher (SOAP API) with SSL disabled: The GroupWise SOAP API provides access to GroupWise Post Office Agents
via the SOAP protocol. The Post Office Agents in your GroupWise system must be enabled for SOAP connection in order to use this
method.
Version 7.02 or higher (SOAP API) with SSL enabled: Choose this option for SOAP API with SSL enabled. Your choice can be
changed after installation on the Netmail Administration Console.
Version 7.02 or lower (Object API): The GroupWise Object API is used to provide connectivity to GroupWise systems at version 7.02 or
below, where SOAP access is not available.
Note: To access and use GroupWise Object API, you must have a 32-bit version of GroupWise Client installed on the server.
2. Select Enable stubbing if you would like to use Netmail Archive’s stubbing functionality.
Important: Stubbing is available for GroupWise 8 (and for Exchange). For GroupWise 8 environments, the SOAP API is strongly
recommended and is also required for stubbing functionality. For GroupWise 7 environments, there is little difference between
SOAP and Object API. While SOAP may be the safer choice as it will be the GroupWise connection method of choice in future
versions of Netmail Archive, it is recommended that the GroupWise client always be installed as a fallback to Object API.
The GroupWise Connectivity Parameters screen allows you to specify GroupWise Access Information.
25
The Trusted Application feature allows specific applications to log in to any GroupWise account without using a password. Create a new Trusted
Application for Netmail Archive using Novell ConsoleOne with the GroupWise snap-ins and copy the trusted application key from the resulting file
for use in this dialog.
1. On the GroupWise Connectivity Parameters screen, select the Import an existing Trusted Application Key option, and then paste the
Trusted Application key value into the Trusted Application Key field.
2. Under Trusted Application Name, enter the name of the application, such as Archive or NetmailArchive.
3. Under POA IP Address, specify the IP address of the Post Office Agent. If you have multiple Post Office Agents, choose a local Post Office
Agent and specify its IP address.
4. By default, the Port of the GroupWise Client is 1677, however, if this port is unavailable you can change the default port number.
5. Specify the Internal Client/Server Port number which this POA is configured to use. The default port number is 1677, however, check the
GroupWise configuration to confirm.
6. Specify the Internal SOAP Port number this POA is configured to use. The default port number is 7191, however, check the GroupWise
configuration to confirm.
7. Under GroupWise Account (dedicated for Netmail Archive), enter the name of a GroupWise account. This is the Netmail Archive account
created in GroupWise as part of the preprequisites prior to installation. See “Administrator Rights and Accounts” for more details.
8. Select Perform Validation if you want the installation program to validate the information provided.
The LDAP Server Connectivity Parameters screen lets you configure how Netmail Archive will access the directory via the LDAP protocol.
26
1. Under LDAP Server Host Name/IP Address, enter the host name or IP Address of a local eDirectory LDAP Server.
2. Select SSL if you require a secure (SSL) connection between Netmail Archive and the eDirectory tree. If you choose for SSL to be enabled, the
default Port Number is 636. If you choose for SSL to be disabled, the default Port Number is 389. However, if your LDAP server is configured to
listen on a different port, you can change the default port number.
3. Under Administrator Common Name, specify the account name with administrator rights to the eDirectory section where the Netmail Archive
configuration it is to be stored. This is the account that was created as part of the prerequisites prior to installation. See “Administrator Rights and
Accounts” for details.
4. Under Administrator Password, specify the password used to access the account.
Note: You can later use this Administrator Name and Password combination to log in to the Netmail Administration Console.
However, for auditing purposes, it is better to add specific administrators of Netmail Archive through Novell’s ConsoleOne. For
more information on adding administrators, refer to the Netmail Archive Administration Guide.
5. Under eDirectory Configuration Container, specify the path where you want to create and store the Netmail Archive objects in eDirectory
using the syntax illustrated in the example.
The Service Logon Information screen allows you to specify which account you want to use to start Netmail Archive services. In order to start
Netmail Archive services you must have Administrator privileges.
27
1. On the Service Logon Information screen, enter the user account you want to use to start Netmail Archive services. User accounts must be
specified using the following syntax: DOMAIN\username. Click Browse to browse to the location.
Tip: To avoid any problems creating files on the server, the account used should ideally be part of the Local Administrators group
on the server. Also, it may be necessary to grant this user file rights to GroupWise Native Archive locations if you plan on
importing Native Archives, or to Export locations if you are going to export data to file system paths. Furthermore, it is typically
recommended that all Archive and Index servers be in the same Windows Domain, and that a dedicated domain account for
Netmail Archive is created for use with this service account.
2. Under Password, enter the password used to access the account.
Tip: If there is no domain controller to authenticate against, you must authenticate locally using the following syntax: .\username.
The Logging Database Configuration and Notification Setting screen allows you to select a database and specify where Netmail Archive will
store logging information.
28
1. If you have installed PostgreSQL, the default Database is PostgreSQL. However, if you do not want to use this database, select which
database you want to use from the available options:
MySQL
MSSQL (2005/Express)
MSSQL (2000/MSDE)
Other
Important: If you are using the PostgreSQL database, the information you enter on the Logging Database Configuration and
Notification Setting screen should match the information that you entered during the installation of PostgreSQL. For instance,
your user name should be postgres and your password should match what was entered during the installation of PostgreSQL.
For more information about installing the PostgreSQL database, see “Installing PostgreSQL”.
2. Under Server name, enter the IP address or host name of your database server (this server, if you installed PostgreSQL).
3. Under Database name, ensure you have the name netmailarchive entered.
4. Under User name, ensure postgres is entered if you are using PostgreSQL, or a valid database user account for connecting to your other
database system.
Note: The user name is case sensitive.
5. Under Password, enter the database user’s password (as entered earlier, if using PostgreSQL).
6. Under Port, ensure your database ODBC connection port is specified (for PostgreSQL, this is the port specified earlier, which is 5432 by
default).
7. Once those settings are entered, click Apply to update the ODBC Connection String in the text box below. If you are using a non-PostgreSQL
database, you may need to verify that the connection string is correct and customize it if necessary.
Note: Make sure you click Apply to update the connection string and create the database tables before clicking Next.
Tip: To avoid the PostgreSQL service account password expiring, it is recommended that you adjust the postgres Windows user
account configuration in the Microsoft Management Console to disable password expiration.
The Enter Values screen is pre-populated with the Netmail Archive WebAdmin URL and the port numbers on which the Netmail Unified UI will
operate. This information does not need to be changed. Click Next to continue.
29
On the Ready to Install screen, click Install to begin the installation.
The installation wizard will now copy the required files to your server and create the Netmail Archive configuration objects in eDirectory.
Command windows will open as the eDirectory schema is being extended and as the eDirectory objects are being created.
On the Wizard Complete screen, click Finish to complete the installation of the Netmail Archive Master node.
30
Note: Because Windows sometimes keeps certain components locked, you may be prompted to restart the server at the end of
the installation sequence. If no other components are to be installed on the node, you can proceed with the restart. Otherwise, it
may be more efficient to wait until all installation tasks have been performed before restarting the machine.
Post-Installation Tasks for GroupWise
After installing Netmail Archive in a GroupWise environment, you must complete the following steps before creating, applying, and deploying
archive policies.
Netmail Archive Licensing
Before you can begin using Netmail Archive, you must have a valid Netmail Archive license file. You will need to manually add the license file to
the appropriate directory. If you installed Netmail Archive in its default installation location, place the license file in the C:\Program Files\Messagin
g Architects directory on the Master node. Otherwise, place the license file in the directory in which you installed Netmail Archive. To activate the
license, you must restart several services from the Windows Start Menu. For more information, see “Start Netmail Archive Services”.
Note: You should also copy the license file to the same folder on any Worker nodes that you will subsequently install, as some of
these may take over the Master role in the case of a server failure.
Important: If you do not restart the services, Netmail Archive will add the MALicense Checker Trigger to its list of tasks, but may
not process the license right away.
If you want to verify that your license has been updated, log in to the Netmail Administration Console using the procedure detailed below, and
expand the left-hand folder view to select the Archive > Clusters > <Cluster Name> > Agents > Archive object, as shown in the figure below. A
license count for the Archive Agent should now appear on the License tab. This license count should match the license count in your file.
31
Important: The MALic.xml file has a digital signature applied to it, so if you attempt to edit the file, the license will be invalid.
How to Count Licenses
Licensing in Netmail Archive controls the maximum number of accounts against which the various Agents can run jobs. Licence usage by a
Netmail Archive agent is defined as the number of accounts currently allocated to jobs for that agent. When this count is being calculated, it is
important to keep two aspects in mind:
Any single mail account will be counted only once for the usage figure of an agent, even if the mail account is currently allocated to
multiple jobs for that agent.
Any distribution lists/groups being used in job user lists will be expanded to the current membership, and the individual mailboxes will be
counted as if listed themselves. Note that the current membership as known by Netmail Archive will be based on the membership at the
time of the last Address Book Sync execution.
Any agent for which the current usage count exceeds the licensed count will not execute any jobs until the license infringement has been rectified.
Note the following important points:
The Netmail Archive license count does not need to match the number of accounts in the mail system, since it only applies to the
accounts allocated to Netmail Archive jobs. The Netmail Archive administrator is at liberty to decide which accounts are to be processed
and may not need to archive all mail system accounts.
Licenses are not applied to archived data. That is, if an email account has been archived and deactivated and no future ILM jobs are
required to run on that account's archived data, then a license is not required for that account, as it will not be allocated to any jobs.
For systems with large user turnovers, it is likely that the ILM and Index Agent license counts will need to be higher, as these agents act
on archived mail accounts, not live mail system accounts. With specific storage systems such as Netmail Store, where a specified data
retention period is part of the storage system properties, there is no need to run an ILM Deletion Job on the data at the end of the
retention period. The deletion job is performed automatically by the storage system.
There are no license limitations on eDiscovery operations against archived data. You can perform eDiscovery on any archived data
without requiring a license.
After completing the Netmail Archive installation, you must start Netmail Archive Services. During the installation program, a shortcut was created
for you in the Windows Start menu. To use the shortcut, choose Start > All Programs > Netmail Archive > Start Netmail Archive Services.
To start these services manually:
32
1. Choose Control Panel > Administrative Tools > Services from the Windows Start menu.
2. Double-click Services to open the Services dialog box.
3. Locate the Netmail Open service in the list of Services, and click Start.
4. Locate and right-click the Netmail Administration Console service in the list of Services, and select Start.
Tip: When Netmail Open is subsequently started or stopped after this first post-install startup, it will auto-start or auto-stop both
the Netmail Administration Console and ThreadPool services. For the first startup, however, Netmail Administration Console nee
ds to be started manually.
Note: Before starting Netmail Archive Services, ensure that the account which services are using has the “log on as a service”
permission enabled in Windows.
Launch the Administration Console and Log In
The Netmail Administration Console is a web-based application that allows administrators to configure Netmail Archive, create policies, and run
jobs.
To launch the Netmail Administration Console, open a standard web browser and enter the IP address of the server where you installed Netmail
Archive, followed by the port number specified during the Unified UI installation (e.g., http://192.168.1.123:8989). The console can be accessed
from any workstation with access to the IP address and port number.
On the Netmail Administration Console login screen, enter your User Name and Password, and click Login. The username and password
requested are those of an eDirectory user with full rights to the container holding the Netmail Archive configuration objects. By default, this is the
dedicated eDirectory user that you created before installation. The username is entered in the following format: username.container.org (e.g.,
nmarchive.archive.myorg).
Note: For more information about logging in to the Netmail Archive Administration Console, refer to the Netmail Archive
Administration Guide.
Confirm Connectivity to GroupWise
In ongoing normal operation, the Address Book Sync job is executed automatically by Netmail Archive in order to read GroupWise user
information into the Netmail Archive system. This allows GroupWise accounts to be allocated to archive jobs, for example. You can run this job
manually now in order to confirm connectivity to the GroupWise system. In the Netmail Administration Console, select the Archive > Clusters > <
Cluster Name> object in the tree. By default, the Configuration tab is displayed. Click the Address Book Sync tab to specify your Address
Book cache settings.
33
To execute the address book sync job and confirm that it has connected correctly to GroupWise:
1. Under Address Book Cache, click Run Now to start the address book sync job immediately.
2. Choose the Archive object in the tree menu on the left-hand side of the Netmail Administration Console, and then click the Monitor tab. The M
onitor tab tracks the jobs currently being processed. Expand the entry for the cluster node and a SyncAB Trigger should appear in the Running
Job ID column. You can monitor the status of the job and the elapsed time of the job.
3. When the job has completed, GroupWise user and Post Office information should have been read into Netmail Archive. To confirm that Post
Office information has been read, navigate to the Archive > Clusters > <Cluster Name> object in the tree, and select the P.O. tab.
Note: For more information about updating your address book cache, refer to the Netmail Archive Administration Guide.
Now that you have successfully installed the Netmail Archive Master node, policy-based retention is now possible. However, to perform
eDiscovery and email lifecycle management, you will need to install additional components, namely the Index Server and Remote Provider. The
installation of these two components is covered in subsequent sections.
34
Indexing Node(s)
After installing the Netmail Archive Master node, you are ready to deploy your first Index Server, which is responsible for indexing and search
functionality. Netmail Archive’s Index Server provides organizations with the means for the archive viewer interfaces, including Netmail Search, to
access and search the archived data. Through a web-based administration console, the Index Server also offers search engine monitoring,
system information, and administration.
Installing your Index Server
System Requirements
Meet Hardware and Software Requirements
Verify .NET Framework 4.0 is installed
Install three versions of Microsoft Visual C++
Redistributable
Index Server Installation
Install the Index Server
Post-Installation Tasks
Index Conversion
Server Requirements
The Index Server must be installed on a separate server than the Netmail Archive Master Node (archive server). Messaging Architects requires
that you install the Index Server on a 64-bit operating system in a production environment. Installing the Index Server on a 32-bit operating system
may degrade performance. Windows 2008 R2 Enterprise Edition 64-bit is the current recommendation, however, you can view the latest
requirements here.
In order to ensure a successful deployment of your Index Server, there are certain things you must do to prepare your system before installing
the Index Server.
.NET Framework
Verify that Microsoft .NET Framework version 4.0 is installed and enabled. To verify that Microsoft .NET Framework is installed, navigate to the
Control Panel and launch the Add and Remove Programs function. In the list of currently installed programs, look for Microsoft .NET Framework
4.0. If Microsoft .NET Framework version 4.0 is not installed, the program is available for download from www.microsoft.com.
Note: If using Windows Server 2008 R2, you can verify that Microsoft .NET Framework is installed through the Server Manager.
To do so, click Start > Administrative Tools > Server Manager. In the Server Manager interface, click Features, and verify that
.NET Framework 4.0 is listed in the right-hand pane.
Install Microsoft Visual C++ 2005 SP1 Redistributable Package (x64)
Verify that the following three versions of Microsoft Visual C++ are installed on the server or servers on which you will be installing the Index
Server:
Microsoft Visual C++ 2005 SP1 Redistributable ATL 32-bit AND 64-bit
These versions can be downloaded here: http://www.microsoft.com/download/en/details.aspx?id=14431.
Microsoft Visual C++ 2008 SP1 Redistributable ATL 64-bit.
35
This version can be downloaded here: http://www.microsoft.com/download/en/details.aspx?id=11895.
Installing the Index Server
Copy the Netmail Indexing files from the Netmail Archive distribution to the server on which you are installing your Index Server, and then run the
setup.exe file. The installation wizard will guide you through the installation process.
Important: The Index Server must be installed on a 64-bit operating system in a production environment. Only a 64-bit setup.exe
file is provided for installation.
On the Welcome screen, click Next to continue.
On the Netmail Indexing Path screen, install the Index Server in the default destination folder, or browse to the location where you want to install
the Index Server. Click Next to continue.
The Netmail Indexing Data Path screen requires you to indicate the path where your indexes will be stored. It is recommended that you keep the
default Netmail Indexing/Cloudview folder name, but you must ensure that you change the drive to your chosen index storage volume. Once you
have done this, click Next to continue.
36
On the Select Node Type and enter your Exalead server screen, specify if you are installing a Master or Slave Index server.
1. Select Master if you are installing the Master Index server, or select Slave if you are installing a Slave Index server.
Note: The first index server to be installed must be set as the Master server. Any subsequent servers installed must be set as Sl
ave servers.
2. If you are installing the Master Index server, specify the IP address of the server where the Master Index server is being installed, as well as
the Base Port and Gateway Port. Unless unavailable, use the default Base port 10000 and the default Gateway port 10011.
If you are installing a Slave Index server, specify the existing Master Index server settings as well as the IP address of the Slave host being
installed.
Click Next to continue.
On the Ready to Install the Program screen, click Install to begin the installation.
37
The installation phase can take several minutes to complete. Towards the end of the installation process, a command window opens, followed by
a message that reminds you to run the Cluster Manager to complete the installation process. Click OK.
On the Wizard Completed screen, click Finish to exit the installation wizard.
After completing the installation of the Index Server, you must start the Index Service.
To start the Index Service:
38
3. Locate the Netmail Indexing (CloudView) service in the list of Services, and click Start.
Important: Do not start the Index Service on a newly installed Slave server until you have run the Cluster Manager tool to
register the Slave with the Master server and configured slice numbers for the Slaver server.
The Cluster Manager tool can be run from any location, but it is most easily run on the Master Index server. The ExaleadClusterManager.exe file
can be found in C:\Program Files\Netmail Indexing\Netmail Archive Tools.
The Cluster Manager tool has two uses:
1. In the case of a new deployment, the tool is used to establish a new Index Server cluster, register all Slave servers and configure slice counts
for all the servers, and apply the settings. To deploy a new Index Server cluster, see “Deploying a New Index Server Cluster”.
2. In the case of an existing Index Server cluster, the tool is used to register a new Slave server to the Index Server cluster and to set the slice
count for that new server. To add a Slave server to an existing Index Server cluster, see “Adding a Slave Server to an Existing Index Server
Cluster”.
Note: Generally, when using the Cluster Manager tool, all configuration should be done through the Master server, and Slave
servers should be registered and have their slice counts configured before they are installed.
A few definitions:
Build Group: A logical component containing an index and a logical collection of Index Server components containing all the processors
and resources needed to accept and analyze documents and to build the index. In Netmail archive there are two core build groups: bg0 f
or the archive items, and bgAudits for the audit files. In addition, for systems being upgraded from M+Archive, a third build group named
bg_4_6 is used to handle converted indexes from the previous version of the Index Server.
Index Slices: A segmentation of the index to facilitate index distribution and load balancing. Within a server, a build group is split into
slices to optimize performance based on the number of processor cores in the server. Indexes are also sliced to allow for distribution
across servers.
Deploying a New Index Server Cluster
39
A new Index Server cluster is deployed when a new installation of Netmail Archive is carried out. All Index Server deployments have a single
Master server. As the need arises for additional capacity, Slave servers are added to the cluster and registered with the Master server. These
Slave servers are configured with additional slices for each build group and thus extend the distribution of the index system. The Master server is
then responsible distributing the indexing load across all servers in the cluster (including itself) and will aim to balance the indexes evenly across
the available servers.
Note: Prior to deploying a new Index Server cluster, you should establish the number of Index Servers you are going to deploy.
This can be done by following the Index Server sizing guidelines.
To configure your new Index Server cluster, follow these steps:
1. Locate and double-click the ExaleadClusterManager.exe file. The Exalead Cluster Manager dialog box opens.
2. Enter the IP address, Base port and Gateway port numbers of the Master server.
3. Click Connect. After a few seconds, a list of installed index hosts appears under Hosts. Initially, this list will only contain the Master server.
You need to register each of the planned Slave servers in order to add them to this list.
Note: If you are implementing a single Index Server, you can skip this registration process and proceed directly to step 5.
40
4. Under Slave, enter the New Host IP address and Base Port number (the default port number is 10000) of a new Slave server you want to
register, and then click Add Host. Repeat this process for all of your Slave servers. Each time you add a new Slave server, it will be added to the
list of Index Servers under Hosts.
Note: There is no need to predict future Slave server needs; you need only register those Slave servers that you are configuring
now as part of the initial deployment.
5. Once you have registered all of your Slave servers, you need to configure the slice numbers for the Master server and each Slave server. To
do so, under Hosts, select the first server in the list, and then click Configure.
41
6. The Slices Configuration dialog box opens. Under Host Parameters, enter the number of processor cores on this host server, and click Eval
uate. The two text fields under Slicesconfiguration are then automatically populated with the recommended slice counts. Note that for the server
on which you are running the Cluster Manager tool, the number of processor cores is automatically detected.
7. Click OK. A message confirming the slice numbers that will be applied appears. Click Yes to proceed. The Cluster Manager tool then makes
the appropriate configuration changes to the Index Server.
42
8. Once the configuration is complete, click OK to dismiss the message confirming that the configuration was a success.
9. Repeat steps 5 through 8 to configure the slice numbers for each of the other hosts (i.e., Slave servers).
10. Once the slice numbers have been configured for all hosts, click Apply to commit the changes to the Master server. A message confirming
that the configuration was a success appears. The message also displays the new Index Server configuration version number. Click OK to
dismiss the message.
11. It is also necessary to install some updates to the Netmail Indexing administrative interface to allow the Index Servers to be managed from the
Netmail Administration Console. To perform this install, click Install/Upgrade in the Cluster Manager window.
12. A popup informing you that the Indexing service needs to stop appears. Click Yes to continue.
13. When the install is complete, another popup appears to inform you of this and that the Indexing service has been restarted. Click OK to return
to the Cluster Manager window, and then click Close to exit the Cluster Manager tool.
43
Adding a Slave Server to an Existing Index Server Cluster
It may become necessary to extend the Index Server cluster to provide additional indexing capacity. Adding a new Index server is a very simple
process. The Cluster Manager tool is used to register the server and to configure the slice numbers for it. The new Slave server is then installed
and started up.
To add a Slave server to an existing cluster, follow these steps:
1. Locate and double-click the ExaleadClusterManager.exe file. The Exalead Cluster Manager dialog box opens.
2. Enter the IP address, Base port and Gateway port numbers of the Master server.
3. Click Connect. After a few seconds, a list of installed index hosts appears under Hosts.
44
4. Under Slave, enter the New Host IP address and Base Port number (the default port number is 10000) of a new Slave server you want to
register, and then click Add Host. Your new Slave server appears in the list of Index Servers under Hosts.
5. Once you have registered your Slave server, you need to configure the slice numbers for it. To do so, under Hosts, select the new Slave server
in the list, and then click Configure.
45
6. The Slices Configuration dialog box opens. Under Host Parameters, enter the number of processor cores on this host server, and click Eval
uate. The two text fields under Slicesconfiguration are then automatically populated with the recommended slice counts.
7. Click OK. A message confirming the slice numbers that will be applied appears. Click Yes to proceed. The Cluster Manager tool then makes
the appropriate configuration changes to the Slave server.
46
8. Once the configuration is complete, click OK to dismiss the message confirming that the configuration was a success.
9. Once the slice numbers have been configured, click Apply to commit the changes to the Master server. A message confirming that the
configuration was a success appears. The message also displays the new Index Server configuration version number. Click OK to dismiss the
message, and then click Close to exit the Cluster Manager.
10. Restart the Index Service on the Master server.
Configure Archive Server to Index Server Communications
Once your Index server(s) are installed, you now need to configure Netmail Archive to enable communications between the Archive node(s) and
the Index server(s).
47
Netmail Administration Console Settings
Open your web browser, and log in to the Netmail Administration Console. Navigate to the Archive > Clusters > Cluster > <Cluster Name> obje
ct and to the Configuration tab, as shown in the figure below.
Under the Index Servers header, complete the following:
1. Under Host, enter the IP address of your Master Index server.
2. Under Base port, enter the base port you specified during installation of your Master Index server. By default, the port number is 10000.
3. Under Gateway port, enter the gateway port of your Master Index server that you specified during installation. By default, the port number is
10011.
4. Under Document Cap, specify the maximum number of documents the Master Index server should index before it is considered at full
capacity. The default value of 50 million documents should be used unless you have been advised otherwise by Messaging Architects. As Index
servers near their caps, additional index capacity can be easily obtained by adding additional Slave Index servers.
5. Under Index nodes, use the Add button to register details of any Slave Index servers which you have already installed. If at any point in the
future you add a Slave Index server, you must return to the Netmail Archive Administration Console to register the new Slave.
6. Click Saveat the bottom of the screen to save the modified configuration.
Proxy Exception Settings on Archive Servers
The Netmail Archive system uses HTTP communication between archive servers and index servers. To avoid degraded performance, it is
preferable that your Master and Worker archive nodes do not use proxy settings to communicate with the Index Server(s). Rather, they should
communicate directly to the Index Server(s). As such, you must add proxy exceptions for each of the Index Server IP addresses to the Internet
settings on your Master and Worker archive nodes.
Note: This process is only required if you currently have a proxy configured on your archive nodes.
Windows proxy configuration is carried out via Internet Explorer.
To add a proxy exclusion in Internet Explorer:
1. In the top toolbar of the Internet Explorer screen, navigate to Tools > Internet Options.
2. In the Internet Select the Connections tab.
48
3. Select LAN settings.
4. In the LAN Settings dialog box that appears, select Use a proxy server for your LAN.
5. Click Advanced.
6. In the Proxy Settings dialog box that appears, enter the requested proxy IP addresses and port information.
7. In the Exceptions section, under Do not use proxy server for addresses beginning with, enter the IP address of your Index Server(s).
8. Click OK to close the Proxy Settings dialog box.
9. Click OK to close the LAN Settings dialog box.
10. Click OK to close the Internet Options dialog box.
Index Conversion
For organizations upgrading an existing M+Archive system to Netmail Archive, there will be existing indexes from the previous version of the
Index Server (Exalead 4.6). These indexes must be converted to the new Index Server (Exalead CloudView) format if they are to be used by the
Netmail Archive viewers.
The Cluster Manager tool and a dedicated Messaging Architects conversion tool are used when converting Exalead 4.6 indexes to CloudView
indexes. Together, these tools complete several key tasks:
Creation of a slice within the bg0 build group for each 4.6 instance being converted
Copying of the index files from the 4.6 instance folder to the appropriate slice folder under the CloudView directory structure
Conversion of the 4.6 index files to CloudView format
The end result is the default build group, bg0, with one slice per 4.6 instance, each of which contains the converted indexes from the
corresponding instance. In order to use these converted indexes, you will also need to carry out a corresponding upgrade of the Archive and
Remote Provider software to Netmail 5.x version, and ensuring that the archive repository names are exactly the same as those on the M+Archive
system.
Preparing for the Conversion
The recommended approach to index conversion is to install CloudView (the indexing version included in Netmail Archive) on top of each existing
Exalead 4.6 server. The software installs to different directories by default and can co-exist quite happily, although only one index system should
have its services running at any time to avoid port conflicts.
Tip: The Index Server housing Exalead 4.6 instance “0” typically becomes the CloudView Master server in an upgrade scenario.
Any additional 4.6 servers become CloudView Slave servers. Before shutting down 4.6 to start the conversion, take note of the
counts from each 4.6 instance. These can be compared to the results of the conversion process. Ensure that no updates are mad
e to the 4.6 instances (data or audit) after you note the counts.
Once CloudView is installed on the Exalead 4.6 servers, complete the following preparatory steps:
1. Stop the Exalead 4.6 Services on all Index servers.
2. Start the Netmail Indexing Service on the Master Index server.
3. Run through the process of registering Slave servers and configuring slice numbers with the Cluster Manager tool, as described in “Adding a
Slave Server to an Existing Index Server Cluster”. Ensure that you configure slice numbers for the Master Index server as well.
When you are configuring the slice numbers, be sure to adjust the numbers to include the converted instances as part of the slice count. To do so,
in the Slices Configuration dialog box, next to Number of 4.6 Instances to be Added to the Host, indicate the number of Exalead 4.6
instances that exist on each server for the host in question. Do this for each individual host. This will create the slices that will house the converted
indexes.
49
4.Once all Slave servers have been registered and slice counts configured, restart the Master Netmail Indexing Service.
Running the Index Conversion Tool
Now that you have prepared the Index Server for conversion, the index conversion can be carried out using Messaging Architects’ Index
Conversion tool.
To run the tool, double-click the IndexConversionTool.exe file located in C:\Program Files\Netmail Indexing\Netmail Archive Tools.
1. On the Prerequisites screen, verify and confirm that you meet all the requirements for index conversion. Click Next to continue.
2. On the Specify the locations screen, complete the following:
Use the Browse buttons to select the appropriate paths to the Exalead 4.6 and CloudView index stores.
Specify the Master Server IP address and Base port number.
Ignore Use Slave Server option as this has been deprecated after Netmail 5.1.1.
50
3. The Select Index Instances to Convert screen lists the Exalead 4.6 instances that have been found on the server at the specified path. Select
the instances that you want to convert (normally all instances are selected). They will be processed sequentially.
The default processing method is Copy, which leaves the 4.6 instances untouched. If, however, you have a limited amount of space on the
indexing volume, you may need to change this to the Move method.
Important: Move should only be used if a confirmed backup of the current state of the 4.6 instances exists.
When ready, click Next to continue. A warning window appears, indicating this is the first run of the conversion tool and that any previously
converted index data residing on this server will be deleted. Click Yes to continue.
51
The conversion process now begins. The Index Conversion Tool dialog box appears, indicating that conversion is being initialized.
Once the conversion process has been initialized, the first Exalead 4.6 instance is checked prior to being converted. The Index Conversion Tool
dialog box displays this in the Conversion Log field.
Once checking is complete, the index data files for this first instance are copied from the 4.6 instance to the slice directory within the CloudView
system, as indicated in the Conversion Log.
Once the copying is complete, the files are then converted into Netmail Archive index format.
52
Towards the end of this process, a command window opens as the index dictionaries are being generated.
Once conversion is complete, it is indicated in the Conversion Log.
If you are converting multiple 4.6 instances, the process is now repeated for the next instance.
53
4. When all instances have been processed, an “Index conversion is done” message is displayed in the Conversion Log, and a popup reminding
you to restart the Netmail Indexing service is displayed. Click OK to dismiss the popup, and then click Finish to exit the Index Conversion tool.
Restart the Netmail Indexing service on the server.
Using the Index Server Administration Console
The Index Server component of Netmail Archive is designed to simplify information search and retrieval for organizations of all sizes. The Index
Server requires minimal additional administration. However, if you need to log in to the Index Server’s Administration Console to fine-tune or
troubleshoot the Index Server, you can access the console by opening a standard web browser and entering the IP address of the server where
you installed the Index Server, followed by the search port of 10001. For example, http://192.168.1.123:10001. The interface can be accessed
from any workstation with access to this IP address and port number. Use the administrator credentials (user name and password) you specified
during installation of the Index Server.
54
Netmail Archive Worker Node(s)
After you have installed the Netmail Archive Master archive node and Index Server, you can install additional Worker archive nodes.
In this section:
Installation sequence for Netmail Archive 5.2
Run the Netmail Archive Installation Wizard
Copy the Netmail Archive distribution files to your proposed Worker node server, and then locate and run the setup.exe file located in the Netmail
Archive directory of the distribution. The installation program will guide you through the installation process. Follow the onscreen instructions to
install Netmail Archive Worker node(s) ina GroupWise environment.
On the Netmail Archive Welcome screen, click Next to proceed.
On the License Agreement screen, carefully review the software license agreement, and then click I accept the terms of the license
agreement to accept the License Agreement. Click Next to continue.
55
On the Choose Destination Location screen, install Netmail Archive in the default destination folder, or browse to the location where you want to
install Netmail Archive. Click Next to continue.
Important: Netmail Archive does not support installing the Netmail Archive software from a USB key. Instead, you should copy
the Netmail Archive installation files to the server on which you will be installing Netmail Archive.
The Cluster Configuration screen is displayed.
56
1. On the Cluster Configuration screen, select the Install Worker Node option. Installing Netmail Archive on a second server will increase the
scalability and processing power of your Netmail Archive system.
Note: The first Archive server installed within a deployment should be the Master node. If additional Archive servers are required,
these will be installed subsequently as Worker nodes. For more information on installing the Master node, see "Installing the
Netmail Archive Master Node in a GroupWise Environment".
2. Under Master Configuration, enter the IP Address of the computer where you installed the Netmail Archive Master node.
Note: If your server has multiple IP addresses (e.g., in the case where you are using iSCSI NICS as well as LAN NICS, then
ensure that you enter the correct IP address for Netmail Archive communication (i.e., the LAN IP address).
Under Port, enter the port number of the Master node. Use the default port number 8585 (or the port number you used to install the Master node,
if you opted not to use the default port).
3. Under Worker Configuration, enter the IP Address of the computer where you are installing the Netmail Archive Worker node.
Note: If your server has multiple IP addresses (e.g., in the case where you are using iSCSI NICS as well as LAN NICS, then
ensure that you enter the correct IP address for Netmail Archive communication (i.e., the LAN IP address).
The Port field specifies the port number that this node will use for Netmail Archive cluster communications. By default, the port number is 8585. It
should be unnecessary to change this, as Netmail Archive should be installed on a dedicated server. However, you can change the default port
number based on which ports are currently in use and your network security requirements.
The Service Logon Information screen allows you to specify which account you want to use to start Netmail Archive Services. In order to start
Netmail Archive services, the specified account must have local Administrator privileges on the server.
57
1. On the Service Logon Information screen, enter the user account you want to use to start Netmail Archive services. User accounts must be
specified using the following syntax: DOMAIN\username. Click Browse to browse to the location.
Tip: To avoid any problems creating files on the server, the account used should ideally be part of the Local Administrators group
on the server. Also, it may be necessary to grant this user file rights to GroupWise Native Archive locations if you plan on
importing Native Archives, or to Export locations if you are going to export data to file system paths. Furthermore, it is typically
recommended that all Archive and Index servers be in the same Windows Domain, and that a dedicated domain account for
Netmail Archive is created for use with this service account.
2. Under Password, enter the password used to access the account.
Tip: If there is no domain controller to authenticate against, you must authenticate locally using the following syntax: .\username.
The Enter Values screen is pre-populated with the Netmail Archive WebAdmin URL and the port numbers on which the Netmail Unified UI will
operate. This information does not need to be changed. Click Next to continue.
58
Once the installation is complete, click Finish on the Wizard Complete screen to exit the installation wizard.
Install PostgreSQL on the Worker Node
Once the installation of the Worker node is complete, you need to install the PostgreSQL ODBC driver on the Worker node to allow it to connect
to the logging database you installed on the Master node. To do so, locate and run the edb_psqlodbc.exe file located in C:\Program files (x86)\Me
ssaging Architects\PGInstall.
The Setup psqlODBC screen appears. Click Next to continue.
59
On the Installation Directory screen, specify the location in which you want to install psqlODBC. Typically, the default path is used.
On the Ready to Install screen, click Next to begin the installation of psqlODBC.
60
On the Completed the psqlODBC Setup Wizard screen, click Finish to exit the wizard.
The PostgreSQL ODBC driver has now been installed on your system.
Once you have installed your Worker node, you must complete a few more steps before you can start using Netmail Archive to create and apply
archive policies.
After completing the Netmail Archive installation, you must start Netmail Archive Services. During the installation program, a shortcut was created
for you in the Windows Start menu. To use the shortcut, choose Start > All Programs > Netmail Archive > Start Netmail Archive Services.
61
To start these services manually:
3. Locate the Netmail Open service in the list of Services, and click Start.
Configure PostgreSQL on the Master node
If you are using the default option of PostgreSQL for your Netmail Archive logging database, then you must configure PostgreSQL on the Master
node to ensure that Worker nodes can connect correctly to the postgres database.
By default, the PostgreSQL database is configured to listen on all Master node IP addresses where the Master node was installed. You should
confirm this is still the case by checking the postgresql.conf file on the master node.
To modify the PostgreSQL configuration file:
1. Locate the postgres configuration file postgresql.conf. By default, this file is located in C:\Program Files (x86)\PostgreSQL\9.1\data on you
Master node.
2. Open the file for editing in Notepad, and navigate to the Connection Settings section.
3. Make sure that postgres is configured to listen on all interfaces. To do so, ensure that the listen_address line is not commented out with a #
symbol at the beginning of the line and that the address is set to ‘*’:
listen_address = ‘*’
Note: If you installed Netmail Archive as a Worker node and are using a database other than PostgreSQL, you should ensure
that database information can be properly exchanged between your Master and Worker nodes.
Additionally, the PostgreSQL database needs to be configured to allow connections from the Master and Worker nodes. This is configured in the
pg_hba.conf file in the same folder on the Master node.
To modify the pg_hba.conf file:
1. Open the file for editing in Notepad.
2. Towards the end of the file, add additional IPv4 connection lines for the Master node and each Worker node IP address. For example:
# TYPE DATABASE USER ADDRESS METHOD
# IPv4 local connections:
host all all 127.0.0.1/32 md5
host all all 192.168.1.126/32 md5
host all all 192.168.1.127/32 md5
Note: Rather than adding a line for each individual Worker node for which you want to allow connections, you may choose to add
a single line that allows authenticated ODBC connection from any IP address. This is done by adding a line having the following
format: host all all 0.0.0.0/0 md5
62
Install and Configure Optional WebViewer Component for GroupWise
WebAccess
The Netmail Archive WebViewer is an end-user archive viewer integrated into the GroupWise WebAccess client interface. Once logged in to
GroupWise WebAccess, users can toggle between the standard WebAccess view of their GroupWise message store and the Netmail Archive
WebViewer view of their XML archives. Maintaining the look and feel of GroupWise WebAccess, the Netmail Archive WebViewer allows users to
easily access their XML archives and live mailboxes for a seamless end-user experience. In addition, a search function is available through the
viewer for easy archive message item retrieval.
The WebViewer is comprised of two main components:
WebViewer Application: The WebViewer Application is a web server application which installs to the server currently acting as the
GroupWise WebAccess Application server (i.e., the one running the WebAccess Application component). The WebViewer Application
extends the WebAccess client interface to include an Archive button which launches the Netmail Archive WebViewer interface. The
WebViewer Application serves this interface to WebAccess client browser sessions and communicates with the Remote Provider
component in order to retrieve archived items for display in this interface.
GroupWise Remote Provider: Connection to the GroupWise Remote Provider component is established by the WebViewer application
when a user starts a WebAccess session. Provided this communication is successful, the Archive button is displayed in the WebAccess
interface. Once a user clicks the Archive button to enter the WebViewer interface, the Remote Provider acts as a gateway between the
WebViewer Application requests and the archive location(s). As a user navigates through their archive mailbox folders using the
WebViewer interface, the WebViewer Application passes requests for archived item information to the Remote Provider. The Remote
Provider communicates with the Index server(s) in order to execute queries identifying where the relevant archived items are stored. It
then fetches these items from the archive locations for provision to the WebViewer Application and subsequent display in the WebViewer
interface.
In small to medium sized environments, the WebViewer Application should be installed to your existing WebAccess Application server, and a
single Remote Provider should be installed to your Master Archive node. In larger environments, where the prospective user load warrants it, you
can install multiple WebViewer Applications, one to each WebAccess Application server in your environment, plus multiple Remote Providers,
typically on dedicated servers.
In scenarios where multiple WebAccess Application servers have been deployed due to the total user demand for WebAccess sessions, it is best
to maintain a one-to-one relationship between WebViewer Applications and Remote Providers. This means you would look to deploy as many
Remote Providers as you have WebAccess Application servers. Where multiple WebAccess Application servers have been deployed for reasons
other than user load (for example, you may have two WebAccess Application web servers, one for external access and one for internal access), it
is possible to point the WebViewer Applications on which you install the WebAccess Application servers to a single Remote Provider (i.e., you
have a many-to-one relationship of WebViewer Applications to Remote Providers).
Having multiple Remote Providers servicing a single WebViewer Application can only be achieved through the use of a network load balancer
system or such like functionality.
If you feel that your environment may warrant multiple Remote Provider servers or you already have a number of GroupWise WebAccess
Application web servers, and you require further advice on the best approach on WebViewer component distribution, please contact Messaging
Architects.
Installation of the two WebViewer components can be carried out individually or via one combined installation session. The following instructions
are based on the individual component installation method, but indicate how combined installation may be carried out.
Important: Before you install the WebViewer components, you should have a GroupWise WebAccess system already configured
and running smoothly
After you have installed and configured all the necessary components of Netmail Archive, there are a number of additional components that you
can install to enhance your archiving system.
Installing the WebViewer Application to Your Web Server
Note: These instructions apply to installation of the WebAccess Application on a NetWare or Windows GroupWise WebAccess
Application server. Please refer to "Installing the WebViewer on a Linux System" for installation to a Linux based WebAccess
Application server.
63
Note: If you install a new version of Novell WebAccess after installing the WebViewer Application, WebAccess might overwrite
the customizations that the WebViewer installation program applied to the webacc.cfg file and the files copied to the WebAccess
Application server. In this case, you should re-install the WebViewer Application.
On your workstation or server from which you are running the installation, ensure that you have a drive mapped to the GroupWise Application
server drive or a volume containing the WebAccess Application files (normally the SYS volume on NetWare or the C: drive on Windows).
Navigate to the WebViewer folder of the Netmail Archive distribution files and run the setup.exe file.
The installation program will guide you through the installation process. Follow the onscreen instructions to install the WebViewer. On the Netmail
Archive WebViewer Welcome screen, click Next to proceed.
On the GW WebAccess Configuration screen, browse to the location of the webacc.cfg file. The WebViewer installation program will
automatically write custom parameters to this file, and therefore needs to know its location.
The default location of the webacc.cfg file varies according to platform. Some examples of default locations are:
Windows: C:\Novell\Webacc\Webaccess
Netware: \\server\SYS\novell\webaccess
64
Linux: opt/novell/groupwise/webaccess
Under Path to folder with WebAccess Template files, browse to the location of the WebAccess templates folder. The default location of the
files varies according to platform.
Windows: C:\Novell\GroupWise\tomcat5.5\webapps\gw\WEB-INF\classes\templates
Netware: \\server\SYS\Tomcat\4\webapps\gw\WEB-INF\classes\templates
Under Path to folder with WebAccess Images, browse to the location of the WebAccess images folder. The default location of the image files
varies according to platform. Some examples of default locations are:
Windows: C:\Novell\GroupWise\tomcat5.5\webapps\gw\webaccess\200908180251\images
Netware: \\server\SYS\Tomcat\4\webapps\gw\webaccess\200908180251\images
Note: The number “200908180251” in the path is specific to the installation, so it will change from system to system.
If you are installing to a GroupWise 2012 WebAccess Application server, ensure to select the GroupWise 2012 checkbox.
After finding and selecting the requested folders, click Next to continue.
At this stage, the Netmail Archive WebViewer installation program asks if you would like to also use this installation session to install the Remote
Provider onto the local machine. This is the combined installation method mentioned earlier. You should only select this option if you intend to
immediately install the Remote Provider component on the machine from which you are running the WebViewer installation program. See “Installi
ng the GroupWise Remote Provider Component” for further information on the Remote Provider installation screens that will be displayed if you
select this option.
For installation of only the WebViewer Application component at this stage, on the Remote Provider and Proxy Access Configuration screen,
deselect the Install the Remote Provider on local machine checkbox.
It is still necessary to provide the configuration information in order to inform the WebViewer Application to know how to contact the Remote
Provider once it is installed:
1. Under Remote Provider Server IP, enter the IP address of the server on which you will be installing the Remote Provider.
2. Under Remote Provider Port, enter the TCP/IP port number that the Remote Provider will listen on for requests from the WebViewer.
3. Under SMTP Server IP, enter the IP address of your SMTP Server (i.e., your GroupWise GWIA server).
65
Important: The WebViewer interface allows users to Forward items out of the archive store to designated email recipients. It will
use the SMTP server specified here as an SMTP relay for sending these forwarded mails. When specifying the SMTP Relay
Server IP (typically your GWIA IP address), ensure that your mail server is configured to allow relaying from the IP address of the
Remote Provider server which you have specified here.
4. Select Enable Proxy Access to Archives if you want to enable proxy access to your archives through the WebViewer. When set, the
WebViewer will make use of GroupWise proxy permissions to allow WebAccess users who proxy into another account to also be able to access
that account’s archive mailbox.
On the Ready to Install screen, click Install to install the Netmail Archive WebViewer.
A progress screen is displayed as the required files are copied to the WebAccess Application server and the webacc.cfg file is modified. Once this
is complete, the Wizard Complete screen is displayed. Click Finish to exit the installation program.
In order to load the WebViewer Application you have just installed, it is necessary to restart the Tomcat service on your GroupWise WebAccess
Application server. The process for doing so depends on the platform you are using:
Windows: Restart the Tomcat windows service on your WebAccess Application server.
NetWare: On your server console, run tc4stop. Allow it to shut down Tomcat, and then run tomcat4 to restart Tomcat services.
66
Installing the WebViewer on a Linux System
In a GroupWise 7 environment, the WebViewer can be installed on a SLES 10 Linux system. In a GroupWise 8 environment, the WebViewer can
be installed on a SLES 10 or SLES 11 Linux system.
In a GroupWise 7 Environment
It is possible to install the WebViewer on a SLES 10 Linux system in a GroupWise 7 environment. In order to facilitate the installation process,
Messaging Architects recommends that you download WINscp, an open source SFTP Client for Windows that allows you to drag files from a
Windows system to a Linux system using an SSH connection. WINscp is available from http://www.winscp.net.
1. On the Linux system, create a GWXMLV subdirectory under var/opt/novell/gw/WEB-INF/classes/com/novell/webaccess/templates/css.
Example: /var/opt/novell/gw/WEB-INF/classes/com/novell/webaccess/templates/css/GWXMLV
2. Navigate to the WebViewer\Program Files\Messaging Architects folder in the Netmail Archive distribution, and copy the files from the
GWXMLV_css folder and the GWXMLV subdirectory you created.
3. In the ../templates/css/ folder on the Linux system, rename caption.htt to caption.htt.old. Copy the caption.htt file from WebViewer\Program
Files\Messaging Architects\GWXMLV701 folder on the Windows system to
/var/opt/novell/gw/WEB-INF/classes/com/novell/webaccess/templates/css.
4. Copy all files from the WebViewer\Program Files\Messaging Architects\WebViewer\WebAccInterface folder on the Windows system to
/var/opt/novell/gw/WEB-INF/classes/com/novell/webaccess/templates/css.
5. On the Linux system, create a GWXMLV subdirectory under /var/opt/novell/gw/WEB-INF/classes/com/novell/webaccess/providers/
Example: /var/opt/novell/gw/WEB-INF/classes/com/novell/webaccess/providers/GWXMLV
6. Copy the files from the WebViewer\Program Files\Messaging Architects\provider folder into the GWXMLV subdirectory you created.
7. On the Linux system, create a GWXMLV subdirectory under /var/opt/novell/gw/com/novell/webaccess/images.
Example: /var/opt/novell/gw/com/novell/webaccess/images/GWXMLV
8. Copy the files from the WebViewer\Program Files\Messaging Architects\WebaccImages folder in the distribution into the GWXMLV
subdirectory you created.
9. Navigate to the WebViewer\Program Files\Messaging Architects folder, and copy the gwxmlv.cfg file to the /opt/novell/groupwise/webaccess
directory on the Linux system.
10. Modify the opt/Novell/GroupWise/WebAccess/gwxmlv.cfg file by editing the following entries:
Provider.Server.IP= <IP of server running provider>
Provider.Server.Port= <Provider port (default 6666)>
11. Modify the var/Novell/GroupWise/WebAccess/webacc.cfg file by appending the following text to the end of the file:
###############################################################################
#TMA: Added for GWXML WebViewer Provider
###############################################################################
#------------------------------------------------------------------------------
67
# Specify the provider's class
#-----------------------------------------------------------------------------Provider.GWXMLV.class=com.novell.webaccess.providers.GWXMLV.GWANWP
#-----------------------------------------------------------------------------# Specify the provider's templates folder.
#-----------------------------------------------------------------------------Templates.GWXMLV.folder=GWXMLV
#-----------------------------------------------------------------------------# Specify the provider's configuration file.
#-----------------------------------------------------------------------------Provider.GWXMLV.Config.file=/opt/novell/groupwise/webaccess/gwxmlv.cfg
#-----------------------------------------------------------------------------# Specify super users. Separated by ';'
#-----------------------------------------------------------------------------Provider.GWXMLV.SuperUser.name=<user IDs of all users with superuser privileges>.
#-----------------------------------------------------------------------------# setting for proxy, value: true or false
#-----------------------------------------------------------------------------Provider.GWXMLV.Proxy.disabled=false
12. Copy the var/opt/novell/gw/WEB-INF/classes/com/novell/webaccess/templates/css/fldricon.inc file into the
var/opt/novell/gw/WEB-INF/classes/com/novell/webaccess/templates/css/GWXMLV folder.
13. After modifying the files, you must restart Tomcat services.
In a GroupWise 8 Environment
You can also install the WebViewer on a SLES 10 or SLES 11 Linux system in a GroupWise 8 environment. In order to facilitate the installation
process, Messaging Architects recommends that you download WINscp, an open source SFTP Client for Windows that allows you to drag files
from a Windows system to a Linux system using an SSH connection. WINscp is available from http://www.winscp.net.
1. On the Linux system, create a GWXMLV subdirectory:
For SLES 10, create it under /srv/www/tomcat5/base/webapps/gw/WEB-INF/classes/templates/webacc/css.
For SLES 11, create it under /srv/tomcat6/base/webapps/gw/WEB-INF/classes/templates/webacc/css.
Example for SLES 10: /srv/www/tomcat5/base/webapps/gw/WEB-INF/classes/templates/webacc/css/GWXMLV
2. Navigate to the WebViewer\Program Files\Messaging Architects folder and copy the files from the GWXMLV_css folder into the respective
GWXMLV subdirectory you created.
3. In the ../templates/css/ folder on the Linux system, rename caption.htt to caption.htt.old.
For SLES 10, copy the caption.htt file from WebViewer\Program Files\Messaging Architects\GWXMLV8 folder in the distribution to
/srv/www/tomcat5/base/webapps/gw/WEB-INF/classes/templates/webacc/css.
For SLES 11, copy the caption.htt file from WebViewer\Program Files\Messaging Architects\GWXMLV8 folder in the distribution to
/srv/tomcat6/base/webapps/gw/WEB-INF/classes/templates/webacc/css.
4. For SLES 10, copy all files from the WebViewer\Program Files\Messaging Architects\WebViewer\CSS folder in the distribution to
/srv/www/tomcat5/base/webapps/gw/WEB-INF/classes/templates/webacc/css.
For SLES 11, copy all files from the WebViewer\Program Files\Messaging Architects\WebViewer\CSS folder in the distribution to
/srv/tomcat6/base/webapps/gw/WEB-INF/classes/templates/webacc/css.
5. On the Linux system, create a GWXMLV subdirectory:
For SLES 10, create it under /srv/www/tomcat5/base/webapps/gw/WEB-INF/classes/com/novell/webaccess/providers.
For SLES 11, create it under /srv/tomcat6/base/webapps/gw/WEB-INF/classes/com/novell/webaccess/providers.
Example for SLES 10: /srv/www/tomcat5/base/webapps/gw/WEB-INF/classes/com/novell/webaccess/providers/GWXMLV
6. Copy the files from the WebViewer\Program Files\Messaging Architects\provider folder into the GWXMLV subdirectory folder you created in the
previous step.
7. On the Linux system, create a GWXMLV subdirectory in:
For SLES 10, create it under /srv/www/tomcat5/base/webapps/gw/webaccess/201010290421/images.
For SLES 11, create it under /srv/tomcat6/base/webapps/gw/webaccess/201010290421/images.
Example for SLES 10: /srv/www/tomcat5/base/webapps/gw/webaccess/201010290421/images/GWXMLV
68
Note: The number “201010290421” in the path is specific to the build of GroupWise installed. It may be different on your system,
and there may be other directories if multiple version of GroupWise 8 have been installed. You should use the most current
directory.
8. Copy the WebViewer\Program Files\Messaging Architects\WebaccImages folder in the distribution into the GWXMLV subdirectory you created.
9. Navigate to the WebViewer\Program Files\Messaging Architects folder, and copy the gwxmlv.cfg file to the /opt/novell/groupwise/webaccess
directory on the Linux system.
10. Modify the var/Novell/GroupWise/WebAccess/webacc.cfg file by appending the following text to the end of the file:
###############################################################################
#TMA: Added for GWXML WebViewer Provider
###############################################################################
#------------------------------------------------------------------------------
# Specify the provider's class
#-----------------------------------------------------------------------------Provider.GWXMLV.class=com.novell.webaccess.providers.GWXMLV.GWANWP
#-----------------------------------------------------------------------------# Specify the provider's templates folder.
#-----------------------------------------------------------------------------Templates.GWXMLV.folder=GWXMLV
#-----------------------------------------------------------------------------# Specify the provider's configuration file.
#-----------------------------------------------------------------------------Provider.GWXMLV.Config.file=/opt/novell/groupwise/webaccess/gwxmlv.cfg
#-----------------------------------------------------------------------------# Specify super users. Separated by ';'
#-----------------------------------------------------------------------------Provider.GWXMLV.SuperUser.name=<user IDs of all users with superuser privileges>.
#-----------------------------------------------------------------------------# setting for proxy, value: true or false
#-----------------------------------------------------------------------------Provider.GWXMLV.Proxy.disabled=false
11. Modify the /opt/Novell/GroupWise/WebAccess/gwxmlv.cfg file by editing the following entries.
Provider.Server.IP= <IP of server running provider>
Provider.Server.Port= <Provider port (default 6666)>
12. For SLES 10, copy the /srv/www/tomcat5/base/webapps/gw/WEB-INF/classes/templates/webacc/fldricon.inc file into the
/srv/www/tomcat5/base/webapps/gw/WEB-INF/classes/templates/webacc//css/GWXMLV folder.
For SLES 11, copy the /srv/tomcat6/base/webapps/gw/WEB-INF/classes/templates/webacc/fldricon.inc file into the
/srv/tomcat6/base/webapps/gw/WEB-INF/classes/templates/webacc/css/GWXMLV folder.
13. After modifying the files, you must restart Tomcat services.
Installing the GroupWise Remote Provider Component
As mentioned earlier, the GroupWise Remote Provider component can be installed on dedicated servers, or for smaller environments, on an
Archive node. The server chosen must have the ability to communicate with the WebAccess Application server where the WebViewer Application
has been installed, as well as with the Index server(s). In addition, it must be able to access the archive locations in order to read archived data.
The installation of the GroupWise Remote Provider is actually carried out in conjunction with another similar component, the Netmail Search
Remote Provider, which is used by the Netmail Search archive viewer utility and other Netmail Archive components in a similar way that the
WebViewer Application uses the GroupWise Remote Provider.
See “Install and Configure the Remote Provider(s) for Netmail Search” for full instructions on installing the GroupWise Remote Provider as part of
the Remote Provider installation process. The key point to note in the installation process is on the Remote Provider Configuration screen. You
must ensure that the Install GroupWise Remote Provider option is selected in order to install the GroupWise Remote Provider in addition to the
Remote Provider used by Netmail Search.
69
WebViewer Post-Installation Tasks
After completing the installation of the Netmail Archive WebViewer components, there are a few post-installation tasks for you to complete in
order for the WebViewer component to function properly.
Starting the GroupWise Remote Provider Windows Service
The GroupWise Remote Provider runs as a Windows service named Netmail Archive Remote Provider. On each server where you have
installed the GroupWise Remote Provider, you need to start this service.
1. To start services manually, choose Control Panel > Administrative Tools > Services from the Windows Start menu.
3. Locate the Netmail Remote Provider service in the list of Services, and click Start.
Configuring the Remote Provider on a Server with Multiple IP Addresses
As a gateway between the WebViewer application and the XML storage repository, the Remote Provider listens on Port 6666 for communications
from the Web server. When the server running the Remote Provider is configured with two NICs and has two different IP addresses on different
subnets (such as NAT), you need to specify which on which address the Remote Provider should listen.
1. On the Remote Provider server, open the xgwxmlv.cfg file located in C:/Program Files/Messaging Architects/Remote Provider.
2. Locate the line in the file which contains: nat.host=
3. Edit the line to include the IP address on which the Remote Provider should listen.
Example: nat.host=192.168.1.124
4. Save the changes to the xgwxmlv.cfg file, and then restart the Netmail Remote Provider service.
70
Install and Configure Optional Stubbing Agent
After successfully installing Netmail Archive in your GroupWise environment, you must install the Stubbing Agent to be able to use the stubbing
function.
Important: Stubbing is available for GroupWise 8. For GroupWise 8 environments, the SOAP API is strongly recommended and
is also required for stubbing functionality.
Installing the Stubbing Agent
The Stubbing Agent (SA) acts as a bridge between the GroupWise Post Office Agent (POA) and Netmail Archive, enabling retrieval of archived
messages directly from the GroupWise Client. The communication between the POA and the SA is based on SOAP over HTTP. The SA also
communicates with the Netmail Archive Index Server over HTTP.
To install the Stubbing Agent, navigate to the Stubbing Agent folder, and run the setup.exe file.
The installation program will guide you through the installation process. Follow the onscreen instructions to install the Stubbing Agent. On the Net
mail Archive Stubbing Agent Welcome screen, click Next to proceed.
On the Choose Destination Location screen, install the Stubbing Agent in the default destination folder, or browse to the location where you
want to install the Stubbing Agent. Click Next to continue.
71
On the Stubbing Agent Configuration screen, enter the required information:
1. Under AWA RemoteProvider IP, enter the IP address of the server on which the Remote Provider is installed.
2. Under AWA RemoteProvider Port, enter the port number on which you configured your AWA Remote Provider service to listen (8888 by
default).
3. Under Name, enter the name of the Trusted Application key.
4. Under GroupWise Trusted Application Parameters, you should enter the Name and Key of an existing GroupWise Trusted Application
entry. It is recommended that you use the same Trusted Application entry that you configured for Archive server access to GroupWise.
Tip: If you no longer have them recorded, the details of the Trusted Application key used for the Archive servers can be found by
using ConsoleOne to view the eDirectory tree in which you installed the Netmail Archive objects. To locate the details, expand
the tree, and find your Netmail Archive Configuration Container. Right-click on the GWOpenNode(Server_IP_Address) object,
and select Properties. Select the Other tab, and scroll down to the bottom of the field to find both the maTrustedKey and maTr
ustedName values. Copy and paste the values into the appropriate fields of the Stubbing Agent installation wizard.
Click Next to continue.
72
On the Ready to Install the Program screen, click Install to begin the installation. The installation should take only a few moments.
On the Wizard Completed screen, click Finish to complete the installation process.
Configure Stubbing for GroupWise 8
After successfully installing Netmail Archive and the Stubbing Agent in your GroupWise environment, there are several steps that must be
performed in order for stubs to function properly in the GroupWise Client.
Configure the Stubbing Agent as a Message Retention Service
The GroupWise Trusted Application entry specified during Stubbing Agent installation must be configured in GroupWise as a Message Retention
Service. Complete the following steps to do so:
1. Open ConsoleOne and connect to the GroupWise system.
2. From the Tools menu, select GroupWise System Operations > Trusted Applications.
73
Tip: ConsoleOne needs to have GroupWise snapins loaded and the GroupWise system needs to be selected in order for these
options to be available.
3. Select the name of the Trusted Application that you are using with the Stubbing Agent, and then click Edit.
4. In the next window, select Provides Message Retention Service and Allow Access to Archive Service.
5. Click the pencil icon next to the Archive Service Address textbox to edit the field. In the Archive Service port field, enter the IP address or
DNS name of the machine where the Stubbing Agent is installed and the port on which it listens (this port was entered during the setup and has a
default value of 8082).
It is now necessary to set this Trusted Application as the default Archive Service for stub resolution in GroupWise. To do this, in ConsoleOne from
the Tools menu, select GroupWise System Operations > System Preferences.
Select the Archive Service Settings tab. In the dropdown list, select the Trusted Application entry which you configured as a Message Retention
Service.
In some scenarios you may prefer to have multiple Stubbing Agents installed (for example, if you have GroupWise POAs running in multiple
locations and want them to access a Stubbing Agent locally). In such a scenario, you need to configure separate Trusted Application entries for
each Stubbing Agent and then use GroupWise Post Office overrides to direct any Post Offices to the Trusted Application entry for their local
Stubbing Agent rather than the System Preference setting.
To apply Post Office overrides in ConsoleOne:
1. Right-click on the Post Office object and select Properties. Note that it is the Post Office object you click, not the POA.
2. From the GroupWise tab, select Post Office Settings.
3. Under Default Archive Service Application, select Override, and from the dropdown list, select the Trusted Application entry that you have
set up for the Stubbing Agent that will be used by this Post Office.
74
4. Click OK to save the changes
Note: Multiple SAs can be defined. For example, for heavy-load systems, where it is preferable to have an SA for each POA. In
this case, during the setup, you should modify the Trusted Application name, so that you have a different TA for each SA
installation. Use different IP addresses and ports for each SA, and then map POAs to SAs.
Run the Stubbing Agent
After the configuration in ConsoleOne is complete, you should start the SA as a standalone application (not as a Windows Service) from the
Program Menu.
When run for the first time, the SA’s Configuration window will appear. Most of the values will be populated with default settings or with the
settings you defined during setup. You can point and hold the mouse over each field to see a description of its purpose.
It is necessary for you to add at least one IP address from the list of detected addresses to the list of the configured IP addresses on which the SA
will listen. The local host IP (127.0.0.1) is added to the list by default.
Check all other settings, and then click OK to save the configuration.
After stubbing has been configured in GroupWise, end users will be able to view stubs directly from the GroupWise Client. A small stubbing icon
will differentiate stubbed items from non-stubbed items in the GroupWise Client. The following diagram shows the stubbing icon:
75
76
Install and Configure the Remote Provider(s) for Netmail Search
In order to gain access to archived items through the Netmail Search viewer or via the Stubbing Agent, you need to install the Remote Provider.
The Remote Provider acts as a proxy between the Netmail Search browser session or the Stubbing Agent (if installed) and the archive data and
indexing engine. Through the installation of the Remote Provider, users and superusers will be able to open Netmail Search and view archived
messages directly. In addition, the Remote Provider installation process also provides the means for installing the additional GroupWise Remote
Provider which is used by the WebViewer component to provide archive access through GroupWise WebAccess.
In this section:
To install the Remote Provider(s), navigate to the WebViewer folder in the Netmail Archive distribution, and then run the RemoteProvider.exe file.
The installation program will guide you through the installation process. Follow the onscreen instructions to install the Remote Provider. On the Re
mote Provider Welcome screen, click Next to proceed.
On the Choose Destination Location screen, install the Remote Provider in the default location, or browse to the location where you would like
to install the Remote Provider. Click Next to continue.
77
On the M+Open and Jexcon Configuration screen, enter the requested information for configuration.
1. Under Netmail Archive Master IP, enter the IP address of the Master Archive server. This will be used by Netmail Search when carrying out
export jobs.
2. Under Netmail Archive Master Port, enter the port number used by the Master Archive server for Netmail Archive Cluster communications.
This should be the default value of 8585 unless you modified it during installation.
3. Select Novell GW 8 or higher or Novell GW 8 or lower, depending on your version of GroupWise.
4. Under Trusted IPs, if you have deployed or plan to deploy the Stubbing Agent, enter the Stubbing Agent IP address.
The Remote Provider LDAP Connectivity Parameters screen lets you configure how the Remote Provider will access the directory server using
LDAP.
Note: When completing the fields on this screen, enter the same information you entered when configuring Netmail Archive’s
access to the directory server using LDAP.
78
1. Under LDAP Server IP Address, enter an IP address of a local eDirectory LDAP server.
2. Select SSL if you require a secure (SSL) connection between Netmail Archive and the eDirectory tree. If you enable SSL, the default Port
Number is 636. If you do not enable SSL, the default Port Number is 389. If, however, your LDAP server is configured to listen on a different port,
you can change the default port number.
3. Under Administrator Common Name, specify the account name with administrator rights to the eDirectory section where the Netmail Archive
configuration objects were stored. This is the account that was created as part of the prerequisites prior to installation. See "Administrator Rights
and Accounts" for details.
4. Under Administrator Password, specify the password used to access the account.
5. Under eDirectory Configuration Container, specify the path to the container where you created the Netmail Archive objects in eDirectory
using the syntax illustrated in the example.
6. Netmail Search uses LDAP authentication against eDirectory when users log in. This authentication lookup is performed by the Remote
Provider, and as such, it needs to know which eDirectory containers to look up to find user objects. Under User container, list the contexts of
each eDirectory container which holds user objects for users you wish to be able to use Netmail Search.
Note: The space in this field of the installation wizard is limited, so you may not be able to specify all of the user containers you
require. Modification to this setting can be made at a later stage by editing a configuration file, as described in “Remote Provider
Post-Installation Tasks”.
7. Select Perform validation if you want the installation program to validate the information provided.
On the Remote Provider Configuration screen, you can configure the Remote Provider.
79
1. Under GroupWise Remote Provider, select Install GroupWise Remote Provider if you want this installation to also install the Remote
Provider used by the WebViewer component (see "Install and Configure Optional WebViewer Component for GroupWise WebAccess" for more
information about the WebViewer). The GroupWise Remote Provider is needed so that WebViewer can access the Index and retrieve archived
items. If you select this option, you must also specify the Provider Service Port for the GroupWise Remote Provider. When specifying the
TCP/IP port number, be sure to match the setting you used when you installed the WebViewer Application component.
Note: When you select the option to install the GroupWise Remote Provider, the Install Netmail Search/AWA Remote Provider
option is also automatically selected.
2. The Netmail AWA Remote Provider is the remote Provider used by Netmail Search and the Stubbing Agent. Under M+Analytics/AWA
Remote Provider, ensure that Install M+Analytics/AWA is selected.
3. Under AWA Port, enter the TCP/IP port number on which the Remote Provider will listen for requests from Netmail Search. The default value
of 8888 should be used, unless it is in use by another service on the server.
Important: The Netmail Search interface allows users to Forward items out of the archive store to designated email recipients. It
will use the SMTP server specified here as an SMTP relay for sending these forwarded mails. When specifying the SMTP Relay
Server IP (typically your GWIA IP address), ensure that your mail server is configured to allow relaying from the IP address of the
this Remote Provider server.
On the Logon Information screen, specify which Windows account you want to use to start Remote Provider services. In order to start Netmail
Archive services, you must have local Administrator privileges on the server. Click Next to continue.
80
On the Wizard Complete screen, click Finish to complete the installation.
81
After you have clicked Finish in the Remote Provider installation wizard, you are prompted as to whether you would like to create the keystore
necessary for SSL communications. Even if you do not plan to use SSL for Remote Provider communications, it is good practice to complete
these steps.
On the first popup that refers you to the Netmail Archive Installation Manual for instructions on configuring certificates, click OK.
On the Question popup, click Yes to proceed with keystore generation.
On the Creating a Keystore screen, enter a password to be used for this process. Note that any random password will suffice, and this password
does not need to be recorded.
82
Click Next to proceed with keystore generation. A command window briefly appears while this is being carried out. Once the command window
closes, the process is complete.
After completing the Remote Provider installation program, there are several post-installation tasks for you to complete in order for Netmail
Search to function properly.
Starting Windows Services
The Remote Provider runs as a Windows service named Netmail AWA Remote Provider. The GroupWise Remote Provider, used by
WebViewer, runs as a Windows service named Netmail Remote Provider. On each server where you have installed the Remote Provider, you
need to start the appropriate services.
1. To start services manually, choose Control Panel > Administrative Tools > Services from the Windows Start menu.
3. Locate the Netmail Remote Provider service in the list of Services, and click Start.
4. Locate the Netmail AWA Remote Provider service in the list of services. Stop and then restart the service.
Configuring the Remote Provider on a Server with Multiple IP Addresses
The Remote Provider listens on port 8888 for communications from the Netmail Search sessions or from the Stubbing Agent. When the server
running the Remote Provider is configured with two or more network interfaces and has two different IP addresses on different subnets (such as
NAT), you need to specify on which address the Remote Provider should listen.
1. On the Remote Provider server, open the xgwxmlv.cfg file located in C:/Program Files/Messaging Architects/Remote Provider.
2. Locate the line in the file which contains: nat.host=
3. Edit the line to include the IP address on which the Remote Provider should listen.
83
Example: nat.host=192.168.1.124
4. Save the changes made to the xgwxmlv.cfg file, and then restart the Netmail AWA Remote Provider service.
It is possible to modify some of the default settings used by the Remote Provider and GroupWise Remote Provider in order to change behavior of
the WebViewer and Netmail Search interfaces. Depending on your compliance needs and wants, you can enable the End-User Delete option.
You can also change Netmail Search audit tags, or add or modify dropdown lists.
Enable End-User Delete
End-User Delete gives administrators the ability to allow ALL users, without any exceptions, to delete their archived items. As such, End-User
Delete should be used with caution. With this feature, items are permanently deleted from the archive, but the audit files are kept for eDiscovery
purposes. This feature works with Netmail Archive WebViewer and Netmail Search. To enable End-User Delete, follow these steps:
1. Browse to the Remote Provider folder C:\Program Files\Messaging Architects\RemoteProvider, and open the xgwxmlv.cfg file.
2. Locate the following line in the file: Message.deletable=false.
3. Edit the line so that it states the following: Message.deletable=true. When this line is set to “true,” users can delete items from their archives
through either Netmail Archive WebViewer or Netmail Search.
4. After modifying and saving the file, restart the Netmail Remote Provider and Netmail AWA Remote Provider services.
Warning: Messaging Architects generally does not advise enterprises to enable End-User Delete, because with this feature,
enterprises no longer have control over their records. Before enabling this feature, please consult your legal counsel.
Once this feature is enabled, a Delete button will appear in users’ Netmail Archive WebViewer or Netmail Search interface.
Customize Netmail Search
It is possible for administrators to customize certain features in Netmail Search. The available default tagging options and the options listed in the
dropdown lists of several fields in the Case Info tab of both the Create Case and Edit Case dialog boxes can be renamed or deleted. New
options can also be added.
To customize tags, follow these steps:
2. Locate the following line in the file: analytics.tags=['Relevant','Privileged','Flagged','Work Product'].
3. Rename or delete items listed within the square brackets, or add new items to the list. New items added to the list must be placed in single
quotation marks and separated by a comma.
4. After modifying and saving the file, restart the Netmail AWA Remote Provider service.
In the Case Info tab of the Create Case and Edit Case dialog boxes, the options in the dropdown lists of the Status, Case Class, Case Type, and
Case Sub Type fields can also be customized.
84
To customize the dropdown lists, follow these steps:
2. To customize the Status field, locate the following line in the file:
analytics.caseStatusList=[['new', 'New'],['opened', 'Opened'],['closed','Closed']].
To customize the Case Class field, locate the following line in the file;
analytics.caseClassList=[['claim', 'Claim'],['litigation', 'Litigation'],['non_litigation', 'Non-Litigation'],['potential_claim', 'Potential Claim']];
To customize the Case Type field, locate the following line in the file:
analytics.caseTypeList=[['general_liability', 'General Liability'],['intellectual_property', 'Intellectual Property'],['employment', 'Employment']];
To customize the Case Sub Type field, locate the following line in the file:
analytics.caseSubTypeList=[['Workplace', 'Workplace']].
3. Rename or delete items listed within the square brackets, or add new items to the list. New items must be added to the list using the following
format: [['new_item', 'New Item']]. The term 'new_item' acts as a placeholder for the new item, while the term 'New Item' is the name of the new
item, as it appears in the dropdown list.
4. After modifying and saving the file, restart the Netmail AWA Remote Provider service.
85
Appendix A - Rebuilding the PostgreSQL Database
Netmail Archive uses a logging database to monitor performance. By default, Netmail Archive uses a PostgreSQL database. PostgreSQL is the
recommended database, though Netmail Archive supports several other databases.
In some cases, it is possible that you may need to manually re-create the Postgres database. This can happen in one of the following instances:
The creation of the Postgres database failed during the installation of PostgreSQL
There is corruption or other problems with the database
The database needs to be moved to another server
Watch the following video to learn how to rebuild your PostgreSQL database, if the need should arise:
86
Appendix B - Confirming eDirectory Schema Extensions and Objects
During installation, Netmail Archive applies several schema extensions to the chosen eDirectory tree. These are made up of object classes and
attributes which are then used by the Netmail Archive eDirectory objects. The installation process also creates the core Netmail Archive
eDirectory objects in the container specified to hold the Netmail Archive configuration.
If LDAP details for eDirectory access were entered incorrectly, if the user specified at installation did not have the correct eDirectory rights, or if
there was a problem with your LDAP server, then it is possible that the eDirectory schema was not extended properly during the Netmail Archive
installation, or the core Netmail Archive objects were not created.
In such scenarios, you can use the information below to confirm the schema extensions and object creation. If there is a problem, you can
manually extend the schemas and create the basic Netmail Archive configuration objects using batch files provided for you. If you installed
Netmail Archive in the default C:\Program Files\Messaging Architects location, then these batch files can be found under C:\Program
Files\Messaging Architects\WebAdmin\mSetup.
To confirm the eDirectory schema extensions:
Following installation, you can double check that the schema of your eDirectory tree was successfully extended by using ConsoleOne.
1. In the ConsoleOne tree view, select your tree or organization object, and then use the menu to select Tools > Schema Manager. The Schema
Manager window opens, listing the Classes present in your tree. Verify that the ma object classes are listed as in the figure below:
Note: This figure shows the eDirectory classes used by the current version of Netmail Archive. Future versions may include more
or less. Typically, if some are present then this indicates that the classes were all correctly added during the installation process.
2. Select the Attributes tab, and verify that the ma attributes are listed, as shown in the next figure:
87
Note: If either or both the ma classes or attributes are missing, then there was a problem with extending the schema during
installation. You can follow the steps outlined in “To manually extend the eDirectory schemas and create core objects” to
manually extend the schema.
To Confirm the Netmail Archive Core eDirectory Objects:
Once the schema is correctly extended, a set of core Netmail Archive eDirectory objects is created in the container specified for this purpose
during installation.
Following installation, you can confirm the existence of the core objects in eDirectory by using ConsoleOne. Simply browse to and expand the
container specified during installation and check for the existence of the objects shown in the following figure:
88
Note: If the objects do not appear, use the manual process described below to create them using the batch files provided.
To manually extend the eDirectory schemas and create core objects:
1. On your Netmail Archive Master archive node, choose Start > Run, and then type cmd to open a command line prompt.
2. If you installed Netmail Archive in its default location, navigate to the C:\ProgramFiles\Messaging Architects\WebAdmin\mSetup folder.
3. To extend the schemas, enter CreateSchema<username> <password> (e.g., CreateSchema admin.org password123). The specified
must have administrative rights to the tree).
To create the core Netmail Archive Objects, enter CreateMaster <username> <password> (e.g., CreateMaster admin.org password123). The
specified user must have administrative rights to the tree.
A note about upgrading from M+Archive:
If you are upgrading existing servers from a previous version of Messaging Architects’ M+Archive to Netmail Archive, some of your existing
eDirectory objects will be automatically upgraded during installation. If you encounter any errors during the upgrade, however, you may need to
perform additional manual upgrades to the existing eDirectory objects using the eDirUpgrade.exe file provided for you. If you installed Netmail
Archive in the default C:\Program Files\Messaging Architects location, then the file can be found under C:\Program Files\Messaging Architects.
To use the eDirUpgrade.exe file:
1. Choose Start > Run, and then type cmd to open a command line prompt.
2. At the prompt, type the following line using the syntax provided, substituting your organization’s credentials for the placeholders used in the
89
example below:
eDirUpgrade.exe /dn <Archive Container> /u <LDAP user> /p <password> /server <LDAP Server> /port <LDAP port> /ssl <true/false>
Example: eDirUpgrade.exe /dn ou=archive,o=corg /u cn=admin,ou=ou1,o=org /p password /server 192.168.1.123 /port 389 /ssl false)
90
Appendix C - Preserving Data & System Integrity of Netmail Archive
As with any electronic data, preserving the integrity of the data is of paramount importance. In the current age of electronic records and electronic
discovery, the preservation of archival email records is even more critical, especially if those records have been ordered preserved by the courts.
Huge gaps in the electronic register due to hardware failures and data corruption can not only cost an organization to recover systems and get
them operational but can also cost an organization severely in a litigation process where incomplete eDiscovery is performed.
Netmail Archive provides a static method for saving archived email records and indexing the content for quick and efficient eDiscovery requests,
but like any electronic data, it is subject to the same risks as all other electronic data unless it is properly managed with respect to data integrity
and data recoverability.
Throughout the years there have been many different technologies for ensuring electronic data integrity and while most are still available, the type
of data and recovery requirements are the critical factors in choosing the most appropriate solution.
Netmail Archive Data Formats
Archive has two separate data formats: the Archived Messages and the indexes of the archived messages.
Archive Data
Archive stores data in two separate formats: XML and binary. When an email is archived, two XML messages are created, one XML message
containing all the message metadata and the text content of the message and a separate XML audit file which is used to track the message file. In
addition, any attachments which may have been part of the original message are stored as binary attachments and linked to the original message
through a URL in the message file.
Email messages tend to be fairly small if we take into account only the actual text of the message and the message metadata. A typical message
is usually about 4kB, which is the equivalent of almost 500 words. Adding attachments, graphics and templates to a message account for almost
99% of the actual message size.
Audit files contain message metadata indicating message chain of custody, message security and message auditing data and are typically only
1-2kB in size.
Given the fact that an average user working 250 days per year and sending or receiving on average 30 messages per day, this equates to 7,500
messages/year, and in a company with 1,000 users, this is over 7.5 million messages per year. Given multiple years of retention, the number of
messages, and consequently the number of files retained on the file system, quickly becomes a huge number. This needs to be taken into
consideration as many backup solutions are based on file backup.
Index Data
Indexes are created by the index server to provide quick and easy searching of what is effectively a huge number of individual data files. Indexes
are not constrained to the same type small size – large volume profile as are the Archive data files and contain far fewer files of larger sizes. This
makes the indexing system easier to back up with a file backup solution. However, there are other dependencies which must be regarded.
Indexes are created by the software which reads the source content and updates its internal indexes. This process doesn’t happen all at once for
the sake of efficiency, and as the data is being indexed, it is held in cached form until it can be written permanently to the system indexes. It is
therefore imperative that when backing up the indexing system, that there are no indexing processes currently running, else the indexes would be
backed up in an inconsistent state.
The one benefit that the indexes have over the archived data is that indexes can always be rebuilt easily from the source data, whereas, if the
source data is destroyed, it cannot be regenerated from the index.
Exalead, the indexing engine used by Archive, can generate indexes in real time as messages are archived, or it can be configured to archive on
a scheduled basis. To do this, the system creates a timestamp so it understands when the last indexing job was run and therefore only indexes
that content which is newer than the timestamp.
With the timestamp, the index server can be backed up at much longer intervals and thus requiring much shorter periods of time to fully
regenerate indexes if having to restore from a disaster. The recommendation would be to back up the index server once per week and therefore
only have to regenerate a week of indexes in the event of a failure and system restore.
The major requirements to backing up the Exalead index server are that there are NO ACTIVE INDEXING jobs running. To ensure this, Exalead
services should be shut down.
Backup Technologies
Tape Backup Systems
Tape technology has advanced significantly over the past 3 decades with higher capacities and higher transfer rates but tape devices still use
linear storage as opposed to random write and seek which is provided by hard drives. The main issue with tape backup is with the software. Tape
backup software provides for different types of backups including full backup and incremental backup. Obviously it is not logical to backup 40 TB
91
of data every night if only 2% of that data has changed. The main issue is determining what 2% needs to be backed up. Traditional tape backup
systems rely on the “Archive” status bit, a file level attribute which is applied when the file is written or changed by the file system. When the
backup software backs up the file, it resets the status bit so it knows the file has been backed up.
For the software to know which files have not been backed up, it must scan every single file on the target system. When dealing with file systems
containing millions of files, this process of scanning the file system can take a very long time and jeopardize the ability to even obtain an
incremental backup in a single day. This not only ties up valuable backup resources but creates a backup inconsistency.
Newer backup software packages can make use of the Windows file journaling feature. With file journaling, instead of modifying the status bit on
every file, the file system itself keeps track of modified files in a table. The tape backup software therefore only has to read the table to obtain a list
of modified files and can perform an incremental backup far more efficiently.
One negative aspect of using tape backup is that it creates a separate copy of the data which survives archival destruction policies and therefore
could be a potential discovery liability. With incremental backups, you will be forced to maintain an original full backup and therefore this presents
loopholes in the records destruction policy.
Disk to Disk Backup
Disk to disk backup has become the standard for larger organizations with Terabytes of data which needs backing up. Because disk is a faster
media, the backup can be conducted at a much faster rate thus reducing the backup window and impact to production systems. Once the
backups are on a secondary storage system, they can be moved to tape for off-site storage. Like tape backup, the critical component is the
software to run the job. Products designed for this such as Commvault® and other enterprise software packages provide for journal based
backup.
Again the one cautionary note is when conducting any backup of data, this creates an external copy of the data and therefore can be contrary to
record destruction policies.
Note: If you cannot guarantee limited retention of the backed up items on disk or tape, then this media should not be used.
SAN Replication and Snapshot
Many of today’s sophisticated Storage Area networks have built in fault tolerance and redundancy capabilities. While most SANs can be
configured with advanced RAID configurations (Redundant Array of Inexpensive Disk) including RAID 10 which effectively duplicates all data and
provides exceptional protection against hardware failure, it does not adequately address protecting against data integrity and data corruption.
Since backups create a static copy whereas replication creates a dynamic copy, corruption with the dynamic copy can be replicated to the
secondary device. In this case one needs to use backup or if the SAN architecture permits, snapshots. A snapshot is a backup function of the
SAN. It allows the SAN to take a block level image recording of the storage area at any given point in time. If there is a corruption, the system can
be restored to that exact point in time. Snapshots are much more efficient than backup, can be performed very quickly and can be performed on
live data systems. The only issue with snapshots is the storage overhead they require. Snapshooting a SAN LUN generally takes more space
than performing a snapshot on a files system which is why snapshots on devices like NetApp Filer with a CIFS (Windows File System) module will
take up less space than a snapshot of a SAN Volume.
Organizations whose SAN architectures support snapshots should consider taking daily if not weekly snapshots. In most cases, data is archived
when it is older than 7-15 days so if a restore of data is required, the source data on the email system is still available to re-archive. Check with
your policies and requirements to determine the best frequency for taking snapshots. It should correspond to the criticality of restoration and data
accessibility.
Netmail Store
Netmail Store is a content addressable storage system or CAS. This means that data is not stored as traditional files on a file system but is stored
on the device as objects with each object having a set of metadata which defines the properties of the data. Netmail Store is designed to
automatically maintain and backup data without administrator intervention or management. As each piece of data is written to the system, the
system creates a hash value for the data written so it can maintain the integrity of the data and determine if the data has changed or become
corrupt. The system also automatically replicates the data into 2 or more copies and distributes them across several different nodes or disk drives
which can be local or located in a separate disaster recovery site. The system manages itself and in the event of a hardware failure, the system
will begin to replicate all files which existed on the failed device to ensure it always maintains multiple copies. In the event of corruption, the
system will automatically repair the corrupted file by using a valid copy. This particular system maintains a real-time backup automatically, always
keeping a copy of files. The system only allows for Writing, Reading and Deleting of files and does not allow for the modification of existing files
thus eliminating any risk of file overwrites or changes. If required, it supports WORM storage whereby a file can be locked against deletion for a
specified period of time.
The solution provides the best method for records management as when the file is destroyed based on organizational retention policies, it and all
copies are destroyed.
Conclusion
Backup of archive data is critical not only because it included irretrievable corporate information but because organizations maintaining data under
litigation hold can be severely penalized by the courts for not adequately taking actions to protect the data. Organizations need to adopt the best
92
and most effective methods for guaranteeing data integrity. From a preferred list of solutions, Content Addressable Storage is the first choice for
Archive data backup, with SAN Replication/Snapshot second and disk/tape backup as a last choice. Not backing up the data is not an option. For
indexes, most existing backup solutions will suffice as long as care is taken not to backup during system operations.
93
Appendix D - Netmail Archive and Anti-virus Software
Anti-virus (AV) software is critical for ensuring that systems are protected and not compromised by malicious software that can not only cause
data loss and system failure but also compromise an organization's security.
Messaging Architects does not discourage the use of AV software on the Netmail Archive platform. However, if improperly configured, the
software can not only interfere with communications between Archive components but can also slow down the system.
Recommendations:
Never install AV software prior to installing Archive Components. This can cause issues with getting the Archive software to work properly and
can increase the complexity of troubleshooting issues. The AV software should be installed only after the Archive components have been installed
and fully validated. If, after installing AV software, there are issues, they can be attributed to the AV software. Try to avoid installing port-blocking
AV products.
All mailstores contain files with viruses that were not caught by updated virus scanners when delivered. Most of these files would be caught with
the updated software running on the client if they were accessed. DO NOT use Messaging Architects servers as a method for scanning and
eradicating viruses from the Archive system or email during the archive process. This only slows down the archive process and causes infected
files to be quarantined or deleted, which causes broken link messages. Exclude Archive Temp Folder and Attachment storage folder from Virus
scanning. If you wish to remove viruses from the Archive store, run this as a manual scanning process either from the Archive server when no
archive jobs are running or from a standalone system.
Isolate your Archive and Index servers from your client workstation network by blocking access. This will prevent potential viruses from
communicating with the Archive servers and infecting them. The only client access to Archive servers required is that for the Outlook Plugin over
port 8443 to the Remote Provider service or server.
94

Netmail Archive 5.2 Installation Guide for Novell GroupWise

Transcription

Similar documents

PDF (Author`s version) - OATAO (Open Archive Toulouse Archive

in construction and facility management

english magazine volume 1, february 2015 primary school videm

Using a bookrest with original archive volumes

State-of-the-Art: Media Archive Solution

Atlantis Energy Systems Inc.

Neely PowerPoint - New England Archivists

Coffing EC3 Manual