How can we help?

  1. JAMS Scheduler
  2. Installation & Configuration

Moving the JAMS Scheduler

Follow
—

The instructions below are for environments that have not been set up for high availability.

NOTE: You must install the same version of JAMS on the new server that is installed on the old server.

Before You Begin

  • Submit a request for a new license. When submitting this request, include the new server name and the name of the server being replaced.
  • If the SQL Server database will move, follow the instructions in Moving the JAMS SQL Database before completing the steps below.
  • Create a Maintenance window on the old JAMS Scheduler and wait for all executing Jobs to complete. If you are running any Jobs from mail or file triggers, those Jobs will continue to run.
  • Backup the database.

Give the New JAMS Scheduler Access to the JAMS Database

The process will vary depending on how the JAMS Services are currently being run. Follow the steps in one of the sections below.

Services running as Local System on the old JAMS Scheduler

If the JAMS Scheduler and JAMS Server services were running as Local System on the old Scheduler, run the query below to grant permissions to the database for the new JAMS Scheduler. JAMSMachine2 can be any label you want. Change the YourDomain and YourMachineName, but the dollar sign is a necessary part of the login name.

exec sp_grantlogin @loginame='YourDomain\YourMachineName$'
exec sp_grantdbaccess @loginame='YourDomain\YourMachineName$', @name_in_db='JAMSMachine2'
exec sp_addrolemember @rolename='JAMSApp', @membername='JAMSMachine2'

Services running as a Domain Account on the old JAMS Scheduler

If the JAMS Scheduler and JAMS Server services are running as a domain account on the old JAMS Scheduler, see Change the Account Running JAMS for more information. The section under "Database Security Requirements" can be omitted because the database already has the provisions for the domain account to have access.

SQL Authentication

If the C:\Program Files\MVPSI\JAMS\Scheduler\Common.config on the old Scheduler is using SQL Authentication, then no additional database permissions should be required.

Otherwise, add the new machine account to the JAMSApp role in the database.

Stop the JAMS Services on the old JAMS Scheduler

Stopping and disabling the services on the JAMS Scheduler also disconnects it from the JAMS database.

  1. On the old JAMS Scheduler, open the Windows Services application.
  2. Complete the steps below for the JAMS Services.
    1. Click the JAMS Executor service and select Stop. This will also stop the JAMS Scheduler service.
    2. Right-click the JAMS Executor Service and select Properties.
    3. Set the Startup type option to Disabled to prevent the service from automatically restarting.
    4. Repeat these steps for the JAMS Server service and JAMS Scheduler service.

Install the Same Version of JAMS on the New Scheduler and Connect to the JAMS Database

  1. On the new JAMS Scheduler, right-click the JAMS installer and select Run as Administrator.
  2. Enter the required information and click Next until you see the SQL dialog.
  3. On the SQL dialog, do the following:
    1. Enter the address to the SQL Server/database.
    2. Enter the name of the database.
    3. Select the SQL Authentication method.
  4. Click Next.
  5. Complete the JAMS installation.
  6. Verify the directories listed below have been created. If they have not, manually create the folders in these directories. Jobs will fail if these directories are missing.
    C:\ProgramData\JAMS\Logs
    C:\ProgramData\JAMS\Temp

Apply the License and Update the Configuration on the New JAMS Scheduler

  1. Apply the new license key that you received from your license request. The default location is C:\Program Files\MVPSI\JAMS\Scheduler. See JAMS Installation Guide for more information.
  2. If you applied changes to any of the .config files on the old JAMS Scheduler, manually add those changes to the .config file or copy/paste the config file onto the new Scheduler.
  3. If the Job log files are stored locally on the old JAMS Scheduler, copy them to C:\ProgramData\JAMS\Logs on the new JAMS Scheduler if you need them to be accessible when viewing JAMS History records.
  4. In the Agents shortcut, verify the Agent with a type of local has a name of “localhost”. If the Agent name is the same as the old JAMS Scheduler, update it to “localhost”.

Run a Test Job on the New JAMS Scheduler

To ensure the new JAMS Scheduler is functioning as expected, run a Job and review its completion status. You can disable the maintenance window to let all queued Jobs to run, or you can run one Job with the maintenance window still enabled.

Do one of the following:

  • Disable the maintenance window by following the instructions in Creating a Maintenance Window in JAMS. All queued Jobs will run.
  • Run one Job with the maintenance window still enabled.
    1. Submit a Job from the Definitions shortcut. In the Monitor view, the Job is displayed as Waiting for Resources.
    2. Right-click the Job and select Release.
    3. Ensure the Ignore Resource Requirements option is selected.
    4. Click Ok.
    5. Disable the maintenance window from the new JAMS Scheduler if the Job ran as expected.
Have more questions? Submit a request

Comments