JAMS 6.X Client Features 5. Working with Jobs 5-6. Defining Workflow Jobs 6. Introduction to Workflow Jobs 6-7. Setting Up a Workflow Job 7-9

(1)

JAMS 6.X Client Features

Working with Jobs

Essentially, every component in JAMS supports or controls how a Job is defined or run. At its core a JAMS Job incorporates a number of properties and resources that ensures that it executes at the right time and under the proper conditions.

In a nutshell, a Job is a task, script or command that can be run on a variety of systems including: Windows, Unix, and PeopleSoft.

Adding a New Job

1. To create a new Job, activate the Jobs View by clicking on the Definitions Group in the Shortcut Bar and selecting the Jobs shortcut.

2. Choose the Add button on the Ribbon Bar to access the JAMS Job Definition Wizard.

Select Next to open the wizard's Jobs Name page. Enter a unique name for the Job along with an optional description. Click the Next button.

4. The Execution Method page follows. Here you can view and choose from a listing of execution methods by clicking the File Browser button.

5. Select Next to access the Notification Email Addresses page where you can supply one or more addresses to alert staff members if a Job fails or doesn’t complete within an allotted time. 6. On the next page, verify the user account for this Job using the dropdown list or by entering a

valid username and password.

7. On the Source page you can (optionally) enter the Job’s commands. Click the Next button. 8. Moving to the Schedule page, use the Scheduled Date dropdown to define a built in

schedules or manually enter single or multiple date specifications. Click Next. 9. Press the Finish button to complete the Job definition process.

Modifying an Existing Job

1. To make changes to an existing Job, open its properties window by right clicking (or double-clicking) the desired Job listing.

2. From the Job’s context menu select the Properties command.

(6)

Deleting an Existing Job

1. Navigate to the Jobs View in the Shortcut Bar 2. Highlight the Job to be deleted

3. Click the Delete button on the Ribbon Bar.

4. Confirm the deletion by clicking Yes or alternatively choose the Cancel or No button.

Defining Workflow Jobs

Introduction to Workflow Jobs

JAMS Workflow Jobs uses the Windows Workflow Foundation to provide an extensible collection of Activities using a rich interface for designing Job execution flows. JAMS extends the base set of these Workflow Activities with a collection of its own Activities for interacting and performing useful tasks directly within the JAMS Client.

(7)

Setting Up a Workflow Job

1. To get started, create a new Job by activating the Jobs View and selecting the Definitions Group in the Shortcut Bar and highlighting the Jobs shortcut.

2. Select the green Add button on the Ribbon Bar. 3. This action opens the JAMS Job Definition Wizard.

4. Select Next to open the Jobs Name page. Enter a unique name for the Job along with an optional description and click the Next button again.

(8)

6. This action opens the Execution Method list. Double-click the Workflow option. This action will close the list window and populate the execution method field on the previous screen.

7. Continue moving through the Job Definition Wizard until you reach the Source Page and the Workflow Designer Panel.

The Workflow Design Panel

The object-oriented workflow interface is made up of three panels. The left Toolbox panel contains a list of Activities that can be used as building blocks to customize a JAMS job to most any specification.

These activities are organized into groupings (e.g., JAMS, SQL, PowerShell, etc.). If specific JAMS Add-ons have been installed, additional Activities/Grouping may also appear on the

(9)

Defining a Workflow Job

The Workflow execution method is designed for Job scenarios that require decision logic that uses different execution paths. Workflows are defined using the Workflow Designer that includes a menu of building blocks (Activities) for submitting Jobs, updating JAMS Variables, and many more JAMS specific tasks.

The Workflow Design Panel

The object-oriented workflow interface is made up of three panels. The left Toolbox panel contains a list of available Activities that can be used to customize a JAMS Job to most any specification.

(10)

To get started, first plan out the Job and then select the appropriate activity or activities from the Toolbox to include in the workflow. Then drag and drop Activities from the Toolbox on to the middle Designer panel. For a detailed description of each Activity please refer to the topc: Workflow Activities Description.

Defining a Workflow using a Sequence Activity

Workflow jobs that contain more than one Activity must be nested within a parent activity such as a Sequence or Flowchart. A Sequence is a container object that can help create a more intricate workflow. Sequences are powerful as they can contain any activity including Flowcharts and decision structures.

1. To include multiple Actvities into Job workflow, drag a Sequence Activity to the Designer panel to setup the workflow framework.

(11)

3. Drag and drop the next Activity to create a child activity within the parent Sequence.

More complex Jobs, such as those requiring branching, can be designed using nested Sequences.

Flowchart Activity

(12)

Please review any task messages appearing on the Activity object. To view the message content hover the mouse over the object in the Designer panel.

Note: All errors must be resolved before a JAMS Job can be successfully submitted.

Select the Save and Close button to complete the JAMS Workflow job definition process.

Note: Some JAMS Activities, such as AskQuestion and ManageActivity, allow for runtime interaction. For

more information on Workflow interaction, select the link: Runtime Workflow Interaction.

Workflow Activities Description

The Workflow execution method is designed for Job scenarios that requires decision logic and different execution paths. Workflows are created and edited using the Workflow Designer which includes many building blocks (Activities) for submitting Jobs, updating JAMS Variables, and many more JAMS specific tasks. Below is a listing and a brief description of the Activities available in JAMS Workflow Designer organized by Grouping.

JAMS Grouping

AskQuestion: is used to halt an executing workflow until user input is provided. This Activity sends the question to the JAMS Scheduler and displays the question in the Monitor View. Users with Manage access for the Job can respond to the question using the Monitor View detail window.

GetVariable: gets the value of a JAMS variable.

ManageActivity: provides an execution scope in which Activities can be canceled or retried.

Repeat: hosts one Activity that is repeated at an interval.

SetJAMSContext: is necessary only if you are using JAMS Activities in a non-JAMS environment. When a JAMS workflow is executed, the JAMS Context is automatically established. If using Activities outside of JAMS, you can either set the JAMS Server in each Activity or add a SetJAMSContext activity to the workflow allowing all

(13)

SubmitEntry: submits another JAMS Job or Setup. The Activity can wait for the completion of the submitted Job or Setup and can take different actions depending on the success or failure of the entry.

SQL Grouping

OdbcScript: runs SQL commands through an ODBC connection.

OleDbScript: runs SQL commands through an OLEDB connection.

SQLScript: runs SQL commands.

SQLStoredProc: executes a SQL Server stored procedure.

Execution Grouping

