6. EME
EME Community Edition 1.1.0
6. EME
6.1. Start EME
The first time you start EME you will have to acknowledge the license before it will let you start.
Open a command prompt or terminal and change directories:
{BIT_EME_CE_HOME}/eme-ce-{version}/
6.1.1. Windows Command
You may receive a security warning about opening ports, make sure you allow access.
Start as a foreground process in the current shell:
eme.bat
Start as a background process (Daemon) so you can leave the current shell:
eme.bat start
6.1.2. Linux / Unix Command
Start as a foreground process in the current shell:
./eme.sh
Start as a background process (Daemon) so you can leave the current shell:
./eme.sh start
6.2. Stop EME
Open a command prompt or terminal and change directories:
{BIT_EME_CE_HOME}/eme-ce-{version}/
6.2.1. Windows Command
Stop a foreground process running in the current shell:
Ctrl-c
Stop a background process running as a Daemon:
eme.bat stop
6.2.2. Linux / Unix Command
Stop a foreground process running in the current shell:
Ctrl-c
Stop a background process running as a Daemon:
./eme.sh stop
6.3 Features
EME-CE has many pre-integrated open source projects and components. Here are just a few that start as part of the default bundle:
- Apache Derby Database
- Mule ESB
- ActiveMQ JMS Server
- Jetty Web Server
When you start EME-CE, you are running all of those as well as many other open source projects and custom code developed by BIT. EME-CE can connect to many different systems, using many different protocols, right out of the box. For assistance integrating into any system please Contact Us
6.3.1. Web Console
EME-CE Web Console has many different screens and functions to help you manage, track, trace, and display messages from both internal and external Trading Partners.
The Web Console is deployed on port 8888: http://localhost:8888
Default access:
| username | password |
|---|---|
admin |
password |
It contains the following screens:
| Screen | Description |
|---|---|
| Activity Monitor | Shows current memory usage, DB, JMS, and Web status, and number of messages sent/received per endpoint |
| Message Viewer | Display message payload and message properties for all inbound or outbound messages |
| JMS Tool | Allows you to view messages on a queue, or upload a message into a queue |
| Event Log | View info and error alerts, and correlate the errors to discrete messages in the message viewer |
| Users | Add and edit users that have access to the EME Web Console |
| Trading Partners | Add and edit Managed File Transfer and integration Trading Partners |
| BDP | Business Document Processor that displays messages in human readable format, and shows relations between inbound and outbound messages, such as Purchase Orders and Invoices. This requires special configuration. |
6.4 Message Transformation
EME supports inbound and outbound message transformations, configurable via the Trading Partner screen.
The XSL must be placed in this location, with an extension of .xsl. EME will pick up changes or new files on the fly WITHOUT having to be restarted.
{BIT_EME_CE_HOME}/eme-ce-{version}/xsl
To add a transformation, select the Trading Partner: http://localhost:8888/tradingpartners.do
To add an inbound or outbound transformation, select the type from the appropriate Transformation Type drop down. If there is nothing selected in the Transformation Type drop down, the transformation will NOT happen, even if there is data in the Transformation text box. You can apply inbound or outbound transformations independently. If you do not want to apply a transformation, leave the drop down box empty for that direction.
In the following example, transformations would only apply to inbound messages using the foobar.xsl.
6.4.1 XML2XML
This transformation chain only supports XSLs.
Select XML2XML from the Transformation Type drop down and enter the name of the XSL without the extension in the appropriate Transformation text box. If the name of your XSL is foobar.xsl, then you would enter foobar. The XSL needs to be in this directory:
{BIT_EME_CE_HOME}/eme-ce-{version}/xsl
6.4.2 XML2FLATFILE
This transformation chain only supports XSLs.
Select XML2FLATFILE from the Transformation Type drop down and enter the name of the XSL without the extension in the appropriate Transformation text box. If the name of your XSL is foobar.xsl, then you would enter foobar. The XSL needs to be in this directory:
{BIT_EME_CE_HOME}/eme-ce-{version}/xsl