Getting Started with RES Automation Manager Agent for Linux

Transcription

1 Getting Started with RES Automation Manager Agent for Linux

2 Contents Chapter 1: Introduction 1 Chapter 2: Prerequisites and General Guidelines 2 Chapter 3: Installation Manual Installation Installation with RES Automation Manager Other Options... 6 Chapter 4: Next steps 7 Chapter 5: Known Issues and Limitations 8 Chapter 6: Where to go from here? 9 ii

3 Chapter 1: Introduction Chapter 1: Introduction RES Automation Manager 2012 introduces the RES Automation Manager Agent for Linux Operating Systems. With this Agent, you can execute the following Tasks on machines running Linux Operating Systems: Linux Command (Execute) Linux Computer (Reboot, Shutdown) Linux Resource (Download) This guide describes the installation of an RES Automation Manager Agent on a Linux operating system. Copyright RES Software 1

4 Chapter 2: Prerequisites and General Guidelines Chapter 2: Prerequisites and General Guidelines Prerequisites RES Automation Manager RES Automation Manager 2012 or later Linux One of the following Linux Operating Systems: Red Hat Enterprise Linux release 4: 4.5 or higher Red Hat Enterprise Linux release 5: 5.3 or higher SUSE Linux Enterprise Server release 10: versions higher than 10.0 IBM AIX 5L: version 5.3 Installation package res-am-agent<version of package>.rpm (Red Hat) Installation package res-am-agent<version of package>.rpm (SUSE Linux) Account Administrator rights to access and add files on the target computer Administrator rights to access and install software on the target computer Network When using multicast in your RES Automation Manager environment (Global Setting Dispatcher discovery set to Autodetect), port 3163 needs to be open on the machine running the RES Automation Manager Agent for Linux. For example, you can do this by adjusting the firewall settings using iptables: iptables -A INPUT -m udp -p udp --dport j ACCEPT iptables -A INPUT -m tcp -p tcp --dport j ACCEPT After activating the firewall rules, the RES Automation Manager Agent for Linux can be configured with: /usr/local/bin/resamad d m File Transfer from Microsoft Windows You may want to use applications such as WinSCP ( or Tunnelier ( to transfer the RPM file of the RES Automation Manager Agent for Linux from a Microsoft Windows share to the target Linux machine. 2 Copyright RES Software

5 Chapter 3: Installation Chapter 3: Installation 3.1 Manual Installation This chapter covers the manual installation of the RES Automation Manager Agent for Linux. The installation procedure is similar for Red Hat Enterprise Linux, SUSE Linux Enterprise Server and IBM AIX. Installation 1. Transfer the RPM file of the RES Automation Manager Agent for Linux (res-amagent<version of package>.rpm to the target Linux machine. 2. On the target Linux machine, log in as root. 3. Change the working directory to the location of the RPM file by typing the following command in a Terminal window: cd /root 4. Install the RPM file of the RES Automation Manager Agent for Linux by typing the following command: rpm ivh res-am-agent<version of package>.rpm. 5. Configure the Agent to start automatically by typing the following command: chkconfig - add resamad 6. Once configured, the auto start of the Agent can be toggled with the following command: chkconfig resamad off or chkconfig resamad on 7. Change the working directory to /usr/local/bin by typing the following command: cd /usr/local/bin 8. Start the Agent for the first time by connecting it to a known and operational RES Automation Manager Dispatcher. To do so, type the following command:./resamad dd<dispatcher IP or hostname> Alternatively, use the command./resamad -d m to search for RES Automation Manager environments. When prompted, select a discovered environment. Use this setting when using multicast in your RES Automation Manager environment. See Prerequisites and General Guidelines (on page 2). 9. After this, the Agent will register itself in the node Infrastructure > Agents of the RES Automation Manager Console. 10. Stop the RES Automation Manager Agent for Linux and subsequently start it again via the official start stop script, which correctly initializes the RES Automation Manager Agent for Linux: /etc/init.d/resamad stop /etc/init.d/resamad start After this, the Agent will automatically start itself when the Linux server is booted. If, however, you need to stop and start the RES Automation Manager Agent for Linux manually, please use the commands /etc/init.d/resamad stop and /etc/init.d/resamad start The configuration of the RES Automation Manager Agent for Linux is stored in /etc/res/resamad.xml. This file contains all necessary information for an Agent to connect to the RES Automation Manager environment. Instead of manual Agent configuration, you can also place a preconfigured resamad.xml file on each Agent. Copyright RES Software 3

6 Chapter 3: Installation 3.2 Installation with RES Automation Manager Instead of installing the RES Automation Manager Agent for Linux manually, you can also install it by executing an RES Automation Manager Task on another Agent. To do so, do the following: 1. Open the RES Automation Manager Console. 2. Configure a Module with a Task Execute Secure Shell (SSH) Commands. 3. Click the Properties tab of the Task Execute Secure Shell (SSH) Commands. 4. In the Host field, click. This opens the Select Connector window. 5. Click Add and add a Remote Hosts connector for the appropriate Linux machine(s). 6. As Authentication method, select Password. 7. In the Security context field, specify the account credentials with sufficient administrator rights to access, add and install files on the Linux machine (for example, root). 8. Select Use Secure Shell commands. 9. Click the Commands tab and add the following commands: smbclient $[SHARE] --user $[USERNAME]%$[PASSWORD] --workgroup $[DOMAIN] -c 'cd "$[LOCATION]"; get "$[RPM]"' rpm -ivh $[RPM] 10. Click the Module Parameters tab and add the following parameters: SHARE: A text parameter that holds the location of the share on which the RPM is located. If the sharename is an UNC path, every backslash should be preceded with a second backslash. So, \\test\builds$ should be added as \\\\test\\builds$. USERNAME: A text parameter that holds the user name to log on with. PASSWORD: A password parameter that holds the user's password. DOMAIN: A text parameter that holds the user's domain. LOCATION: A text parameter that holds the location of the RPM. RPM: A text parameter that holds the name of the RPM. 11. Schedule a regular Job with the Module on one of the Agents in your RES Automation Manager environment. When reviewing the parameters on the Job Parameters tab, adjust any values if necessary. 12. When the RES Automation Manager Agent for Linux has been installed, log on to the Linux machine and continue from step 5 of the Manual Installation procedure. See Manual Installation (on page 3). 4 Copyright RES Software

7 Chapter 3: Installation Example Copyright RES Software 5

8 Chapter 3: Installation 3.3 Other Options Tracing To start the Agent in trace mode, start resamad with option v 3. All trace information will be logged in the file /var/log/resamad.log Uninstallation To uninstall an RPM package on a Linux machine, type the following command: rpm ev res-am-agent<version of package> Upgrading To upgrade RES Automation Manager Agents for Linux to a newer version, please uninstall your current version first. This needs to be done manually on each Linux machine: 1. Stop the currently installed RES Automation Manager Agent for Linux by using the command /etc/init.d/resamad stop. 2. Uninstall the RES Automation Manager Agent for Linux. 3. Install the new version of the RES Automation Manager Agent for Linux. 4. Start the new RES Automation Manager Agent for Linux. 6 Copyright RES Software

9 Chapter 4: Next steps Chapter 4: Next steps After installing the RES Automation Manager Agent for Linux, it can be used to execute the following Tasks: Linux Command (Execute) Linux Resource (Download) Linux Computer (Reboot, Shutdown) In the Task library, you can find these Tasks at: Notes The Linux Tasks will only be available in the Console if your RES Automation Manager environment contains at least one RES Automation Manager Agent for Linux. With the Task Download Linux Resource it is only possible to download Resources that are stored in the Datastore. Resources stored on a fileshare or RES Automation Manager Resource Packages are not supported. Copyright RES Software 7

10 Chapter 5: Known Issues and Limitations Chapter 5: Known Issues and Limitations Dispatcher Discovery in the Global Settings of RES Automation Manager should be configured to Use Dispatcher address list if a firewall prevents sending multicast signals. Only the following Agent settings are supported: Dispatcher discovery Dispatcher location Dispatcher recovery: This is always set to Retry discovery. Protocol encryption Snapshot Intelligence is not supported for RES Automation Manager Agents for Linux. The following functions are @[GET-COMPUTERFUNCTION] The following Team rules are not supported: Computer Function Operating System > Suite Operating System > Type Scripts that you run on the RES Automation Manager Agent for Linux using the Task Execute Linux Command cannot include reboot and shutdown computer commands or shutdown or restart Agent commands. Use the Tasks Reboot Linux Computer or Shutdown Linux Computer instead. With the Task Download Linux Resource it is only possible to download Resources that are stored in the Datastore. Resources stored on a fileshare or RES Automation Manager Resource Packages are not supported. When a Resource is downloaded, parameters and functions can be parsed. Environment variables will not be replaced. Using the Prepare for Image functionality will bring the Agent daemon down and remove all Agent information from the Datastore. The configuration settings of the Agent will be preserved and only the GUID will be removed from the resamad.xml. This means that the Agent can be restarted with the same name, as long as it has another GUID. 8 Copyright RES Software

11 Chapter 6: Where to go from here? Chapter 6: Where to go from here? You can find information about the use and configuration of RES Automation Manager in the Help, which is available in the Console by pressing F1. RES Software Support Europe and Asia Monday - Friday 08:00 18:00 CET US and Canada Monday - Friday 08:00 18:00 EST Knowledge Base: Belgium Denmark France Germany Netherlands Norway Sweden UK All other countries (Toll Free) support@ressoftware.com Support can also be reached on (Toll Free) (Toll Free) (Toll Free) (Toll Free) +31 (0) (Toll Free) (Toll Free) (Toll Free) +44 (0) (0) Copyright RES Software 9

12 Disclaimer Whilst every care has been taken by RES Software to ensure that the information contained in this publication is correct and complete, it is possible that this is not the case. RES Software provides the publication "as is", without any warranty for its soundness, suitability for a different purpose or otherwise. RES Software is not liable for any damage which has occurred or may occur as a result of or in any respect related to the use of this publication. RES Software may change or terminate this publication at any time without further notice and shall not be responsible for any consequence(s) arising there from. Subject to this disclaimer, RES Software is not responsible for any contributions by third parties to this publication. Copyright Notice Copyright on software and all Materials Real Enterprise Solutions Development BV, P.O. Box 33, 5201 AA `s- Hertogenbosch, The Netherlands. RES and the RES Software Logo are either registered trademarks or service marks of Real Enterprise Solutions Nederland B.V. in Europe, the United States and other countries. RES Automation Manager, RES Workspace Manager, Dynamic Desktop Studio, Virtual Desktop Extender and RES VDX are trade names of Real Enterprise Solutions Nederland B.V. in Europe, the United States and other countries. All other product and company names mentioned may be trademarks and/or service marks of their respective owners. Real Enterprise Solutions Development BV, The Netherlands has the following patents: U.S. Pat. "US 7,433,962", "US 7,565,652", "US 7,725,527", other patents pending or granted. x