Upgrade Requirements
Prior to upgrading JAMS from V5.x to V6.x, carefully review the following requirements:
-
SQL 2000 is no longer supported for the JAMS database. JAMS V6.x supports SQL 2005, 2008, 2012, and 2016.
-
Version 4.5 of the .NET Framework is required.
-
JAMS V6.x Clients are not compatible with JAMS V5.x Servers; and JAMS V5.x Clients are not compatible with JAMS V6.x Servers.
 |
Note: If you are using the JAMS Client on a remote workstation machine (a machine other than the JAMS Server itself), you must upgrade the JAMS Client to V6.x to access a newly upgraded V6.x Server. However, if you need to access a JAMS V5.x Server, the JAMS V6.x also includes an option to install a JAMS V5.4 Client. This client installs in a new directory to allow for the simultaneous usage of both clients. |
-
JAMS V6.x Servers can execute Jobs on all versions of the JAMS Agents.
-
JAMS V5.x Servers can execute Jobs on all version of the JAMS Agents, including V6.x.
-
The upgrade process creates a new JAMS SQL database for V6.x and keeps your existing JAMS database intact and remains in a static state. Once the upgrade is complete, any changes to your JAMS Job/Setup definitions, Job Schedule, etc. are updated to the new V6.x JAMS database.
-
Since a single JAMS Client is not able to connect to both a V5.x and V6.x JAMS server, the only way to move Jobs between V5.x and V6.x JAMS Servers is with the Export-JAMSXml and Import-JAMSXml PowerShell commands.
-
JAMS Systems in 5.x have been renamed to Folders. Folders in JAMS V6.x serve the same purpose as Systems in earlier versions of JAMS. In JAMS V6.x, you have the ability to define multiple levels of folders and subfolders, allowing for greater organizational capabilities for your Jobs and Setups. In addition to Jobs and Setups, Triggers and JAMS Variables can now be stored inside Folders.
-
When the JAMS V5.x Client is upgraded to V6.x all custom groups and shortcuts for that Client are lost and must be recreated in the JAMS V6.x Client if you wish to continue using them.
-
It is recommend that you put any scheduled Jobs on hold and stop any batch queues in place so that no Jobs are interrupted during the upgrade process.
-
The installation package must be run as a user account with SA access to your SQL instance, as the JAMS Installation makes critical updates to the database’s Master Records and creates a new JAMSV6 database.
-
If you used a custom database name during the initial installation of JAMS V5.x, you must update the common.config file located in the root installation of JAMS.
A Special Note on PowerShell Scripts in JAMS V6.x
Current JAMS PowerShell scripts should continue to work unless there is a change to the path to a JAMS object. Prior to V6.x, JAMS included a number of "simulated" folders.
For example, in JAMS V5.X, to access a Trigger, the path might be:
JAMS:localhost\Triggers\TriggerName
The "Triggers" portion of that path represents a simulated folder. The conversion process now puts all triggers into the “root” folder. Variables are converted in the same manner.
If you use these paths in PowerShell scripts, you can now create real folders named Triggers and Variables and move all Trigger and Variable definitions into them to maintain the functionality of your existing PowerShell scripts.
Systems, Jobs, and Setups within JAMS are also updated. In V5.x, you could access a Job as:
JAMS:localhost\Systems\MySystem\Jobs\MyJob
In this case, the "Systems" and "Jobs" folders are both “simulated”. However, in V6.x, the same Job is accessed using the path:
JAMS:localhost\MyFolder\MyJob
Users who would like to retain the V5.x syntax have the option to create a folder named "Systems", move their "MySystem" folder into it. This creates a nested "Jobs" Folder allowing you to move Jobs to that Folder.