Getting Started with JAMS

Full text

(1)Getting Started with JAMS 1. Table of Contents. 1.. Table of Contents. 1. 2.. Key Concepts. 2. 2.1. JAMS Overview. 2. 2.2. Getting To Know The JAMS Client. 2-3. 2.3. Customizing the JAMS Client. 3-5. 2.4. Working With Servers. 5-6. 2.5. Working with Views. 6-7. 2.6. Defining Jobs, Setups & Folders 3.. Getting Started with the JAMS Scheduler. 8. 3.1. JAMS Scheduler Overview. 8. 3.2. Services. 8. 3.2.1. Executor Service. 8. 3.2.2. Scheduler Service. 9. 3.2.3. Server Service. 9. 3.3. Configuration 3.3.1. JAMS Scheduler Configuration 3.3.2. Editing .exe.config 3.4. After Installation 3.4.1. Security 3.4.2. Add a User to the JAMS Database 3.4.3. Log on as Batch. 9 9-10 10-11 11 11-12 12 12-13. 3.5. Running Scripts over the LAN. 13-16. 3.6. Running Scripts Across Platforms. 16-17. 4.. Glossary. 5.. Index. 1. 7. 18-20 21. Getting Started with JAMS.

(2) Getting Started with JAMS 2. Key Concepts. Understanding the JAMS Key Concepts will assist you as you develop and manage batchprocessing activities on the computers at your site. The key concepts covered in this section include: JAMS Overview (Section 2.1). Provides an overview of JAMS. Client Overview ('JAMS Client Overview' in the on-line documentation). Provides an overview of the Windows-based application that allows you to interact with JAMS. Server Overview ('JAMS Server Overview' in the on-line documentation). Provides an overview of the Server, the middle tier positioned between one-tomany Clients and one-to-many Schedulers. Scheduler Overview ('JAMS Scheduler Overview' in the on-line documentation). Provides an overview of the Scheduler that actually schedules or submits scripts to run on one or more computer systems. Jobs, Setups, and Folders. Describes the basic building blocks within JAMS that you will work with most often.. 2.1 JAMS Overview What is JAMS? The Job Access and Management System (JAMS) is designed to automate and enhance your organization’s batch processing capabilities across multiple platforms. Windows, UNIX, Linux and System i can be easily tied together using the JAMS enterprise scheduling engine. Whether your organization’s servers are virtualized or physical, uniform or diverse, JAMS provides secure control mechanisms that can enable you to submit batch processing jobs or alternatively create schedules for automatic execution. JAMS is highly customizable and ready to provide benefits right out of the box. In addition, JAMS is scalable, allowing you to grow your business without worry that future upgrades will negate existing work or settings. Once properly configured, JAMS will enhance and simplify the most complex batch scheduling processes; providing your organization with increased system reliability and reduced cost of operation.. JAMS Components JAMS integrates three components that work together to create a unique and powerful management system. 1. JAMS Client: provides the main user controls for JAMS in a Windows-based GUI. 2. JAMS Scheduler: schedules all Jobs, Scripts, or Tasks that run on your organization’s servers. It is also monitors the status of all Jobs and communicates this information to the JAMS Client. 3. JAMS Server: the application service that facilitates communication between JAMS Clients, the JAMS Scheduler.. 2.2 Getting To Know The JAMS Client The JAMS Client is the primary user component in the JAMS system. Specifically, this Windows application enables users to interact with the two other JAMS components: the JAMS Scheduler and JAMS Database. The JAMS Client has a familiar Outlook-style interface that includes a Ribbon Bar at the top (outlined in red) containing a variety of tools and commands, a Shortcut Bar (in blue) that includes a collection of customizable 2. Getting Started with JAMS.

(3) Getting Started with JAMS commands, and a large View area.. 2.3 Customizing the JAMS Client The JAMS Client gives users a flexible palette of controls. Here you can modify and organize Shortcuts into Groups to create an interface that works best for you. Keep in mind the following rules regarding Groups and Shortcuts: Shortcuts, like aliases, provide access to JAMS functions. 3. Getting Started with JAMS.

