Architecture
| ANZEN-Messenger is a state-of-the-art messaging system developed using Java/J2EE technologies to provide secure, robust and reliable internet message services. Its design embodies Service Oriented Architecture principles with loosely-cled external system integration. ANZEN-Messenger is a set of standards based integrated components: ANZEN-Messenger Message Engine - designed to ISO 15000-2 standards (OASIS/UNCEFACT)The component for managing the transmission and receipt of messages. ANZEN-Messenger Business Service Interface - A set of Application Programmer Interfaces (API) for external applications to be created and respond to message transactions. ANZEN-Messenger Persistence Storage Interface - Provides the recording and integrity of message actions. ANZEN-Messenger Security Manager - Provides pluggable interface for industry standard security components such as PKI. |
| |
| ANZEN Messenger Stack The following diagram summarises the message process via the ANZEN-Messenger over the internet to another ebXML/ebMS compliant server or ebXML Gateway. |
| |
| Application The application represents any back office system that requires communication between other parties across the internet. This may be an accounting application, ERP, or other business specific application. Business Service Interface (BSI) BSI is the interface which manages all aspects of communication with the external application and ANZEN-Messenger engine. Application Extension Interface The BSI also provides further extensibility in that user developed functions can be developed and added to the application. ANZEN-API ANZEN-Messenger has been designed with flexibility and extensibility in mind. The API provides developers a set of plug-in points and interfaces to create, send and manage messages and interface with other applications. This means, if required specific messaging capability can be easily incorporated. This "open architecture" design exposes flexible integration paths with other products and applications. ANZEN-Messenger Engine Security A significant effort has gone into the development of the security layer for the ANZEN-Messenger. The security model is largely pluggable and configured declaratively. It incorporates industry standard protocols including SSL, PKI and certificated authorisation required for secure, non-repudiative business transactions over the internet. Reliable Messaging ANZEN-Messenger supports reliable message delivery capabilities like once-only and in-order delivery. Reliable messaging can be split into two parts lost messages and duplicate messages. Acknowledgment plays an integral part to reliable messaging. Once a message has been dispatched it expects an acknowledgement. if this is not received it will then forward the message again at a set interval until a response is received. The process will continue for a set number of tries. Another aspect is that all despatched messages are stored in a reliable persistent storage for the purpose of reconciliation. This allows for the elimination of duplicates. Message Structure and payload flexibility ebXML messages are structured according to SOAP with attachments (SWA) specification. An ebMS message package consists of: The header container containing SOAP 1.1 - compliant message. (a SOAP Message) Any number of MIME parts containing the application payloads which themselves can contain XML documents EDI messages, or any arbitrary binary file type (Payload Containers) The general structure of an ebXML message is depicted below. |
| |
| Error Processing
Validity checks are performed in various states of the ANZEN-Messenger MSH engine processing. The types of errors checked are: MIME structure error. SOAP structure errors. Errors in structure and contents of ebXML namespace qualified SOAP Extension elements. Errors encountered during reliability messaging. Errors encountered during security processing. |
| Standard | ISO 15000-2, OASIS/UNCEFACT |
| Operating Systems | Linux, Windows 2000 , Windows XP |
| Servers | Tomcat-Jakarta, Websphere, Weblogic, JRun |
| Databases | MySql, PostgressSQL, MS SQL, Oracle |
| Transport Types |  HTTP, HTTPS; |
| Documents | XML, word documents, pictures |