Frequently Asked Questions - Systemwalker Operation Manager
| Q | A |
|---|---|
| What is Systemwalker OperationMGR? |
Systemwalker OperationMGR is a tool that enables you to:
|
| What functions does Systemwalker OperationMGR provide? | OperationMGR offers the following functions:
|
| What are the differences among EE, and SE? | SE is the standard model. EE contains all the SE functions. It also supports large-scale job operations and reliable, stable batch processes. EE offers the following functions:
|
| What competitive products exist in the market? | Hitachi's JP1 |
| Is a client necessary to run Systemwalker OperationMGR? | Yes. The client has console windows for scheduling and job monitoring. Note that the client does not require a license. It’s FREE. |
| Is it possible to manage jobs across different platforms? | You can manage jobs on UNIX, Linux, and Windows servers, global servers, and Windows clients. |
| Is it possible to schedule backup tasks in Systemwalker OperationMGR? | Yes. OperationMGR for Windows supports ARCserve, and Systemwalker OperationMGR for Solaris OS supports Tivoli Storage Manager (TSM). This enables you to automatically back up resources on the server synchronously with job startup and system operations. You may also use backup software that provides a command for detecting the backup result from the exit code and scheduling the backup. For backup software that does not provide such a command, you can execute the backup command directly. |
| What are jobs, job nets, and groups? | Job: Individual shell scripts, commands, and executables that configure a job net. The following files can be registered as jobs.
A group of related jobs that have a specific start order. A job net can be started, monitored, and operated. Group A group of job nets. A group can be started, monitored, and operated. |
| How many jobs can I add to a job net? | Up to 255. |
| How many job nets can I add to a project? | SE: Up to 255 EE: Unlimited You may create multiple projects if the number of job nets exceeds 255 in SE. Although EE does not restrict the number of job nets, you should test the performance in advance and ensure that every job net starts as scheduled. |
| How many job nets can I add to a group? | SE: Up to 50 EE: Up to 255 |
| What criterion determines if the job exited normally or abnormally? | The result is determined by the exit code of the program registered as a job. You may define the upper limit for the normal exit. Note that the exit code of a batch file is the return code of the last command (program) in the file. Since this may raise a problem, Systemwalker OperationMGR provides the commands that exit with an arbitrary code. |
| Is it possible to run other server’s job nets? | Yes. You may run a job net on other servers by using a message event as a startup trigger. These “network jobs” are useful for running a job net on a different server on the network. |
| Can I view the job result? | Yes. Default logs and default error logs are available to view on the screen. |
| Is it possible to notify other systems of job errors? | Yes. Systems that have Systemwalker CentricMGR installed can receive error notifications. |
| Can I register a recovery job to execute after abnormal exit of jobs? | Yes. The registered recovery job starts automatically to recover the failed process when a job exited abnormally. Administrators do not need to handle errors manually. |
| Is it possible to schedule an application to start up and open a window when launched? (Jobscheduler does not allow it.) | The Job Linkage function allows you to schedule application startups |
| Can I execute a command to register job nets? | Yes. |
| Can I set startup priority among jobs? | Yes. The Job Startup Control function allows you to specify the startup priority among jobs. |
| Is it possible to monitor and manage job schedules for multiple servers from a client? | Yes. You may monitor and manage schedules for multiple systems. |
| What controls are available for jobs? | You can control:
|
| What is exclusive control of jobs? | Exclusive control prevents jobs that use an identical resource from running at the same time. To enable this feature, specify
the exclusion attribute and virtual resources for each job. Exclusive control:
|
| What triggers automatic startup of job nets? | The startup triggers include the start date/time and interval specified in the schedule.You can also start job nets in response to server startup, events, job net exit codes, and received e-mail. |
| Does a job net exit normally when it runs beyond the day change? | Yes. The job nets scheduled on the next day are suspended until all job nets exit. It does not cause a problem. |
| Can I print the status of job nets to make sure? | Yes. You can print these in color. |
| Is it possible to manage the history of job results? | Yes. You may export job results and their latency data to a CSV file and create a report with spreadsheet applications such as Excel. |