CMDScript: runs a command script.

ExecuteCMD: executes a single command using CMD.EXE.

ExecuteProcess: executes any process or executable.

Cancelable: includes an option to send a cancellation request to its body Activity.

PowerShell Grouping ____

PSWrapper: wrapper around a PowerShell function or command.

PSRunspace: defines the scope of a PowerShell runspace.

PSScript: runs a PowerShell script.

Communication Grouping ___

SendEmail: sends an email using SMTP.

Files Grouping

ForEachFile: finds designated files within a directory matching a wildcard pattern.

UnzipFiles: unzips a .Zip file.

WaitForFile: waits for events on a specified file.

ZipFiles: creates a .Zip file.

Files Transfer Grouping

FtpDownload: downloads a file using FTP or Secure FTP (SFTP).

FtpUpload: uploads a file using FTP or SFTP.

SftpDownload: downloads a file using SFTP.

SftpUpload: uploads a file using SFTP.

ScpDownload: downloads a file using Secure Copy Protocol (SCP).

ScpUpload: uploads a file using SCP.

S3Download: downloads a file using Amazon’s Simple Storage Service (S3).

S3Upload: uploads a file using Amazon's Simple Storage Service (S3).

File Transfer Session Grouping

SFTPSession: hosts an SFTP connection for other FileTransferSession Activities.

FTPSession: hosts an FTP connection for other FileTransferSession Activities.

ScpSession: hosts an SCP connection for other FileTransferSession Activities.

S3Session: hosts an Amazon S3 connection for other FileTransferSession Activities.

(14)

FileTransferSessionGetFileLength: get a file’s size for the current file transfer session.

FileTransferSessionSendCommand: sends a command during the current file transfer session.

Mail Server Session Grouping

IMAPSession: creates an IMAP session that hosts a mail server connection.

POPSession: creates an POP session that hosts a mail server connection.

DeleteMailMessage: deletes a mail message on a mail server with a corresponding header.

GetMailHeaderList: gets a collection of mail headers on a mail server that matches the specified mask. The returned collection is a list of JAMSMailMessageInfo objects.

GetMailMessage: gets a JAMSMailMessage object for the specified header on a mail server.

GetMailServerFolder: gets the current folder on a mail server.

ProcessEmails: looks for one or more emails matching a specified mask and invokes the body Activity once for all matching email.

SaveMessageAttachments: saves attachments on a mail message to the file system.

SetMailServerFolder: sets the current folder on the mail server.

ForEachMailMessage: looks for one or more email messages matching a mail specification and invokes the body Activity once for each matching message.

ForEachAttachment: looks for one or more mail messages matching a mail specification, downloads the attachments to the specified working directory and invokes the body Activity for each matching file.

Coordinators Grouping

ClearEvent: sets the specified event to false.

SetEvent: sets the event time.

WaitForEvent: waits for the specified event to be set by a SetEvent Activity. If the event has already been set, WaitForEvent completes immediaetly.

Control Flow Grouping

DoWhile: executes the Activity contained in its body at least once until a specified condition evaluates to false.

ForEach<T>: executes an Activity action once for each value provided in the values collection. If: provides a conditional if-then-else condition.

Parallel: is a container object that executes multiple child Activities at the same time. This class cannot be inherited.

ParallelForEach: enumerates a collection and executes an Activity for each element of the collection in parallel.

(15)

Switch<T>: evaluates a specified expression and executes using a collection of Activities whose associated key matches the value obtained from the evaluation.

Flowchart Grouping

Flowchart: is a container object that executes multiple child activities one after another. Similar to a

Sequence, a Flowchart is more flexible allowing control to return to an earlier step. Sequences can only execute forward, not backward.

FlowDecision: is a conditional node that provides a branch for the flow of control into one of two alternatives based on whether a specified condition is satisfied. If the flow requires more than two branches, use FlowSwitch instead.

FlowSwitch<T>: is a conditional node that provides branching for the flow of control based on matching criterion when more than two alternative branches are required. If the flow branching requires only two paths, use the FlowDecision activity instead.

Messaging Grouping

CorrelationScope: provides implicit CorrelationHandle management for child messaging Activities.

InitializeCorrelation: initializes correlation without sending or receiving a message.

Receive: receives a message.

ReceiveAndSendReply: receives a message as part of a request/reply message exchange pattern.

Send: sends a message to a service.

SendAndReceiveReply: sends a message as part of a request/reply message exchange pattern.

TransactedReceiveScope: scopes the lifetime of a transaction which is initiated by a received message. The transaction may be flowed into the workflow on the initiating message or created by the dispatcher when the message is received.

RunTime Grouping __

Persist: saves a workflow to disk, if possible. This Activity cannot be executed in a non-persistence zone, for example, within a TransactionScope Activity.

TerminateWorkflow

: terminates the execution of a workflow.

Primatives Grouping _

Assign: assigns a value to a variable at the current scope.

Delay: puts one path of execution into an idle state, possibly allowing the workflow to be unloaded.

InvokeMethod: executes a public method of a CLR object.

WriteLine

: writes a specified string to the console or a specified TextWriter object.

Transactions Grouping

CancellationScope: specifies an Activity for execution and cancellation logic for that Activity.

CompensableActivity: supports compensation of its child activities.

Compensate: used to explicitly invoke the compensation handler of a CompensableActivity.

Confirm: used to explicitly invoke the confirmation handler of a CompensableActivity.

TransactionScope: demarcates a transaction boundary.

Collection Grouping

AddtoCollection<T>: adds an item to a specified collection.

ClearCollection<T>: clears a specified collection of all items.

ExistsInCollection<T>: determines whether a specified item exists in a particular collection.

(16)

DeleteLetterFile: Removes a letter file from the “LETTERSPECS” folder on the Symitar server.

EmailReports: attaches one or more reports to an email message and sends it to the designated receipient(s).

FileToPC: generates an FTP download from any Symitar directory to a local PC.

LetterFileToPC: FTP download from the “LETTERSPECS” folder on the Symitar server.

PCToDataFile: FTP upload to the “DATAFILES” folder on the Symitar server.

PCToEditFile: initiates an FTP from a PC to the Symitar edit file.

PCToFile: creates a generic upload to any directory on the Symitar system.

PCToLetterFile: FTP upload to the “LETTERSPECS” folder on the Symitar server.

ReportFileToPC: FTP download from the “REPORT” folder on the Symitar server.

RunJobFile: runs a job file in the specified SYM (e.g. Sym222).

