2.1 Functions 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 Pack) are not supported. However, plug-ins provided by JP1/AO (JP1/AO standard package and JP1/AO Content Pack) that are called from such unsupported service templates are supported.

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

In the imported service template, enter information that is suitable for the environment, and create services. By using one service template, you can create multiple services suitable for different operation procedures and jobs.

Scheduling according to jobs - running services

Enter information necessary for running a service and the schedule type, 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. You can specify (for the schedule type) immediate execution, repeated executions on a specified day of every week or at the end of each month, or execution of services on a certain date, at a certain time. Thus, you can plan a detailed schedule suitable for the users' jobs. This allows you to set a detailed schedule tailored to your business needs.

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.

Categorizing and searching service templates and services, depending on the purpose (such as, for each job or for each division) - setting tags

For a service template or service, you can set a tag that indicates the purpose or type of the template or service. You can also search service templates or services by using tags.

By setting multiple tags for one service, you can get a search result that is suitable for the condition (such as for each job or for each division).