A.8 Version changes
- Organization of this subsection
(1) Changes in version 13-00
- Coexistence with JP1/OA is not supported, and descriptions about JP1/OA were deleted.
- The procedure for replacing was changed.
- The description of the notes on restarting JP1/AO services was changed.
- The description of the integrated trace log was deleted.
(2) 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
-
Descriptions of periodically archiving tasks and periodically deleting histories were added.
-
Descriptions of adding and managing user accounts were added.
-
Notes were added regarding the use of products that use the same Common Component.
-
Descriptions of agentless Connection Destinations were added.
-
The procedure for updating the components used in a service template was added.
-
Descriptions of the setting items for agentless Connection Destination definitions were changed.
-
Descriptions of task behavior when the JP1/AO service is restarted were added.
-
Descriptions of public log files were added.
-
The following restrictions were changed:
- Character string specified as a user ID of a JP1/AO user
- Character string specified as a password of a JP1/AO user
- Port number used for connections with SMTP server
- Character string specified as the user ID for an SMTP server
- Character string specified as a recipient of notification emails
-
The following item was added:
- Size of the property files or the external resource provider definition files imported from windows
-
The types of events output to the audit log were added.
-
External Resource Providers were added to the types of events output to the audit log.
(3) Changes in version 12-01
-
An explanation was added regarding the email notification that is sent when a service template is run that uses a user-response wait plug-in.
-
A description was added regarding the External Resource Provider defined in the service template.
-
A description was added regarding the function for setting constraints in the Service Definition window (editing).
(4) Changes in version 12-00
-
None
(5) Changed in version 11-50
-
The descriptions of forcibly stopping tasks were changed.
-
Notes on retrying tasks were added.
-
The location of the folder where definition files are stored was changed.
-
The descriptions of the behavior of tasks when the system switches from standard time to daylight saving time, and vice versa, were changed.
(6) Changes in version 11-10
-
The definitions of web service connection-destinations can now be managed. This is now described in the manual, and figures depicting the relevant windows were added.
-
JP1/AO no longer uses JP1/AJS3 as a task processing engine, and content indicating otherwise was deleted.
-
An explanation of the case where changing the setting for whether a task can be retried around the time that the task was executed was added to the examples of statuses in which tasks can be retried.
-
Restored tasks can now be retried and their progress can be displayed, and content indicating otherwise was deleted.
-
Task statuses can now be detected immediately. Accordingly, the explanations of task status transitions and the timing of JP1 event notifications were changed.
-
The Service Builder window was updated and the name of the window was changed.
-
The following was added: a description of the arrow statuses that are displayed when an arrow conditional-expression is set.
-
JP1/AO no longer requires JP1/Base as a prerequisite product, and descriptions of this requirement were deleted.
-
Detecting a task status of Long Running was added to the trigger of JP1 event notifications, and an description of this was added.
-
Adobe Flash Player is no longer required, and descriptions of this requirement were deleted.
-
Search criteria can now be saved as a filter. This is now described in the manual, and figures depicting the relevant windows were changed.
-
Available Actions can now be set for services. This is now described in the manual, and figures depicting the relevant windows were changed.
-
A string up to 1,024 characters can now be specified for the description of the following items:
Tasks, service templates, steps, property groups, plug-in properties, and services
-
An explanation was added noting that services can be forcibly terminated or retried only when doing so is permitted in the service settings.
-
Connected Time and Connection Status were added to the list of agentless remote connections. This is now described in the manual, and figures depicting the relevant windows were changed.
-
Agentless remote connections can now be tested, and a description of this was added.
-
Within Service Share Properties, the JP1 user name and password no longer need to be set. The manual was revised accordingly, and figures depicting the relevant windows were changed.
-
AJS_log.jar is no longer output when the hcmds64getlogs command is executed, and content indicating otherwise was deleted.
-
The return values of the following plug-ins are now output to the task log: flow plug-ins, interval plug-ins, branch by return code plug-ins, abnormal end plug-ins, and branch by property value plug-ins. The manual was revised accordingly.
(7) Changes in version 11-01
The last login time now appears in the main window.
The description of the Step Start Time item displayed in the tasks list was changed.
A situation in which the Login window does not appear was added to the troubleshooting procedures.
An explanation was added regarding information output to the task log, stating that when the value of a property with the Composite data type is 4,097 characters or longer, an ellipsis (...) replaces the 4,097th and subsequent characters.
(8) Changes in version 11-00
(a) Changes from 3021-3-083-70
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 port numbers used for communication between JP1/AO and Web browsers were changed.
The structure and contents of the manual were changed to reflect the redesign of the JP1/AO interface.
Status of service was added as a way to classify JP1/AO services.
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 exports service templates.
A function was added that updates the service templates used by a service to a chosen version.
A Dashboard window was added in which users can view statistical information about services and tasks.
Service groups were added as a way to manage resources. Accordingly, resource groups were removed.
A function that imports and exports service properties was added. Accordingly, the section on setting preset properties was removed.
The section on starting Hitachi Command Suite products using the Link&Launch function was removed.
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 3021-3-314-20(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 port numbers used for communication between JP1/AO and Web browsers were changed.
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.
The maximum number of concurrently executable plug-ins in an ordinary task was changed to 100.
Keyboard interactive authentication was added as an authentication method used for SSH connections with connection-target hosts.
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.
A cautionary note was added explaining that the version, revision number, and restriction code of JP1/AO must match on the source and destination hosts of backup and restoration operations.
A description of the services registered when setting up a cluster system was added.
Status of service was added as a way to classify JP1/AO services.
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 exports service templates.
A function was added that updates the service templates used by a service to an arbitrary version.
A Dashboard window was added in which users can view statistical information about services and tasks.
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. Accordingly, the section on setting preset properties was removed.
The section on starting Hitachi Command Suite products using the Link&Launch function was removed.
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 10-52
(a) Changes in 3021-3-083-70
Linux was added as a supported operating system.
The maximum number of concurrently executable plug-ins in an ordinary task was changed to 100.
Keyboard interactive authentication was added as an authentication method used for SSH connections with connection-target hosts.
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.
A cautionary note was added explaining that the version, revision number, and restriction code of JP1/AO must match on the source and destination hosts of backup and restoration operations.
A description of the services registered when setting up a cluster system was added.
(10) Changes in 10-50
(a) Changes in 3021-3-083-60
JP1/AO can now perform external authentication linkage by linking with Active Directory.
Public key authentication was added as an authentication method for managed devices.
The https protocol can now be used between the JP1/AO server and a Web browser.
A description was added indicating that the following files are excluded from command-based backup and restore operations:
SSL server certificate file for https connections
Private key files for https connections
Private key files for public key authentication
The stopcluster command was added.
This command can be executed when preparing to stop JP1/AO services in a cluster environment.
A description of the procedure for restoring a JP1/AO server remotely from a backup file was added.
(b) Changes in 3021-3-314-20(E)
As of December 2014, the manual name and document number have changed as follows:
- Before
JP1/Automatic Operation GUI and Command Reference (3021-3-315)
- After
JP1/Automatic Operation GUI, Command, and API Reference (3021-3-366)
Windows Server 2012 R2 was added as a supported operating system.
JP1/AO can now perform external authentication linkage by linking with Active Directory.
A function was added that allows users to forcibly stop tasks.
A function to retry steps was added.
Users can now view the progress of tasks in the Task Monitor view.
A description of the maximum number of plug-ins in a task that can be executed concurrently was added.
Public key authentication was added as an authentication method for managed devices.
The maximum number of preset properties that can be added to one service template can now be set in a property file (config_user.properties).
For General command plug-ins, file-forwarding plug-ins, and content plug-ins, you can now specify whether to elevate the user to superuser.
Detailed task information can now be output as a batch, and scheduled and recurring tasks can now be re-registered in a batch operation.
The https protocol can now be used between the JP1/AO server and a Web browser.
Descriptions of the procedures for displaying and downloading the task log were added.
A description was added indicating that the following files are excluded from command-based backup and restore operations:
SSL server certificate file for https connections
Private key files for https connections
Private key files for public key authentication
The stopcluster command was added.
This command can be executed when preparing to stop JP1/AO services in a cluster environment.
A description of the procedure for restoring a JP1/AO server remotely from a backup file was added.
A note was added regarding the action to take when a task is taking too long to execute in an environment with no external network connection.
The recommended action when a task does not end was changed.
The information output to the task log was changed. A description of the plug-in return values recorded in the task log was added.
(11) Changes in version 10-12
(a) Changes in 3021-3-083-50
Windows Server 2012 R2 was added as a supported operating system.
A function was added that allows users to forcibly stop tasks.
A function to retry steps was added.
Users can now view the progress of tasks in the Task Monitor view.
A description of the maximum number of plug-ins in a task that can be executed concurrently was added.
The maximum number of preset properties that can be added to one service template can now be set in a property file (config_user.properties).
For General command plug-ins, file-forwarding plug-ins, and content plug-ins, you can now specify whether to elevate the user to superuser.
Descriptions of the procedures for displaying and downloading the task log were added.
The recommended action when a task does not end was changed.
The information output to the task log was changed. A description of the plug-in return values recorded in the task log was added.
(12) Changes in version 10-11
(a) Changes in 3021-3-083-40
Detailed task information can now be output as a batch, and scheduled and recurring tasks can now be re-registered in a batch operation.
A note was added regarding the action to take when a task is taking too long to execute in an environment with no external network connection.
(13) Changes in version 10-10
(a) Changes in 3021-3-083-30
A description of how to set preset properties was added.
A description of linking with JP1/IM - NP operational content was added.
The Develop role was added as a role that can be set for resource groups.
The DevelopGroup built-in user group was added.
Users in the Admin role can now develop service templates.
A procedure for developing service templates was added.
The Develop role was added under the Who can perform this task heading.
Restrictions regarding category specification were added.
(b) Changes in 3021-3-314-10(E)
A description of how to set preset properties was added.
Information about linking with JP1/AJS3 was added.
A description of linking with JP1/IM - NP operational content was added.
A description of the storage locations of the service templates in the JP1/AO standard package and the JP1/AO Content Set was added.
The Develop role was added as a role that can be set for resource groups.
The DevelopGroup built-in user group was added.
Telnet was added as a supported protocol.
Users in the Admin role can now develop service templates.
A description of maintenance was added.
A function was added that allows users to specify task names, task descriptions, and property values for direct-access URLs in the Submit Service dialog box.
A method for estimating the length of query parameters was added.
A procedure for developing service templates was added.
The Develop role was added under the Who can perform this task heading.
Restrictions regarding category specification were added.
(14) Changes in version 10-02
(a) Changes in 3021-3-083-20
Information about linking with JP1/AJS3 was added.
Telnet was added as a supported protocol.
A function was added that allows users to specify task names, task descriptions, and property values for direct-access URLs in the Submit Service dialog box.
A method for estimating the length of query parameters was added.
(15) Changes in version 10-01
(a) Changes in 3021-3-083-10
A description of the storage locations of the service templates in the JP1/AO standard package and the JP1/AO Content Set was added.
A description of maintenance was added.