(4) Getting Started with JAMS Groups can be used to organize Shortcuts into useful clusters. You can have as many Groups and Shortcuts as you like.. The table below provides three examples and benefits of using Shortcuts.. Shortcut Type. Shortcut Setup. Benefit. History. Query History entries for a Job that runs between two dates. You can specify start and end dates of Monday through Friday. When the History shortcut is activated, JAMS automatically substitutes the current Monday and Friday dates for the current week.. By clicking one Shortcut you can view how this Job is doing for the current week without specifying search criteria over and over again.. Monitor. Select backup Jobs only.. One click displays all JAMS backup Jobs.. Jobs. Filter those jobs in a specific folder.. One click lists all Jobs in the JAMS folder you choose.. Customizing Shortcuts Adding a Shortcut 1. Right-click the Shortcut Bar to display the context menu. 2. Select the Add Shortcut command. 3. This opens the Add a Shortcut wizard. On the first page, select the properties: icon, name, title, and description. Click the Next button. 4. Select from a list of Views to assign the Shortcut and click the Next button to move to the next page. 5. Set the Shortcut properties for the View by populating the fields and checkboxes. The fields will change depending on the View selected. 6. Choose Finish or select the Add Another View button to include additional Views for the shortcut.. Modify the Shortcut Properties 1. Right-click the Shortcut to open its context menu. 2. Select the Properties command. 3. Update the icon, name, title, and description for the Shortcut. Also, you can add, modify, or delete any view the Shortcut activates. 4. Click the OK button to save the changes.. Removing a Shortcut 1. Right-click the selected Shortcut to open its context menu. 2. Select Remove Shortcut. 3. Confirm the removal or select No to cancel the action. Move a Shortcut's Icon Up or Down within a Group. 4. Getting Started with JAMS.

(5) Getting Started with JAMS 1. Right-click the Shortcut to display its context menu. 2. Select either the Move Up or Move Down command.. Customizing Groups You can add, rename, or delete a Shortcut by right-clicking on the selected Group.. Adding or Renaming a Group 1. Right-click a Group to display its context menu. 2. Select the Add Group or Rename Group command. 3. Enter a name of the Group in the Shortcut Tab field. 4. Click the OK button.. Removing a Group 1. Right-click on the Group to open the context menu. 2. Select Remove Group. 3. Confirm the removal or select No to cancel.. Moving a Group's Postion Up or Down within the Shortcut Bar 1. Right-click the Group to display its context menu. 2. Select either the Move Up or Move Down command.. 2.4 Working With Servers Every instance of a JAMS client must connect to at least one server. If the JAMS Server Service is installed on the same machine as the client, a server definition is automatically added that points to the local server. Adding, removing, and editing JAMS Servers can be controlled from the JAMS icon in the top left corner of the Client interface.. Adding a Server 1. Click the JAMS icon in the top left corner and select the Servers command. 2. Click the Add button to open the JAMS Server window. 3. In the Server Name field, located on the Server tab, enter the name of the Windows server where the JAMS Server is installed. 4. Complete the User name and Password boxes on the Authentication tab. 5. If required by your JAMS administrator, modify the Port field on the Server tab. 6. Click the OK button.. 5. Getting Started with JAMS.

(6) Getting Started with JAMS. Modifying Server Properties 1. 2. 3. 4.. On the JAMS icon, click the Servers command. Select the specific server from the list and click the Change button Modify the properties. Click OK.. Removing a Server 1. From the JAMS icon click the Servers command. 2. Select the server from the list and click the Remove button 3. Confirm the settings and selectthe OK button.. 2.5 Working with Views A View is a data grid consisting of columns and rows of items. Each View displays data that corresponds with a particular Shortcut. A View typically displays table listings for Jobs, Setups, Triggers, Resources, and includes variety of JAMS settings.. Views come with a few basic rules: While several Views can be active, you can only work with one View at a time. In order to switch between active Views, select a Shortcut on the Shortcut Bar. The data in any View can be sorted by clicking on a column header.. Customizing Views Using the Column Chooser The Column Chooser tool allows you to add, remove and repositions columns in the Monitor, History and folder Views. To activate this tool, follow the steps below: 6. Getting Started with JAMS.

