Tips for converting jobs out of a third party scheduler


It is possible to automate the creation of JAMS Jobs by taking the information from another Enterprise scheduler and feeding information into a JAMS XML which can then be imported automatically.

There are a few things to keep in mind:

  • The imported Jobs must be in JAMS XML format
  • An extract of a Sample Job to see the XML format that should be used or a temporary Job can be created based on common Properties from the other scheduler
  • Many other schedulers use their own database, or have their own proprietary mark up language which could be parsed into the JAMS XML

Below is an example of an exported job from JAMS.

<?xml version="1.0" encoding="UTF-8"?>

-<Jobs xmlns="" xmlns:xsi="" xmlns:xsd="">

-<Job name="ShowEnvironment">

<Description>Show the Job's environment</Description>




















<Require name="Maintenance_Resource"/>



-<Parameter name="Param1" Length="0" DataType="Text">




-<Parameter name="Param2" Length="8" DataType="DateTime">

<DefaultFormat>MM/dd/yy HH:mm</DefaultFormat>















Job Properties are represented by their own keys. By default, keys that do not have any data in them are not defined. This information is based off of our .NET API Job Object definition list.

Job Properties from a third party scheduler would simply be fed into this XML markup between each key. For example, the Agent Node, Job Name, Scheduled Date, etc.

Each Property will be an XML element of the same name unless the documentation shows an override name or an XmlIgnore attribute.

For Job Definitions, the only required item is the Job Name. If errors are encountered during the import, adding the -Verbose flag to the Import-JAMSXml cmdlet can give grater details as to the failure.

Instructions on how to use the JAMS XML cmdlets can be found here.

Have more questions? Submit a request