GroupWise: Protocol Flow Diagram...

1 Likes

One of your Strategic Services Architects put this diagram together a few months back and I thought it is an excellent resource to share.

This diagram illustrates how a GroupWise system should be configured to ensure proper message flow, agent communication and system access.


A few notes to know while viewing this diagram.

    • The port assignments are 'defaults', most are configurable.

 

    • Communication between agents/services is bi-directional. The arrows simply indicate where the IP session is initiated from.

 

    • Not all of the Web Console ports for all agents are displayed. This is for simplicity. There is one example, but the other agents also have Web Console Ports.

 

    • This diagram is intended to show as many configurations as possible. Obviously, your GroupWise system may not have every component and it will be less complex.



There are also sub-sets of this diagram in the GroupWise Documentation. They show message flow for several different configurations, user to user, administrative messages, etc.

Here is the link:

This information is very useful as you configure your system, troubleshoot port conflicts, validate standard practices and look for message flow problems.

The architect, Ed Hanley, tried to represent enough of the system to give an administrator all of the information he/she would need to assess protocol flow. Multiple MTAs, GWIA's, WebAccess and Post Offices configurations are represented. Also the interaction with Novell Instant Messenger, GroupWise Mobility Pack, BlackBerry Enterprise Server and Monitor. In addition to port numbers and connections, Ed also conveniently identified the type of protocol each connection is using: MTP, WAP, SOAP, TCP, CP, UDP, SMTP, ActiveSync, etc.

Let us know if you have questions or need further clarifications.

Dean

Labels:

Collateral
How To-Best Practice
Comment List
Anonymous
Parents
  • Some have questioned the protocol flow from the GWIA gateway service on the diagram.

    The GWIA has four services of SMTP, POP, IMAP and LDAP.

    The SMTP service when sending and receiving messages uses the path to the MTA that owns the gateway via the UNC and MTP path. Its a store and forward transport of the messages.

    The POP and IMAP services use the C/S 1677 tcp path which goes direct IP to the various GWPOAs where the users mailbox resides. Its a real time live connection to the users mailbox. The path through the MTA is not used in this case.

    The LDAP service uses the UNC path to the MTA that owns the gateway via the UNC path. It does a look-up within the DB file to satisfy the LDAP query.

    There you go.
Comment
  • Some have questioned the protocol flow from the GWIA gateway service on the diagram.

    The GWIA has four services of SMTP, POP, IMAP and LDAP.

    The SMTP service when sending and receiving messages uses the path to the MTA that owns the gateway via the UNC and MTP path. Its a store and forward transport of the messages.

    The POP and IMAP services use the C/S 1677 tcp path which goes direct IP to the various GWPOAs where the users mailbox resides. Its a real time live connection to the users mailbox. The path through the MTA is not used in this case.

    The LDAP service uses the UNC path to the MTA that owns the gateway via the UNC path. It does a look-up within the DB file to satisfy the LDAP query.

    There you go.
Children
No Data
Related Discussions
Recommended