Skybot Scheduler Release Notes

Transcription

1 Skybot Scheduler Release Notes The following is a list of new features and enhancements included in each release of Skybot Scheduler. Skybot Scheduler 3.3 Oracle interface The new Skybot Scheduler Oracle Interface allows for submitting concurrent requests on an Oracle EBS (E-Business Suite) server as a command within a Skybot job. Multiple Oracle System Definitions may be defined in Skybot to run requests under various users or application settings. Requests may be submitted with a user-defined Program Name (request name) or the Skybot job name and its run number for ease of tracking on the Oracle system. New Security Report Skybot has a new Security Report. It lists all the roles that have been set up in Skybot. For each role, it shows the users who are assigned to that role. It also shows the Role s settings for Secured Areas, Actions, and Objects. Macintosh agents Skybot can automatically run your scheduled processes on Macintosh IOS systems after you install the Skybot Agent software. However, there is not Desktop integration, so you will need to use command line processing whenever you are using a Mac agent. Text matching for Return Codes The Return Code processing has been enhanced to allow you to specify text matching that can determine the pass/fail status of a command. Command retry options When adding commands to a Job, Member Job, or Command Set, click in the Failed Action column to set the action that should be taken if the command fails. In this same dialog box, you can use the Command Retry Options to indicate how many times the command should be retried and at what intervals. ing Reports When generating a report, you can name it and save it to a specific directory. You can also it to yourself, a Notification List, or a specific address. New Job History preference There is a new preference on the Job History page that allows you to exclude timed interval jobs from the display. New filter on the Job History and Member Job History pages If you have selected Run Duration as one of the columns to view on the Job History and Member Job History pages, click the arrow in the column heading to filter the display by that column. Restart Job Suite after Member Job fails When a Member Job fails, you can go to the Member Job History page, right-click the Member Job, and mark it as Completed. This allows the Job Suite to restart. Delete source files after FTP transfer The File Transfer Command has a new option that allows you to specify that the source file should be deleted after the file has been transferred. Allow active FTP transfer rather than passive If you need Skybot FTP to transfer via active transfer rather than passive transfer, you can enable this by setting the following environment variable prior to the request: set SKYBOT_FTP_LOCAL_MODE=active Page 1 of 5

2 Skybot Scheduler Different address for Notifications If the Authentication Configuration (in System Settings) is set to Use LDAP Authentication with User Authorization, the Skybot users and their addresses are pulled from the LDAP server. However, for any particular user you can now specify an address, other than the one from LDAP, to be used for notifications. Support for Agent clustering The settings for Agents now include an option that allows connecting agents with the same name to share the same agent definition. This supports agent clustering and high availability. Skipping Special Instances If the Job Suite that a Member Job belongs to has a Special Instance assigned to it, you can choose to skip the Member Job runtimes that either match or don t match the Special Instance run. Day of Period Special Instance type You can now select a Day of Period instance type for Special Instances (similar to the Day of Period scheduling type). Job Suites and Variables In the Job Suite settings, there is an option that allows you to select whether to use the Member Job s scheduled time or the Job Suite s scheduled time as the base date for the dynamic date Skybot variable calculation. Support for implicit FTPS The File Transfer Protocol page has a new setting that specifically allows for an implicit FTPS connection. Therefore, you can now connect to FTP servers that have been configured for either explicit or implicit SSL/TLS transfers. Improved Job auditing When a job is either put on hold or released, an audit entry is written that includes information on who performed the action. This can be viewed in Server History. Restoring backups If you must restore from an older backup, you can set an option to ignore all the missed jobs that are in the backup. Starting multiple Jobs When manually starting jobs, you can select multiple jobs and start them all at once instead of having to start each one individually. Creating Member Jobs When you are creating a new Member Job for a Job Suite, there s a new option that allows you to create the Member Job by copying the common attributes of an existing individual job. Exporting Member Jobs Previously, when you exported a Job Suite, all of its Member Jobs were exported along with it. Now, you can export Member Jobs separately from the Job Suite they belong to. Creating Jobs from the Run Intercepted Jobs page There is now a Create Job button on the Run Intercepted Jobs page. Auto-refresh the Agent list The Preferences button on the Agent page includes an option to refresh the list automatically at a timed interval that you specify. Job History Report The total duration of each Job has been added to the Job History Report. Page 2 of 5

3 Skybot Scheduler 3.0 Job Suites Job Suites let you group multiple jobs and refer to and see them as one process. Fewer jobs provide greater clarity and make it easier to understand the relationships between processes. The Member Jobs in a Job Suite can run concurrently or in serial reactivity to one another. Member Jobs also can be used across multiple suites to reduce maintenance. High Availability support Skybot Scheduler 3.0 supports high availability with a master server and a standby server. The standby server replicates the database of the master server and stands ready to take its place in the event of a failure. LDAP/Active Directory (AD) Support Users can enable either the Use LDAP Authentication or Use LDAP Authentication with User Authorization option under System Settings. The Use LDAP Authentication option configures Skybot Scheduler to verify passwords for user profiles using your LDAP server. Administrators still need to create users and assign roles within Skybot Scheduler when using this authentication type. The Use LDAP Authentication with User Authorization option configures Skybot Scheduler to verify users and passwords using the LDAP server. Once LDAP groups are linked to Skybot Scheduler roles, users are automatically maintained from the LDAP server. New Agent Environment:setuid Users can select this Agent Environment to run jobs as a user on a UNIX agent without specifying a username and password. This environment type is secured by running the script allownopwd.sh on your UNIX agent. Skybot Scheduler 2.5 Export/Import Users can export jobs and scheduling objects from a Skybot Scheduler test server and import them to a Skybot Scheduler production server. This helps mitigate transition risk and speeds implementation. The Import Center also can be used for conversion. If you are converting from an existing job scheduling tool, export job information to a.csv file, then use a program to map the data for Skybot Scheduler s.json file format. See the Help topic, Formatting Import Files, for detailed instructions. Agent Aliases field As part of the Export/Import feature, use the Aliases field to map external systems, such as test agents, to agents on the import server. Define the mapping once and it works for all subsequent imports. This also helps map data from other scheduling tools into Skybot Scheduler, as the other tool will likely use different agent names. Display Agent Event Monitors menu option to Agent page Users now can access Agent Event Monitors directly from the Agent page. To see all agent event monitors assigned to an agent, right-click the agent and select Display Agent Event Monitors. Display Jobs menu option to Agent Groups page Users now can access Jobs directly from the Agent Groups page. To see all jobs assigned to the Agent Group, right-click the Agent Group and select Display Jobs. Prerequisites for timed and daily interval jobs Prerequisites now can be added to timed and Page 3 of 5

