Messaging Servers Brick

Home > Architecture Library > Review by Architecture Type > Technology Architecture > Messaging Servers Brick

Description

Messaging servers are enterprise applications that run on a central computer and enable synchronous and asynchronous, peer-to-peer communications.

Brick Information
Tactical (0-2 years)	Strategic (2-5 years)
Blackberry (RIM Server) Instant Messaging (various technologies) Listserv Microsoft Exchange 2000	Additional Wireless (Palm,etc.) Microsoft Exchange 2003
Retirement (To be eliminated)	Containment (No new development)
Meeting Maker Netscape Messaging Server Wylbur	CODON Fax Helix KRONOS Microsoft Exchange 5.5 Novell GroupWise (NLM) Send Mail (SMTP/relay)
Baseline (Today)	Emerging (To track)
Blackberry CODON Fax Helix Instant Messaging (various technologies) KRONOS Meeting Maker Microsoft Exchange 5.5 Netscape Messaging Server Novell GroupWise (NLM) Send Mail (SMTP/relay) Wylbur	Unified Messaging

For a successful Exchange 2000 migration, Active Directory (AD) must be in place. To gain the largest benefits from the Exchange 2000 system (more databases per server), AD must be running in its native mode.
Mac OS X MAPI Client not yet released (Q4—2003) preventing the widespread use of the new Exchange infrastructure by NIH’s considerable Mac population.11 June 2003.
Tactical and strategic products were selected to leverage NIH's investment in products that are a proven fit for NIH's known future needs. Leveraging baseline products in the future will minimize the operations, maintenance, support and training costs of new products.
Some baseline products have been designated retirement and containment. These products are either not as widely or successfully deployed at NIH, or they do not provide as much functionality, value, or Total Cost of Ownership as the selected tactical and strategic products.