SymConfig: the parent activity that allows users to set the configuration settings (e.g., Server Name, SymUserId, Symitar logon credentials) for all Symitar activities contained within it

Working with Setups

A Setup defines a particular occurance or view for one or more Jobs. Setups are commonly used to schedule a Job or stream of Jobs that automatically execute at regular intervals. Setups are created and defined usng a Setup Wizard.

Start by selecting the Setups shortcut located on the bottom of the JAMS Client View window and then click the

Add button on the Ribbon Bar.

This action opens the JAMS Setup Definition Wizard's title page.

The JAMS Setup Definition Wizard

(17)

2. Select Next to access the Notification Email Addresses page where you can supply one or more addresses to alert specific staff members if a Setup fails or doesn’t complete within an allotted timeframe. Click the

Next button.

3. On the Jobs page, add the name of individual Jobs that make up this Setup. In addition, you can remove a Job and modify the properties of an existing Job using the buttons located below the Jobs view area.

(18)

5. Click the Next button to open the Finish page. Choose the Finish button to complete the new Setup definition process.

Working with Views

(19)

The data in any View can be sorted by clicking on a column header.

Customizing Views Using the Column Chooser

With the Column Chooser tool you to add, remove and repositions columns in the Monitor, History and folder Views. To activate this tool, follow the steps below:

1. Right click on any column header within a View to open its context menu.

2. Select the Column Chooser command to view all the column titles in the Customization window.

3. To add a column to the current View, drag and drop a column title to the left or right of an existing column.

Note: Double-clicking a column title appends the new column to the rightmost position within the

current View.

4. To remove an existing column, just drag and drop its header out of position until an “X” appears and then release the mouse.

5. To reposition any column, drag and drop the column header into the desired position within the current View.

Working with Folders

A JAMS Folder contains a user defined grouping of Jobs and Setups that appear on the Shortcut Bar. Folders can be defined by department (e.g., Accounting, IS, Sales), by function (e.g., EDI, Web, Security, Audit), or any other way that is meaningful to your organization. Follow the steps below to add, edit and delete a JAMS Folder.

Adding a Folder

1. Right-click anywhere in the Definitions group on the Shortcut Bar. 2. Select the Add Folder command from the context menu.

3. The JAMS Folder Definition Wizard Introduction page opens. Click the Next button to move to the Folder Name page.

4. Enter a unique name for the new Folder. Click the Next button. 5. On the Notification page, enter one or more email addresses to

alert staff if there’s a problem with a Job or Setup contained inthe Folder. Leave the entry field blank if no one needs to receive notifications. Click the Next button.

6. Click the Finish button to complete the Folder definition process.

Editing a Folder

1. In the Definitions window, right-click the Folder that requires editing.

2. Select the Properties command from the context menu to open the Folder Properties window. 3. Using the four tabs on the right portion of the window, make any necessary changes to the Folder

properties.

(20)

all previously run Jobs, their execution statistics and completion status.

1. To get started, select the History shortcut. This action opens the History Query dialog box.

2. Enter specific parameters to narrow your Job query and then select the OK button.

(21)

4. Double-click a specific Job from the list to display its statistics, log file or audit trail data in the job detail window.

5. Select the Statistics tab to view the current Job's runtime compared to its historical data.

Submitting Jobs Manually

(22)

Once the end-user selects a Job they may be presented with a fill-in-the-blank form to define the Job’s required parameters, which can then be edited and verified before the Job is submitted.

With the built-in security model, JAMS users can submit Jobs as long as they have the proper access. As part of the submittal process, users can also modify Job output characteristics such as the print queue or number of copies to output a report.

To submit a Job or Setup follow the steps below:

1. Click the Submit Shortcut if the Submit Jobs View is not already active.

2. Expand the Folder and locate the Job or Setup to be submitted. 3. Double-click or right-click the desired Job or Setup to open the

Submit dialog box.

4. Include the desired information in the Parameters, Reports, and Schedule tabs.

Note: Depending on the Job's parameters, there may only

be one or two tabs visible.

(23)

Working with Projected Schedules

The Projected Schedule displays a graphical view of pending JAMS Jobs and Setups. Users can view all scheduled Jobs or filter a subset of Jobs over a specified time range.

To generate a projected schedule for all scheduled Jobs, click on the Projected

Schedule Shortcut in the Shortcut Bar. The resulting display defaults to the current

24 hour timeline view.

Filtering the Projected Schedule Results

To filter a specific group of Jobs and Setups, use the Query button located on the JAMS Ribbon Bar.

1. This action opens the query dialog box. Select a Folder Name using the Folder search button or enter a Job Name.

Note: including multiple Job entries is not allowed; however, the Job Name field does allow

for wildcard queries (e.g., *workflow).

2. Enter a Time Range using the date and time selector. 3. Activate the appropriate checkboxes to refine your query.

Use Current Schedule: when enabled, pulls in the current schedule from the Monitor View.

Include Planned: filters all scheduled Jobs including those with the “Automatically Submit?” option

unchecked.

(24)

4. Click the OK button to build the Projected Schedule based on your query parameters.

Modifying the Timeframe Display

After generating a Projected Schedule, users can modify their results by selecting different views: Day, Work Week, Week, Month and Timeline.

To change the timeframe, right-click within the Projected Schedule display to view the context menu. Make a selection from the Change View To submenu or use the Go to Today or Go To Date options to modify the timeframe display. Depending on the selected view, you can also adjust the Time Scales and Captions.

(25)

parameters as detailed below:

Items (Jobs or Setups) in red are expected to run beyond their designated SLA (Service Level Agreement) time.

Jobs and Setups displaying orange have run past their predefined end time. Items in yellow have run beyond their original schedule time.

Note: double-clicking or right-clicking a Job within the display will open its settings window.

Installing the Projected Schedule Shortcut after Upgrading JAMS

JAMS V6.1.281 added the Projected Schedule function to the Shortcut Bar. For new JAMS installations, the Projected Schedule Shortcut appears by default. However, if you are running an earlier version of JAMS you must first upgrade to JAMS 6.1 or later and then add the Projected Schedule Shortcut using the manual process described below.

1. Right-click the Shortcut Bar and select Add Shortcut command from the context menu.

2. In the Add a Shortcut wizard, define the Name and Title (e.g., Projected Schedule) and choose an icon. Click the Next button.

3. On the View page, choose the Projected Schedule option from the list and click Next.