4 daily interval jobs. A timed interval job (job1) with a job (job2) as a prerequisite will run at scheduled intervals when job2 has completed between the intervals. If job2 doesn t complete, job1 will not run at the next timed interval. Ignore queue rules menu option on Agent Job Queue This option temporarily ignores the max active jobs count on the agent, the held status of the job queue, and the global job queue lock. To ignore queue rules and run a job immediately, right-click the job and select Run Immediately. The held status of the job queue and all other settings remain the same after the selected job(s) runs. Match Any Tag option This option lets users filter by several tags at once. Admin password reset This release includes executable files that reset the Administrator s password to Scheduler1 and force the user to change it again after logging in. See the Help topic, Reset the Admin Password, for detailed instructions. Time filter limit expanded from 72 to 168 hours Users can filter up to 168 hours on Job History, Agent Event Monitor History, Job Monitor History, Output Distribution History, and SNMP Trap Monitor History pages. Fix for explicit time zone settings Users using the posix extension on their time zone now have times displayed in the server s time zone. If users prefer GMT, they need to override the time zone environment variable on the startup commands. Fix for reverse proxy webserver configuration and Job Flow Diagrams Skybot Scheduler now supports proxy settings in Apache and Tomcat to allow proper functionality of Job Flow Diagrams. Fix for Firefox 10 and Job Flow Diagrams The zoom and print preview options under Job Flow Diagrams work properly using Firefox 10 web browser. Change to execute authority for users Users with the specific authority to start a job now are able to end the same job. Various fixes for specific browser issues. Fix to audit history This fix corrects missing data from a specific job s audit history record when accessed from the Jobs page. Fix to recognition of agent time zone in Forecast This fix corrects an issue with the Forecast and Schedule Activity Monitor not accounting for agent time zone when setting the reactivity range. Forecast now sets the proper time zone before simulating reactivity. Fix to file transfers directory issue File transfers with a space in the name of the directory now complete as intended. Skybot Scheduler 2.4 Update Agent option Users can update the Skybot Scheduler software on all agents from the Agent List in the browser. Page 4 of 5

5 Job queue priority Users can add numeric priority to Skybot Scheduler jobs. If sent to a queue at the same time, jobs with high priority run before jobs with low priority. Job Notes Use notes to record and store additional information related to a job, such as updates, contact information, procedures, or any other text documentation. Longer job names and descriptions The allowed length of job names has increased from 20 to 50 characters and the description length from 50 to 255 characters. Replace Agent Replace Agents lets users replace an offline agent with a new, unused agent. The unique hardware ID of the new agent replaces the offline agent s record in the Skybot Scheduler database and maintains the offline agent s history. Current jobs on the agent queue will run immediately, and the history for the Agent will be seamless. This is helpful for a virtual card failure, port change, or when moving a virtual server. Report commands for scheduling reports Users can schedule report generation using these report commands. The commands are located in the Agent\reports directory. The required and optional parameters for the commands are listed in the.bat file. Skipped Job status A Skipped Job status will be applied to jobs that did not run because another instance of the job was already running or prerequisites were not met. Skip if running option for all jobs When setting up the schedule for a job, users may indicate whether Skybot Scheduler should skip the job if a previous submission of the job is running. This may occur if the previous submission of a job runs long. Generate history when skipping option for all jobs When setting up the schedule for a job, users can indicate whether the Scheduler will keep a record of a skipped job instance. Hold on failure option for all jobs When setting up the schedule for a job, users can select this option so if an instance of a job fails, the Scheduler will hold the job. This lets you diagnose the problem and release the job when you are ready, instead of having the Scheduler continue to submit a job that repeatedly fails. If the job is assigned to an Agent Group, the job will be held only for the agents where it has failed. Additional Report filtering options When generating reports, users can filter by specific scheduling objects, such as Jobs, Agents, Tags, or Agent Event Monitors. Filters vary by report type. Users also can choose relative time as opposed to a specific date/time range. Restart Job option from SAM From the Schedule Activity Monitor, users can right-click on a job and choose Restart Job from the drop-down menu. Show date on history pages option Unchecking this option will hide dates that match the date filters on the History screens. This option is located under Profile Settings. Management information base (.mib) file Update If users are using the skybot-scheduler.mib file with a 3rd party SNMP software package and encounter any problem with Skybot Scheduler SNMP traps, they should update the current skybot-scheduler.mib file by re-importing it in the 3rd party package. The skybot-scheduler.mib file is located in the top directory where the Skybot Scheduler Server is installed. Page 5 of 5