Knowledge Base Home

Call Support


Search the Knowledge Base

Skip to end of metadata
Go to start of metadata

Environment

 

Netmail Archive 5.3 with GroupWise 8 (and higher)

Synopsis

This article will describe the fields in the different GroupWise Address Book contact categories that are collected by the Netmail Migrator after connecting to the GroupWise mail system using either SOAP or OAPI. These items are subsequently injected into O365/Exchange 2013 so they are accessible to end users.

Solution

Before GroupWise data can be injected into O365\Exchange 2013, it must be converted by Netmail Archive to XML format as illustrated in the following diagram:


GroupWise 8.0.2 data to Netmail 5.3.x XML format into O365


There are two protocols that can be used by Netmail to connect to the GroupWise mail system to Extract GroupWise data:

  • OAPI (Object API), used to enable inter-process communication and dynamic object creation in a large range of programming languages, i.e., it is a language-neutral way of implementing objects that can be used in environments different from the one in which they were created. Note that if OAPI is implemented, it will scan items in a GroupWise mailbox, but will not provide any markup information about whether or not those items are accessible.

     

  • SOAP (Simple Object Access Protocol), used to exchange structured information when implementing web services. SOAP relies on Extensible Markup Language (XML) for its message format and usually relies on other Application layers protocols, most notably HTTP and SMTP for message negotiation and transmission.

 

Both protocols are made available by the Novell GroupWise Post Office Agent. The differences between SOAP and OAPI are highlighted in this article.

 

Migrating Address Book Contact Fields & Categories

Table 1 below lists the GroupWise address book contact fields collected and migrated to Outlook 2013/O365 using version 5.3.0.1439 of the Netmail Archive migrator (with either SOAP or OAPI). The column on the right lists the address books/contact categories that are migrated to Outlook/O365. Note that for this migration to succeed, the GroupWise client must be deployed when OAPI is in use, but this is not necessary if using SOAP.

 

     Table 1.     Address Book Contacts Field Migration Table

Address Book Migration Category

Fields Collected and Migrated Using SOAP

(doesn't require the GroupWise Client)

Fields Collected and Migrated Using OAPI

(requires the GroupWise Client)

O365-Migrated Contacts
Address Books
  • All Address Books Migrated except System Address Book

  • Frequent Contact migration is optional

  • All Address Books Migrated except System Address Book
  • Frequent Contact migration is optional
  • Separate address books are migrated to Outlook as separate address book folders

External Contacts (in a Group)

 
  • Email Address and 'Display as' (*see table footnote) are the only fields collected 
  • Email Address and 'Display as' (*see table footnote) are the only fields collected 

  • All other fields are populated from the Global Address List (GAL) in Exchange if there is a matching user 
Shared Address Book
  • All contacts are collected if address book is owned by user
  • All contacts are collected if address book is owned by user
  • Address book and contacts are migrated to Outlook as a personal address book
Individual Contacts
  • All populated contact fields are collected as per   Table 2 (below)
  • All populated contact fields are collected as per  Table 2 (below)
  • All populated contact fields are collected as per Table 2 (below)

Group Contacts (Personal Distribution Lists)

  • Email Address and 'Display as' (*see table footnote) are the only fields collected
  • Email Address and 'Display as' (*see table footnote) are the only fields collected
  • Netmail creates distribution lists in Outlook and performs lookups against GAL       to change the GroupWise formatted addresses to Exchange format
  • All remaining fields within the contact are populated from the GAL
Organization Contacts
  • Email Address, Comments, Description, Street Address, Phone and 'Display as' (*see table footnote) are the only fields collected

  • Email Address, Comments, Description, Street Address, Phone and 'Display as' (*see table footnote) are the only fields collected
  • There is NO corresponding Organization / Company object in Outlook
  • All contact properties in Outlook are associated with a user contact
  • Organizational contact information is migrated as individual contacts
Resource Contacts
  • No data is collected
  • Name, phone, type, email address and Owner are collected
 
 


Notes


Help us improve!
Is this article helpful?
Is it well written?
Is the content complete?

  • No labels