EME 1.2.2

3. Quick Start

After completing this entire Quick Start section you will have a fully functioning installation of Protocol Proxy and EME. You will then be ready to proceed onto the Managed File Transfer Hello World tutorial.

---

3.1. Java

BIT EME requires that a Java Development Kit (JDK) be properly installed, added to your path, and the JAVA_HOME environment variable set correctly. The following section will walk you through the steps required to achieve these requirements.

3.1.1. Download / Install Java

Download Java JDK 1.6+ for your operating system and follow the installation instructions. You MUST use a JDK (version 1.6+) for EME to function properly.

3.1.2. Add Java to your System PATH

After installation Add Java to your System PATH.

3.1.3. Set JAVA_HOME environment variable

You also need to create an Environment Variable JAVA_HOME, set to the root directory where you installed the JDK.

3.1.4. Verify Java Installation

Test your installation by opening a command prompt and typing javac -version, if you receive an error then your JDK is NOT setup correctly. You most likely need to add Java to your PATH, Click here for instructions on adding java to your System PATH.

Please do NOT try to continue with the rest of this guide until the Java JDK is correctly installed and tested.

---

3.2. Protocol Proxy

3.2.1. Start Protocol Proxy

• Verify that you have Administrator privileges, root access or have proper sudo privileges
• Open a command prompt or terminal and change directories:
  

    {BIT_EME_CE_HOME}/protocol-proxy-ce-{version}/bin

3.2.1.1. Windows Command

• You may receive a security warning about opening ports. You will need to allow access.
  

    startup.bat

3.2.1.2. Linux / Unix Command

• If you are root, type:
  

    ./startup.sh

• Otherwise type:
  

    sudo ./startup.sh

3.2.2. Protocol Proxy Login

Protocol Proxy will start up in the background

Login: http://localhost/proxy-admin

username	password
eme	password

After a successful login you will see a screen similar to below.

If this fails you probably did NOT start Protocol Proxy with the required privileges. Please contact your System Administrator for the proper privileges.

---

3.3. EME

3.3.1. Start EME

The first time you start EME you will have to acknowledge the license before it will allow you to start.

Open a command prompt or terminal and change directories:

    {BIT_EME_HOME}/eme-{version}/

3.3.1.1. Windows Command

You may receive a security warning about opening ports. You will need to allow access.

    eme.bat

3.3.1.2. Linux / Unix Command

    ./eme.sh

3.3.1.3. Startup Verification

You will see a lot of output ending similar to the following:

**********************************************************************
* Mule ESB and Integration Platform                                  *
* Version: 2.2.2-SNAPSHOT Build: 15252                               *
* MuleSource, Inc.                                                   *
* For more information go to http://mule.mulesource.org              *
*                                                                    *
* Server started: 1/21/10 10:59 AM                                   *
* Server ID: 4287daec-06ae-11df-a14e-qitn48t83l20                    *
* JDK: 1.6.0_17 (mixed mode)                                         *
* OS encoding: MacRoman, Mule encoding: UTF-8                        *
* OS: Mac OS X (10.6.2, x86_64)                                      *
* Host: laptop.local (10.10.10.34)                                   *
*                                                                    *
* Agents Running:                                                    *
*   jmx-log4j                                                        *
*   Wrapper Manager: Mule PID #0, Wrapper PID #16375                 *
*   Rmi Registry: rmi://localhost:1098                               *
*   Jmx Notification Agent (Listener MBean registered)               *
*   jmx-agent: service:jmx:rmi:///jndi/rmi://localhost:1098/server   *
*   MX4J Http adaptor: http://localhost:9999                         *
*   Default Jmx Support Agent                                        *
*   BITDerbyAgent: Port = 1528                                       *
*  BITJettyAgent: Port = 8888, context = /, location =               *
*  /mule-standalone-2.2.2-SNAPSHOT/webapp                            *
*  ActiveMQAgent:tcp://localhost:61616 &                             *
* vm://embeddedActiveMQBroker                                        *
**********************************************************************

3.3.2. EME Login

Login into EME: http://localhost:8888

username	password
admin	password

After a successful login you will see a screen similar to below.

---

3.4. Test Install / Connectivity

We will create a fictional Trading Partner (test) to confirm that the installation and start-up completed successfully.

Verify that BOTH Protocol Proxy and EME are running

Login to EME: http://localhost:8888 (if you are not still logged in from Step 3.3.2)

username	password
admin	password

Go to the Trading Partners tab and click Create New Trading Partner.

You will see a screen similar to below.

Fill out the form and click Save:

• Set Name to test.
• Set Password to password.

Name and Password are mandatory. The other fields are optional and are not required for this test. They will be covered in Section 4.1.

If your new Trading Partner is successfully created in both Protocol Proxy and EME, the screen will refresh and you will see a result similar to below. You will see Trading Partners > TEST breadcrumbs at the top, left of the screen, and the Integrations section will now appear on the screen.

This is proof your installation is working. You are now ready to progress to the next section, the Managed File Transfer tutorial.