4. On the following page, define the Properties for the Projected Schedule view. For each view you can set different parameters for displaying the schedule (e.g., by Folder or Job name). Select the JAMS Server from the dropdown list, or choose the Active Server option to automatically generate a Projected Schedule using any accessible JAMS server.

Use Current Schedule: pulls in the current schedule from the Monitor View which is controlled from

the “ScheduleAdvance” option in Configuration Settings.

Include Planned: filters all scheduled Jobs including those with the “Automatically Submit?” option

unchecked.

Include Repeated: allows the Projected Schedule to include Jobs submitted based on their

recurrence schedule.

5. On the last page of the wizard, confirm your choices. At this point you can create additional Views or change the View properties by selecting the Query button from the Ribbon Bar. Click the Finish button to close the wizard.

6. The Projected Schedule Shortcut should now appear in the Shortcut list.

Using Alerts

JAMS has several built-in alerts that can be configured to send e-mail notifications to users when certain conditions are met. The following table describes the conditions that can trigger a predefined alert.

State Description

(26)

average completion times.

EntryMissedWindow A Job or Setup that missed the window for its scheduled run time.

Creating Alerts

1. Click on the Alerts shortcut in the Management group. 2. Select the Add button to start the Alert Definition Wizard.

3. Step through the wizard to define the Alert name, events, and notification. Mimimaly, you must provide a unique name for the Alert.

4. Click the Finish button to complete the Alert definition process.

Assigning an Alert

Once an Alert has been created you can assign it to any JAMS Job, Setup or Folder. To get started:

1. Double-click on a JAMS object (Job, Setup or Folder) to open the details window and click on the

Properties tab located on the left side of the window.

2. At the lower part of the Properties tab expand the Alerts group. To assign an Alert to the JAMS object check the listed Alert to activate.

Note: Alerts inherited from a higher level will appear grayed out as shown below.

(27)

Note: If an Alert is assigned to a Folder it will be applied to all Jobs and Setups located within

that Folder.

Customizing Alerts

You can customize the Alert notifications by adding or removing information about a particular JAMS Job. Custom alerts can be defined in the Alerts property for any Job, Setup or folder. These notifications can be defined by adding email address to the Notification Names section for that alert.

Emails defined at the Folder and Job level can be removed on a per Job/Setup basis by placing a “-*” (excluding quotes) in front of the entered email address.

JAMS has additional built-in alert capabilities which can be referenced when making calls to the JAMS SDK. These additional alerts tend to be used more for in-house development purposes rather than for end-users.

Parsing in Alerts

Parsing makes alerts more useful by including additional information about the assigned Job, Setup or other JAMS object.

(28)

Using the Monitor and Gantt Views

The Monitor enables users to view current Jobs and Setups in the Scheduler and provides access to comprehensive Job management tools. Use the following steps to open and manage current Jobs and Setups.

Accessing the Monitor

To get started, select the Monitor shortcut to open the Current Jobs View.

(29)

To manage a Job currently in the Schedule, right-click on a Job from the

Monitor Current Jobs View to open its context menu.

Select the Show Details command or just double-click the Job name to open its detail window.

Each Job or Setup listed in the Scheduler displays a number of properties as shown in the above screenshot and detailed in the table below.

Job

Properties

Description

General Displays Folder, Setup, Submit and Job status information. Statistics Shows times, execution statistics and related charts. Log File Lists all OS generated logs.

Dependencies Details the dependencies for the Job or Setup.

Parameters Details parameter names and values associated with the Job or Setup.

Audit Trail Lists audit trail items for the Job, including: message, comment, user name, local and UTC audit times.

Using the Gantt View

The Gantt View provides a visual representation of currently scheduled Jobs or Setups. It plots their current run times against average run times.

Like the Monitor, the Gantt View provides quick access to the properties (e.g. parameters, security and dependencies) for each JAMS Job or Setup.

(30)

Using the SQL Agent Job Monitor

The Monitor lists all SQL Server Agent Jobs running on the current JAMS Client and those located on remote servers.

Accessing SQL Server Agent Jobs on the Local Machine

To view all SQL Agent Jobs located on the current machine, select the External tab on the JAMS Ribbon Bar and click on the SQL Agent Jobs shortcut.

(31)

1. On the External tab, right-click on the Shortcut Bar (in the SQL Agents group) and choose the

Add Shortcut command to open the Add Shortcut Wizard.

2. Choose an icon and then enter the name and title for the shortcut. Select the Next button.

3. On the next page select a View. Choose SQL Agent from the list and click Next. 4. Enter the SQL Server instance in the appropriate field and click Next.

5. Select the Finish button to complete the Shortcut defintion.

When the newly added shortcut is selected, all Jobs on the specified remote machine are displayed. If no Jobs appear, make sure there are SQL Agent Jobs present and your user account can access the remote Jobs.

Supported SQL Scheduler Versions

JAMS agents support monitoring of SQL Agent jobs for the following versions of SQL Server. SQL Server 2014

SQL Server 2012 SQL Server 2008 SQL Server 2005

The version in use is determined by SQL Server currently installed with the JAMS Client. If the client is running SQL Server 2012, then it can access Jobs from instances running previous versions of SQL Server. However, if the JAMS Client is running SQL Server 2005, it can only access Job information from instances running from that server version.

Converting Tasks

1. To convert a SQL Server Agent Job to a JAMS Job, select a Job from the SQL Job Definitions list, right-click, and choose the Convert option or use the Convert to JAMS button on the Ribbon Bar to access the conversion wizard.

2. On each step of the wizard, fields will be pre-populated with information from the selected SQL Agent Job.

(32)

Using the Task Scheduler Monitor

The Task Scheduler Monitor allows you to view a description of all Windows Task Scheduler Tasks on the machine running the JAMS Client as well as those located on other computers.

Accessing and Displaying Scheduler Tasks

To view the installed Tasks running on the current machine, select the External tab on the JAMS Ribbon Bar and click on the Scheduler Tasks shortcut.

By default, this will display all Windows Scheduler Tasks currently configured on the local machine.

Displaying Configured Tasks on a Remote Machine

To display a listing of configured tasks located on a remote machine, go to the External tab. Right-click the Shortcut Bar and choose the Add Shortcut option to start the Add Shortcut Wizard.

(33)

2. On the following page choose a View to associate with this shortcut. In this example, select the

Scheduled Tasks option from the View list and click the Next button. 3. On the wizard's Property page enter the UNC path for the remote computer.

Note: For Windows Vista, Windows 7 or Server 2008, the Task Scheduler supports folders to