(7) Getting Started with JAMS 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 in 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.. 2.6 Defining Jobs, Setups & Folders Jobs, Setups, and Folders are basic objects used to define and organize batch processing on your organization’s systems. A Job is a task, script (known as a command procedure), or command. A JAMS Job includes a number of properties that specify when and under what conditions it should run. If your organization uses command procedures for batch processing, you can continue to deploy them using JAMS. 1. To create a new Job, activate the Jobs View by clicking on the Definitions Group in the Shortcut bar and choose the Jobs shortcut.. 2. Select the Add button located on the Ribbon Bar. This actions opens the Job Definition Wizard.. A Setup defines a particular occurrence or view for one or more Jobs. Setups are commonly used to schedule a Job or a stream of Jobs that automatically execute at regular intervals. Setups are created and defined using the Setup Definition Wizard. 1. To create a new Setup, activate the Setups View by selecting a directory in the Definitions Group and clicking on the the Setups shortcut. 2. Select the Add button located on the Ribbon Bar. This action opens the Setup Definition Wizard. A Folder contains a logical grouping of Jobs. Folders can be structured 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. 1. To create a new Folder, right-click the root Folder in the Definitions Group on the Shortcut Bar and choose the Add Folder command from the context menu. 2. This opens the JAMS Folder Definition Wizard. Define the Folder by entering a folder name and optionally an email address for notification purposes.. 7. Getting Started with JAMS.

(8) Getting Started with JAMS 3. JAMS Scheduler—Getting Started with the JAMS Scheduler. Getting Started with the JAMS Scheduler The JAMS Scheduler is the portion of the JAMS system responsible for preparing, running, and then reporting the results of execution of Scripts or Tasks. Scheduler Overview ('JAMS Scheduler Overview' in the on-line documentation). Provides an overview of the Scheduler. Services (Section 3.2). Describes the Windows Services that make up the Scheduler. Configuration (Section 3.3). Describes where the Scheduler Configuration information is stored and how it can be modified to affect changes in your environment. After Installation (Section 3.4). Describes the things you must do after installation before you can use JAMS in a meaningful way. Running Scripts over the LAN (Section 3.5). Describes what steps you must take to have the Scheduler run Scripts or Tasks on other Windows systems anywhere on the network. Running Scripts Across Platforms (Section 3.6). Describes the steps you must take to have JAMS orchestrate the execution of Scripts or Tasks that must run on more than one operating system.. 3.1 JAMS Scheduler Overview The Scheduler is the JAMS component that schedules and monitors the status of all Jobs, Scripts, and Tasks. A JAMS Scheduler can run on any number of computer systems on your network and can be configured in a centralized or decentralized manner. For example, a single JAMS Scheduler can execute tasks on many systems utilizing the power of JAMS Agents. Alternatively, to distribute the manangement of tasks and eliminate single points of failure, you can choose to run multiple JAMS Schedulers each residing on a different machine. Dependencies can be defined between multiple instances of JAMS Schedulers to provide enterprise-wide control.. 3.2 JAMS Scheduler—Services Services There are three Windows Services that make up the Scheduler: JAMS Executor Service (Section 3.2.1). This Service executes the Scripts or Tasks once they are prepared to run. JAMS Scheduler Service (Section 3.2.2). This Service is responsible for preparing Scripts or Tasks to run, monitoring them during execution, and taking required actions upon completion. JAMS Server Service (Section 3.2.3). This Service provides connectivity between JAMS Clients and the JAMS Database.. 3.2.1 JAMS Scheduler—Executor Service Executor Service The JAMS Executor Service is responsible for the actual execution of any given Script. Scripts are prepared to run by the JAMS Scheduler. When the Scheduler determines the Script is ready to run, the Executor is notified and will begin executing the Script. The Executor writes output generated from the Script to the Script's log file. Finally, the Executor notifies the Scheduler when the Script has completed. If the script is supposed to run on a different machine, the Executor service contacts the Agent on the remote machine and directs it to run the script.. 8. Getting Started with JAMS.

