Help Center

Knowledge Base

[DOC:Netmail Documentation]

Documentation for Netmail Archive 5.4.
Documentation for [Netmail Archive 5.3] and [earlier versions of Netmail] is also available.

Skip to end of metadata
Go to start of metadata

The Configuration tab of each Netmail Archive cluster displays software version, messaging server type, and network address information about Netmail Archive. The Configuration tab also allows you to edit the settings for your Index Server(s), to test your Index Server connectivity, and to configure your default log settings. For more information about configuring default log settings, see Specifying Default Log Settings.

In the Netmail Administration Console, select the Archive > Clusters > <Cluster Name> object in the tree. By default, the Configuration tab is displayed.


 On this page:

Reviewing Product Information

The About section of the Netmail Archive Administration Console displays software version, server type, and network address information about Netmail Archive.

Software Version

Under Software version, you can verify which version of Netmail Archive is installed on your system.

Network Address

Under Network Address, the IP address of the Netmail Archive server which is running the Netmail Administration Console service to which you are connected (typically the Master archive server) is listed.

Messaging Server Type

This setting displays the mail system type to which Netmail Archive is connected, Novell GroupWise or Microsoft Exchange. If you are using Novell GroupWise as your collaboration system, you have the option of choosing from the following standard GroupWise connectivity methods: GroupWise Object API or GroupWise SOAP API.

  • Object API: GroupWise Object API (or simply OAPI) was introduced by Novell in early versions of GroupWise for connectivity by third-party applications. The OAPI code is embedded within the GroupWise client. As such, to access and use the GroupWise Object API with Netmail Archive, you must have a 32-bit version of GroupWise installed on your archive servers.
  • SOAP API: The GroupWise SOAP API was introduced as an additional connectivity mechanism by Novell in GroupWise 7 and above. It uses the industry standard SOAP protocol to directly communicate with the GroupWise Post Office Agent (POA). SOAP connectivity must be enabled on your POAs in order for you to be able to use this connectivity method. In addition, stubbing functionality requires the use of SOAP API.

Netmail recommends the use of SOAP connectivity for GroupWise 7.02 and above, and OAPI for any earlier versions of GroupWise. If you want to dynamically switch to GroupWise SOAP API through the Netmail Administration Console, you must be running GroupWise version 7.02 or higher and you must have specified a SOAP Port for your primary POA connection during the Netmail Archive installation.

Index Servers

Netmail Archive features a powerful Index Server that performs indexing and enables searching of archived data to allow you to quickly retrieve archived email. During the Index Server portion of the Netmail Archive installation, you specified various network communication ports to be used by the Index Server(s). After installing the Index Server(s), you must configure the Index Servers settings on the Configuration tab in the Netmail Administration Console to inform your archive servers how to connect to the Index Server(s). For most installations, the default ports are used. Select No index server if you are not using an Index Server.

Master IP

Under Master IP, indicate the IP address where you installed your Master Index Server.

Base Port

Under Base Port, enter the port number configured as the base port of your Master Index Server (default is 10000).

Gateway Port

Under Gateway Port, enter the port number configured as the gateway port of your Master Index Server (default is 10011, or if you altered the base port, it will default to the base port value plus 11).

Document Cap

As more and more archived data is indexed, your indexes grow as well. Larger indexes require more processing when they are added to or searched. As such, each Index Server has an operational maximum number of documents that can be indexed before performance starts to significantly degrade. The number of documents varies depending on an Index Server’s resources (mainly RAM and CPU).

To avoid overloading any Index Server, Netmail Archive allows you to specify a limit to the number of documents which can be submitted to it for indexing. Once an Index Server has reached its cap, its existing indexes can still be searched, but no new data will be submitted to it for indexing.

Under Document Cap, enter the maximum number of documents allowed for to be submitted for indexing by your Master Index Server. The default value is set to 50 million documents. You can increase this limit if you reach the limit and see that your Index Server still has spare CPU and memory capacity during index operations, or you can decrease the limit if your Index Server is maxing out on resources before reaching the current cap.

Update Only

If you have an Index Server that you believe has reached maximum capacity or you simply do not want it to receive any more index data, then the Update Only setting will allow you to manually flag that Index Server so that it does not receive any more data for indexing. The server will still be updated when archived data is deleted or re-indexed, hence the setting name of Update Only. Selecting Update Only will apply this setting to your Master Index Server.

Worker Servers

The Worker Servers field allows you to add, edit, or remove Worker Index Servers, or “nodes.” You must add an entry for an index node whenever you add a new Worker server to the index cluster.

  • Add: Click Add to add a new index node. In the Index Node Configuration dialog box, enter the IP address and the Document Cap for the new Worker server. Use the Update Only option if you want to prevent any more data from being submitted to this Worker server for indexing. Click Save.
  • Edit: To edit an existing index node entry, highlight the index node in the list of available nodes, and click Edit. Edit the fields in the Index Node Configuration dialog box as required, and then click Save.

  • Remove: To remove an index node, highlight the index node in the list of available nodes, and click Remove. This should only ever be done if you have actually removed the Slave Index Server from your index cluster.

Testing Index Server Connectivity:

Click Test connections to index servers to verify that the Master archive server can successfully contact your Master Index Server using the settings provided. When you are finished configuring your index servers, Click Save to save your configuration settings.

Important: If you do not click Save, any configuration changes will not be saved when you navigate to a different tab.

  • No labels