A.1 Functional differences between basic plug-ins by version
- Organization of this subsection
(1) Basic plug-ins available in each version
The table below lists the basic plug-ins that can be used with JP1/AO version 10-50. Plug-ins cannot be used with an earlier version of JP1/AO than the first version to feature the plug-in.
Plug-in |
Version |
---|---|
General command plug-in |
01.00.00 01.02.00 01.10.00 01.12.00 01.50.00 |
File-forwarding plug-in |
01.00.00 01.02.00 01.11.00 01.12.00 01.50.00 |
Repeated execution plug-in |
01.00.00 |
Email notification plug-in |
|
User-response wait plug-in |
|
Standard output plug-in |
|
Terminal connect plug-in |
01.02.00 01.50.00 |
Terminal command plug-in |
01.02.00 |
Terminal disconnect plug-in |
|
Flow plug-in |
01.10.00 |
Interval plug-in |
|
Judge returncode plug-in |
|
Test value plug-in |
|
Abnormal-end plug-in |
|
Judge value plug-in |
(a) Difference in functionality of general command plug-in between versions
Functional differences between versions 01.00.00 and 01.02.00
-
Devices running Solaris and HP-UX can now be specified as operation target devices.
-
The configuration of the following property keys has changed.
Table A‒2: Functional differences between property keys Property key
Functionality in 01.00.00
Functionality in 01.02.00
stdoutProperty1
- Description
-
Specifies the property key of the service property in which to store the value extracted by the stdoutPattern1 property. The character string assigned to the service property can be a maximum of 1,024 characters long. The 1,025th and subsequent characters are discarded.
- Input/Output type
-
in
- Mandatory/optional
-
false
- Description
-
The character string extracted by Standard Output Pattern 1 is output to this property.
- Input/Output type
-
out
- Mandatory/optional
-
Not specified.
stdoutProperty2
- Description
-
Specifies the property key of the service property in which to store the value extracted by the stdoutPattern2 property. The character string assigned to the service property can be a maximum of 1,024 characters long. The 1,025th and subsequent characters are discarded.
- Input/Output type
-
in
- Mandatory/optional
-
false
- Description
-
The character string extracted by Standard Output Pattern 2 is output to this property.
- Input/Output type
-
out
- Mandatory/optional
-
Not specified.
stdoutProperty3
- Description
-
Specifies the property key of the service property in which to store the value extracted by the stdoutPattern3 property. The character string assigned to the service property can be a maximum of 1,024 characters long. The 1,025th and subsequent characters are discarded.
- Input/Output type
-
in
- Mandatory/optional
-
false
- Description
-
The character string extracted by Standard Output Pattern 3 is output to this property.
- Input/Output type
-
out
- Mandatory/optional
-
Not specified.
commandLine
When the operation target device is running a version of UNIX other than Linux, specify ASCII characters in the commandLine property.
If the operation target device is running UNIX, you can specify ASCII characters in the commandLine property. Certain conditions must be met to use non-ASCII characters. For details about these conditions, see A.5 Prerequisites for executing command lines containing non-ASCII characters in UNIX.
commandLineParameter
When the operation target device is running a version of UNIX other than Linux, specify ASCII characters in the commandLineParameter property.
If the operation target device is running UNIX, you can specify ASCII characters in the commandLineParameter property. Certain conditions must be met to use non-ASCII characters. For details about these conditions, see A.5 Prerequisites for executing command lines containing non-ASCII characters in UNIX.
Functional differences between versions 01.02.00 and 01.10.00
-
Devices running AIX can now be specified as operation target devices.
Functional differences between versions 01.10.00 and 01.12.00
-
The elevatePrivileges property was added, allowing the operator to specify whether to elevate user privileges to root for operation target devices running UNIX.
Functional differences between versions 01.12.00 and 01.50.00
-
The publicKeyAuthentication property was added, allowing you to specify whether to use public key authentication when connecting to operation target devices via SSH.
(b) Difference in functionality of file-forwarding plug-in between versions
Functional differences between versions 01.00.00 and 01.02.00
-
The configuration of the following property keys has changed.
Table A‒3: Functional differences between property keys Property key
Functionality in 01.00.00
Functionality in 01.02.00
remoteFilePath
If the operation target device is running Linux, you can only specify ASCII characters in the names of the files and folders to be forwarded.
If the operation target device is running Linux, the character set of the files and folders to be forwarded must match the character set being used by the connecting user. Certain conditions must be met to use non-ASCII characters in the remoteFilePath property. For details about these conditions, see A.5 Prerequisites for executing command lines containing non-ASCII characters in UNIX.
Functional differences between versions 01.02.00 and 01.11.00
-
Devices running AIX, HP-UX, and Solaris can now be specified as operation target devices.
Functional differences between versions 01.11.00 and 01.12.00
-
The elevatePrivileges property was added, allowing the operator to specify whether to elevate user privileges to root for operation target devices running UNIX.
Functional differences between versions 01.12.00 and 01.50.00
-
The publicKeyAuthentication property was added, allowing you to specify whether to use public key authentication when connecting to operation target devices via SSH.
(c) Difference in functionality of terminal connect plug-in between versions
Functional differences between versions 01.02.00 and 01.50.00
-
The publicKeyAuthentication property was added, allowing you to specify whether to use public key authentication when connecting to operation target devices via SSH.
(2) Handling of locales and character sets in each version
This subsection describes the values assigned to the locale environment variable when each version of a plug-in communicates with operation target devices, and whether the plug-in can automatically detect the character set. This automatic detection allows you to use non-ASCII characters in command lines, standard output, standard error output, and the file names of forwarded files.
Note that because the following plug-ins do not connect to connection destinations, they do not set a locale or automatically detect the character set.
-
Repeated execution plug-in
-
Email notification plug-in
-
User-response wait plug-in
-
Standard output plug-in
-
Flow plug-in
-
Interval plug-in
-
Judge returncode plug-in
-
Test value plug-in
-
Abnormal-end plug-in
-
Judge value plug-in
Plug-in name |
Plug-in version |
|
---|---|---|
01.00.00 |
01.02.00 or later |
|
General command plug-in |
LC_ALL=C |
The default locale of the connecting user is assigned to LC_ALL and LANG. |
File-forwarding plug-in |
LC_ALL=C |
The default locale of the connecting user is assigned to LC_ALL and LANG. |
Terminal connect plug-in |
-- |
None |
Terminal command plug-in |
-- |
None |
Terminal disconnect plug-in |
-- |
None |
- Legend:
-
None: No value is assigned. --: No applicable version.
Plug-in |
Plug-in version |
|
---|---|---|
01.00.00 |
01.02.00 or later |
|
General command plug-in |
N |
Y |
File-forwarding plug-in |
N |
Y |
Terminal connect plug-in |
-- |
S |
Terminal command plug-in |
-- |
S |
Terminal disconnect plug-in |
-- |
S |
- Legend:
-
Y: Detected automatically when the protocol is SSH. S: Not detected automatically so must be specified in the Character Set property. N: Not detected automatically. --: Not applicable version.
Related topics
-
Locale set for operation target devices during plug-in execution in the Job Management Partner 1/Automatic Operation Service Template Development Guide
-
Character set used for communication by JP1/AO during plug-in execution in theJob Management Partner 1/Automatic Operation Service Template Development Guide
(3) Operation target devices usable as connection destinations
This subsection shows the operation target devices that can be used as connection destinations. For details about the specific operating system version that must be running on an agentless connection destination and the commands required to execute plug-ins, see the release notes.
Note that the following plug-ins do not connect to connection destinations:
-
Repeated execution plug-in
-
Email notification plug-in
-
User-response plug-in
-
Standard output plug-in
-
Flow plug-in
-
Interval plug-in
-
Judge returncode plug-in
-
Test value plug-in
-
Abnormal-end plug-in
-
Judge value plug-in
Plug-in |
Operation target device |
|||||
---|---|---|---|---|---|---|
Windows |
Linux |
Solaris |
HP-UX |
AIX |
Device compatible with SSH or Telnet |
|
General command plug-in |
01.00.00 |
01.00.00 |
01.02.00 |
01.02.00 |
01.10.00 |
N |
File-forwarding plug-in |
01.00.00 |
01.00.00 |
01.11.00 |
01.11.00 |
01.11.00 |
N |
Terminal connect plug-in |
01.02.00# |
01.02.00# |
01.02.00# |
01.02.00# |
01.02.00# |
01.02.00 |
Terminal command plug-in |
01.02.00# |
01.02.00# |
01.02.00# |
01.02.00# |
01.02.00# |
01.02.00 |
Terminal disconnect plug-in |
01.02.00# |
01.02.00# |
01.02.00# |
01.02.00# |
01.02.00# |
01.02.00 |
- Legend:
-
01.00.00: Can be used with plug-in version 01.00.00 or later.
01.02.00: Can be used with plug-in version 01.02.00 or later.
01.10.00: Can be used with plug-in version 01.10.00 or later.
01.11.00: Can be used with plug-in version 01.11.00 or later.
N: Not supported.
- #
-
Can be used if configured as a server with SSH or Telnet support.