organize Tasks. However, if the Folder Name field is left blank, then Tasks from all folders will be displayed. To limit the results, simply enter the path of the desired folder. Entering a single backslash "\" displays all Tasks in the root folder. However, using the above example, Tasks within the \Microsoft\Windows\Defrag\ directory will appear in the Task Definitions View.

4. Click the Finish button to complete the wizard.

When the newly added shortcut is selected, all Tasks within the Defrag directory on the remote machine are displayed. If no tasks appear, make sure there are Tasks present and your current user account can access the remote Tasks.

Note: After changing the shortcut’s Query properties, select the shortcut in the Shortcut Bar and click

the Refresh button in order for the Query changes to take effect.

Scheduler Versions

There are two supported versions of Windows Scheduler. The version in use is determined by the operating system on which the JAMS Client is installed. If the JAMS Client is running on Windows Vista, Windows 7 or Server 2008, then it will be able to access Task information from other machines.

However, if the client is running Windows XP or Server 2003, it will only be able to access Task information from other machines running XP or Server 2003. That’s because the libraries required to access Tasks on Vista and Server 2008 machines are not present and cannot be retrieved from these servers.

Converting Tasks

To convert a Task Scheduler Task to a JAMS Job, right-click any Task from the Task list and select Convert from the context menu. You can also use the Convert to JAMS button located on the Ribbon Bar.

A Conversion Wizard opens. On each step of the wizard, fields will be pre-populated with information. You can modify the information before the new JAMS Job is created.

(34)

It is also possible to convert multiple Tasks concurrently. Just select several Tasks from the Task list and click the

Convert to JAMS button. This will start the Wizard for converting multiple Tasks. The first few steps will prompt for information. The Wizard will then attempt to convert all of the selected Tasks to JAMS Jobs.

Converting Task Scheduler, SQL Agent and CRON Jobs to JAMS

Jobs

Converting Windows Task Scheduler Tasks

During the installation process, JAMS searches for all local Task Scheduler tasks, and if any are detected, a converter window opens listing these jobs.

To convert the local Task Scheduler tasks to JAMS Jobs, right-click on a listed Task Scheduler task and select the

Convert to JAMS command from the context menu.

Note: Task Scheduler tasks are supported for these operating systems: Windows XP, Vista, Windows 7,

8 and Windows Server 2003, 2008 and 2012.

Accessing and Converting Remote Task Scheduler Tasks

All Task Scheduler tasks located on an external machine can be queried using the Task Scheduler Monitor.

To convert a remote Task Scheduler task to a JAMS Job, highlight the job and press the Convert to JAMS button on the Ribbon Bar or use the steps below:

(35)

For more information on how to convert Task Scheduler tasks, please refer to the help topic: Using the Task

Scheduler Monitor.

Converting Multiple Remote Task Scheduler Tasks

To convert multiple Scheduler tasks to JAMS Jobs. . .

1. Highlight two or more tasks from the Task View (control + Click).

2. Right-click one of the highlighted tasks and select the Convert to JAMS command from the context menu. 3. This will open the Conversion Wizard. The first few steps will prompt for information common to all the

selected tasks. The wizard then converts the selected tasks to JAMS Jobs.

Converting SQL Agent Jobs

SQL Agent jobs are converted using the same steps as the Windows Task Scheduler tasks, described in the previous section.

To convert a Server Agent job to a JAMS Job, select the job and use the Convert to JAMS button on the Ribbon Bar or follow the steps below:

1. Using the External tab, click the SQL Agent Jobs shortcut. 2. Select a Job from the SQL Job Definitions list and right-click.

3. From the context menu choose the Convert command to open the Conversion Wizard. 4. Use the wizard to define the necessary conversion parameters.

For more information on how to convert SQL Jobs, please refer to the topic: Using the SQL Agent Monitor.

Converting Multiple SQL Agent Jobs

To convert multiple SQL Agent jobs simultaneously . . .

1. Highlight two or more jobs from the SQL Job Definitions View (control + Click).

2. Right-click one of the highlighted jobs and choose the Convert to JAMS command from the context menu.

3. This action opens the Conversion Wizard. The first few steps will prompt for information common to all the selected jobs. The wizard then converts the SQL jobs to JAMS Jobs.

External Conversion Utility for CRON

JAMS can quickly convert CRON jobs to JAMS Jobs using a free UNIX Cron2JAMS converter. This tool converts your crontab configuration files to a single PowerShell script which can then be run from the JAMS Client.

1. To start, use the link to download the UNIX Cron2JAMS converter by first logging into the JAMS Technical Support site.

2. When launched, the Cron2JAMS.exe converter tool uses a script that converts existing CRON jobs into a single PowerShell script that can be quickly converted into a JAMS Job.

3. Open a command prompt (cmd.exe) on your JAMS Scheduler machine.

4. Change the directory to the location where you extracted the Cron2JAMS.exe zip file. 5. Call the Cron2JAMS with the necessary parameters that are described below.

Cron2JAMS Parameters

Inputfile: the path to the crontab file to be converted to JAMS Job definition. If the crontab file is in same

location as the Cron2JAMS.exe file, just use the file name.

Outputfile: the path and filename for the PowerShell script that Cron2JAMS creates. If the output file is in the

same location with the Cron2JAMS.exe file, use the file name.

JAMSServer: the JAMS Server where the JAMS Jobs reside. If the Cron2JAMS converter is located on the same

(36)

JAMS includes different methods for scheduling Jobs and Setups. One is to create a straight-forward schedule with fixed start and end execution times. Another method defines a flexible windows of time when Jobs may be scheduled. Using this “Named Times” option JAMS can prevent Jobs from executing until their scheduled window is enabled and can also take various actions when a Job’s window closes before the Job completes.

Defining or Modifying Scheduling Windows to Jobs and Setups

You can assign a Named Time to Jobs and Setups using a scheduling window. If the time window needs to be shorter or longer, or a new time-of-day-range needs to be set, you make just one entry that applies to all Jobs and Setups that use it. This simplifies the process of making schedule modifications to Jobs and Setups to just a few key strokes.

To assign a new or edit an existing Named Time definition, follow the steps below: 1. From the JAMS Client click the Times shortcut in the Management Group. 2. The Named Time Definitions View opens.

3. To create a new Named Time definition, click the Add button on the Ribbon Bar to open the JAMS Named Time Definition Wizard. Enter a unique name for the Named Time and specify a start and end scheduled time. Click the Finish button.

To modify an existing Name Time, double-click a definition from the list to open its property window. Select the Times tab and make any modifications to the start and end time schedules.

