Home › Products › B2B Gateway › Architecture

TradeXpress Technical Architecture

Compliance of the EAI model in six layers in the TradeXpress EAI platform is represented in the schema below. Each layer depends on the services offered by the lower layer.

TX Architecture

The communication or transport layer is used to convey data or messages to or from applications connected to the EAI System. TradeXpress Enterprise facilitates various communication layers depending on the connectivity needs of the connected applications:

  • JORAM*: This MOM assures the conveyance of messages and also offers value added services required for transport services:
    •  
      • Delivery guarantee
      • Priority management
      • Security
        *JORAM is integrated in the EAI TradeXpress platform via the JMS standard. 
  • Web/Services: This component meets the requirements of SOA (service oriented architecture) problem analysis and resolution methodology.

The adapters layer is responsible for connecting applications to the EAI platform. The connection to Oracle or SQL Server type data applications is provided by a JDBC or Native Oracle connector. Message exchange with Microsoft Exchange servers is assured by a Microsoft Exchange connector. Connections to J2EE servers are done via an EJB Connect connector.

connectors

 

The integration or routing engine layer is driven by the message broker, TradeXpress Runner. Runner is a software component for the management of inter-application messages. It makes use of services provided by the Transport layer. It includes a rules engine and a formatting engine.

The Process layer is driven by the TradeXpress business process modelling (BPM). The language used to define the tasking rules functionally meets the conditions of the BPML standard. The tasking processes are defined via a graphical Interface TradeXpress Modeller.

The trading model layer, enables the EAI solution to communicate with external partners will be supplied via TradeXpress Enterprise’s EDI and LDAP connectors. 

The transformation or component layer is responsible for the transformation of data formats from a source format into a target format. This is achieved via a transformation-oriented L4G language (RTE).  Transformations are defined through a graphical interface for drag and drop mapping. This allows the graphial definition and connections between input and output formats, whilest in the background the RTE code is generated.