JAMS PowerShell integration
PowerShell Script Scheduling and Automation
JAMS Scheduler runs PowerShell scripts in 64-bit, 32-bit, or PowerShell Core, and its own PowerShell module lets you script job creation and changes in JAMS itself.
Four ways to run
PowerShell, PowerShell32, PowerShellCore, JAMSPowerShell
JAMS cmdlets
Dozens, plus a PowerShell provider
Script your setup
Create and change jobs with New-Item and Get-Item
What JAMS Scheduler Runs in PowerShell
Paste the script into the job and set the credential it runs as. Schedules, dependencies, and alerts work like any other job.
Managing JAMS Scheduler with PowerShell
The JAMS Client includes a PowerShell module with dozens of cmdlets and a PowerShell provider. Use native commands like New-Item and Get-Item to create or change jobs, folders, and sequences from a script.
The JAMS cmdlets don’t run under PowerShell Core. Use Windows PowerShell for scripts that manage JAMS itself.
Requirements
Script jobs
JAMS Scheduler or a JAMS Agent for Windows
JAMS module
Installed with the JAMS Client
JAMS cmdlets
Windows PowerShell, not PowerShell Core
PowerShell Jobs in a Cross-Platform Workflow
A PowerShell cleanup can wait for a SQL Server job, then start a file transfer. The module also handles FTP, FTPS, and SFTP transfers from inside a script.
More examples are on the PowerShell automation page.
PowerShell FAQ
Does JAMS Scheduler support PowerShell Core?
Yes, for script jobs. The PowerShellCore execution method runs PowerShell Core scripts on Windows. The JAMS cmdlets themselves need Windows PowerShell.
Can I create JAMS jobs with PowerShell?
Yes. The JAMS module includes a PowerShell provider, so New-Item creates a job and Get-Item opens one to change it.
Can PowerShell run file transfers in JAMS?
Yes. The JAMS module includes cmdlets for FTP, FTPS, and SFTP transfers, starting with Connect-JFTP.