Use the following controls to modify each Named Time definition.

Start Time: enter the time of day this Named Time is scheduled to be enabled.

Automatically enable: Enable the checkbox if you want JAMS to automatically enable this Named Time at the Start Time specified. If unchecked, the Named Time remains disabled until it is manually enabled.

End Time: enter the time of day this Named Time is scheduled to be disabled.

Automatically disable: Enable the checkbox if you want JAMS to automatically disable this Named

(37)

Named Times can be used to limit when manually submitted Jobs are allowed to run; for example, during periods when other Jobs may use significant system resources. See the Missed Windows Action No Action option described in item #6 below.

Assigning Named Times to Jobs and Setups

Once a Named Time has been created you can then associate it with any Job or Setup. 1. To get started, double-click a Job or Setup to open its definitions window.

2. From the definitions window, select the Properties tab. Locate and expand the Submit Times option.

3. Click the File browser button to view a list of existing Name Time definitions. Double-click a definition to populate the field.

4. Use the adjusters to define the desired schedule time window.

5. From the dropdown list, select an action when a Job or Setup fails to execute within the defined scheduling window. The options include:

No Action: the scheduling window is used to limit the times when the Job or

Setup is manually submitted.

Continue: the Job or Setup does not start until the time window opens but

does not reschedule or abort if the window closes before the Job or Setup completes.

Abort or Delete: the Job or Setup does not start until the time window opens and is aborted or

deleted if the window closes before the Job or Setup completes.

Reschedule or Continue: if the Job or Setup has not started when the window closes it is then

rescheduled to start during the next open window. However, if the Job or Setup has started, it can continue.

Restart or Reschedule: If the Job or Setup has not completed when the window closes, it is

rescheduled for the next open window. If the Job or Setup is executing when the window closes it is aborted and then rescheduled.

Not Specified: no action is taken.

6. Optionally, enable the Notify of missed window? checkbox to tell JAMS to perform a Job or Setup notification if a Schedule Window is missed.

7. Save the changes in the definitions window.

(38)

Scheduled dates: generic dates can be used

when scheduling a Job or Setup in JAMS.

Default parameters: if a Job parameter’s data type is DATE, you can specify a default value using

generic date specifications.

Note: When a user selects a Job, they are presented with a form to set values for the Job's

parameters. Parameters with a data type of DATE are presented using the standard MM/DD/YY date field, but JAMS uses the generic date specification to determine the default date.

Setup parameter values: When defining a Setup, JAMS prompts for the Job's parameter values. If the

Job parameters uses the DATE data type, the parameter form displays a sixty-character text field for the date parameter rather than the standard MM/DD/YY field. You can then enter a generic date specification.

Note: When JAMS automatically submits Jobs, prompting for the parameter values is not

possible. Instead, the generic date specification is evaluated to obtain the value for the parameter.

Simple Date Specifications

Simple date specifications specify a date relative to the current date. The format and description for a simple date specification is as follows:

Day-of-Week: can be the full name of a weekday or the first three letters of a weekday name. When

specifying a day of the week, e.g., MONDAY, JAMS interprets this as “Monday of this week.” In this context, a week begins on Monday and ends on Sunday.

The days of the week can be preceded by a modifier such as LAST, THIS, or NEXT. Inserting a THIS

modifier has no effect and is used only for readability.

When using a modifier, such as LAST, JAMS interprets this to mean " the weekday from last week."

Workdays: If you specify "WORKDAY" or "WORKDAYS", JAMS determines if a day is a workday using a two-step process.

1. JAMS looks at the WORK_ddd configuration setting, where ddd indicates the day of the week (e.g. Wed). This sets up the initial true or false indication that the day is indeed a workday.

2. For the date in question, JAMS also searches for special dates. To access, selet the Date shortcut and double-click the desired date.

If the Workday check box is enabled, the date is a workday. If the Workday box is unchecked, the date is not a workday.

However, if the check box is filled, it indicates that the special date should have no effect on the workday status.

(39)

Valid Simple Date Specifications

Included below are some examples of valid, simple-date specifications:

TODAY + 5 NEXT MON LAST TUESDAY WORKDAYS

Complex Date Specifications

Complex date specifications are used to stipulate a date relative to an arbitrary period of time (e.g., describing a month or fiscal period).

A complex date specification may be thought of as two components: the day specification and the period

specification. For example, in the text "1st WORKDAY of NEXT MONTH," the day specification is 1st WORKDAY and the period specification is NEXT MONTH.

The general format of a complex date specification is as follows: [day-of-period OF] period [+/- number of days] The syntax for the day-of-period specification can take one of two forms. Both forms are comparable.

The two forms for the day-of-period specification are:

Form 1 FIRST LAST 1[st] 2[nd] 3[rd] integer [st, nd, th] Day-of-week WORKDAY WEEKDAY DAY MONTH Or . . . Form 2 Day-of-week WORKDAY WEEKDAY WEEK DAY MONTH OF FIRST LAST 1[st] 2[nd] 3[rd] integer [st, nd, th]

Note: If you do not specify the day of period, the default becomes the current day.

The syntax for the period specification is:

(40)

Note: While this syntax specification may seem overly complex it actually a mimics how people

commonly specify dates.

User Defined Period

When specifying a period with user defined Date Types, you may need to supply both specific and generic Date Types. For example, if you defined the Date Type FISCAL with specific Date Types of PERIOD_01 through PERIOD_12, you can specify the second period as: FISCAL PERIOD_02 or PERIOD_02.

If you defined two Date Types that both use the specific Date Type PERIOD_02, then you must specify FISCAL PERIOD_02.

Specifying Weeks

When used in the context of a time period, a week is defined as starting on the first day of the period and continuing for seven days.

Valid Complex-Date Specifications The following examples of valid complex-date specifications are based on the current date being January 1st, 2014.

Specification Date

FIRST MONDAY OF NEXT MONTH 03-FEB-2014

2ND MONDAY OF THIS MONTH 13-JAN-2014

FIRST MONDAY OF LAST JANUARY 07-JAN-2013

6TH WEEKDAY OF NEXT MONTH 10-FEB-2014

6TH WEEKDAY OF MONTH 08-JAN-2014

LAST DAY OF LAST MONTH 31-DEC-2013

Setting Triggers

Triggers are used to define event-based schedules. A Trigger contains two important settings: events and actions. When JAMS determines that all Trigger's events are true, it then executes a user-defined list of actions.

Setting up a New Trigger

