Netmail Archive 5.2 Installation Guide for Novell GroupWise

Netmail Archive 5.2Installation Guide for Novell GroupWise

Netmail Archive 5.2 Installation Guide for Novell GroupWise

2 Copyright © 2013, Messaging Architects. Updated: 10/05/2013

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 emailarchiving, retention, regulatory compliance, and fast retrieval of email messages. Netmail Archive integrates seamlessly and transparently intoyour corporate email system, improves server performance, lowers storage costs, and offers you the tools to individually or globally searcharchived 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. Theseservices are controlled by policies that allow organizations to define their rules for information retention centrally. The Netmail Archive solutionaddresses an organization’s long-term archiving requirements by managing and maintaining a platform-independent external XML data repositoryfeaturing 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 ArchiveAbout Novell GroupWiseNetmail Archive Deployment ScenariosNetmail Archive Feature OverviewComponent OverviewOverall Installation SequenceDocumentation List

Netmail Archive Master NodeSystem RequirementsPre-Installation Tasks for a GroupWise DeploymentInstalling the Netmail Archive Master Node in a GroupWise EnvironmentPost-Installation Tasks for GroupWise

Indexing Node(s)Server RequirementsPre-Installation TasksInstalling the Index ServerStart the Index ServiceRun the Cluster Manager ToolConfigure Archive Server to Index Server CommunicationsIndex ConversionUsing the Index Server Administration Console

Netmail Archive Worker Node(s)Installing Worker Node(s) in a GroupWise EnvironmentPost-Installation Tasks for Worker Nodes

Install and Configure Optional WebViewer Component for GroupWise WebAccessInstalling the WebViewer Application to Your Web ServerInstalling the WebViewer on a Linux SystemInstalling the GroupWise Remote Provider ComponentWebViewer Post-Installation Tasks

Install and Configure Optional Stubbing AgentInstalling the Stubbing AgentConfigure Stubbing for GroupWise 8

Install and Configure the Remote Provider(s) for Netmail SearchInstalling the Remote Provider(s)Remote Provider Post-Installation TasksAdditional Configuration for the Remote Providers

Appendix A - Rebuilding the PostgreSQL DatabaseAppendix B - Confirming eDirectory Schema Extensions and ObjectsAppendix C - Preserving Data & System Integrity of Netmail ArchiveAppendix D - Netmail Archive and Anti-virus Software



Introducing Netmail Archive

This section covers the following:

About Novell GroupWise

Netmail Archive Deployment Scenarios

Netmail Archive Feature Overview

Component Overview

Overall Installation Sequence

Documentation List

About Novell GroupWise

Novell GroupWise is a messaging and collaboration system that supports email, calendaring, personal information management, and documentmanagement. Netmail Archive adds value to your GroupWise system by providing secure, centralized archiving and retrieval of information.

Netmail Archive Deployment Scenarios

Integrating seamlessly and transparently into the email system, Netmail Archive frees up server space, improves server performance, andensures fast retrieval of archived email and attachments. Netmail Archive allows administrators to enforce flexible email policies without breachingprivacy and freedom of information rights, and at the same time, to tackle an exponentially growing volume of electronic data by easily integratingwith 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 usersQuantity of new daily messages to processAverage size of attachments to processRecords retention policy (size of archive indexes)Frequency of Archival accessArchiving 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. TheNetmail Archive server requires a Windows 2003 Server or a Windows 2008 Server. A single Netmail Archive server should be able to effectivelyarchive 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 APIintegration.

Exchange

In an Exchange environment, the Netmail Archive server is responsible for extracting information from Exchange, indexing XML content, exporting



1.

2.

3. 4.

content from the data repository, and running grooming and deletion jobs on the archive repository. The Netmail Archive server requires aWindows 2003 Server or a Windows 2008 Server. A single Netmail Archive server should be able to effectively archive more than 500,000 itemsin less than 24 hours.

Netmail Archive integrates with both Exchange 2007 and Exchange 2010 viaNote: 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 Exchangein 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 Environmentappendix 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 toenable multiple servers to work together. Netmail Archive is configured to automatically detect any additional nodes and cluster together formaximum performance and uptime. Within a cluster, the Master node will automatically detect the current load of any of the Worker nodes in thecluster 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:

Through the Netmail Archive Administration Console, archiving jobs are defined and stored in eDirectory. The Master node scanseDirectory and executes jobs based on their schedules. When executing a job, the Master node allocates work across the availablenodes in the cluster.The nodes query the messaging servers for data. Data is then sent to the nodes from the messaging server for processing throughNetmail Archive.After processing, Netmail Archive converts the data to XML format and writes the data to the storage system.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. TheNetmail Archive solution helps organizations proactively gather, restore, search, organize, and deliver email and other records for litigationdiscovery and regulatory investigations. Netmail Archive’s high performance email archiving capabilities quickly archive and index selectedelectronic records that are easily transferred to a choice of media for storage. With Netmail Archive’s sophisticated new indexing and powerfulsearch tools, archived email and other electronic records can be located and accessed instantly from any web browser where approved users cansearch, 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 yourNetmail Archive deployment will vary depending on a number of factors. For example, as the volume of email increases, you should take intoconsideration the number of messages you expect to index. Also, performance is proportional to the number of spindles available to the IndexServer. A basic Index Server should have four disks or more to store the index.



A single Netmail Archive Index Server should be able to index between 50 and 75 million documents. For more information on installing the IndexServer, see .“Installing the Index Server”

Netmail Archive Feature Overview