(9) Getting Started with JAMS 3.2.2 JAMS Scheduler—Scheduler Service Scheduler Service The Scheduler Service does the work necessary to prepare Scripts to run, takes actions if required to do so during Script execution, and takes actions that may be required when Scripts complete. Before a Script can run, the Scheduler Service will: Make sure the Script's Dependencies are satisfied. Execute the Script's Precheck Script if one is specified, and verify that its Precheck Script completes successfully. Make sure the Script's Queue is started and there is a slot available. Make sure the Script's Resources are available. Make sure the Script's Scheduling Window is open. If the Script's Execution Method calls for parsing, the Script's source is parsed and substitution will occur for Parameter and Variable values. While any given Script is running, the Scheduler service will: Report the Script's execution details to all JAMS Clients monitoring the schedule. Perform Notification if the Script runs longer than its limit. Take the Script's defined action if the Scheduling Window closes during execution. When the Script completes, the Scheduler service will: Report the Script's completion to all JAMS Clients monitoring the schedule. Record this Script's run instance in the JAMS History, which is available for query in the JAMS Client. Perform notification if required. See if this Script's completion satisfies Dependencies for other Scripts in the schedule. See if this Script's completion satisfies Trigger Events so that Trigger Actions can fire. Make sure the Script's Resources are released. Read the following article on JAMS Support site for more information: Monitoring Large Numbers of Jobs on OpenVMS. 3.2.3 JAMS Scheduler—Server Service Server Service The JAMS Server Service is primarily responsible for database access for one to many JAMS Clients.. 3.3 JAMS Scheduler—Configuration Configuration Configuration settings for JAMS are accessed using the JAMSWin GUI Client as well as being stored in configuration files. Using the JAMSWin GUI (Section 3.3.1). Configuration via the JAMSWin GUI. Editing .exe.config (Section 3.3.2). Configuration files.. 9. Getting Started with JAMS.

(10) Getting Started with JAMS 3.3.1 JAMS Scheduler Configuration Using the JAMS Client GUI To view or modify configuration settings available using the JAMSWin GUI Client: Select Configuration from the menu bar and then the Configuration shortcut. A dialog will appear showing all configuration settings. Each setting has both a description and a value. Configuration settings you modify usually take affect immediately. In some cases, you will need to restart the JAMS Scheduler Service before the change will take affect.. Read the following article on the JAMS Support site for more information: Client GUI Settings. 3.3.2 JAMS Scheduler—Configuration—Editing .exe.config Editing .exe.config Configuration settings are also found in one of several .config files found in Program Files\MVPSI\JAMS\Scheduler. 10. Getting Started with JAMS.

(11) Getting Started with JAMS The filename of each configuration file is: Common.config JAMScheduler.exe.config JAMSExecutor.exe.config JAMSServer.exe.config Common.config is shared by the other .config files and contains all of the user-specific settings. You should only change one of the other .config files under the direction of JAMS Technical Support or if you understand the implications of changing these files. The Common.config file is preserved when upgrading JAMS; the other files are overwritten every time you upgrade JAMS. You can change settings in these configuration files at any time; however, in most cases, these settings are only loaded when the service starts.. 3.4 JAMS Scheduler—After Installation After the JAMS Scheduler is installed, you'll need to address the following: Security (Section 3.4.1). Initial security settings allow the Built-In\Administrator to have full access to all JAMS items. Add a User to the JAMS Database (Section 3.4.2). Scripts run under specific user names; this information must be entered into the JAMS Database. Log on as Batch (Section 3.4.3). JAMS Scripts run as batch processes; the user names the Scripts run under must have the "Log on as Batch" right.. 3.4.1 JAMS Scheduler—After Installation—Security Security JAMS uses access control lists (ACLs) to secure features, and in many cases secure specific items. When JAMS is installed, the default ACLs grant full access to Administrators and limited access to Authenticated users; however, the "Server" ACL grants Administrators full access and Authenticated Users no access. This effectively restricts access to only Administrators because you must first be able to access the Server before you can do anything else. This also makes it easy to control access to JAMS without requiring Administrator privileges. Simply open the JAMS Client (as an Administrator), select the Access Control button from the Ribbon Bar, select the Server drop down menu item, and adjust that ACL.. 11. Getting Started with JAMS.

(12) Getting Started with JAMS. Global Bypass You can also define a Windows group that entitles a user to bypass the JAMS ACLs. You define this group by selecting Configuration from the menu bar and then the Configuration shortcut. Set the value of the GrantBypassGroup configuration to the name of the Windows group that should grant bypass access. When running the JAMSWin Client on Windows Vista or Windows 7, by default you will not be in the Builtin\Administrator group, which means that your access to JAMS will be limited. You can right-click the JAMS shortcut and select Run as administrator to get full access to JAMS. Please also see the following: Securing your JAMS installation JAMS Client Configuration Settings. 3.4.2 JAMS Scheduler—After Installation—Add a User to the JAMS Database Add a User to the JAMS Database In order to run a job under Windows, the JAMS Scheduler must supply a valid user name and password. You can use the Management -> Users menu option in the JAMS Client to define the user/password combinations. You can also specify an access control list (ACL), which is used to determine who can submit Jobs under the user name.. 3.4.3 JAMS Scheduler—After Installation—Log on as Batch JAMS Jobs run as batch processes under Windows. The Windows account that the batch Job will run as must have the Log on as Batch user right. You can grant this right to specific accounts or to a group and make the accounts members of the group. When the JAMS Scheduler is initially installed, it can create a Windows group and assign the Log on as Batch user right to the group. The default name of this group is "JAMSBatchGroup," but you may have changed it during the installation. 12. Getting Started with JAMS.

