EME Technical Details
EME Technical Details
Integration in EME is implemented with one or more components consisting of endpoints (both inbound and outbound), filters, and transformers. Multiple filters and a chain of transformers can be associated with a channel. EME allows for reuse of filters and transformers across implementations.
Wide Variety of Connectors
Endpoints are used to configure connections and their protocol details. Inbound endpoints are used to designate the type of listener to use for incoming messages, such as TCP/IP or a web service. Outbound endpoints are used to designate the destination of outgoing messages, such as an application server, a JMS queue, or a database. EME can be configured to listen and send messages and connect to a variety of protocols: 
- TCP-IP
- HTTP/HTTPS
- Relational databases (Oracle, SQL Server, Derby, MySQL, etc.)
- File systems (local and network shares)
- JMS message queues (WebSphere MQ, Active MQ, TIBCO, etc.)
- FTP/SFTP
- SOAP Web services
- REST Web services
BIT’s standards-based architecture for integration facilitates custom and legacy interfaces for a comprehensive integration solution. If you wish to implement your own communications server hub, BIT can configure EME to work with BIT’s Protocol Proxy for secure exchange of messages.
Message transformation
EME allows for creation of transformations and mappings of industry-standard data. The EME XSLT transformer can perform XSL Transformations on incoming or outgoing XML, EDI or other message formats. For a user-friendly mapping interface we recommend the use of a low-cost standards-compliant tool like oXygen, Stylus Studio, or XML Spy to create XSL that can be deployed in EME’s open architecture.
System Requirements
EME requires a server system with 2 GB of memory and 500 MB of storage available. The server must run a recent, stable release of Linux, Windows, or a major Unix variant. The server must be capable of supporting the Java™ 2 Runtime Environment, Standard Edition version 1.5. EME must be deployed behind a secure firewall without restriction on outbound connection for the chosen B2B integration protocol.
BIT requires a privileged account on the EME server and access to internal support for both the server and the chosen enterprise connection. The B2B trading partner must have an existing server configured to accept your B2B connection and must provide support for testing the B2B implementation.
Open-Source
EME is based on Spring, Mule and other proven open-source projects such as Derby, Jetty, ActiveMQ and xFire. There are no up-front license fees for EME. BIT provides a complete solution with services on either a project or subscription basis.