This documentation supports the 19.08 version of Remedy and applies only to the on-premises deployment model.

To view an earlier version, select the version from the Product version menu.


Installing Email Engine remotely

This topic discusses remotely installing or upgrading Email Engine on the following platforms:

Remotely installing Email Engine on Microsoft Windows

Note

If you are creating a service where the Email Engine form and arx data are not present, follow these steps first:

  1. Import the AR_Email_Workflow.def file located in the AREmail folder, using BMC Remedy Developer Studio.
  2. Import the approval_templates.arx file located in the AREmail folder, using the BMC Remedy Data Import tool.

After following these steps, continue with the following procedure.

  1. Copy the Email Engine binaries to the AREmail folder.
    For example: C:\Program Files\BMC Software\ARSystem\AREmail.
  2. Update or add the following entry in the logging.properties file, located in the lib folder where JRE is installed:
    com.bmc.arsys.emaildaemon.level=SEVERE
  3. Update or add the following entries in the javamail.providers file, located in the lib folder where JRE is installed:
    protocol=mbox; type=store; class="gnu".mail.providers.mbox.MboxStore;vendor=dog@gnu.org;
    protocol=mapistore;type=store;class=com.bmc.mail.mapi.MAPIStore;vendor=mapi@bmc.com;
    protocol=mapitransport;type=transport;class=com.bmc.mail.mapi.MAPITransport;vendor=mapi@bmc.com;
  4. Set the following entries in the EmailStart.bat file (Microsoft Windows), located in the AREmail folder:
    set LIBVER=<BuildVersion> For example, <BuildVersion> = 90_build002
    set JavaPath=<BinPathOfInstalledJRE> For example, <BinPathOfInstalledJRE> =C:\Program Files\Java\jre7\bin
  5. Set the following entry in the EmailStop.bat file (Microsoft Windows), located in the AREmail folder:
    set JavaPath=<BinPathOfInstalledJRE> For example, <BinPathOfInstalledJRE> =C:\Program Files\Java\jre7\bin
  6. Update or add the following entries to the EmailDaemon.properties file, located in the AREmail folder:
    com.bmc.arsys.emaildaemon.servers=<ARServerHostName>
    com.bmc.arsys.emaildaemon.<ARServerHostName>.TCP=<ARServerPort>
    com.bmc.arsys.emaildaemon.<ARServerHostName>.RPC=<EmailEngineRPCPort>
    com.bmc.arsys.emaildaemon.<ARServerHostName>.Language=en_US
    com.bmc.arsys.emaildaemon.<ARServerHostName>.Password=<EncryptedARApplicationPassword>
    com.bmc.arsys.emaildaemon.<ARServerHostName>.Interval=30
    com.bmc.arsys.emaildaemon.<ARServerHostName>.Authentication=
  7. Create an empty logs folder under the AREmail folder.
  8. Open the command prompt and navigate to the AREmail folder.
  9. Create the Email Engine Service using the armaild.bat file, located in the AREmail folder.
  10. Pass the following arguments to the batch file in the specified sequence:
    1. Action: either "install" or "uninstall".
    2. The full path to the Java VM .dll file; that is, C:\Program Files\Java\jre7\bin\client\jvm.dll.
    3. The Email daemon installation directory where the libraries are located; for example, emaildaemon.jar,arapi90_build002.jar, and other .jar files).
    4. The AR library version; for example, 90_build002.
    5. The AR Server name where the Email Engine is configured.
      For example:
      C:\Program Files\BMC Software\ARSystem\AREmail>armaild.bat install "C:\Program Files\Java\jre6\bin\client\jvm.dll" "C:\Program Files\BMC Software\ARSystem\AREmail" 90_build002 VW-PUN-REM-QA5L.bmc.com

      You must run the command with administrator privileges; otherwise, the following error is displayed in the command prompt:
      Error while checking to see if service is installed: Access is denied.

  11. Start the Email Engine service.

Remotely installing Email Engine on UNIX

Note

If you are creating a service where the Email Engine form and arx data is not present, follow these steps first:

  1. Import the AR_Email_Workflow.def file located in the AREmail folder, using BMC Remedy Developer Studio.
  2. Import the approval_templates.arx file located in the AREmail folder, using the BMC Remedy Data Import tool.

After following the preceding steps, continue with the following procedure.

  1. Copy the AREmail folder from the installed UNIX system to the other UNIX system. For example, the Email Engine Install Directory will be /opt/bmc/ARSystem/AREmail.
  2. Update or add the following entry in the logging.properties file, located in the lib folder where JRE is installed:
    com.bmc.arsys.emaildaemon.level=SEVERE
  3. Update or add the following entries in the javamail.providers file, located in the lib folder where JRE is installed:
    protocol=mbox; type=store; class="gnu".mail.providers.mbox.MboxStore;vendor=dog@gnu.org;
    protocol=mapistore;type=store;class=com.bmc.mail.mapi.MAPIStore;vendor=mapi@bmc.com;
    protocol=mapitransport;type=transport;class=com.bmc.mail.mapi.MAPITransport;vendor=mapi@bmc.com;
  4. Update the following entries to the EmailDaemon.properties file, located in the AREmail folder. For example,/opt/bmc/ARSystem/AREmail:
    com.bmc.arsys.emaildaemon.servers=<ARServerHostName>
    com.bmc.arsys.emaildaemon.<ARServerHostName>.TCP=<ARServerPort>
    com.bmc.arsys.emaildaemon.<ARServerHostName>.RPC=<EmailEngineRPCPort>
    com.bmc.arsys.emaildaemon.<ARServerHostName>.Language=en_US
    com.bmc.arsys.emaildaemon.<ARServerHostName>.Password=<EncryptedARApplicationPassword>
    com.bmc.arsys.emaildaemon.<ARServerHostName>.Interval=30
    com.bmc.arsys.emaildaemon.<ARServerHostName>.Authentication=
  5. Update the following entries in the emaild.sh (UNIX) file, located in the AREmail folder: 
    • JAVA_DIR=<HomePathOfInstalledJRE> 
      For example: /usr/jdk/jdk1.7.0_55/jre 
    • JAVA_BIN=<BinPathOfInstalledJRE>  
      For example: /usr/jdk/jdk1.7.0_55/jre/bin/sparcv9 
    • InstallPath=<EmailEngineInstallLocation>  
      For example: /opt/bmc/ARSystem/AREmail 
    • LIBVER=<BuildVersion> 
      For example: 90_build002
  6. Start the Email Engine service by running the ./emaild.sh start & command.
Was this page helpful? Yes No Submitting... Thank you

Comments