EagleML/EJM Installation Prerequisites
While EagleML and EJM are version independent, your Eagle product suite must be at least version 12.1.5.
The same installation package and steps are used for both EagleML and EJM.Â
Java v1.6 or higher is required to be installed in the environment for correct Installer performance
The following prerequisites are required for the first time you are installing EagleML/EJM on an environment. Â
On this page
For Windows OS Server Only
The following applications must exist in the preprocessors folders (example of paths: estar\dynamic\msgcenter\preprocessors\ and estar\servers\msgservice\preprocessors\) :
base64.exe
pkzip25.exe
unzip.exe
tartool.exe
Similar commands are typically available in the default builds of Linux/Unix OS. This is why it is not necessary to copy to the preprocessors folders for Linux  servers.
For Both Linux and Windows OS Servers
The eagle_ml-2-0_default_cm_w_setup stream will not actually exist on your environment if you are installing for the first time. Therefore, please do this particular step after you perform the actual install.
Create the CMW directory structure:
This step is necessary to create the required cmw directory as well as perform configuration tasks
In your Eagle environment:
Open the Message Center Console.
Locate the stream eagle_ml-2-0_default_cm_w_setup  and right click on it.
Click Send Data.
Select your EagleDBMLRequest.xml file and click OK (If you do not have this file already, you can save the code below. Due to the HTML content, the wiki site will not allow the file itself to be stored here).
<EagleML xmlns="http://www.eagleinvsys.com/2011/EagleML-2-0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" eaglemlVersion="2-0" eaglemlType="ReferenceTransactionMessage" xsi:schemaLocation="http://www.eagleinvsys.com/2011/EagleML-2-0Â eagleml-main-2-0.xsd" xsi:type="ReferenceTransactionMessage"> Â <header> Â Â <messageId messageIdScheme="http://www.eagleinvsys.com/coding-scheme/message-id-2-0">1634B431F2296D98</messageId> Â Â <sentBy>AUTOGENERATOR</sentBy> Â Â <creationTimestamp>2012-02-20T14:54:27-05:00</creationTimestamp> Â </header> Â <referenceTransaction> Â Â <header> Â Â Â <identifier> Â Â Â Â <versionedTransactionId> Â Â Â Â Â <transactionId transactionIdScheme="http://www.eagleinvsys.com/coding-scheme/transaction-id-2-0">1634B431F2296D98</transactionId> Â Â Â Â Â <version>1</version> Â Â Â Â </versionedTransactionId> Â Â Â </identifier> Â Â Â <transactionDate>2012-02-20</transactionDate> Â Â Â <action>ADD</action> Â Â Â <objectType>EagleDBMLRequest</objectType> Â Â </header> Â Â <EagleDBMLRequest> Â Â Â <REQUEST> Â Â Â Â <MSG_TYPE>ORCH_PROCESS</MSG_TYPE> Â Â Â Â <SUB_MSG_TYPE>INS</SUB_MSG_TYPE> Â Â Â Â <INPUT_PAR> Â Â Â Â Â <P n="orch_name">EJM Process</P> Â Â Â Â Â <P n="orch_descr">Eagle Job Manager Process</P> Â Â Â Â Â <P n="purge_flag">0</P> Â Â Â Â Â <P n="update_source">MCADMIN</P> Â Â Â Â </INPUT_PAR> Â Â Â </REQUEST> Â Â </EagleDBMLRequest> Â </referenceTransaction>Â </EagleML>
Â
Â