(13) Getting Started with JAMS Granting Rights Under Windows 2000/2003 Under Windows 2000/2003, you can grant the Log on as a batch job right at the domain level or local level. To manage rights under Windows 2000, use the Local Security Policy or Domain Security Policy Administrator Utilities.. Granting Rights Under Windows NT V4.0 Under Windows NT V4.0, you must grant the Log on as a batch job right on each machine that will be running the JAMS Agent. You only have to grant the right on one domain controller, and it will propagate to the other domain controllers in the domain. It will not propagate to member servers or workstations; you must grant the right on each of those machines. You can use User Manager for Domains to grant the right for both the domain and individual machines. Select the User Rights option from the Policy menu. You must check the Show Advanced User Rights check box to display the Log on as a batch job user right. To manage user rights on member servers and workstations, select the Select Domain... option from the User menu. Enter ‘‘\\machinename’’ in the Domain field and click Ok. You will then be connected to the specified machine and will be able to manage the user rights on that machine.. Granting Rights with the NTRights.exe Utility The NTRights.exe utility is included in the Windows NT Server 4.0 Resource Kit supplement 3 and in the Windows 2000 Resource Kit. If you have this utility, you can grant the Log on as a batch job right with a command like this: ntrights +r SeBatchLogonRight -u user_or_group -m \\computername. Note that the rights name is case sensitive.. 3.5 JAMS Scheduler—Running Scripts Over the LAN Running Scripts Over the LAN By default, JAMS will run Scripts on the server where the JAMS Scheduler is running. Frequently, data centers will have the need to run Scripts on many different servers. In addition to running Scripts on the JAMS Scheduler node, JAMS can run Scripts on specific nodes, load balance across several nodes, or run Scripts in queues that can be configured to run n-threads on one or more nodes. A JAMS Agent is required to run Scripts on servers other than the server where the Scheduler is running.. Running Scripts on Specific Nodes Modify the Job and specify the server where you would like the Job to run in the Agent Node Name property found on the Submit Options tab.. 13. Getting Started with JAMS.

(14) Getting Started with JAMS. Load Balance Across Several Nodes Modify the Job and specify a list of servers where the Job is allowed to run in the Agent Node Name property found on the Submit Options tab. The list of servers should contain a list of node names, each one separated by a comma (NODEA,NODEB,NODEC). Or, leave the Agent Node blank and run the Job in a Queue that is started on multiple nodes.. 14. Getting Started with JAMS.

(15) Getting Started with JAMS. Run Scripts in Queues JAMS Queues can be configured to run one or more Scripts simultaneously. They can also be started on one or more nodes at the same time. This is the simplest way to spread the workload and load balance at the same time. Queues are easy to define and then assign to Jobs (or Scripts), Setups, and Folders. You create or define Queues using the JAMSWin Client menu bar Management option, and then select Queues.. To run a Job or Script in a Queue, modify the Job's Batch Queue property found on the Submit Options tab. Enter the Queue name or select it from the drop-down list.. 15. Getting Started with JAMS.

(16) Getting Started with JAMS. To run a Setup in a Queue, modify the Setup's Batch Queue property found on the Submit Options tab. Enter the Queue name or select it from the drop-down list. To set the default Queue for Jobs and Setups in any given Folder, modify the Folder's Batch Queue property found on the Submit Options tab. Enter the Queue name or select it from the drop-down list.. 3.6 JAMS Scheduler—Running Scripts Across Platforms JAMS can orchestrate the execution of Scripts or Tasks that must run on more than one operating system. Business processes that span operating systems are easy to implement with JAMS. Supported operating systems are Windows, Unix/Linux, OpenVMS, and any other operating system that supports REXEC. Jobs or Scripts are designed to run on specific operating systems. When designing a Job, keep in mind the following: The Job or Script Source property contains commands specific to the operating system the Script is designed to run on. The Job or Script Source Options->Execution Method property tells JAMS how to run the Job. JAMS ships with Execution Methods for all supported operating systems. Execution Methods can be modified or new user-defined Execution Methods can be created. The Submit Options->Agent Node property tells JAMS where to run the Job. If 16. Getting Started with JAMS.

