EagleML/EJM Installation Prerequisites

Owned by Copy Page Tree (Unlicensed)
Last updated: Oct 22, 2024 by Kinga Huszno
1 min read

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.  

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.

Configuration of FTP or SFTP is recommended. Configuration of SMTP is optional, but you need to configure this if you plan on leveraging email notifications.

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:

  1. Open the Message Center Console.

  2. Locate the stream eagle_ml-2-0_default_cm_w_setup  and right click on it.

  3. Click Send Data.

  4. 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>

     

    Â