JAMS is completely exposed to the developer using class libraries that allows you easily interact with JAMS from your applications. In addition, you can also extend JAMS to provide additional notification options or even invent new ways to execute Jobs.
JAMS incorporates a number of assemblies but, only a small number of these should be directly referenced from your applications. This section explains which assemblies can be referenced.
The JAMSShr assembly is your main interface into JAMS. It defines the JAMS objects and provides a means to read and store those objects.
The JAMSSchedulerShr assembly exposes the public parts of the JAMSScheduler service. You need to reference this assembly to create custom notification event handlers.
The JAMS.Activities assembly contains Windows Workflow Foundation activities. You need to reference this assembly when building workflows.
The JAMSHostBase assembly exposes the IJAMSHost interface and related classes. This is used when you want to create your own custom execution methods in a .NET environment.
The JAMSWebControls assembly exposes ASP.NET Web controls that you can drop into your web sites.