Getting Started with
Contents
Chapter 1: Introduction 1
Chapter 2: Prerequisites and General Guidelines 2
Chapter 3: Installation 3
3.1 Manual Installation ... 3 3.2 Installation with RES Automation Manager ... 4 3.3 Other Options ... 6
Chapter 4: Next steps 7
Chapter 5: Known Issues and Limitations 8
Chapter 6: Where to go from here? 9
Chapter 1: Introduction
Copyright © 1998-2012 RES Software 1
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.
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 3163 -j ACCEPT iptables -A INPUT -m tcp -p tcp --dport 3163 -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 (http://winscp.net) or Tunnelier
(http://www.bitvise.com) to transfer the RPM file of the RES Automation Manager Agent for Linux from a Microsoft Windows share to the target Linux machine.
Chapter 3: Installation
Copyright © 1998-2012 RES Software 3
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-am-agent<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.
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
Chapter 3: Installation
Copyright © 1998-2012 RES Software 5
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.
Chapter 4: Next steps
Copyright © 1998-2012 RES Software 7
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.
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 not supported:
@[FILEVERSION(<filename>)] @[REGISTRY(<registry value>)] @[GET-ASSETTAG] @[GET-COMPUTERFUNCTION] @[GET-OS-SUITES] @[GET-OS-VERSION]
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.
Chapter 6: Where to go from here?
Copyright © 1998-2012 RES Software 9
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 Belgium Denmark France Germany Netherlands Norway Sweden UK
All other countries
0800-753-12 (Toll Free) 8088-6779 (Toll Free) 0800-911178 (Toll Free) 0800-182-7475 (Toll Free) +31 (0)73 622 8900 800-10-731 (Toll Free) 020-791-079 (Toll Free) 0-800-520-0427 (Toll Free) +44 (0) 845 838 5550 +31 (0)73 622 8900 US and Canada Monday - Friday 08:00 18:00 EST +1 800-580-0786 (Toll Free) E-mail: Knowledge Base: [email protected] http://support.ressoftware.com Support can also be reached on Twitter @res_support
