GroupWise: Protocol Flow Diagram...

GroupWise: Protocol Flow Diagram...

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
Attachments

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Comments
Dean,

Excellent presentation of what can become a complex system! I have one simple request... Publish the original files used to build this diagram so we can use this as a base to diagram our own systems. Visio is a very common tool for building such diagrams and a Visio project we could use as a template would be wonderful!

Thanks!
Hi,

You can find the VISIO files for GroupWIse here : http://www.gwcheck.com/wpml/?p=718
or as well via the Freeware URL for GroupWIse : http://freeware.gwcheck.com

Gert
GWCheck.com
I also would like to see the original Visio file published like jburrell stated.

One thing I see incorrect is the default IP Port for Novell Messenger is 8300 not 443. But I know of many setups that change it to IP Port 443 to get past many firewalls that allow HTTPS traffic through. There is also the Archive Agent IP Port of 8310 (if enabled) that could be added.

Thanks for such a diagram in the first place.
ghoman is correct. The default IP Ports for Novell Instant Messenger is 8300 for the Messaging Agent and 8310 for the Archive Agent.

I do promote using IP Port 443 for the Messaging Agent which allows users that roam around out on the Internet to be able to reach back to the IM service by getting through on IP Port 443 since most firewalls allow that through.

Dean will post the original Visio file here soon, so you will be able to make those corrections yourself.

Keep the feedback coming.
I have now posted the Visio version of this document!! It is an attachment included above.

It was kind of large, so it is in a ZIP file. Look for it just below the main blog post...

Here is the fine name: groupwise_8_protocol_flow_diagram_v1.3.zip

Dean
Just wanted to give a Big Thank You to both Ed and Dean!

We will use this as our base document!

Thanks again!

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.
Come see the revised GroupWise 2012+ Protocol Flow Diagram that is in high resolution PDF file format at

http://www.novell.com/documentation/groupwise2012/pdfdoc/ProtocolFlowDiagram/ports_protocolflow_a.pdf

Enjoy.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2011-07-11 19:38
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.