To setup a new Trigger, follow the steps below:

1. Highlight the Triggers shortcut, located at the bottom of the window, to open the Trigger Definitions View.

(41)

4. On the Triggers Events page create the event(s) that you need to initiate the Trigger actions. Use the Add dropdown to choose the Event type. Depending on the Event type selected (Job, Setup, File, Variable Event, or Mail Event) an Event window opens.

For each selection (except for the Mail event) click the File Browser button and navigate to the desired trigger event (Job, Setup, File or Variable Event) in the search window. Double-click the selection to close the Event type window.

5. The selected Trigger Event appears on the Trigger Events page. Complete the remaining entries. Click the

Close button and save the entry. The selected event now appear on the Trigger Events page. Continue to

add more events or choose the Next button.

6. The Trigger Actions wizard page opens. Click the Add button to open the dropdown menu and choose an action type (Submit Job or Submit Setup). Depending on your choice a Trigger Job or Setup action window appears.

7. Click the File Browser button and navigate to the desired trigger Job or Setup and double-click the selection. Set the Date and Time fields. Click the Close button to save the entry. The selected Trigger Event now appears on the Trigger Actions page. Click the Next button.

8. Click Finish to complete the Trigger setup process.

Modifying Existing Triggers

1. To change the properties for an existing Trigger, open the Trigger Definitions View by selecting the Triggers shortcut at the bottom of the window.

2. Open the selected Triggers definition by right-clicking the Trigger entry and choosing the Properties command from the context menu or just double-click the Trigger item from the list.

3. From the Triggers definition window, use the property tabs to make changes.

On the Events tab insert a new Trigger by choosing the Add button or modify any existing properties by double-clicking the Trigger under the Description header or choose the Properties button.

(42)

5. Click the Close button on the top right corner of the window and confirm the changes. 6. On the Actions tab follow the same procedure as described in the previous 5 steps. 7. Select the Close button to update the Trigger.

Using Resources

JAMS Resources are powerful tools that can help you allocate how batch Jobs are run. Resources let you define the necessary requirements for all Jobs and Setups, allowing JAMS to determine which Jobs can run concurrently. Resources can be assigned to Folders, Jobs, and Setups. The Resource itself is defined by setting a specific quantity. Jobs and Setups typically utilize a portion of this quantity when they run.

Resource Allocation-Automatic and Manual Configuration

JAMS can automatically control how each Job or Setup acquires and releases the Resources assigned to them. The Resource quantity available can be manually increased or decreased at any time. You make the modifications in one place and it is available to all Jobs and Setups that need it.

As your batch processes move from one operating system to another JAMS continues to enforce the assigned Resources requirements.

Resource Behavior

Resources have some unique characteristics that are listed below:

Jobs and Setups inherit the Resources that have been defined in their respective Folders. Jobs and Setups can actually reduce or increase the inherited Resource requirements. Jobs and Setups can add their own Resource requirements.

Sufficient Resources must be available for a Job or Setup to run.

During the Setup execution process you can hold Resources across for all component Jobs. Resources can be specific to a node or server.

Resources can be used on any JAMS supported operating system.

The available Resource quantity can be increased or decreased at any time.

(43)

1. To define a Resource quantity, select the Resources shortcut located on the Configuration group.

2. The Resources Definitions View opens.

3. From the Ribbon, choose the Add button to access the Resource Definition wizard.

4. On the first page of the wizard enter a name and optional description for the new Resource. Choose the Next button.

5. On the following page set the Resource’s Quantity Available value. Click the Next button and then choose Finish to complete the Resource

definition process. The new Resource now appears in the Resource Definitions View.

Modifying an Existing Resource Definition

1. Open the Resources shortcut.

2. From the Resource Definitions View, double-click the selected Resource to open its definitions window. 3. Use the Available tab to change the Quantity Available

setting.

4. Click the Security tab to choose the access level for the Resource. See the following subsection (Setting Resource Security) for a description of each access level.

5. Click the Close button to save your changes.

Determining How Much Resource to Assign a Job or Setup

When manually modifying Resources, as described above, how do you know how much or how little to assign to a particular Job or Setup?

JAMS provides several ways to determine if a Resource is working above or below its effective allocation.

Use the Dashboard

Both the Advanced and Current Load Balancing Dashboards (available on the JAMS Client version 6.1 and newer) incorporate a graphical summary of information and trends within the JAMS environment. Specifically, both include a Resources subpanel to determine the load availability for each available Resource. For more information on using the built in Dashboards, go to the topic: Other Preinstalled

Dashboards.

Insert a Quantity in Use Column

To see what Resources are currently active, use the Column Chooser to insert a

Quantity in Use column in the Resource Definitions View.

Access the Monitor

(44)

Resources in Use

You can query the JAMS SQL database to determine what Resource definitions are currently in use. SELECT M.resource_name,

M.qty_available,

IsNull((select SUM(U.qty_in_use) from dbo.ResourceInUse as U

where U.resource_id = M.resource_id), 0) as InUse FROM dbo.ResourceM as M

Setting Resource Security

The Resources Security tab defines the level of access for this Resource. Essentially, this is an Access Control List with one to many Access Control Entries (ACE). Each ACE can specify the following rights:

Acquire: allows the user to obtain a portion or all of the Resource's quantity allocation.

Change: permits the modification of this Resource definition provided the user has CHANGE access in

Resource Definitions.

Control: allows users to modify the Resource’s Access Control List.

Delete: permits deletion of the Resource definition provided that the user also has DELETE access for

Resource Definitions.

Inquire: users have the ability to inquire into the Resource definition as long as they have INQUIRE

access to Resource Definitions.

Adding an Existing Resource to a Job, Setup or Folder

1. Open a Job or Setup definition by double-clicking the selecting the item.

2. Select the Properties tab. Open the Resources subsection and choose the Add button.

(45)

4. Save the Job by clicking the Close button at the upper right of the definitions window.

Deleting a Resource

To delete a Resource, open the Resource Definitions View and highlight the Resource to be removed. From the Ribbon Bar choose the Delete button.

Note: you must have the proper level of access in order add or delete a Resource.

Inheriting a Resource Definition via Folders

Jobs and Setups can inherit the Resources defined within their Folder. This inheritance feature simplifies the assignment of Resources to any Job or Setup.

To assign a new Resource definition: open the Folder’s definition by right-clicking and choosing Properties > Resources. Follow the steps described in the previous section: Adding an Existing Resource to a Job, Setup or

Folder.

Working with Dependencies

