A.3 Version changes
- Organization of this subsection
(1) Changes in version 12-60
-
The following operating systems are now supported:
-
Windows Server 2022
-
Red Hat Enterprise Linux 8
-
Oracle Linux 8
-
CentOS 8
-
-
The tips for the procedure for directly specifying the input property values of steps were changed.
-
Descriptions of the reserved property for property mapping were changed.
-
Descriptions of setting items for the input property of a service were changed.
-
Specify List Items was deleted from the items set for the input property of a service.
-
Descriptions of the presentation format corresponding to the data types were changed.
-
Descriptions of the data type of the items that can be set for the output property of a service were changed.
-
Descriptions of the procedure for specifying the External Resource setting were added.
-
The Javascript sample and descriptions were changed.
-
Descriptions of the shared built-in service properties were changed.
-
The items set for property groups were changed.
-
The tips for copying a service template were changed.
-
The description of inserting the input property in the command line when creating or editing a plug-in was changed.
-
The description of "Important" for the specification method of Output Filter was changed.
-
"Build" was changed to "debug".
-
The description of the hierarchical flow plug-in in "Changes in version 11-10" was deleted.
(2) Changes in version 12-01
-
Descriptions regarding the presentation format setting function were added, modified, and deleted.
-
A description was added regarding the External Resource Provider function.
-
Figures were replaced and descriptions were added or modified in accordance with the structural changes to the following dialog boxes:
-
Create Input Property for Service dialog box
-
Edit Input Property for Service dialog box
-
Create Output Property for Service dialog box
-
Edit Output Property for Service dialog box
-
-
An explanation was added to indicate that multi-byte characters cannot be used in the file path when a script file is created.
(3) Changes in version 12-00
-
The return values "1" and "2" of service components were added, and the explanation of the subsequent step conditions was changed.
(4) Changes in version 11-51
In the Specify Component Input Property Mapping Parameters dialog box or the Specify Component Output Property Mapping Parameters dialog box, by selecting the View Property radio button, you can now display only the properties that can be mapped. As such, the relevant descriptions were changed.
(5) Changes in version 11-50
-
Descriptions of screen displays and procedures related to steps were changed.
-
The descriptions of the following shared built-in service properties were deleted:
- com.hitachi.software.dna.sys.jp1.username
- com.hitachi.software.dna.sys.jp1.password
-
The supplementary explanation for the procedure for importing service templates was deleted.
-
Notes on command execution were added.
(6) Changes in version 11-10
- The Service Builder window was redesigned.
-
Available Actions was added to the items that can be specified in the Edit Service Template Attributes dialog box.
-
A description about the Next Steps tab that is displayed in the Step Properties area was added.
-
The description about repeated steps was changed. A nested structure, where a maximum of three hierarchical levels of repeated steps can be used, is now available.
-
The description was changed because the labels for the conditions displayed in the Determine the return value based on the threshold > Condition pull-down menu in the Create Step window and the Edit Step window were changed.
-
A description about conditional expressions that use arrows to indicate connections with subsequent steps was added.
-
A description about the RESERVED PROPERTY dialog box, which displays the reserved properties related to repeated execution plug-ins, was added.
-
The reserved properties reserved.loop.indexN and reserved.loop.inputN were added.
-
A description about the Select Reference Property window was added for cases where repeated execution plug-ins are defined in a nested structure.
-
Because JP1/AJS3 is no longer bundled with JP1/AO, descriptions related to return values were deleted.
-
Regarding the interval plug-in, branch by returncode plug-in, abnormal-end plug-in, and branch by property value plug-in, the specifications concerning the availability of interruption and skipping during debugging were changed. The manual was revised accordingly.
-
The reserved properties reserved.loop.indexN and reserved.loop.inputN were added to the information displayed for repeated execution flows.
(7) Changes in version 11-01
A note about the file sizes of imported service templates was added.
An explanation was added noting that if you enable the Run as system account(Windows) option when creating or editing a plug-in, commands and scripts will be executed on the connection destination host with the permissions of the System account.
The description of the information displayed in a flow was changed.
A cautionary note regarding the procedure for starting debugging was changed.
Changes were made to the step information that can be changed when step execution is interrupted.
(8) Changes in version 11-00
(a) Changes from the manual (3021-3-087-40)
The following operating systems are now supported:
Linux 7
Oracle Linux 6 (x64)
Oracle Linux 7
CentOS 6 (x64)
CentOS 7
SUSE Linux 12
The following operating systems are no longer supported:
Linux 5 (AMD/Intel 64)
Linux 5 Advanced Platform (AMD/Intel 64)
The product was migrated from 32-bit Windows to 64-bit Windows.
The installation folder was changed for the Windows version of JP1/AO and the Common Component.
A description of using JP1/AO in English and Chinese-language environments was added.
The structure and contents of the manual were changed to reflect the redesign of the JP1/AO interface.
A function was added that exports service templates.
A function was added to place a release service template as a service component in a flow of a service template. Accordingly, the existing plug-ins and service components are now collectively called components.
Descriptions about visibility and display settings for service properties were added.
Functions were added to specify visibility and display settings for service properties and the property group to which the service properties belong.
A function was added to map step properties.
Auto-completion of property values was added.
A function was added to specify an image file for service overview as a custom file.
A function was added that sets the following items in the service resource file:
Service property name
Service property description
Step property name
Step property description
A description of property mapping was added.
Descriptions about whether properties can be mapped depending on the visibility or data type were added.
A function was added that elevates step properties to service properties.
Tag management was added as a way to classify service templates and services. Accordingly, category management was removed as a classification method.
Service groups were added as a way to manage resources. Accordingly, resource groups were removed.
A function was added that imports and exports service properties.
Step-into, step-over, step-return, and breakpoint setting were added as the functions for executing a debug task during debugging.
The following were added as the causes in the description of return value 71 of a content plug-in:
An attempt to move to the execution directory failed.
An attempt to set an environment variable failed.
The total data output to the standard output and standard error output exceeds 100KB was added to the description of return value 72 of a content plug-in.
The name of a basic plug-in was changed from File-Forwarding Plug-in to File-Transfer Plug-in.
The name of a basic plug-in was changed from Judge ReturnCode Plug-in to Branch by ReturnCode Plug-in.
The name of a basic plug-in was changed from Judge Value Plug-in to Branch by Property Value Plug-in.
(b) Changes from the manual (3021-3-363-10(E))
Linux was added as a supported operating system.
The installation folder was changed for the Windows version of JP1/AO and the Common Component.
The product was migrated from 32-bit Windows to 64-bit Windows.
The structure and contents of the manual were changed to reflect the redesign of the JP1/AO interface.
A procedure for changing a plug-in version was added as part of the addition of the plug-in version management function.
A description of the local execution function was added. This function allows users to start processes directly on local hosts and perform tasks such as executing commands and copying files.
Keyboard interactive authentication was added as an authentication method used for SSH connections with operation target devices.
Service groups were added as a way to manage resources. Accordingly, resource groups were removed.
A function was added that exports service templates.
A function was added to place a release service template as a service component in a flow of a service template. Accordingly, the existing plug-ins and service components are now collectively called components.
Descriptions about visibility and display settings for service properties were added.
Functions were added to specify visibility and display settings for service properties and the property group to which the service properties belong.
A function was added to map step properties.
Auto-completion of property values was added.
A function was added to specify an image file for service overview as a custom file.
A function was added that sets the following items in the service resource file:
Service property name
Service property description
Step property name
Step property description
A description of property mapping was added.
Descriptions about whether properties can be mapped depending on the visibility or data type were added.
A function was added that elevates step properties to service properties.
Tag management was added as a way to classify service templates and services. Accordingly, category management was removed as a classification method.
A function was added that imports and exports service properties.
Step-into, step-over, step-return, and breakpoint setting were added as the functions for executing a debug task during debugging.
The following were added as the causes in the description of return value 71 of a content plug-in:
An attempt to move to the execution directory failed.
An attempt to set an environment variable failed.
The total data output to the standard output and standard error output exceeds 100KB was added to the description of return value 72 of a content plug-in.
The name of a basic plug-in was changed from File-Forwarding Plug-in to File-Transfer Plug-in.
The name of a basic plug-in was changed from Judge ReturnCode Plug-in to Branch by ReturnCode Plug-in.
The name of a basic plug-in was changed from Judge Value Plug-in to Branch by Property Value Plug-in.
(9) Changes in version 10-52
(a) Changes in the manual (3021-3-087-40)
Linux was added as a supported operating system.
A procedure for changing a plug-in version was added as part of the addition of the plug-in version management function.
A description of the local execution function was added. This function allows users to start processes directly on local hosts and perform tasks such as executing commands and copying files.
Keyboard interactive authentication was added as an authentication method used for SSH connections with operation target devices.
A description of characters that can be specified in the Command line text box was added.
(10) Changes in version 10-50
(a) Changes in the manual (3021-3-087-30)
A description of the case in which the user wants to use a content plug-in provided by JP1/AO in service template development was added.
Public key authentication was added as an authentication method for operation target devices.
An explanation that user profiles are not inherited when the OS of the operation target device is Windows was added.
A description of the specification in the Command line text box to execute a non-standard script was added.
(b) Changes in the manual (3021-3-363-10(E))
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 to facilitate the debugging of service templates. The manual structure was changed to accommodate this new functionality.
A description of the case in which the user wants to use a content plug-in provided by JP1/AO in service template development was added.
Public key authentication was added as an authentication method for operation target devices.
Release plug-ins can now be deleted.
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
For the reserved.step.prevReturnCode reserved property, a description of a scenario in which the preceding step is not executed when retrying a task was added.
Subsequent-step execution conditions were added as information inherited when pasting a step or relational line.
In addition to Windows and Linux, content plug-ins that execute commands and scripts in AIX, HP-UX, and Solaris are now supported.
The description of the execution user for commands and scripts by using content plug-ins was clarified.
An explanation that user profiles are not inherited when the OS of the operation target device is Windows was added.
A function was added to allow users to select whether to elevate user permission to root privilege when executing a content plug-in. This function can be used when the OS of the operation target device is UNIX.
A description was added regarding the conditions under which files can be transferred.
The folder in which transferred files are stored can now be set in the property file (config_user.properties).
The manual now mentions that certain commands must be installed in the OS of the operation target device before executing content plug-ins.
The ibm-943 character set used for communication by JP1/AO during plug-in execution was changed to ibm-943C.
The manual now mentions that certain commands must be installed in the OS of the operation target device before executing plug-ins.
A description of the setting in the plugin.suPassword reserved plug-in property when execution with root privileges is not specified was added.
A description of the specification in the Command line text box to execute a non-standard script was added.
A cautionary note about specifying the command line for a content plug-in was added.
A description of the return values of content plug-ins was added.
A description of the relationship among the return values of executed commands or scripts, plug-ins, and steps was added.
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 a value outside the 0 to 63 range.
A section on the standard output of plug-ins was added.
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.
(11) Changes in version 10-12
(a) Changes in the manual (3021-3-087-20)
Windows Server 2012 R2 was added as a supported operating system.
Functionality was added to facilitate the debugging of service templates. The manual structure was changed to accommodate this new functionality.
For the reserved.step.prevReturnCode reserved property, a description of a scenario in which the preceding step is not executed when retrying a task was added.
Subsequent-step execution conditions were added to the information inherited when pasting a step or relational line.
A function was added to allow users to select whether to elevate user permission to root privilege when executing a content plug-in. This function can be used when the OS of the operation target device is UNIX.
A description was added regarding the conditions under which files can be transferred.
The folder in which transferred files are stored can now be set in the property file (config_user.properties).
A description of the setting in the plugin.suPassword reserved plug-in property when execution with root privileges is not specified was added.
A description of the return values of content plug-ins was added.
A description of the relationship among the return values of executed commands or scripts, plug-ins, and steps was added.
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 a value outside the 0 to 63 range.
(12) Changes in version 10-11
(a) Changes in the manual (3021-3-087-10)
Release plug-ins can now be deleted.
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
In addition to Windows and Linux, content plug-ins that execute commands and scripts in AIX, HP-UX, and Solaris are now supported.
The description of the execution user for commands and scripts by using content plug-ins was clarified.
The manual now mentions that certain commands must be installed in the OS of the operation target device before executing content plug-ins.
The ibm-943 character set used for communication by JP1/AO during plug-in execution was changed to ibm-943C.
The manual now mentions that certain commands must be installed in the OS of the operation target device before executing plug-ins.
A cautionary note about specifying the command line for a content plug-in was added.
A section on the standard output of plug-ins was added.
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.