(17) Getting Started with JAMS this property contains a list of node names, JAMS will also perform load balancing. Once Jobs or Scripts are created, JAMS can orchestrate their execution in one or more of the following ways: Dependencies ensure that prerequisite processing occurs. Any Job can serve as a Dependency for any other Job regardless of where or how the Job runs. Scripts will not be released to run until all their dependent Scripts complete properly. For example, a Script designed to run on Windows could have dependent Scripts that must properly complete one or more of the other supported operating systems first. Precheck Jobs serve as user-defined dependencies. Scripts that utilize Precheck Jobs will not be released to run until that Precheck Job completes properly. For example, a Script designed to run on OpenVMS could have a Precheck Script that must complete properly on Windows or any other supported operating system first. Triggers support event-based scheduling. When all Trigger Events occur, the Trigger will fire. When a Trigger fires, it submits one to many Jobs or Scripts. Any JAMS Job or Script can serve as a Trigger Event or a Trigger Action, regardless of the operating system it is designed to run on. For example, a Trigger could be created to submit one or more scripts on a Unix system when one or more Scripts from a Windows or OpenVMS system completes. Setups are the simplest way to sequence Jobs or Scripts to run. Setups essentially set up one or more Jobs or Scripts to run as a unit. Scripts within the Setup run one right after the other or simultaneously depending on your business process needs. Parameter values for any given Script within a Setup can be shared with other Scripts in that same Setup. For example, a Setup could easily be created that contains multiple Jobs or Scripts, each one running on different supported operating systems. A JAMS Agent is required to run Scripts on servers other than the server where the Scheduler is running. Read the following article on the JAMS Support site for more information:. Can a Trigger submit a Job each time a file arrives?. 17. Getting Started with JAMS.

(18) Getting Started with JAMS 4. Glossary. Access Control Dialog that maintains access-control lists. These lists are used to define access restrictions for various capabilities within the JAMS system. Add Tool Bar button that initiates a JAMS Add Wizard to add a new JAMS Job, Setup, or Folder. Configuration Defines and maintains many of the JAMS system-wide options. Generally, you will need to review and update these options when you first install JAMS, but usually will not want to change the definitions frequently. Dates Definitions used to mark dates significant to your batch processing. These dates may be company-observed holidays, fiscal periods, etc. You should be careful when defining these dates since they are used to schedule (or not schedule) Jobs, and they are used to create the defaults for dates used as Parameters for Jobs. If your Data Center operates 365 days a year and schedules Jobs based on calender months, you do not need to define any special dates. Date Types High-level definitions of special dates, such as holidays or fiscal periods. Date Types are used to define the various classes of dates significant to your environment. This is not where you define the specific dates for these classes; rather it is where you define the classes themselves. The specific dates are defined using the Date Definitions menu option. Delete Toolbar button that deletes a JAMS Job, Setup, or Folder. Execution Method Defines how a Job will run. Execution Methods are optional, but a default Execution Method is assigned to every Job if one is not specifically assigned. JAMS ships with Execution Methods to run Jobs on Windows, UNIX, OpenVMS, and REXEC-compliant operating systems. You can create your own Execution Methods, too. Folders A logical group of Jobs. A JAMS Folder Definition defines things common to all Jobs within the Folder. You could create Folders by department (Acctng, IS, Sales) or by function (EDI, Web, Security, Audit) or any other way meaningful to your site. At least one Folder must exist for JAMS to function properly. Group Used to hold collections of Shortcuts. Groups can be customized. You can add as many Groups as you need in order to organize your Shortcuts in a way that is meaningful to you. The default Groups are Control, Definitions, Configuration, and Management. Groups are embedded in the Shortcut Bar. History Shortcut that allows you to see the execution results of how a Job or Setup has run in the past. JAMS 18. Getting Started with JAMS.