Netmail Archive provides a set of tools which enable the user to proactively address three key concerns: policy-based retention/deletion, fullInformation 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 corporateemail policy by extracting information and retaining it according to relevant business drivers is the best approach to tackling regulatorycompliance. Moreover, a corporate-wide email retention policy ensures reliable protection of corporate records and preparedness for legaldiscovery. 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 asNetApp storage systems from Network Appliance, Inc., the Hitachi Content Archive Platform (HCAP), and hardware-agnostic Netmail Storestorage software. Messages can be tagged by Netmail Archive with retention dates that deny the capabilities of modifying or deleting thesemessages 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 AreaNetwork (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 effectiveretention and archiving policies to reduce current storage requirements and database sizes. It provides organizations with the ability to improvetheir collaboration system performance and reliability, as well as reduce their storage costs and recovery times in the event of system failure. Bydeploying Information Lifecycle Management policies, organizations can more effectively manage their archive store(s) through grooming anddeletion.

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 datamanagement. 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 andrecord retrieval enables you to perform search and discovery of email content and records with granular control that greatly facilitates the processof 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 ina non-modifiable and undeletable state until a specified retention date is reached.

Message discovery options include:

Global search of single or multiple mailboxesStandard content, subject, date, and address searchesAttachment searchRefined searchesEnhanced Proximity, Wordlist, and Approximate Spelling searchesAudit trail searches

All searches are performed on email archives containing mail messages, appointments, tasks, notes, and attachments. Electronic messages areexported 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 anon-SIS archiving environment, every archived message attachment is stored, even if the attachments are identical. SIS reduces storage costs bystoring only a single copy of identical attachments. In Netmail Archive, SIS is implemented at the application level, so organizations benefit fromthis feature regardless of their storage integration.

Component Overview



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-basedapplication that allows administrators to configure Netmail Archive, create policies, and run jobs. Upon login, administrators can access systeminformation, view and configure Master and Worker nodes, and view, modify and/or create policies and jobs through the various available jobagents.

Policy Engine

The Policy Engine is the back-end component that creates, organizes, and manages policies within Netmail Archive. The Policy Engine facilitatesthe 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 tovarious Job Agents in the Netmail Administration Console. Polices may be as simple or as complex as your business needs dictate, and becauseNetmail Archive gives you flexible control over the organization’s email policies, you can always amend existing policies or create new ones asyour 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 ASCIIform 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 anyinformation held in your email system’s message store, such as messages, calendar information, and any attachments, to an external repositoryin XML format. The Archive Agent provides more granular archiving to XML by allowing enhanced criteria searching including advanced dateselection 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 existingGroupWise 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 makeinformed storage management decisions. These comprehensive reports enable organizations to protect information and better manage theirelectronic assets through all stages of its lifecycle. The Discovery Agent can also be used as a tool to help administrators create intelligentArchive 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 variouspurposes (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



The Group Agent allows you to schedule a series of jobs to run consecutively. The Group Agent helps you make intelligent scheduling decisionsby 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 recordsretention 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 thearchiving 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, andon 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 GroupWisenative 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 advancedsearch 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 usersfilter 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 CaseManagement Dashboard that lets them create and manage multiple cases. Through this case management system, administrators can respondto any and all eDiscovery requests simultaneously and are spared the headache of sifting through all archived data each time an eDiscoveryrequest is made. Advanced search options and guided navigation, plus the logic of case management, are delivered to administrators in aneasy-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 GroupWiseWebAccess, users can toggle between the standard WebAccess view of their GroupWise message store and the Netmail Archive WebAccessview of their XML archives. Maintaining the look and feel of GroupWise WebAccess, the Netmail Archive WebViewer allows users to transparentlyaccess their XML archives and live mailboxes for a seamless end-user experience. The Netmail Archive WebViewer displays the archive contentcategorized 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 GroupWisearchives via a web browser. The WebViewer interface also provides users with enhanced searching capabilities in addition to the standardGroupWise WebAccess search interface.

Administrative Utilities



1. 2. 3. 4. 5. 6. 7.

Netmail Archive includes a number of optional utilities to complement your Netmail Archive system. These utilities can be used to helpadministrators organize and manage their archives. If you installed Netmail Archive in the default location, these utilities can be found in the C:\Pr

folder.ogram Files\Messaging Architects\GWArchive\Deployment

Indexing Server

The Indexing Server is the component that makes eDiscovery possible. This highly advanced piece of technology acts, within the platform, as thecreator of the index of all messages and attachments archived by the system. It is also responsible for processing the search queries (which areapplied 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 searchinterface 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 useraccess to the archived items. This component receives the requests for information (queries) from Netmail Search, and passes them on to theIndex 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 andpresents 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; itreceives requests for specific messages from the GroupWise client, fetches the requested items from the archive, and presents them for displayin the GroupWise client. The main difference with the Stubbing Agent is that the items are requested via the stubs, visible as special items in thelist 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.

Overall Installation Sequence

For a typical deployment of the Netmail Archive solution, a number of components need to be installed and/or configured to ensure effective andproper functionality of the archiving system. The following is an outline of the overall installation procedure for the entire Netmail Archive system:

Verify that the system requirements are met on all servers and/or VMsInstall and configure the Netmail Archive Master nodeInstall and configure the Indexing node(s)Install the Worker node(s) (if applicable)Install and configure the optional WebViewer componentInstall and configure the optional Stubbing AgentInstall and configure the Remote Provider(s) for Netmail Search

Documentation List

The and the combine to explain how to install and configure the NetmailNetmail Archive Installation Guide Netmail Archive Administration GuideArchive Server and Web components, as well as various helpful administrative utilities. After installing and configuring Netmail Archive with thehelp of this guide, refer to the to learn how to easily use the Netmail Administration Console to createNetmail Archive Administration Guideretention and archiving policies and schedule archiving jobs. Below is a brief description of the components of Netmail Archive and thedocumentation available for each. The documentation listed below can be found in the folder in the NetmailMessaging Architects DocumentationArchive package.

Component Description Available Documentation

Netmail Administration Console A web-based administrative interface thatallows for configuration and management ofpolicies and jobs, as well as configuration andmonitoring of the Netmail Archive system.

Netmail Archive Installation and Guide Netmail Archive Administration Guide

Policies Criteria filters used by jobs to determine whichitems they will act upon.

Netmail Archive Administration Guide

Archive Agent Allows administrators to create archiving jobsto move any information held in your emailsystem’s message store to an external XMLrepository.




Discovery Agent Allows administrators create policies toregularly analyze the state of the messagestore to help organizations make informedstorage management decisions.


Group Agent Allows administrators to schedule a series ofjobs to run consecutively.


ILM Agent Allows organizations to deploy full informationlifecycle management policies to address theirlong-term records retention and recordsmanagement needs.


Index Agent Allows organizations to create separate IndexJob for their XML repositories rather thanhaving the indexing completed by thearchiving job.


Utility Agent Allows administrators to perform variousmaintenance tasks on the GroupWisemessage store or the XML repositories.


Netmail Search for eDiscovery A powerful web-based eDiscovery tool thatoffers several advanced search capabilities toallow administrators to find and managerelevant information quickly and efficiently.

Netmail Search User Guide for eDiscovery

Netmail Search for End Users A powerful web-based eDiscovery tool thatoffers several advanced search capabilities toallow end users to easily search and managetheir personal archives.

Netmail Search User Guide

Netmail Search for External Reviewers A powerful web-based eDiscovery tool thatoffers several advanced search capabilities toallow external reviewers to search throughand review relevant information quickly andefficiently.

Netmail Search User Guide for ExternalReviewers

WebViewer for Administrators A GroupWise WebAccess plug-in that allowsadministrators to access and search thearchive data for all users in the XMLrepositories to which they have access.

WebViewer User Guide for Administrators

WebViewer A GroupWise Client plug-in that allows endusers to view their archived data.

WebViewer User Guide

Indexing Server Creates the index of all messages andattachments archived by the system andprocesses users’ search queries.

Netmail Archive Installation Guide

Remote Provider Receives information requests from NetmailSearch, sends them to the Index Server forprocessing, and prepares the results forviewing in Netmail Search.

Netmail Archive Installation Guide

http://help.netmail.com/display/EDISC51/Netmail+Search+User+Guide+for+eDiscovery

http://help.netmail.com/display/SEARCH51/Netmail+Search+User+Guide

http://help.netmail.com/display/REVIEWERS51/Netmail+Search+User+Guide+for+External+Reviewers

http://help.netmail.com/display/REVIEWERS51/Netmail+Search+User+Guide+for+External+Reviewers

http://help.netmail.com/download/attachments/12650943/MPlusArchive+WebViewer+for+Administrators.pdf?version=1&modificationDate=1363770673379

http://help.netmail.com/download/attachments/12650943/MPlusArchive+WebViewer+User+Guide.pdf?version=1&modificationDate=1363770684314



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 belowhave 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

Pre-Installation Tasks

Install GroupWise Client (if required)

Verify the Secondary Logon Service isrunning on the server

Install Novell Client (if required)

Install Outlook Client (for exporting to PSTformat)

Verify .NET Framework 4.0 is installed

Verify Netmail Open Framework NOTinstalled

Install Java Runtime Environment 6.0 32-bit(on the Archive Node)

Choose your SQL-Based Logging Database

Netmail Archive Installation Deploy Netmail Archive

Post-installation Tasks

Start Netmail Archive Services

Launch the Administrative Console and Log In

Update the Address Book Cache

Verify Netmail Archive Licensing

Configure Web Browser for Index ServerCommunications

System Requirements

For a successful installation of Netmail Archive and optimum expected performance of the solution, ensure that your servers or VMs have beenbuilt according to the minimum recommended system requirements. For the most up-to-date system information and requirements, please referto or contact Messaging Architects.System Requirements for Netmail Archive

Furthermore, ensure that the following miscellaneous prerequisites are met before proceeding with the pre-installation tasks:

Miscellaneous Prerequisites

Anti-Virus Software Turn OFF all AV Software until the NetmailArchive software is installed and validated

Management Software Do not install any management software,including Manufacturer monitoring or Backupsoftware



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 prepareyour system installing Netmail Archive. The following list of requirements must be met before installing Netmail Archive in a GroupWisebeforeenvironment.

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 ArchiveGroupWise to Exchange Provisioning Utility on your Netmail Archive archive server(s), then verify that the server(s) to be used as an archiveserver has the appropriate GroupWise Client for your environment installed on it (minimum supported version is 6.5.6 or higher). If the serverdoes 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 usedduring installation for extending the eDirectory schema and creating the Netmail Archive configuration objects. Once operational, Netmail Archiverequires 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, thisaccount 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 SystemAddress Book content. These combined eDirectory and GroupWise account requirements are most easily achieved by creating an eDirectoryuser (perhaps named "NMArchive") within a container created in eDirectory specifically for storing the Netmail Archive configuration objects. ThiseDirectory 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 Windowsservices. To facilitate larger (or variable-size) deployments, it is usually more expedient to create a Windows domain-level account (withmembership of each archive server's local Administrators group) for this purpose. Furthermore, it may be necessary to grant this account user filerights to any and all storage locations where GroupWise Native Archives may be located on your organization’s network.

Best practice is to use an Active Directory user account. To do so, create anTip: 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 theControl Panel and launch the Add and Remove Programs function. In the list of currently installed programs, look for Microsoft .NET Framework

. If Microsoft .NET Framework version 4.0 is not installed, the program is available for download from www.microsoft.com.4.0

If using Windows Server 2008 R2, you can verify that Microsoft .NETNote: 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 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 yourIndex 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 want to use the PostgreSQL database, make sure that the database you are using is fully installed and accessible from the Netmail Archivet

server(s). If you are using a database other than PostgreSQL, Oracle, MySQL, MSSQL (2005/Express), or MSSQL (2000/MSDE), the databasemust 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 “NetmailArchive Logging Database”.

Installing the Netmail Archive Master Node in a GroupWise Environment

Installation sequence for Netmail Archive 5.2

Locate and run the file located in the directory. It is recommended that you right-click on the file and selectsetup.exe NetmailArchive setup.exethe option. The Netmail Archive Setup Program will install the Netmail Archive Master node and the Corporate ArchiveRun as administratorViewer. The installation program will guide you through the installation process. Follow the onscreen instructions to install Netmail Archive in aGroupWise 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 screen, click to proceed.Netmail Archive Welcome Next

On the screen, carefully review the software license agreement, and then click License Agreement I accept the terms of the license to accept the License Agreement. Click to continue.agreement Next

http://www.oracle.com/technetwork/java/javase/downloads/index.html

http://www.oracle.com/technetwork/java/javase/downloads/index.html



On the screen, install Netmail Archive in the default destination folder, or browse to the location where you want toChoose Destination Locationinstall Netmail Archive. Click to continue.Next

The screen allows you to choose whether you are installing a Master or Worker archive node. Where workloads require,Cluster ConfigurationNetmail Archive can be configured to run a cluster of archive nodes. The first server installed should always be chosen as a Master node and allsubsequent archive nodes installed as Worker nodes. Within a cluster, the Master node will automatically distribute the workload across theavailable archive nodes to better utilize system resources. For smaller environments intending to use only one archive node, the Master role mustbe chosen.



1. On the screen, select the option, since you are installing the first archive node of the cluster, orCluster Configuration Install Master Nodeyou 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 , enter the of the computer where you are installing Netmail Archive.Master Configuration IP Address

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 field specifies the port number that will be used for Netmail Archive cluster communications by this node. By default, the port numberPortof the Master node is 8585. It should not have to be changed, as Netmail Archive should be installed on a dedicated server. However, you canchange the default port number based on which ports are currently in use and your network security requirements. Whichever port you choose, besure to verify that there are no firewalls or filters on the port that would impede communications.

4. Click to continue.Next

If you do not have an SQL database installed on your system, the dialog box appears, prompting you to installPostgreSQL InstallationPostgreSQL as your logging database. If you want to use PostgreSQL as your logging database, click to proceed with the PostgreSQLYesinstallation. Otherwise, click to continue with the Netmail Archive installation (which continues with the ).No Messaging Server screen

Note: If you choose not to install PostgreSQL, you can opt to manually install a different supported database.

After clicking , you are reminded to include the ODBC drivers as part of the PostgreSQL installation. Click to acknowledge the reminderYes OKand continue with the PostgreSQL installation.



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 theduration 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 screen, click to proceed with the installation.Welcome Next



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 theinstallation of Netmail Archive.

Note: If the , this is typically a Windows file system rights issue and/or a user rights issue.installation of PostgreSQL failsConfirm that both have the required rights before proceeding with the install.

If, during the installation of PostgreSQL, the , refer to creation of the Postgres database fails Appendix A - Rebuilding the for information on how to manually rebuild your Postgres database.PostgreSQL Database

On the screen, use the default location or specify the location in which you want to install PostgreSQL. Click toInstallation Directory Nextcontinue.



On the screen, use the default location or specify the location in which you want to store your data, and then click toData Directory Nextcontinue.

On the screen, enter and confirm the password for the postgres database super user and service account. If a service account alreadyPasswordexists, enter the corresponding password for the account. If a service account does not exist, a new one will be created when you click . ClickNext

to continue.Next



On the screen, enter the number of the port on which the PostgreSQL system should listen for connections. It is recommended to use thePortdefault value of 5432 unless you have good reason to change it. Click to continue.Next

On the screen, select the locale to be used by the new database cluster, and click .Advanced Options Next



On the screen, click to install PostgreSQL.Ready to Install Next

On the screen, you are asked if you want to launch Stack Builder upon closing the Setup wizard.Completing the PostgreSQL Setup WizardThe 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



On the screen, use the dropdown list to select the version of postgres you have just installed, and click to continue.Stack Builder Welcome Next

The next screen allows you to select the applications you want to install. Select , and then select the Categories > Database Drivers psqlODBCdriver. Click to continue.Next



On the next screen, ensure that the ODBC driver is listed in the list. Choose a directory to which you want to download yourSelected packagesselected application, if required (the default download location should not need to be changed). Click to download the installation file.Next

Note: Internet connectivity is required for a successful download.

Once the installation file has been successfully downloaded, the application can be installed. Click to begin the installation of the ODBCNextdriver.



The screen appears. Click to continue.Setup psqlODBC Next

On the screen, specify the location in which you want to install psqlODBC.Installation Directory



On the screen, click Next to begin the installation of psqlODBC.Ready to Install

On the screen, click to exit the wizard.Completed the psqlODBC Setup Wizard Finish



On the Stack Builder screen, click to exit the wizard.Installation Completed Finish

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 , this is typically due to a Windows file system rights issue and/or a user rightsinstallation of PostgreSQL failedissue. Confirm that both have the required rights before you proceed with the install.

If, during the installation of PostgreSQL, the , refer to creation of the Postgres database failed Appendix A - Rebuilding the for information on how to manually rebuild your Postgres database.PostgreSQL Database

The screen allows you to select which type of messaging server you are using with your Netmail Archive system.Messaging Server



1. On the screen under Novell GroupWise, select the default connectivity method Netmail Archive should use to communicateMessaging Serverwith 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 Agentsvia the SOAP protocol. The Post Office Agents in your GroupWise system must be enabled for SOAP connection in order to use thismethod.

Version 7.02 or higher (SOAP API) with SSL enabled: Choose this option for SOAP API with SSL enabled. Your choice can bechanged 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 orbelow, 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 if you would like to use Netmail Archive’s stubbing functionality.Enable stubbing

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 screen allows you to specify GroupWise Access Information.GroupWise Connectivity Parameters



The Trusted Application feature allows specific applications to log in to any GroupWise account without using a password. Create a new TrustedApplication for Netmail Archive using Novell ConsoleOne with the GroupWise snap-ins and copy the trusted application key from the resulting filefor use in this dialog.

1. On the screen, select the option, and then paste theGroupWise Connectivity Parameters Import an existing Trusted Application KeyTrusted Application key value into the field.Trusted Application Key

2. Under , enter the name of the application, such as Archive or NetmailArchive.Trusted Application Name

3. Under , specify the IP address of the Post Office Agent. If you have multiple Post Office Agents, choose a local Post OfficePOA IP AddressAgent and specify its IP address.

4. By default, the of the GroupWise Client is 1677, however, if this port is unavailable you can change the default port number.Port

5. Specify the Internal Client/Server number which this POA is configured to use. The default port number is 1677, however, check thePortGroupWise configuration to confirm.

6. Specify the Internal SOAP number this POA is configured to use. The default port number is 7191, however, check the GroupWisePortconfiguration to confirm.

7. Under , enter the name of a GroupWise account. This is the Netmail Archive accountGroupWise Account (dedicated for Netmail Archive)created in GroupWise as part of the preprequisites prior to installation. See for more details.“Administrator Rights and Accounts”

8. Select if you want the installation program to validate the information provided.Perform Validation


The screen lets you configure how Netmail Archive will access the directory via the LDAP protocol.LDAP Server Connectivity Parameters



1. Under , enter the host name or IP Address of a local eDirectory LDAP Server.LDAP Server Host Name/IP Address

2. Select if you require a secure (SSL) connection between Netmail Archive and the eDirectory tree. If you choose for SSL to be enabled, theSSLdefault is 636. If you choose for SSL to be disabled, the default is 389. However, if your LDAP server is configured toPort Number Port Numberlisten on a different port, you can change the default port number.

3. Under , specify the account name with administrator rights to the eDirectory section where the Netmail ArchiveAdministrator Common Nameconfiguration it is to be stored. This is the account that was created as part of the prerequisites prior to installation. See “Administrator Rights and

for details.Accounts”

4. Under , specify the password used to access the account.Administrator Password

You can later use this Administrator Name and Password combination to logNote: 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 , specify the path where you want to create and store the Netmail Archive objects in eDirectoryeDirectory Configuration Containerusing the syntax illustrated in the example.



The screen allows you to specify which account you want to use to start Netmail Archive services. In order to startService Logon InformationNetmail Archive services you must have Administrator privileges.



1. On the screen, enter the user account you want to use to start Netmail Archive services. User accounts must beService Logon Informationspecified using the following syntax: DOMAIN\username. Click to browse to the location.Browse

To avoid any problems creating files on the server, the account used should ideally be part of the Local Administrators groupTip:on the server. Also, it may be necessary to grant this user file rights to GroupWise Native Archive locations if you plan onimporting Native Archives, or to Export locations if you are going to export data to file system paths. Furthermore, it is typicallyrecommended that all Archive and Index servers be in the same Windows Domain, and that a dedicated domain account forNetmail Archive is created for use with this service account.

2. Under , enter the password used to access the account.Password


If there is no domain controller to authenticate against, you must authenticate locally using the following syntax: .\username.Tip:

The screen allows you to select a database and specify where Netmail Archive willLogging Database Configuration and Notification Settingstore logging information.



1. If you have installed PostgreSQL, the default is PostgreSQL. However, if you do not want to use this database, select whichDatabasedatabase you want to use from the available options:

MySQLMSSQL (2005/Express)MSSQL (2000/MSDE)Other

If you are using the PostgreSQL database, the information you enter on the Important: Logging Database Configuration and screen should match the information that you entered during the installation of PostgreSQL. For instance,Notification Setting

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 , enter the IP address or host name of your database server (this server, if you installed PostgreSQL).Server name

3. Under , ensure you have the name entered.Database name netmailarchive

4. Under , ensure is entered if you are using PostgreSQL, or a valid database user account for connecting to your otherUser name postgresdatabase system.

The user name is case sensitive.Note:

5. Under , enter the database user’s password (as entered earlier, if using PostgreSQL).Password

6. Under Port, ensure your database ODBC connection port is specified (for PostgreSQL, this is the port specified earlier, which is 5432 bydefault).

7. Once those settings are entered, click to update the ODBC Connection String in the text box below. If you are using a non-PostgreSQLApplydatabase, you may need to verify that the connection string is correct and customize it if necessary.


Make sure you click to update the connection string and create the database tables before clicking .Note: Apply Next


To avoid the PostgreSQL service account password expiring, it is recommended that you adjust the postgres Windows userTip:account configuration in the Microsoft Management Console to disable password expiration.

The screen is pre-populated with the Netmail Archive WebAdmin URL and the port numbers on which the Netmail Unified UI willEnter Valuesoperate. This information does not need to be changed. Click to continue.Next



On the screen, click to begin the installation.Ready to Install Install

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 screen, click to complete the installation of the Netmail Archive Master node.Wizard Complete Finish



Because Windows sometimes keeps certain components locked, you may beNote: 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 deployingarchive 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 tothe appropriate directory. If you installed Netmail Archive in its default installation location, place the license file in the C:\Program Files\Messagin

directory on the Master node. Otherwise, place the license file in the directory in which you installed Netmail Archive. To activate theg Architectslicense, you must restart several services from the Windows Menu. For more information, see .Start “Start Netmail Archive Services”

You should also copy the license file to the same folder on any Worker nodes that you will subsequently install, as some ofNote:these may take over the Master role in the case of a server failure.

If you do not restart the services, Netmail Archive will add the MALicense Checker Trigger to its list of tasks, but mayImportant: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, andexpand the left-hand folder view to select the object, as shown in the figure below. AArchive > Clusters > <Cluster Name> > Agents > Archivelicense count for the Archive Agent should now appear on the tab. This license count should match the license count in your file.License



The MALic.xml file has a digital signature applied to it, so if you attempt to edit the file, the license will be invalid.Important:

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 aNetmail Archive agent is defined as the number of accounts currently allocated to jobs for that agent. When this count is being calculated, it isimportant 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 tomultiple 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 becounted as if listed themselves. Note that the current membership as known by Netmail Archive will be based on the membership at thetime 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 theaccounts allocated to Netmail Archive jobs. The Netmail Archive administrator is at liberty to decide which accounts are to be processedand 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 arerequired 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 acton archived mail accounts, not live mail system accounts. With specific storage systems such as Netmail Store, where a specified dataretention 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 theretention 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 datawithout requiring a license.


After completing the Netmail Archive installation, you must start Netmail Archive Services. During the installation program, a shortcut was createdfor you in the Windows menu. To use the shortcut, choose .Start Start > All Programs > Netmail Archive > Start Netmail Archive Services

To start these services manually:



1. Choose from the Windows Start menu.Control Panel > Administrative Tools > Services

2. Double-click to open the dialog box.Services Services

3. Locate the service in the list of Services, and click .Netmail Open Start

4. Locate and right-click the service in the list of Services, and select .Netmail Administration Console Start

When Netmail Open is subsequently started or stopped after this first post-Tip: install startup, it will auto-start or auto-stop boththe Netmail Administration Console and ThreadPool services. For the first startup, however, neeNetmail Administration Consoleds to be started manually.

Before starting Netmail Archive Services, ensure that the account whichNote: 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 runjobs.

To launch the Netmail Administration Console, open a standard web browser and enter the IP address of the server where you installed NetmailArchive, followed by the port number specified during the Unified UI installation (e.g., ). The console can be accessedhttp://192.168.1.123:8989from any workstation with access to the IP address and port number.

On the Netmail Administration Console login screen, enter your and , and click . The username and passwordUser Name Password Loginrequested are those of an eDirectory user with full rights to the container holding the Netmail Archive configuration objects. By default, this is thededicated eDirectory user that you created before installation. The username is entered in the following format: username.container.org (e.g.,nmarchive.archive.myorg).

For more information about logging in to the Netmail ArchiveNote: Administration Console, refer to the Netmail ArchiveAdministration 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 userinformation into the Netmail Archive system. This allows GroupWise accounts to be allocated to archive jobs, for example. You can run this jobmanually now in order to confirm connectivity to the GroupWise system. In the Netmail Administration Console, select the Archive > Clusters > <

object in the tree. By default, the tab is displayed. Click the tab to specify your AddressCluster Name> Configuration Address Book SyncBook cache settings.



To execute the address book sync job and confirm that it has connected correctly to GroupWise:

1. Under , click to start the address book sync job immediately.Address Book Cache Run Now

2. Choose the object in the tree menu on the left-hand side of the Netmail Administration Console, and then click the tab. The Archive Monitor M tab tracks the jobs currently being processed. Expand the entry for the cluster node and a SyncAB Trigger should appear in the Runningonitor

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 PostOffice information has been read, navigate to the object in the tree, and select the tab.Archive > Clusters > <Cluster Name> P.O.

For more information about updating your address book cache, refer to theNote: .Netmail Archive Administration Guide

Now that you have successfully installed the Netmail Archive Master node, policy-based retention is now possible. However, to performeDiscovery and email lifecycle management, you will need to install additional components, namely the Index Server and Remote Provider. Theinstallation of these two components is covered in subsequent sections.



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 searchfunctionality. Netmail Archive’s Index Server provides organizations with the means for the archive viewer interfaces, including Netmail Search, toaccess 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

Pre-Installation TasksVerify .NET Framework 4.0 is installed

Install three versions of Microsoft Visual C++Redistributable

Index Server Installation Install the Index Server

Post-Installation Tasks

Start the Index Service

Run the Cluster Manager Tool

Index Conversion

Server Requirements

The Index Server must be installed on a separate server than the Netmail Archive Master Node (archive server). Messaging Architects requiresthat you install the Index Server on a 64-bit operating system in a production environment. Installing the Index Server on a 32-bit operating systemmay degrade performance. Windows 2008 R2 Enterprise Edition 64-bit is the current recommendation, however, you can view the latestrequirements .here

Pre-Installation Tasks

In order to ensure a successful deployment of your Index Server, there are certain things you must do to prepare your system installingbeforethe 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 theControl Panel and launch the Add and Remove Programs function. In the list of currently installed programs, look for Microsoft .NET Framework

. If Microsoft .NET Framework version 4.0 is not installed, the program is available for download from .4.0 www.microsoft.com

If using Windows Server 2008 R2, you can verify that Microsoft .NETNote: 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 IndexServer:

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.

http://www.microsoft.com/en-us/default.aspx

http://www.microsoft.com/download/en/details.aspx?id=14431



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 file. The installation wizard will guide you through the installation process.setup.exe

The Index Server must be installed on a 64-bit operating system in aImportant: production environment. Only a 64-bit setup.exefile is provided for installation.

On the screen, click to continue.Welcome Next

On the screen, install the Index Server in the default destination folder, or browse to the location where you want to installNetmail Indexing Paththe Index Server. Click to continue.Next

The screen requires you to indicate the path where your indexes will be stored. It is recommended that you keep theNetmail Indexing Data Pathdefault folder name, but you must ensure that you change the drive to your chosen index storage volume. Once youNetmail Indexing/Cloudviewhave done this, click to continue.Next

http://www.microsoft.com/download/en/details.aspx?id=11895



On the screen, specify if you are installing a Master or Slave Index server.Select Node Type and enter your Exalead server

1. Select if you are installing the Master Index server, or select if you are installing a Slave Index server.Master Slave

The first index server to be installed must be set as theNote: Master server. Any subsequent servers installed must be set as Sl ave servers.

2. If you are installing the Index server, specify the of the server where the Master Index server is being installed, as well asMaster IP addressthe and . Unless unavailable, use the default Base port 10000 and the default Gateway port 10011.Base Port Gateway Port

If you are installing a Index server, specify the existing Master Index server settings as well as the of the Slave host beingSlave IP addressinstalled.

Click to continue.Next

On the screen, click to begin the installation.Ready to Install the Program Install



The installation phase can take several minutes to complete. Towards the end of the installation process, a command window opens, followed bya message that reminds you to run the Cluster Manager to complete the installation process. Click .OK

On the screen, click to exit the installation wizard.Wizard Completed Finish

Start the Index Service

After completing the installation of the Index Server, you must start the Index Service.

To start the Index Service:



1. Choose from the Windows menu.Control Panel > Administrative Tools > Services Start


3. Locate the service in the list of Services, and click .Netmail Indexing (CloudView) Start

DoImportant: 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.

Run the Cluster Manager Tool

The Cluster Manager tool can be run from any location, but it is most easily run on the Master Index server. The fileExaleadClusterManager.execan 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 countsfor 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 slicecount 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”

Generally, when using the Cluster Manager tool, all configuration should beNote: done through the Master server, and Slave before servers should be registered and have their slice counts configured 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 processorsand resources needed to accept and analyze documents and to build the index. In Netmail archive there are two core build groups: fbg0or the archive items, and for the audit files. In addition, for systems being upgraded from M+Archive, a third build group named bgAudits

is used to handle converted indexes from the previous version of the Index Server.bg_4_6

Index Slices: A segmentation of the index to facilitate index distribution and load balancing. Within a server, a build group is split intoslices to optimize performance based on the number of processor cores in the server. Indexes are also sliced to allow for distributionacross servers.

Deploying a New Index Server Cluster



A new Index Server cluster is deployed when a new installation of Netmail Archive is carried out. All Index Server deployments have a singleMaster server. As the need arises for additional capacity, Slave servers are added to the cluster and registered with the Master server. TheseSlave servers are configured with additional slices for each build group and thus extend the distribution of the index system. The Master server isthen responsible distributing the indexing load across all servers in the cluster (including itself) and will aim to balance the indexes evenly acrossthe available servers.

Prior to deploying a new Index Server cluster, you should establish theNote: 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 file. The dialog box opens.ExaleadClusterManager.exe Exalead Cluster Manager

2. Enter the address, port and port numbers of the Master server.IP Base Gateway

3. Click . After a few seconds, a list of installed index hosts appears under . Initially, this list will only contain the Master server.Connect HostsYou need to register each of the planned Slave servers in order to add them to this list.

If you are implementing a single Index Server, you can skip this registrationNote: process and proceed directly to step 5.



4. Under , enter the address and number (the default port number is 10000) of a new Slave server you want toSlave New Host IP Base Portregister, and then click . Repeat this process for all of your Slave servers. Each time you add a new Slave server, it will be added to theAdd Hostlist 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. Todo so, under , select the first server in the list, and then click .Hosts Configure



6. The dialog box opens. Under , enter the number of processor cores on this host server, and click Slices Configuration Host Parameters Eval. The two text fields under are then automatically populated with the recommended slice counts. Note that for the serveruate Slicesconfiguration

on which you are running the Cluster Manager tool, the number of processor cores is automatically detected.

7. Click . A message confirming the slice numbers that will be applied appears. Click to proceed. The Cluster Manager tool then makesOK Yesthe appropriate configuration changes to the Index Server.



8. Once the configuration is complete, click to dismiss the message confirming that the configuration was a success.OK

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 to commit the changes to the Master server. A message confirmingApplythat the configuration was a success appears. The message also displays the new Index Server configuration version number. Click toOKdismiss 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 theNetmail Administration Console. To perform this install, click in the window.Install/Upgrade Cluster Manager

12. A popup informing you that the Indexing service needs to stop appears. Click to continue.Yes

13. When the install is complete, another popup appears to inform you of this and that the Indexing service has been restarted. Click to returnOKto the window, and then click to exit the Cluster Manager tool.Cluster Manager Close



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 simpleprocess. The Cluster Manager tool is used to register the server and to configure the slice numbers for it. The new Slave server is then installedand started up.

To add a Slave server to an existing cluster, follow these steps:

1. Locate and double-click the file. The dialog box opens.ExaleadClusterManager.exe Exalead Cluster Manager

2. Enter the address, port and port numbers of the Master server.IP Base Gateway

3. Click . After a few seconds, a list of installed index hosts appears under .Connect Hosts



4. Under , enter the address and number (the default port number is 10000) of a new Slave server you want toSlave New Host IP Base Portregister, and then click . Your new Slave server appears in the list of Index Servers under .Add Host Hosts

5. Once you have registered your Slave server, you need to configure the slice numbers for it. To do so, under , select the new Slave serverHostsin the list, and then click .Configure



6. The dialog box opens. Under , enter the number of processor cores on this host server, and click Slices Configuration Host Parameters Eval. The two text fields under are then automatically populated with the recommended slice counts.uate Slicesconfiguration

7. Click . A message confirming the slice numbers that will be applied appears. Click to proceed. The Cluster Manager tool then makesOK Yesthe appropriate configuration changes to the Slave server.



8. Once the configuration is complete, click to dismiss the message confirming that the configuration was a success.OK

9. Once the slice numbers have been configured, click to commit the changes to the Master server. A message confirming that theApplyconfiguration was a success appears. The message also displays the new Index Server configuration version number. Click to dismiss theOKmessage, and then click to exit the Cluster Manager.Close

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) andthe Index server(s).



Netmail Administration Console Settings

Open your web browser, and log in to the Netmail Administration Console. Navigate to the objeArchive > Clusters > Cluster > <Cluster Name>ct and to the tab, as shown in the figure below.Configuration

Under the header, complete the following:Index Servers

1. Under , enter the IP address of your Master Index server.Host

2. Under , enter the base port you specified during installation of your Master Index server. By default, the port number is 10000.Base port

3. Under , enter the gateway port of your Master Index server that you specified during installation. By default, the port number isGateway port10011.

4. Under , specify the maximum number of documents the Master Index server should index before it is considered at fullDocument Capcapacity. The default value of 50 million documents should be used unless you have been advised otherwise by Messaging Architects. As Indexservers near their caps, additional index capacity can be easily obtained by adding additional Slave Index servers.

5. Under , use the button to register details of any Slave Index servers which you have already installed. If at any point in theIndex nodes Addfuture you add a Slave Index server, you must return to the Netmail Archive Administration Console to register the new Slave.

6. Click at the bottom of the screen to save the modified configuration.Save

Proxy Exception Settings on Archive Servers

The Netmail Archive system uses HTTP communication between archive servers and index servers. To avoid degraded performance, it ispreferable that your Master and Worker archive nodes do not use proxy settings to communicate with the Index Server(s). Rather, they shouldcommunicate directly to the Index Server(s). As such, you must add proxy exceptions for each of the Index Server IP addresses to the Internetsettings 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 tab.Connections



3. Select .LAN settings

4. In the dialog box that appears, select .LAN Settings Use a proxy server for your LAN

5. Click .Advanced

6. In the dialog box that appears, enter the requested proxy IP addresses and port information.Proxy Settings

7. In the section, under , enter the IP address of your Index Server(s).Exceptions Do not use proxy server for addresses beginning with

8. Click to close the dialog box.OK Proxy Settings

9. Click to close the dialog box.OK LAN Settings

10. Click to close the dialog box.OK Internet Options

Index Conversion

For organizations upgrading an existing M+Archive system to Netmail Archive, there will be existing indexes from the previous version of theIndex Server (Exalead 4.6). These indexes must be converted to the new Index Server (Exalead CloudView) format if they are to be used by theNetmail Archive viewers.

The Cluster Manager tool and a dedicated Messaging Architects conversion tool are used when converting Exalead 4.6 indexes to CloudViewindexes. 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, , with one slice per 4.6 instance, each of which contains the converted indexes from thebg0corresponding instance. In order to use these converted indexes, you will also need to carry out a corresponding upgrade of the Archive andRemote Provider software to Netmail 5.x version, and ensuring that the archive repository names are exactly the same as those on the M+Archivesystem.

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 existingExalead 4.6 server. The software installs to different directories by default and can co-exist quite happily, although only one index system shouldhave its services running at any time to avoid port conflicts.

The Index Server housing Exalead 4.6 instance “0” typically becomes theTip: 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 made 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. Ensure that you configure slice numbers for the Master Index server as well.Slave Server to an Existing Index Server Cluster”

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 dialog box, next to , indicate the number of Exalead 4.6Slices Configuration Number of 4.6 Instances to be Added to the Hostinstances 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 convertedindexes.



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’ IndexConversion tool.

To run the tool, double-click the file located in .IndexConversionTool.exe C:\Program Files\Netmail Indexing\Netmail Archive Tools

1. On the screen, verify and confirm that you meet all the requirements for index conversion. Click to continue.Prerequisites Next

2. On the screen, complete the following:Specify the locations

Use the buttons to select the appropriate paths to the Exalead 4.6 and CloudView index stores.Browse

Specify the address and number.Master Server IP Base port

Ignore option as this has been deprecated after Netmail 5.1.1. Use Slave Server



3. The screen lists the Exalead 4.6 instances that have been found on the server at the specified path. SelectSelect Index Instances to Convertthe instances that you want to convert (normally all instances are selected). They will be processed sequentially.

The default processing method is , which leaves the 4.6 instances untouched. If, however, you have a limited amount of space on theCopyindexing volume, you may need to change this to the method.Move

Important: Move should only be used if a confirmed backup of the current state of the 4.6 instances exists.

When ready, click to continue. A warning window appears, indicating this is the first run of the conversion tool and that any previouslyNextconverted index data residing on this server will be deleted. Click to continue.Yes



The conversion process now begins. The dialog box appears, indicating that conversion is being initialized.Index Conversion Tool

Once the conversion process has been initialized, the first Exalead 4.6 instance is checked prior to being converted. The Index Conversion Tooldialog 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 CloudViewsystem, as indicated in the Conversion Log.

Once the copying is complete, the files are then converted into Netmail Archive index format.



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.



4. When all instances have been processed, an “Index conversion is done” message is displayed in the Conversion Log, and a popup remindingyou to restart the Netmail Indexing service is displayed. Click OK to dismiss the popup, and then click to exit the Index Conversion tool.Finish

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 IndexServer requires minimal additional administration. However, if you need to log in to the Index Server’s Administration Console to fine-tune ortroubleshoot the Index Server, you can access the console by opening a standard web browser and entering the IP address of the server whereyou installed the Index Server, followed by the search port of 10001. For example, . The interface can be accessedhttp://192.168.1.123:10001from any workstation with access to this IP address and port number. Use the administrator credentials (user name and password) you specifiedduring installation of the Index Server.



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:

Installing Worker Node(s) in a GroupWise EnvironmentPost-Installation Tasks for Worker Nodes

Installing Worker Node(s) in a GroupWise Environment

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 file located in the setup.exe Netmail directory of the distribution. The installation program will guide you through the installation process. Follow the onscreen instructions toArchive

install Netmail Archive Worker node(s) ina GroupWise environment.

On the screen, click to proceed.Netmail Archive Welcome Next

On the screen, carefully review the software license agreement, and then click License Agreement I accept the terms of the license to accept the License Agreement. Click to continue.agreement Next



On the screen, install Netmail Archive in the default destination folder, or browse to the location where you want toChoose Destination Locationinstall Netmail Archive. Click to continue.Next

Netmail Archive does not support installing the Netmail ArchiveImportant: 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 screen is displayed.Cluster Configuration



1. On the screen, select the option. Installing Netmail Archive on a second server will increase theCluster Configuration Install Worker Nodescalability and processing power of your Netmail Archive system.

The first Archive server installed within a deployment should be the MasterNote: 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 , enter the of the computer where you installed the Netmail Archive Master node.Master Configuration IP Address

If your server has multiple IP addresses (e.g., in the case where you areNote: 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 , 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,Portif you opted not to use the default port).

3. Under , enter the of the computer where you are installing the Netmail Archive Worker node.Worker Configuration IP Address

If your server has multiple IP addresses (e.g., in the case where you areNote: 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 field specifies the port number that this node will use for Netmail Archive cluster communications. By default, the port number is 8585. ItPortshould be unnecessary to change this, as Netmail Archive should be installed on a dedicated server. However, you can change the default portnumber based on which ports are currently in use and your network security requirements.


The screen allows you to specify which account you want to use to start Netmail Archive Services. In order to startService Logon InformationNetmail Archive services, the specified account must have local Administrator privileges on the server.



1. On the screen, enter the user account you want to use to start Netmail Archive services. User accounts must beService Logon Informationspecified using the following syntax: DOMAIN\username. Click to browse to the location.Browse

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 , enter the password used to access the account.Password


If there is no domain controller to authenticate against, you mustTip: authenticate locally using the following syntax: .\username.

The screen is pre-populated with the Netmail Archive WebAdmin URL and the port numbers on which the Netmail Unified UI willEnter Valuesoperate. This information does not need to be changed. Click to continue.Next




Once the installation is complete, click on the screen to exit the installation wizard.Finish Wizard Complete

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 connectto the logging database you installed on the Master node. To do so, locate and run the file located in edb_psqlodbc.exe C:\Program files (x86)\Me

.ssaging Architects\PGInstall

The screen appears. Click to continue.Setup psqlODBC Next



On the screen, specify the location in which you want to install psqlODBC. Typically, the default path is used.Installation Directory

On the screen, click Next to begin the installation of psqlODBC.Ready to Install



On the screen, click to exit the wizard.Completed the psqlODBC Setup Wizard Finish

The PostgreSQL ODBC driver has now been installed on your system.

Post-Installation Tasks for Worker Nodes

Once you have installed your Worker node, you must complete a few more steps before you can start using Netmail Archive to create and applyarchive policies.


After completing the Netmail Archive installation, you must start Netmail Archive Services. During the installation program, a shortcut was createdfor you in the Windows menu. To use the shortcut, choose .Start Start > All Programs > Netmail Archive > Start Netmail Archive Services



To start these services manually:

1. Choose from the Windows Start menu.Control Panel > Administrative Tools > Services


3. Locate the service in the list of Services, and click .Netmail Open 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 Masternode 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 shouldconfirm this is still the case by checking the file on the master node.postgresql.conf

To modify the PostgreSQL configuration file:

1. Locate the postgres configuration file . By default, this file is located in on youpostgresql.conf C:\Program Files (x86)\PostgreSQL\9.1\dataMaster node.

2. Open the file for editing in Notepad, and navigate to the section.Connection Settings

3. Make sure that postgres is configured to listen on all interfaces. To do so, ensure that the line is not commented out with a #listen_addresssymbol at the beginning of the line and that the address is set to ‘*’:

listen_address = ‘*’

If you installed Netmail Archive as a Worker node and are using a databaseNote: 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 file in the same folder on the Master node.pg_hba.conf

file:To modify the pg_hba.conf

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

Rather than adding a line for each individual Worker node for which youNote: 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

host all all 0.0.0.0/0 md5format:



Install and Configure Optional WebViewer Component for GroupWiseWebAccess

The Netmail Archive WebViewer is an end-user archive viewer integrated into the GroupWise WebAccess client interface. Once logged in toGroupWise WebAccess, users can toggle between the standard WebAccess view of their GroupWise message store and the Netmail ArchiveWebViewer view of their XML archives. Maintaining the look and feel of GroupWise WebAccess, the Netmail Archive WebViewer allows users toeasily access their XML archives and live mailboxes for a seamless end-user experience. In addition, a search function is available through theviewer 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 theGroupWise WebAccess Application server (i.e., the one running the WebAccess Application component). The WebViewer Applicationextends the WebAccess client interface to include an button which launches the Netmail Archive WebViewer interface. TheArchiveWebViewer Application serves this interface to WebAccess client browser sessions and communicates with the Remote Providercomponent 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 applicationwhen a user starts a WebAccess session. Provided this communication is successful, the button is displayed in the WebAccessArchiveinterface. Once a user clicks the button to enter the WebViewer interface, the Remote Provider acts as a gateway between theArchiveWebViewer Application requests and the archive location(s). As a user navigates through their archive mailbox folders using theWebViewer interface, the WebViewer Application passes requests for archived item information to the Remote Provider. The RemoteProvider communicates with the Index server(s) in order to execute queries identifying where the relevant archived items are stored. Itthen fetches these items from the archive locations for provision to the WebViewer Application and subsequent display in the WebViewerinterface.

In small to medium sized environments, the WebViewer Application should be installed to your existing WebAccess Application server, and asingle Remote Provider should be installed to your Master Archive node. In larger environments, where the prospective user load warrants it, youcan 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 bestto maintain a one-to-one relationship between WebViewer Applications and Remote Providers. This means you would look to deploy as manyRemote Providers as you have WebAccess Application servers. Where multiple WebAccess Application servers have been deployed for reasonsother than user load (for example, you may have two WebAccess Application web servers, one for external access and one for internal access), itis possible to point the WebViewer Applications on which you install the WebAccess Application servers to a single Remote Provider (i.e., youhave 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 balancersystem or such like functionality.

If you feel that your environment may warrant multiple Remote Provider servers or you already have a number of GroupWise WebAccessApplication web servers, and you require further advice on the best approach on WebViewer component distribution, please contact MessagingArchitects.

Installation of the two WebViewer components can be carried out individually or via one combined installation session. The following instructionsare based on the individual component installation method, but indicate how combined installation may be carried out.

Before you install the WebViewer components, you should have aImportant: GroupWise WebAccess system already configuredand running smoothly

After you have installed and configured all the necessary components of Netmail Archive, there are a number of additional components that youcan install to enhance your archiving system.

Installing the WebViewer Application to Your Web Server

These instructions apply to installation of the WebAccess Application on aNote: 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.



If you install a new version of Novell WebAccess after installing theNote: WebViewer Application, WebAccess might overwrite webacc.cfg the customizations that the WebViewer installation program applied to the 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 Applicationserver drive or a volume containing the WebAccess Application files (normally the SYS volume on NetWare or the C: drive on Windows).

Navigate to the folder of the Netmail Archive distribution files and run the file.WebViewer setup.exe

The installation program will guide you through the installation process. Follow the onscreen instructions to install the WebViewer. On the Netmail screen, click to proceed.Archive WebViewer Welcome Next

On the screen, browse to the location of the file. The WebViewer installation program willGW WebAccess Configuration webacc.cfgautomatically write custom parameters to this file, and therefore needs to know its location.

The default location of the file varies according to platform. Some examples of default locations are:webacc.cfg

Windows: C:\Novell\Webacc\Webaccess

Netware: \\server\SYS\novell\webaccess



Linux: opt/novell/groupwise/webaccess

Under , browse to the location of the WebAccess templates folder. The default location of thePath to folder with WebAccess Template filesfiles 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 , browse to the location of the WebAccess images folder. The default location of the image filesPath to folder with WebAccess Imagesvaries 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

The number “200908180251” in the path is specific to the installation, so itNote: will change from system to system.

If you are installing to a GroupWise 2012 WebAccess Application server, ensure to select the checkbox.GroupWise 2012

After finding and selecting the requested folders, click to continue.Next

At this stage, the Netmail Archive WebViewer installation program asks if you would like to also use this installation session to install the RemoteProvider onto the local machine. This is the combined installation method mentioned earlier. You should only select this option if you intend toimmediately install the Remote Provider component on the machine from which you are running the WebViewer installation program. See “Installi

for further information on the Remote Provider installation screens that will be displayed if young the GroupWise Remote Provider Component”select this option.

For installation of only the WebViewer Application component at this stage, on the screen,Remote Provider and Proxy Access Configurationdeselect the checkbox.Install the Remote Provider on local machine

It is still necessary to provide the configuration information in order to inform the WebViewer Application to know how to contact the RemoteProvider once it is installed:

1. Under , enter the IP address of the server on which you will be installing the Remote Provider.Remote Provider Server IP

2. Under , enter the TCP/IP port number that the Remote Provider will listen on for requests from the WebViewer.Remote Provider Port

3. Under , enter the IP address of your SMTP Server (i.e., your GroupWise GWIA server).SMTP Server IP



The WebViewer interface allows users to Forward items out of theImportant: 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 if you want to enable proxy access to your archives through the WebViewer. When set, theEnable Proxy Access to ArchivesWebViewer will make use of GroupWise proxy permissions to allow WebAccess users who proxy into another account to also be able to accessthat account’s archive mailbox.

On the screen, click to install the Netmail Archive WebViewer.Ready to Install Install

A progress screen is displayed as the required files are copied to the WebAccess Application server and the file is modified. Once thiswebacc.cfgis complete, the screen is displayed. Click to exit the installation program.Wizard Complete Finish

In order to load the WebViewer Application you have just installed, it is necessary to restart the Tomcat service on your GroupWise WebAccessApplication 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 . Allow it to shut down Tomcat, and then run to restart Tomcat services.tc4stop tomcat4



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 canbe 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 aWindows 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 theGWXMLV_css folder and the GWXMLV subdirectory you created.

3. In the ../templates/css/ folder on the Linux system, rename to . Copy the file from WebViewer\Programcaption.htt caption.htt.old caption.httFiles\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 GWXMLVsubdirectory you created.

9. Navigate to the WebViewer\Program Files\Messaging Architects folder, and copy the file to the /opt/novell/groupwise/webaccessgwxmlv.cfgdirectory on the Linux system.

10. Modify the file by editing the following entries:opt/Novell/GroupWise/WebAccess/gwxmlv.cfg

Provider.Server.IP= <IP of server running provider>Provider.Server.Port= <Provider port (default 6666)>

11. Modify the file by appending the following text to the end of the file:var/Novell/GroupWise/WebAccess/webacc.cfg

################################################################################TMA: Added for GWXML WebViewer Provider################################################################################------------------------------------------------------------------------------

http://www.winscp.net



# 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 file into thevar/opt/novell/gw/WEB-INF/classes/com/novell/webaccess/templates/css/fldricon.incvar/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 installationprocess, Messaging Architects recommends that you download WINscp, an open source SFTP Client for Windows that allows you to drag filesfrom 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 respectiveGWXMLV subdirectory you created.

3. In the ../templates/css/ folder on the Linux system, rename to .caption.htt caption.htt.old

For SLES 10, copy the file from WebViewer\Program Files\Messaging Architects\GWXMLV8 folder in the distribution tocaption.htt/srv/www/tomcat5/base/webapps/gw/WEB-INF/classes/templates/webacc/css.For SLES 11, copy the file from WebViewer\Program Files\Messaging Architects\GWXMLV8 folder in the distribution tocaption.htt/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 theprevious 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

http://www.winscp.net



The number “201010290421” in the path is specific to the build ofNote: 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 file to the /opt/novell/groupwise/webaccessgwxmlv.cfgdirectory on the Linux system.

10. Modify the file by appending the following text to the end of the file:var/Novell/GroupWise/WebAccess/webacc.cfg

################################################################################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 file by editing the following entries./opt/Novell/GroupWise/WebAccess/gwxmlv.cfg

Provider.Server.IP= <IP of server running provider>Provider.Server.Port= <Provider port (default 6666)>

12. For SLES 10, copy the file into the/srv/www/tomcat5/base/webapps/gw/WEB-INF/classes/templates/webacc/fldricon.inc/srv/www/tomcat5/base/webapps/gw/WEB-INF/classes/templates/webacc//css/GWXMLV folder.

For SLES 11, copy the file into the/srv/tomcat6/base/webapps/gw/WEB-INF/classes/templates/webacc/fldricon.inc/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 anArchive node. The server chosen must have the ability to communicate with the WebAccess Application server where the WebViewer Applicationhas 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 SearchRemote Provider, which is used by the Netmail Search archive viewer utility and other Netmail Archive components in a similar way that theWebViewer Application uses the GroupWise Remote Provider.

See for full instructions on installing the GroupWise Remote Provider as part of“Install and Configure the Remote Provider(s) for Netmail Search”the Remote Provider installation process. The key point to note in the installation process is on the screen. YouRemote Provider Configurationmust ensure that the option is selected in order to install the GroupWise Remote Provider in addition to theInstall GroupWise Remote ProviderRemote Provider used by Netmail Search.



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 inorder for the WebViewer component to function properly.

Starting the GroupWise Remote Provider Windows Service

The GroupWise Remote Provider runs as a Windows service named . On each server where you haveNetmail Archive Remote Providerinstalled the GroupWise Remote Provider, you need to start this service.

1. To start services manually, choose from the Windows menu.Control Panel > Administrative Tools > Services Start


3. Locate the service in the list of Services, and click .Netmail Remote Provider 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 communicationsfrom the Web server. When the server running the Remote Provider is configured with two NICs and has two different IP addresses on differentsubnets (such as NAT), you need to specify which on which address the Remote Provider should listen.

1. On the Remote Provider server, open the file located in .xgwxmlv.cfg 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 file, and then restart the Netmail Remote Provider service.xgwxmlv.cfg



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 stubbingfunction.

Stubbing is available for GroupWise 8. For GroupWise 8 environments,Important: 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 archivedmessages directly from the GroupWise Client. The communication between the POA and the SA is based on SOAP over HTTP. The SA alsocommunicates with the Netmail Archive Index Server over HTTP.

To install the Stubbing Agent, navigate to the Stubbing Agent folder, and run the file.setup.exe

The installation program will guide you through the installation process. Follow the onscreen instructions to install the Stubbing Agent. On the Net screen, click to proceed.mail Archive Stubbing Agent Welcome Next

On the screen, install the Stubbing Agent in the default destination folder, or browse to the location where youChoose Destination Locationwant to install the Stubbing Agent. Click to continue.Next



On the screen, enter the required information:Stubbing Agent Configuration

1. Under , enter the IP address of the server on which the Remote Provider is installed.AWA RemoteProvider IP

2. Under , enter the port number on which you configured your AWA Remote Provider service to listen (8888 byAWA RemoteProvider Portdefault).

3. Under , enter the name of the Trusted Application key.Name

4. Under , you should enter the and of an existing GroupWise Trusted ApplicationGroupWise Trusted Application Parameters Name Keyentry. It is recommended that you use the same Trusted Application entry that you configured for Archive server access to GroupWise.

If you no longer have them recorded, the details of the TrustedTip: 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 to continue.Next



On the screen, click to begin the installation. The installation should take only a few moments.Ready to Install the Program Install

On the screen, click to complete the installation process.Wizard Completed Finish

Configure Stubbing for GroupWise 8

After successfully installing Netmail Archive and the Stubbing Agent in your GroupWise environment, there are several steps that must beperformed 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 RetentionService. Complete the following steps to do so:

1. Open ConsoleOne and connect to the GroupWise system.

2. From the menu, select .Tools GroupWise System Operations > Trusted Applications



ConsoleOne needs to have GroupWise snapins loaded and the GroupWiseTip: system needs to be selected in order for theseoptions 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 and .Provides Message Retention Service Allow Access to Archive Service

5. Click the pencil icon next to the textbox to edit the field. In the field, enter the IP address orArchive Service Address Archive Service portDNS 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 adefault 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 fromthe menu, select .Tools GroupWise System Operations > System Preferences

Select the tab. In the dropdown list, select the Trusted Application entry which you configured as a Message RetentionArchive Service SettingsService.

In some scenarios you may prefer to have multiple Stubbing Agents installed (for example, if you have GroupWise POAs running in multiplelocations and want them to access a Stubbing Agent locally). In such a scenario, you need to configure separate Trusted Application entries foreach Stubbing Agent and then use GroupWise Post Office overrides to direct any Post Offices to the Trusted Application entry for their localStubbing Agent rather than the System Preference setting.

To apply Post Office overrides in ConsoleOne:

1. Right-click on the object and select . Note that it is the object you click, not the .Post Office Properties Post Office POA

2. From the tab, select .GroupWise Post Office Settings

3. Under , select , and from the dropdown list, select the Trusted Application entry that you haveDefault Archive Service Application Overrideset up for the Stubbing Agent that will be used by this Post Office.



4. Click to save the changesOK

Multiple SAs can be defined. For example, for heavy-load systems, where itNote: 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 theProgram Menu.

When run for the first time, the SA’s window will appear. Most of the values will be populated with default settings or with theConfigurationsettings 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 SAwill listen. The local host IP (127.0.0.1) is added to the list by default.

Check all other settings, and then click to save the configuration.OK

After stubbing has been configured in GroupWise, end users will be able to view stubs directly from the GroupWise Client. A small stubbing iconwill differentiate stubbed items from non-stubbed items in the GroupWise Client. The following diagram shows the stubbing icon:



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 andindexing engine. Through the installation of the Remote Provider, users and superusers will be able to open Netmail Search and view archivedmessages directly. In addition, the Remote Provider installation process also provides the means for installing the additional GroupWise RemoteProvider which is used by the WebViewer component to provide archive access through GroupWise WebAccess.

In this section:

Installing the Remote Provider(s)Remote Provider Post-Installation TasksAdditional Configuration for the Remote Providers

Installing the Remote Provider(s)

To install the Remote Provider(s), navigate to the WebViewer folder in the Netmail Archive distribution, and then run the file.RemoteProvider.exe

The installation program will guide you through the installation process. Follow the onscreen instructions to install the Remote Provider. On the Re screen, click to proceed.mote Provider Welcome Next

On the screen, install the Remote Provider in the default location, or browse to the location where you would likeChoose Destination Locationto install the Remote Provider. Click to continue.Next



On the screen, enter the requested information for configuration.M+Open and Jexcon Configuration

1. Under , enter the IP address of the Master Archive server. This will be used by Netmail Search when carrying outNetmail Archive Master IPexport jobs.

2. Under , enter the port number used by the Master Archive server for Netmail Archive Cluster communications.Netmail Archive Master PortThis should be the default value of 8585 unless you modified it during installation.

3. Select or , depending on your version of GroupWise.Novell GW 8 or higher Novell GW 8 or lower

4. Under , if you have deployed or plan to deploy the Stubbing Agent, enter the address.Trusted IPs Stubbing Agent IP


The Remote Provider screen lets you configure how the Remote Provider will access the directory server usingLDAP Connectivity ParametersLDAP.

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.



1. Under , enter an IP address of a local eDirectory LDAP server.LDAP Server IP Address

2. Select if you require a secure (SSL) connection between Netmail Archive and the eDirectory tree. If you enable SSL, the default PortSSLNumber 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 , specify the account name with administrator rights to the eDirectory section where the Netmail ArchiveAdministrator Common Nameconfiguration objects were stored. This is the account that was created as part of the prerequisites prior to installation. See "Administrator Rights

for details.and Accounts"

4. Under , specify the password used to access the account.Administrator Password

5. Under , specify the path to the container where you created the Netmail Archive objects in eDirectoryeDirectory Configuration Containerusing 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 RemoteProvider, and as such, it needs to know which eDirectory containers to look up to find user objects. Under , list the contexts ofUser containereach eDirectory container which holds user objects for users you wish to be able to use Netmail Search.

The space in this field of the installation wizard is limited, so you may notNote: 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 if you want the installation program to validate the information provided.Perform validation


On the screen, you can configure the Remote Provider.Remote Provider Configuration



1. Under , select if you want this installation to also install the RemoteGroupWise Remote Provider Install GroupWise Remote ProviderProvider used by the WebViewer component (see for more"Install and Configure Optional WebViewer Component for GroupWise WebAccess"information about the WebViewer). The GroupWise Remote Provider is needed so that WebViewer can access the Index and retrieve archiveditems. If you select this option, you must also specify the for the GroupWise Remote Provider. When specifying theProvider Service PortTCP/IP port number, be sure to match the setting you used when you installed the WebViewer Application component.

When you select the option to install the GroupWise Remote Provider, theNote: 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, ensure that is selected.Remote Provider Install M+Analytics/AWA

3. Under , enter the TCP/IP port number on which the Remote Provider will listen for requests from Netmail Search. The default valueAWA Portof 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 screen, specify which Windows account you want to use to start Remote Provider services. In order to start NetmailLogon InformationArchive services, you must have local Administrator privileges on the server. Click to continue.Next




On the screen, click to complete the installation.Wizard Complete Finish



After you have clicked in the Remote Provider installation wizard, you are prompted as to whether you would like to create the keystoreFinishnecessary for SSL communications. Even if you do not plan to use SSL for Remote Provider communications, it is good practice to completethese steps.

On the first popup that refers you to the Netmail Archive Installation Manual for instructions on configuring certificates, click .OK

On the popup, click to proceed with keystore generation.Question Yes

On the screen, enter a password to be used for this process. Note that any random password will suffice, and this passwordCreating a Keystoredoes not need to be recorded.



Click to proceed with keystore generation. A command window briefly appears while this is being carried out. Once the command windowNextcloses, the process is complete.

Remote Provider Post-Installation Tasks

After completing the Remote Provider installation program, there are several post-installation tasks for you to complete in order for NetmailSearch to function properly.

Starting Windows Services

The Remote Provider runs as a Windows service named . The GroupWise Remote Provider, used byNetmail AWA Remote ProviderWebViewer, runs as a Windows service named . On each server where you have installed the Remote Provider, youNetmail Remote Providerneed to start the appropriate services.

1. To start services manually, choose from the Windows menu.Control Panel > Administrative Tools > Services Start


3. Locate the service in the list of Services, and click .Netmail Remote Provider Start

4. Locate the service in the list of services. Stop and then restart the service.Netmail AWA Remote Provider

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 serverrunning the Remote Provider is configured with two or more network interfaces and has two different IP addresses on different subnets (such asNAT), you need to specify on which address the Remote Provider should listen.

1. On the Remote Provider server, open the file located in .xgwxmlv.cfg 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 made to the file, and then restart the Netmail AWA Remote Provider service.xgwxmlv.cfg

Additional Configuration for the Remote Providers

It is possible to modify some of the default settings used by the Remote Provider and GroupWise Remote Provider in order to change behavior ofthe 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-UserDelete should be used with caution. With this feature, items are permanently deleted from the archive, but the audit files are kept for eDiscoverypurposes. 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 and open the file.C:\Program Files\Messaging Architects\RemoteProvider, xgwxmlv.cfg

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 archivesthrough 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 button will appear in users’ Netmail Archive WebViewer or Netmail Search interface.Delete

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 thedropdown lists of several fields in the tab of both the and dialog boxes can be renamed or deleted. NewCase Info Create Case Edit Caseoptions 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 singlequotation marks and separated by a comma.

4. After modifying and saving the file, restart the Netmail AWA Remote Provider service.

In the tab of the and dialog boxes, the options in the dropdown lists of the Status, Case Class, Case Type, andCase Info Create Case Edit CaseCase Sub Type fields can also be customized.



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 followingformat: [['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 newitem, as it appears in the dropdown list.

4. After modifying and saving the file, restart the Netmail AWA Remote Provider service.



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 therecommended 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 PostgreSQLThere is corruption or other problems with the databaseThe 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:



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 andattributes which are then used by the Netmail Archive eDirectory objects. The installation process also creates the core Netmail ArchiveeDirectory 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 ifthere was a problem with your LDAP server, then it is possible that the eDirectory schema was not extended properly during the Netmail Archiveinstallation, 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 canmanually extend the schemas and create the basic Netmail Archive configuration objects using batch files provided for you. If you installedNetmail Archive in the default location, then these batch files can be found under C:\Program Files\Messaging Architects 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 . The Tools > Schema Manager Schema window opens, listing the present in your tree. Verify that the ma object classes are listed as in the figure below:Manager Classes

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 tab, and verify that the ma attributes are listed, as shown in the next figure:Attributes



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 purposeduring installation.

Following installation, you can confirm the existence of the core objects in eDirectory by using ConsoleOne. Simply browse to and expand thecontainer specified during installation and check for the existence of the objects shown in the following figure:



If the objects do not appear, use the manual process described below toNote: 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 , and then type to open a command line prompt.Start > Run cmd

2. If you installed Netmail Archive in its default location, navigate to the folder.C:\ProgramFiles\Messaging Architects\WebAdmin\mSetup

3. To extend the schemas, enter (e.g., ). The specifiedCreateSchema<username> <password> CreateSchema admin.org password123must have administrative rights to the tree).

To create the core Netmail Archive Objects, enter (e.g., ). TheCreateMaster <username> <password> CreateMaster admin.org password123specified 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 existingeDirectory objects will be automatically upgraded during installation. If you encounter any errors during the upgrade, however, you may need toperform additional manual upgrades to the existing eDirectory objects using the file provided for you. If you installed NetmaileDirUpgrade.exeArchive in the default location, then the file can be found under .C:\Program Files\Messaging Architects C:\Program Files\Messaging Architects

To use the eDirUpgrade.exe file:

1. Choose , and then type to open a command line prompt.Start > Run cmd

2. At the prompt, type the following line using the syntax provided, substituting your organization’s credentials for the placeholders used in the



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)



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 electronicdiscovery, 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 getthem 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 integrityand data recoverability.

Throughout the years there have been many different technologies for ensuring electronic data integrity and while most are still available, the typeof 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 messagecontaining 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. Inaddition, any attachments which may have been part of the original message are stored as binary attachments and linked to the original messagethrough 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 messageis usually about 4kB, which is the equivalent of almost 500 words. Adding attachments, graphics and templates to a message account for almost99% of the actual message size.

Audit files contain message metadata indicating message chain of custody, message security and message auditing data and are typically only1-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,500messages/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 ofmessages, and consequently the number of files retained on the file system, quickly becomes a huge number. This needs to be taken intoconsideration 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. Indexesare 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. Thismakes 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 forthe 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 istherefore imperative that when backing up the indexing system, that there are no indexing processes currently running, else the indexes would bebacked 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 thesource 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 ona scheduled basis. To do this, the system creates a timestamp so it understands when the last indexing job was run and therefore only indexesthat 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 fullyregenerate indexes if having to restore from a disaster. The recommendation would be to back up the index server once per week and thereforeonly 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, Exaleadservices 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 uselinear storage as opposed to random write and seek which is provided by hard drives. The main issue with tape backup is with the software. Tapebackup software provides for different types of backups including full backup and incremental backup. Obviously it is not logical to backup 40 TB



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 backupsystems 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 thebackup 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 systemscontaining millions of files, this process of scanning the file system can take a very long time and jeopardize the ability to even obtain anincremental 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 onevery 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 listof 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 thereforecould be a potential discovery liability. With incremental backups, you will be forced to maintain an original full backup and therefore this presentsloopholes 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 fastermedia, the backup can be conducted at a much faster rate thus reducing the backup window and impact to production systems. Once thebackups are on a secondary storage system, they can be moved to tape for off-site storage. Like tape backup, the critical component is thesoftware to run the job. Products designed for this such as Commvault® and other enterprise software packages provide for journal basedbackup.

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 torecord destruction policies.

If you cannot guarantee limited retention of the backed up items on disk or tape, then this media should not be used.Note:

SAN Replication and Snapshot

Many of today’s sophisticated Storage Area networks have built in fault tolerance and redundancy capabilities. While most SANs can beconfigured with advanced RAID configurations (Redundant Array of Inexpensive Disk) including RAID 10 which effectively duplicates all data andprovides 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 thesecondary device. In this case one needs to use backup or if the SAN architecture permits, snapshots. A snapshot is a backup function of theSAN. 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 canbe restored to that exact point in time. Snapshots are much more efficient than backup, can be performed very quickly and can be performed onlive data systems. The only issue with snapshots is the storage overhead they require. Snapshooting a SAN LUN generally takes more spacethan performing a snapshot on a files system which is why snapshots on devices like NetApp Filer with a CIFS (Windows File System) module willtake 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 archivedwhen 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 withyour policies and requirements to determine the best frequency for taking snapshots. It should correspond to the criticality of restoration and dataaccessibility.

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 storedon the device as objects with each object having a set of metadata which defines the properties of the data. Netmail Store is designed toautomatically maintain and backup data without administrator intervention or management. As each piece of data is written to the system, thesystem 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 becomecorrupt. The system also automatically replicates the data into 2 or more copies and distributes them across several different nodes or disk driveswhich can be local or located in a separate disaster recovery site. The system manages itself and in the event of a hardware failure, the systemwill begin to replicate all files which existed on the failed device to ensure it always maintains multiple copies. In the event of corruption, thesystem will automatically repair the corrupted file by using a valid copy. This particular system maintains a real-time backup automatically, alwayskeeping a copy of files. The system only allows for Writing, Reading and Deleting of files and does not allow for the modification of existing filesthus eliminating any risk of file overwrites or changes. If required, it supports WORM storage whereby a file can be locked against deletion for aspecified 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 allcopies are destroyed.

Conclusion

Backup of archive data is critical not only because it included irretrievable corporate information but because organizations maintaining data underlitigation hold can be severely penalized by the courts for not adequately taking actions to protect the data. Organizations need to adopt the best



and most effective methods for guaranteeing data integrity. From a preferred list of solutions, Content Addressable Storage is the first choice forArchive data backup, with SAN Replication/Snapshot second and disk/tape backup as a last choice. Not backing up the data is not an option. Forindexes, most existing backup solutions will suffice as long as care is taken not to backup during system operations.



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 causedata 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, thesoftware 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 andcan increase the complexity of troubleshooting issues. The AV software should be installed only after the Archive components have been installedand fully validated. If, after installing AV software, there are issues, they can be attributed to the AV software. Try to avoid installing port-blockingAV products.

All mailstores contain files with viruses that were not caught by updated virus scanners when delivered. Most of these files would be caught withthe updated software running on the client if they were accessed. DO NOT use Messaging Architects servers as a method for scanning anderadicating viruses from the Archive system or email during the archive process. This only slows down the archive process and causes infectedfiles to be quarantined or deleted, which causes broken link messages. Exclude Archive Temp Folder and Attachment storage folder from Virusscanning. If you wish to remove viruses from the Archive store, run this as a manual scanning process either from the Archive server when noarchive 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 fromcommunicating with the Archive servers and infecting them. The only client access to Archive servers required is that for the Outlook Plugin overport 8443 to the Remote Provider service or server.

Netmail Archive 5.2 Installation Guide for Novell GroupWise

Documents

Transcript of Netmail Archive 5.2 Installation Guide for Novell GroupWise