Dependencies are prerequisites that must be completed before a scheduled Job or Setup can execute. A single Job or Setup can have an unlimited number of Dependencies. In fact, a JAMS Job can serve as a Dependency for any other Job regardless of where or how the Job runs.

Other JAMS components, including Scripts, cannot be released to run until all their dependent Scripts have been successfully completed. For example, a Powershell script designed to run on Windows could have dependent Scripts that must complete first on other JAMS supported operating systems.

Dependency Types

JAMS supports the following types of Dependencies: Job Completion Setup Completion File Presence File Absence File Availability Variable Value

Remote Job Completion Remote Setup Completion

Completion versus Wait States

JAMS evaluates each Dependency at the entry's scheduled start time. If the Dependencies are all satisfied, JAMS allocates the necessary resource and runs the Job. However, if any of the Dependencies are not satisfied, the entry is moved into a “wait state”. When other Jobs complete, JAMS checks to see if the Job completion will satisfy any ‘waiting’ Dependencies and, if it does, releases the waiting entries.

Defining a Dependency

Dependencies are defined within the Job’s properties and can only be created after a Job has been initially defined.

(46)

2. Choose the Add button to open the Dependency wizard’s initial screen. 3. Select a Dependency Type from the dropdown menu and click the Next

button.

4. The following screen displays entry fields based on the Dependency Type selected on the previous screen. In this example, the Job type was chosen. Enter a dependent Job using the adjacent file browser button. Click Next.

5. Choose the name of a Job used as a reference point when determining if the ‘Depends on Job’ has

completed. Often this will be the same as the current Job (e.g., Job A must have completed since the last time it ran). This is an optional property and can be left blank.

6. Click the Finish button to complete the Dependency Definition process.

Working with Variables

A Variable contains a single slice of data that can be globally defined for all JAMS Jobs. Variables are a powerful tool that can make batch processing easier and more effective. Once a Variable is defined, you can use it in a variety of ways including . . . .

As a default value for a Job parameter. When working with multiple Jobs that require the same

(47)

Directly within the Job Source. Variables can be specified in the Job Source using

<<VariableName>>.When the Job runs it uses the value of the Variable in place of its original

specification.

As an undefined parameter in a parsed Job. Parsed Jobs can use the value of a Variable. In fact, the

Variable does not need to be associated with the Job, other than to include the Variable within the command file where you need the Variable's value to appear.

In Job Dependencies. One type of Job and Setup Dependency relies on

the value of a Variable. You can quickly define Dependencies that require a specific Variable condition to execute a Job or Setup.

In Trigger Events. Triggers are used in event-based scheduling scenarios.

JAMS supports both event and calendar scheduling simultaneously. You can design a Trigger event to use the value of a Variable to fire Trigger

actions.

In your application programs and/or DCL command procedures. You can retrieve or set the value of

Variables using command procedures. This can be very useful for Jobs that do not use a parsed execution method, but still need to use the value of the Variable for their process. Whether parsed or not, Jobs that have access to the JAMS command-line interface can set the value of Variables.

Using Queues

A JAMS Queue provides a temporay holding place for pending Jobs and Setups on a first-in-first-out basis. Queues can be assigned to Jobs, Setups and Folders.

Queues remain in either a started or stopped state and can be adjusted to run multiple jobs simultaneously. To enhance load balancing capabilities you can also specify what node a Queue is started on.

Note: Defining and using Queues in JAMS is optional.

Defining a New Queue

To define a new Queue, follow the steps below: 1. On the JAMS Client select the Queues shortcut. 2. This opens the Queues Definitions View.

3. Choose the Add button on the JAMS Ribbon to open the JAMS Queue Definition Wizard.

4. On the Queue Name page, enter a unique name and description for the Queue. Click the Next button.

5. Choose Finish to complete the Queue definition process.

(48)

2. A Queue definition is organized into two tabs. The Name tab displays a Queue’s basic name and modification data. The Status tab allows you to change the Queue’s (start/stop) status, Job Limit and update.

From the Status tab use the Job Limit adjustment to define the maximum the number of Jobs that can run concurrently.

Add, delete or modify the Agent nodes where the Queue originates using the Started On section. This can include a single node or a list of nodes.

Note: An Agent node name in a Job definition overrides an Agent node name in a Queue

definition. However, the Job still runs on the assigned Queue and adheres to any Job Limit settings defined within that Queue.

Manually Stopping and Starting a Queue

When a Job is waiting for a Queue Job limit slot it cannot execute. However, you can manually start a Queue by right-clicking the Queue’s context menu from the Queue

Definitions View and choosing the Start command. Conversely, select the Stop command to manually halt the Queue.

Queues verses Resources

(49)

Resource requirements can be defined at the System, Folder and the Job level. These values are then added together to define the total units required for the Job to begin executing.

Working with Execution Methods

An Execution Method defines how a Job runs within the JAMS environment. A default Execution Method is assigned to every Job if one is not specifically assigned. To manually assign an Execution Method, open the Job definition and select Properties > Source Options. Use the File Browser button to select from a listing of

available Execution Methods, as shown below.

JAMS ships with dozens of predefined Execution Methods that can run a variety of Jobs on Windows, UNIX operating systems. A few of these built-in Execution Methods include:

File Transfer supports file transfers between operating systems.

PeopleSoft Job Windows enables JAMS Jobs to work directly with PeopleSoft and Windows systems. PowerShell supports the JAMS specific PowerShell host. This Execution Method operates in similar ways

to a standard PowerShell command window.

Workflow runs with Windows Workflow Foundation Jobs. This Execution Method is designed for Job

scenarios requiring decision logic and multiple execution paths.

You can also customize your own Execution Methods to apply other technologies that JAMS does not interface with out of the box. Or you can modify an existing Execution Method to modify its functionality.

Customizing an Execution Method entails a two step process: creating a Execution Method and modifying/updating its definition. Both steps are described below.

Creating a New Execution Method

To define a new custom Execution Method, start by clicking on the shortcut to access the Execution Method View.

1. Choose the Add button from the Ribbon Bar to open the Execution Method Defintion Wizard.

2. On the Execution Method Name page enter the name and description of the new Execution Method. Click

Next.

3. On the following wizard page select the File Browser button.

4. This opens a search list of other Execution Methods from which to base this new entry.

JAMS 6.X Client Features 5. Working with Jobs 5-6. Defining Workflow Jobs 6. Introduction to Workflow Jobs 6-7. Setting Up a Workflow Job 7-9

Table of Contents