2.1 Functions for automating operation procedures

You use JP1/AO to automate operation procedures. This section explains the procedure for automating operation procedures and provides an introduction to the principal functions needed to achieve automation.

Figure 2‒1: Procedure for automating operation procedures

Providing a wide variety of templates that define operation procedures - managing the service templates

JP1/AO provides various templates (called service templates) that define operation procedures.

The user selects job-appropriate templates and imports them into JP1/AO. When templates are imported, their automated operation procedures can be used as services.

In addition to using the templates provided by JP1/AO as they are, the user can modify them to create new service templates in which to define user-specific operation procedures.^#

#

User-created service templates that are not based on those provided by JP1/AO (JP1/AO standard package and JP1/AO Content Set) are not supported. However, plug-ins provided by JP1/AO (JP1/AO standard package and JP1/AO Content Set) that are called from such unsupported service templates are supported.

Creating services that are suitable for operation procedures and jobs - adding services

You develop a service by entering environment-specific information into an imported service template and adding the service template to JP1/AO as a service. You can create multiple services suitable for your various operation procedures and jobs from a single service template.

Scheduling according to jobs - running services

You enter the information necessary for running a service and the execution timing, and then run the service. When a service is run, a task is generated and the automatic processing is started at the date and time that you have specified. JP1/AO supports (as execution timings) immediate execution, repeated executions on a specified day of every week or at the end of each month, and date-and-time-specified executions for executing services on a specified date and time. This allows you to set a detailed schedule tailored to your business needs.

Using task lists to check the processing status and the details window to check the progress of each job - managing tasks

JP1/AO provides task lists that enable you to determine the processing status at a glance and a details window that enables you to check the progress of each job and output task logs. If you use a plug-in (the User-response wait plug-in) that enables the user to select the subsequent processing on the basis of the current processing results, you can enter the appropriate information to a task during processing, as necessary.

Sharing settings to reduce the time and effort needed in entering and changing settings - managing shared service properties

JP1/AO enables you to share the values specified for a service among multiple services. Settings that are shared are called the shared service properties.

For example, if you use a service template to manage a common server and you define the host name, user ID, and password for that server at the connection destination as shared service properties, you save the time needed to enter this server information each time a service is run.

Figure 2‒2: Relationship between shared service properties and services

Classifying operation targets by jobs, groups, and usages - setting categories

You can classify services and tasks by usage and type categories and display them in a hierarchical structure.

Because JP1/AO enables you to register the same service in multiple categories, you can display a list of services according to purpose, such as for checking services by job or by the person in charge.

To Page Top