Description
This operation component checks the access permissions for a file or directory.
If the operating system type is Windows, this component checks whether the attribute value is "read only" or "read/write".
If the operating system type is Linux or Solaris, this component checks whether the user that executed the component has the specified access permissions.
Options
Basic Options
Target host name or IP address where the operation component will be executed.
To execute the operation component on the Management Server, specify the following:
For IPv4: 'localhost' or '127.0.0.1'
For IPv6: 'localhost' or '::1'
An argument error occurs if the host name or IP address is omitted.
The maximum length of the host name or IP address is 1,024 characters. An argument error occurs if this is exceeded.
The name (full path) of the file/directory, where the file/directory access permissions are checked.
An argument error occurs if the file name or directory name is omitted.
The maximum length of the file name or directory name is 1,024 characters. An argument error occurs if this is exceeded.
access permissions information where the file/directory access permissions are checked.
When the operating system is Windows and the access permissions for the existing file/directory are checked, the file/directory attribute value is checked.
Specify "X" (execute), "R" (read) or "W" (write).
Multiple access permissions can be specified.
Specify access permissions as follows:
If the operating system type is Windows, any of the following can be specified.
To check "read-only", specify "X", "R" or "RX".
To check "read/write", specify "W", "WX", "RW" or "RWX".
Permissions content | Operating system type: Linux, Solaris | Operating system type: Windows |
|---|---|---|
X | Execute permission only | Read only |
W | Write permission only | Writable |
WX | Write and execute permission | Writable |
R | Read permission only | Read only |
RX | Read and execute permission | Read only |
RW | Read and write permission | Writable |
RWX | Full control | Writable |
Permissions content must be entered using the uppercase letters shown above in the shown order.
An argument error will occur if any value other than those shown above is specified for permissions content.
An argument error will occur if the content of the access permissions is omitted.
The maximum length of the string for the content of the access permissions is 1,024 characters. An argument error occurs if this is exceeded.
Advanced Options
Operating system of the host executing the operation component.
Specify Windows, Linux or Solaris. This option is not case sensitive.
If the OS type is omitted, the Configuration Management Database (CMDB) will be searched based on the specified host name or IP address, and Systemwalker Runbook Automation automatically sets the acquired OS type as the value.
The maximum length of the OS type is 1,024 characters. An argument error occurs if this is exceeded.
This is the name of the user that uses SSH to connect to the target host where the operation component is to be executed.
If the connected user name and password required for connection are not specified, the Configuration Management Database (CMDB) is searched based on the specified host name or IP address and Systemwalker Runbook Automation automatically sets the acquired connected user name as the value.
If the operation component connects with the file transfer infrastructure, the connected user name will be fixed at either of the following names and cannot be changed. In this case, the user name is ignored even if specified.
If the Business Server is running on Windows: SYSTEM user
If the Business Server is running on Linux or Solaris: root
The maximum length of the connected user name is 1,024 characters. An argument error occurs if this is exceeded.
This is the password of the user that uses SSH to connect to the target host where the operation component is to be executed.
If the connected user name and password required for connection are not specified, the Configuration Management Database (CMDB) is searched based on the specified host name or IP address and Systemwalker Runbook Automation automatically sets the acquired connected user password as the value.
If it connects with the file transfer infrastructure, the connected user password is invalid.
The maximum length of the connected user password is 1,024 characters. An argument error occurs if this is exceeded.
This is the name of the user that executes the command on the target host where the operation component is to be executed.
If the "execusername" and "execpassword" are not specified, the Configuration Management Database (CMDB) is searched based on the specified host name or IP address and Systemwalker Runbook Automation automatically sets the acquired administrator user as the value. If an administrator user has not been registered with the CMDB, the command will be executed using the name of the connected user.
If the host specified in "hostname" is running on Windows and the connection is made using the file transfer infrastructure, execute the command as a SYSTEM user. In this case, the user name is ignored even if specified.
The maximum length of the executing user name is 1,024 characters. An argument error occurs if this is exceeded.
This operation component does not use the value of "execpassword". The value of "execpassword" is ignored even if specified.
This is the completion timeout (seconds) for the execution of operation components.
Values between 300 and 86400 (1 day) can be specified.
Example) If the completion timeout is 10 minutes: 600
If the operation component has not finished executing even though the specified time has passed, the processing for the operation component will be interrupted with return value 201.
This is the retry count for the execution of operation components.
Specify the number of retry attempts to be used when operation components terminate with return value 161. Values between 0 and 5 can be specified.
If an operation component terminates with a return value other than "161" as a result of being re-executed from a retry, execution of the operation component will terminate even if the specified number of retries has not been reached. The return value for the operation component will be the value from the last time the operation component was executed.
Example) To retry the operation component twice: 2
This is the retry interval (seconds) for operation components.
Specify the time to wait before a retry is attempted if operation components terminate with return value 161. Values between 1 and 14400 can be specified.
Example) To retry at 300 second intervals: 300
If the specification of the timeout, retry and retry_interval is omitted, and a value beyond the limits of the above-mentioned is input, the value specified with the operation components definition file becomes effective. Refer to "2.5 Definition File for Operation Components" for details.
Return Values
Icon | Name | Return value | Description |
|---|---|---|---|
| Matches | 0 | The access permissions for a file or directory have been checked successfully. The access permissions match the content of the access permissions being checked. |
| Does not match | 1 | The access permissions for a file or directory have been checked successfully. The access permissions do not match the content of the access permissions being checked. |
| Failure | 161 | An attempt to check the access permissions for a file or directory failed. If a retry count has been specified, retries will be attempted. |
177 | An attempt to access a file or directory has failed. | ||
187 | Authentication failed when an attempt was made to connect to the Business Server over the network (using SSH). Alternatively, an error occurred during the processing of communications with the Business Server (file transfer infrastructure). In this case, the error code for the file transfer infrastructure is output to the execution results. Refer to "3.21 Detailed Code of File Transfer Infrastructure" for information on error codes. | ||
188 | When an operation component was performing an operation on a Business Server where an RBA Agent has not been installed, an SSH network connection with the Business Server was closed. | ||
189 | An attempt to connect to the Business Server over the network (using SSH) failed. Alternatively, an error occurred during the processing of communications with the Business Server (file transfer infrastructure). In this case, the error code for the file transfer infrastructure is output to the execution results. Refer to "3.21 Detailed Code of File Transfer Infrastructure" for information on error codes. | ||
197 | There is an error with the input information. | ||
200 | Checking the access permissions for a file or directory has terminated abnormally. | ||
- | - | 201 | Execution of the operation component timed out. |
202 | The operation component has not been executed. There is a problem with the settings for executing the operation component. | ||
203 | The operation component has not been executed normally. There is a problem with the Management Server environment. | ||
205 | The operation component has not been executed. There is a problem with the input information specification of the operation component. | ||
206 | The operation component has not been executed normally. There is a problem with the output information specification of the operation component. | ||
207 | The operation component has not been executed. The operation component may not have been registered on the Management Server. | ||
208 | The Automated Operation Process has been canceled because the Automated Operation Process was recovered while the operation component was executing. |
Output information
Variable | Description |
|---|---|
message | This variable will be set to the following message if the access permissions for a file or directory are checked successfully. The operation component was successful. If checking the access permissions for a file or directory fails, the content of the error will be output as a string. |
file_attribute | This variable is set to the access permissions for a file or directory. |
returnCode | This variable is set to the return value. |
If the operating system is Windows, the "file_attribute" variable will be set using the following format. For FAT32 file systems, however, the following access permissions will not be displayed.
C:\sample.txt BUILTIN\administrators:F
NT AUTHORITY\SYSTEM:F
BUILTIN\Users:RIf the operating system is Linux or Solaris, the "file_attribute" variable will be set using the following format.
-rw-r--r-- 1 root root 155 2011/07/25 15:55:58 sample.sh
Notes
If information other than the Management Server is entered for the "hostname" option, this operation component will execute actions using either the file transfer infrastructure or SSH. Specify settings so that communications can be performed using at least one of these methods. Refer to "3.16 Notes of Each Communication Method" for information on communication methods.
Refer to "3.16.7 Notes When Connected User And Executing User Are Different" for information on different connected and executing users.
For the name of the file or directory for which access permissions are to be checked, use only alphanumeric characters and white space and full width characters, and the symbols below:
Symbols that can be used: "!" "~" "_" "-" "."
If the specified filename is a symbolic link, the access permissions of the linked file/directory will be checked.
Use the Web console to check the return value. Refer to "Confirming the Operation Component Execution Status/Execution Results" in the Systemwalker Runbook Automation Operation Guide for details.
If a return value between 201 and 208 has been output, the Automated Operation Process will enter an aborted state or an error state, and error messages will be output to the following locations:
Event logs for the Management Server (if the Management Server is running on Windows(R))
syslogs for the Management Server (if the Management Server is running on Linux)
Custom messages for BPMN
Check for messages in these locations and take the appropriate action. Refer to the Systemwalker Runbook Automation Message Guide for details.