JAMS Dynamics AX integration
Microsoft Dynamics AX Batch Job Scheduling
JAMS Scheduler runs Microsoft Dynamics AX jobs through the .NET Business Connector and keeps AX batch tied to the rest of your workload.
Execution method
MSDAX2012Job
Connects through
The .NET Business Connector
Version match
The JAMS add-on matches your AX version
What JAMS Scheduler Runs in Dynamics AX
JAMS Scheduler reads the AX job list through a local client and runs jobs through the Business Connector. Schedules, dependencies, and alerts work like any other job.
How JAMS Scheduler Connects to Dynamics AX
In Microsoft Dynamics AX Configuration, set up two targets: a Local Client, where JAMS Scheduler reads the job list, and a Business Connector, where jobs run. Both point at your Application Object Server.
Open the TCP and WSDL ports from the JAMS Client machine to the AOS, and install the JAMS add-on for your AX version from the JAMS Support site.
Requirements
Configuration targets
Local Client and Business Connector
Ports
TCP and WSDL open to the AOS
JAMS add-on
The same AX version as your installation
Dynamics AX Jobs in a Cross-Platform Workflow
An AX batch can wait for a SQL Server job or a file transfer, then hand off to an SSRS report.
When it fails, you get the same alert as any other job.
Dynamics AX FAQ
How does JAMS Scheduler run Dynamics AX jobs?
Through the .NET Business Connector, with the MSDAX2012Job execution method. JAMS Scheduler reads the job list through a local client configuration.
What ports need to be open?
The TCP and WSDL ports from the machine running the JAMS Client to the AOS.
Does the JAMS add-on need to match my AX version?
Yes. Install the JAMS add-on built for your Dynamics AX version. Installers are on the JAMS Support site.
