Installing JAMS on a Single Machine

You can install JAMS on a single machine or virtual machine for testing or setup purposes. Additional configurations, such as high availability, can be setup, but they are not covered in this Getting Started Guide. For this process, the JAMS Scheduler and JAMS Client are installed on the same machine.

NOTE: If your system is missing the prerequisite software, the JAMS installer will display a message and the installation will stop. See System Requirements for more information.
NOTE: If you have already installed JAMS by following the instructions in the JAMS Installation Guide, you can skip this section.

Before You Begin

  • Verify the machine meets the System Requirements described in the JAMS Installation Guide.
  • Download the latest installer from the JAMS Support Site, and you save it to the Windows Server machine.
  • Log in with a user account with administrator privileges and the ability to create the JAMS Database in SQL Server. Typically, using an account with dbcreator and securityadmin or sysadmin rights in SQL Server provides the necessary permissions.)
  • Ensure you have received a license file.

Installing JAMS on a Windows Server

Follow the steps below to install JAMS on a Windows Server machine.

  1. Log in to Windows using an account with administrator privileges and the ability to create the JAMS Database in SQL Server.
    NOTE: Users must also be able to create a database on the database server. The default database server is the local machine.
  2. Right-click the SetupJAMS executable and select Run as Administrator to start the JAMS installer.
  3. On the Welcome page, click Next.
    NOTE: You may see an error message on the Welcome screen that the certificate chain was issued by an authority that is not trusted. If this message appears, see Managing the JAMS Database for more information before continuing with the installation.

  4. On the License Agreement page, review the JAMS license agreement.
  5. Select the checkbox next to I accept this license agreement.
  6. Click Next.

  7. On the Core Components page, select the JAMS Client and JAMS Scheduler options.
  8. Click Next.

  9. On the Message Queue (MSMQ) page, view the message regarding installing MSMQ.
  10. Click Next.
  11. On the Integration Packs page, select any required integrations.
  12. Click Next.

  13. If WebView2 is not installed and you are installing the JAMS Client, select the checkbox on the WebView2 Runtime page. See WebView2 Runtime for more information.
  14. Click Next.

  15. On the Contact Information step, enter the information that will be used when working with Technical Support. Two new objects are created from the last two fields:
    • Default_SMTP_Connection_Credential: This Credential stores the value of the “Default From Address for Sent Messages” field. It is also assigned as a mail credential in Default_SMTP_Connection.
    • Default_SMTP_Connection: This Connection stores the value of the "SMTP Server for Sent Email Messages” field. It is also assigned to the Configuration Settings as a mail server.

    Completing this page is optional but entering accurate information can help Technical Support improve its support capabilities. If you are unsure about the information, leave it blank and enter it at a later date.

  16. Click Next.

  17. On the SQL page, select the check box to install SQL Express locally to create the JAMS Database.

    JAMS Services rely on a connection to SQL to start properly, and they will fail to start if a SQL connection to a valid JAMS database cannot be made. When installing or updating your SQL Instance, review the startup sequence of the MSSQL Services and ensure they are set to an appropriate startup type, such as Automatic.

  18. Enter the information to create the JAMS Database as well as the authentication method used to connect to it.
    NOTE: Windows Authentication uses the Machine Account to connect to SQL Server after the initial install. The user performing the install needs to also have dbcreator rights for the JAMS Database to be created. The rights can be removed after the install is completed and the database is created.

    If you select SQL Server Authentication, JAMS connects to SQL with these credentials. The credentials are saved in the Common.config file located at C:\Program Files\MVPSI\JAMS\Scheduler.

  19. Click Next.
    NOTE: Users should NEVER attempt to manually create the JAMS Database.
  20. On the Locations page, accept the target directory where JAMS will be installed. The directory can be adjusted, but doing this may require additional customization of some features in JAMS.
  21. Click Next.
  22. On the JAMS Sample Jobs page, select the checkbox to install sample jobs.
  23. Define a JAMS user to run the sample Jobs. This is required because it sets the Execute As property for the Jobs.
  24. Click Next.
  25. Click Next. The installation begins.
  26. View the progress of the installation. You may also see a progress bar displaying the SQL Express installation, if you selected to install it in a previous step.
  27. On the Install page, click Close after the installation is completed.

Applying the JAMS License 

JAMS licenses are sent out as XML files. To apply a JAMS license, copy the license key file(s) into the C:\Program Files\MVPSI\JAMS\Scheduler directory. No other actions should be necessary.

If a license is properly placed in the C:\Program Files\MVPSI\JAMS\Scheduler directory and it is not recognized, the license file may be blocked by the File Blocking feature in Windows. To check the status and unblock files:

  1. Right-click the license file and select Properties.
  2. In the Properties dialog, ensure the General tab is selected.
  3. Check the lower right corner to see if an Unblock button is displayed. If it is displayed, the file is blocked. Otherwise, the file is not blocked.
  4. Click Unblock.
  5. Click OK or Apply to save the changes.

If the license file is not recognized and is not blocked, restart the JAMS Scheduler Service:

  1. Close the JAMS Client.
  2. Open Windows Services on the JAMS Server.
  3. Restart the JAMS Scheduler Service.
  4. Open the JAMS Client. The license should be recognized. If problems persist, contact Technical Support.

For more information about the JAMS license, see Licenses in JAMS.