Summary of amendments

For the manual issued in December 2014 or later, the title and reference number were changed as shown below.

Before the change:

Job Management Partner 1/Automatic Operation GUI and Command Reference (3021-3-315(E))

After the change:

Job Management Partner 1/Automatic Operation GUI, Command, and API Reference (3021-3-366(E))

--

Windows Server 2012 R2 was added as a supported operating system.

--

Functionality was added that facilitates the debugging of service templates. Changes were made to the manual structure to accommodate this new functionality.

1.1, 1.2, 1.3, 1.4, 1.6, 5., 6., A.1

A description was added regarding the use of the content plug-ins provided by JP1/AO in service template development.

1.1.1

A function was added that allows users to be promoted to root privilege when executing a content plug-in. This function can be used when the OS of the operation target device is UNIX.

4.1.3

A description was added regarding the conditions under which files can be transferred.

4.1.5, 4.1.6

The folder in which transferred files are stored can now be set in the property file (config_user.properties).

4.1.6

A description of the setting in the plugin.suPassword reserved plug-in property when a plug-in is executed without promoting user permission to root was added.

4.3.6

Public key authentication was added as an authentication method for operation target devices.

2.2.13, 4.3.4, 4.3.6, 4.3.11

Release plug-ins can now be deleted.

2.5.1, 4.1.4, 4.4.1

A description of reserved properties was added. Also, the following reserved properties were added:

• reserved.loop.index

• reserved.service.category

• reserved.service.name

• reserved.service.resourceGroupName

• reserved.step.path

• reserved.step.prevReturnCode

• reserved.task.description

• reserved.task.id

• reserved.task.name

• reserved.task.submitter

• reserved.task.url

3.2.7

For the reserved.step.prevReturnCode reserved property, a description of a scenario in which the preceding step is not executed when trying a task again was added.

3.2.7

Subsequent-step execution conditions were added to the information inherited when pasting a step or relational line.

3.3.7

In addition to Windows and Linux, content-plug-ins that execute commands and scripts in AIX, HP-UX, and Solaris are now supported.

4.1.2, 4.1.6, 4.3.6, 4.3.9, 4.3.10, 4.3.14, 4.3.15, 4.3.16

The description of the execution user for commands and scripts executed using content plug-ins was clarified.

4.1.3

An explanation that user profiles are not inherited when the OS of the operation target device is Windows was added.

4.1.3

The manual now mentions that certain commands must be installed in the OS of the operation target device before executing a content plug-in.

4.1.7

The ibm-943 character set used for communication by JP1/AO during plug-in execution was changed to ibm-943C.

4.1.8

The manual now mentions that certain commands must be installed in the OS of the operation target device before executing a plug-in.

4.1.10

A description of executing a non-standard script in the Command line text box was added.

4.3.10

A cautionary note about specifying the command line for a content plug-in was added.

4.3.10

A section on the standard output of plug-ins was added.

4.3.14

A description of the return values of content plug-ins was added.

4.3.11

A description of the relationship among the return values of executed commands or scripts, plug-ins, and steps was added.

4.3.12

A procedure for using a return value as the branching condition for a flow was added, for situations when a command or script executed as a plug-in returns codes outside the 0 to 63 range.

4.3.13

The manual now instructs users not to enclose the path of the execution directory in double or single-quotation marks, even if the path contains spaces.

4.3.16