(19) Getting Started with JAMS Job Access and Management System. JAMS is a software application that manages all aspects of batch processing on computer systems. There are several software components that work together to provide this management ability. The components include: JAMS Scheduler, JAMS Server, JAMS Client. JAMS Client Windows application used to interact with the JAMS Database and JAMS Scheduler. JAMS Database Database where JAMS definitions are stored. JAMS Scheduler Software application that manages batch processing on computer systems. It is the component that actually submits Jobs to run on your servers. It is also responsible for keeping track of the status of all Jobs and communicating that status back to the JAMS Client through the JAMS Server. JAMS Server Middle-tier software application service that facilitates communication between one or many JAMS Clients and the JAMS Database as well as the JAMS Scheduler. Job A command or command procedure. JAMS Jobs have a number of properties you may use to ensure they run at the right time under the right circumstances. Main Window The Main Window within the JAMS Client contains a Menu Bar, Shortcut Bar, Groups, Shortcuts, and a View. Menu Bar Provides the menu options for the JAMS Client. The Menu Bar is embedded within the Main Window of the JAMS Client. Monitor Shortcut that allows you to Monitor and interact with Jobs and Setups that are currently running as well as those that are scheduled to run in the near future. Named Times Provide flexible windows of time when Jobs may be scheduled. JAMS can prevent Jobs from starting until their Named Time window is enabled and can take various actions when a Job’s window closes before the Job completes. Query This is the Query that is executed when the Shortcut is activated. It is customizable. Stored within a Shortcut. Queues Represent a line of first-in-first-out Jobs (or Setups) to be run. Refresh Tool Bar button that re-queries the JAMS Database and refreshes the information displayed in the View. REXEC Service running on a remote computer that executes a command or script. Setup 19. Getting Started with JAMS.

(20) Getting Started with JAMS A definition of a particular occurrence or view of one or more Jobs. Setups are commonly used to schedule a Job or stream of Jobs to automatically execute at a regular interval. Shortcut Activating a Shortcut will fill the View with a list based upon the Query defined within the Shortcut. You may put as many Shortcuts within a Group as you would like. Shortcuts are customizable; you may change the Shortcut's name or the Query associated with the Shortcut. Shortcuts are held in Groups. Shortcut Bar Holds both Groups and Shortcuts. It is embedded within the Main Window of the JAMS Client. Submit Shortcut that allows you to submit a Job to run in an ad-hoc fashion. Tool Bar Used to perform tasks in the JAMS Client. To perform a specific task, click the Tool Bar button associated with that task. There are four buttons on the tool bar: Refresh, Query, Add, and Delete. The Tool Bar is embedded within the Main Window of the JAMS Client. Usernames Usernames are defined and then later assigned to JAMS Folders, Jobs, and Setups. When a Job is submitted, it will run under the Username specified. The use of Usernames is secured with an access control list (ACL) that determines who may assign or change the Username for JAMS Folders, Jobs, and Setups. View A data grid that holds lists created as a result of activating (clicking) Shortcuts. You may switch from one View to another by activating different Shortcuts. It is embedded within the Main Window of the JAMS Client.. 20. Getting Started with JAMS.

(21) Getting Started with JAMS 5. Index. Customizing the JAMS Client,. 3-5 Defining Jobs, Setups & Folders,. 7 Getting Started Customizing the JAMS Client, 3-5 Defining Jobs, Setups & Folders, 7 Getting To Know The JAMS Client, 2-3 JAMS Overview, 2 JAMS Scheduler Overview, 8 Working With Servers, 5-6 Working with Views, 6-7 Getting To Know The JAMS Client,. 2-3 Glossary,. 18-20 JAMS Overview,. 2 JAMS Scheduler Configuration,. 9-10 JAMS Scheduler Overview,. 8 JAMS Scheduler—After Installation,. 11 JAMS Scheduler—After Installation—Add a User to the JAMS Database,. 12 JAMS Scheduler—After Installation—Log on as Batch,. 12-13 JAMS Scheduler—After Installation—Security,. 11-12 JAMS Scheduler—Configuration,. 9 JAMS Scheduler—Configuration—Editing .exe.config,. 10-11 JAMS Scheduler—Executor Service,. 8 JAMS Scheduler—Getting Started with the JAMS Scheduler,. 8 JAMS Scheduler—Running Scripts Across Platforms,. 16-17 JAMS Scheduler—Running Scripts Over the LAN,. 13-16 JAMS Scheduler—Scheduler Service,. 9 JAMS Scheduler—Server Service,. 9 JAMS Scheduler—Services,. 8 Key Concepts,. 2 Working With Servers,. 5-6 Working with Views,. 6-7. 21. Getting Started with JAMS.

(22)

No results found