Follow 
Join 
Read 
Isode X.400 Messaging and EDI Whitepapers
Whitepapers with a special relevance to those with an interest in X.400 Messaging or building EDI solutions together with those of a more general relevance to those with an interest in X.400.
X.400 Disaster Recovery |
| Using Message Acknowledgements for Tracking, Correlation and Fire & Forget This whitepaper looks at how tracking end to end message acknowledgements can improve service reliability for mission critical messaging. This is achieved by enhancing message tracking services and providing information on messages being delivered and read. It then describes how this can be extended to provide a "Fire and Forget" quality service, using operator alerts and guaranteed action points (GAP). The paper also shows how these capabilities are provided in Isode's M-Switch product. (7th December 2011) |
| ACP 145: Isode Support of International MMHS Gateways ACP 145 is a specification from the CCEB (Australia, Canada, New Zealand, UK, USA) of how Military Messaging is exchanged between nations. This white paper gives an overview of ACP 145, and how it is supported by the Isode product set. It looks at how this can be used to support both STANAG 4406 national systems, and SMTP national systems using MIXER conversion. (10th November 2011) |
| File Transfer by Email File Transfer by Email can be useful for moving data between systems when standard file or data transfer mechanisms are not available. In particular it is useful for supporting Directory Replication, as described in the Isode white paper Directory Replication by Email and over 'Air Gap'. This paper looks at requirements for File Transfer by Email, and describes the architecture of Isode’s solution. (27th Jan 2009) |
| Messaging Protocols for HF Radio Messaging is important for military and other deployments of HF Radio. Formal Military Messaging (STANAG 4406) over HF Radio is described in a previous Isode White Paper. This paper looks at how to optimize STANAG 4406 messaging for point to point HF networks and how to provide Internet Messaging over multi-node and point to point HF networks. (28th Aug 2008) |
| Testing STANAG 4406 Military Messaging over IP Differentiated Services IP Differentiated Services (DiffServ) is a standardized Internet approach for dealing with different classes of traffic. We have added support for differentiated services to M-Switch X.400, so that its priority handling (which supports standard X.400 three level priority, and the STANAG 4406 military messaging six level priority) can utilize differentiated services at the IP level. Isode and NATO staff put together a setup to test military messaging in conjunction with DiffServ, and ran tests on two days in August and November 2007. This paper describes the tests that were done and analyses the results. (20th Dec 2007) |
| M-Switch
X.400 Benchmarks This paper gives performance benchmarks for Isode's M-Switch X.400, a high-performance X.400 Message Transfer Agent. M-Switch X.400 is deployed by Isode customers in a number of solutions areas and these benchmarks re-enforce our belief that M-Switch X.400 is substantially faster than any other X.400 MTA. (20th Nov 2007) |
| Why use a P7 Message Store? Getting
X.400 messages to and from end-users The goal of this paper is to give an understanding of what an X.400 Message Store, such as Isode’s M-Store X.400 does, and where and how it should be used. In order to do this, the paper looks at general requirements for sending and receiving (X.400) messages, and looks at various approaches that can be taken. (19th June 2007) |
| M-Store X.400 Benchmarks This paper provides performance benchmarks for Isode's M-Store X.400 product (R14) in a number of common usage scenarios including core P3 and P7 operations, throughput tests and handling of large messages. (31st May 2007) |
| X.400 Bridgehead for Microsoft Exchange:
Technical Architecture and Back-end Features X.400 Bridgehead for Microsoft Exchange ("X.400 Bridgehead") is a new product from Boldon James, produced in collaboration with Isode. It's primary goal is to provide X.400 protocol connectivity for Microsoft Exchange 2007, this capability was provided as a part of Exchange 2003 and earlier versions, but is not included with Exchange 2007. This paper describes the architecture of X.400 Bridgehead, and summarizes it's key features. It is particularly oriented towards understanding the capabilities of X.400 Bridgehead in the context of older versions of Exchange and full X.400 Message Transfer Agents (MTAs). (11th May 2007) |
| Sending FLASH Messages Quickly: Techniques
for Low Latency Message Switching and Precedence Handling Military Messaging systems, and other messaging systems with time critical operational requirements such as Aviation (AMHS), require that high precedence messages are submitted, transferred and delivered very quickly. In this paper we look at how messages can be handled to achieve message switching times of a few hundred milli-seconds, for both low and high volumes of traffic. The importance of Permanent Associations as a way of avoiding delays in opening a connection is described and consideration is given to Precedence Handling, describing techniques that ensure high precedence traffic gets optimum (low) latency. (9th May 2007) |
| Why X.400 is
good for high reliability messaging X.400 was specified in the 1980s, with the expectation that it would be the universal standard for email. While this did not happen, X.400 is still used for many applications, particularly where high reliability is required. This paper summarizes the key features of X.400 that make it good for applications needing high reliability, with particular focus on capabilities not available with Internet email. (11th May 2006) |
| Providing
Reliable Message Transport using X.400 For many commercial and personal applications, Internet mail is sufficiently reliable to be trusted and treated as if it were 100% reliable. For some applications, such as aviation, military, and key government communications this is not good enough. This paper looks at what is needed to provide highly reliable message transport: reliably taking a message from its originator and delivering to the recipient(s). (8th Feb 2005) |
| X.400 Technology for Internet Service
Providers Isode markets its X.400 and Internet messaging solutions as different products. However, Isode's core M-Switch product is the same for both X.400 and Internet deployments, with some modules specific to Internet and X.400 deployments. This white paper looks at features which are present in Isode's products primarily to address X.400 markets, but can add significant value to ISP messaging deployments. (21st Sept 2004) |
| MIXER: X.400 and Internet Mail
Conversion This article by Steve Kille, published in Messaging Magazine, describes MIXER (MIME Internet X.400 Enhanced Relay), the Internet Standard for conversion between X.400 Messaging and Internet mail. |
General
| SNMP and Isode Servers This white paper looks at the role of SNMP (Simple Network Management Protocol) in managing systems using Isode messaging and directory servers. It explains why SNMP support is provided, the sub-agent architecture used by Isode products, and approaches to deploying SNMP monitoring. (29th May 2007) |
| Operational Monitoring and
Control of Systems using Isode Servers Isode server products are deployed in a wide variety of situations, and usually there is a high service reliance placed on them. Isode’s approach to server design and management is that the products are building blocks, with maximum use of open standard protocols for interconnection. Management is almost entirely client/server. This combination of building block + client/server means that the approach to operational management needs to be considered as part of the overall system design. This paper explains the approach Isode has taken and the options provided, that can be used to build an operational system. (1st March 2006) |
| AMHS Security The Aeronautical Traffic Services (ATS) Message Handling Service (ATSMHS) defines a set of security services for use as part of the Extended ATS Message Service for providing that ATS Message Handling System (AMHS). This White Paper describes these security services, how they are provided and how they can be deployed. The paper concludes that AMHS Security is needed now, and should be pursued urgently as a part of AMHS deployment. (3rd Feb 2006) |
| Delivering the ATS Message Service to
the End User using AMHS AMHS (Air Traffic Services (ATS) Message Handling Services), as specified in the ICAO ATN (Aeronautical Telecommunications Network) SARPs, is the new standard for ground to ground messaging communications. The "ATS Message Service" is the end to end message service that AMHS provides. AMHS specifies the service, and the underlying infrastructure that is used in order to provide this service. To build a complete system, the ATS Message Service needs to be provided to end users, sitting at terminals. This paper looks at various approaches to doing this. (14th Dec 2004) |
| Monitoring and Managing Messaging
Deployments with Very High Service Requirements: Isode Servers and
Sentra In order to provide a very high grade messaging service, it is critical to monitor the service and be able to take action where problems are detected. This white paper looks at various approaches to monitoring systems containing the Isode servers, and in particular looks at use of the Sentra product from Insider Technologies. (2nd Nov 2004) |
| Isode Management Architecture:
Client/Server and Directory Isode's core business is messaging and directory servers. Isode products are designed for service oriented environments, such as ISPs, military, government and aviation. These are environments where there are stringent management requirements. This white paper sets out the approaches that Isode takes to address management requirements. (21st Sept 2004) |
| Addressing in AMHS: Building a solution
that works for the end-user AMHS provides a complex addressing scheme, which is used in conjunction with the ATN Directory. Users need to address messages, and the complexity of the AMHS addressing has potential to make this difficult. This whitepaper explains how AMHS and the ATN Directory can be used together to provide a simple and effective user experience. (14th Sept 2004) |
