You can integrate BMC Release Process Management (RPM) with Secure Shell (SSH) to dispatch the RPM processes through the SSH client target servers. With this integration, you can perform the deployments on remote target servers by using the existing SSH clients. You can use the set of default scripts available for this integration to trigger your deployment tasks. Before you can start using SSH in RPM, you need to create and assign the following properties to the source and target servers where SSH is installed:
SSH properties starting with RPM 5.0.01.00
- SOURCE_SSH_USER: User name for authentication to the source server
- SOURCE_SSH_PASSWORD: Password for authentication to the source server
- SSH_USER: User name for authentication to the target server
- SSH_PASSWORD: Password for authentication to the target server
(Optional) SS_CHANNEL_ROOT: File path on the target server
Note
Enter this value if you do not want to use the default path.
The default value for SS_CHANNEL_ROOT is the following:
- (Linux) '/tmp'
- (Windows) 'C:/windows/temp'
SSH properties for RPM 5.0.00.01 and earlier
- SSH_USER: User name for authentication
- SSH_PASSWORD: Password for authentication
(Optional) SS_CHANNEL_ROOT: File path on the target server
Note
Enter this value if you do not want to use the default path.
The default value for SS_CHANNEL_ROOT is the following:
- (Linux) '/tmp'
- (Windows) 'C:/windows/temp'
After you create the SSH properties for the required servers that you want to use in a step, you need to specify the values for these properties.
On the Properties tab for a source server:
On the Server properties tab for a target server:
Integrating-with-Secure-Shell-SSH
Managing-properties