You can deploy software on Linux-based machines using .rpm files.
1. Click Distribution > Managed Installations.
The Managed Installations page appears.
2. In the Choose Action menu, click Add New Item.
The Managed Installation: Edit Detail page appears.
3. Select the software from the Software drop-down list.
You can filter the list by entering any filter options.
4. By default, the appliance agent attempts to install the .rpm file using the following command. In general, this is sufficient to install a new package or update an existing one to a new version:
rpm -U packagename.rpm
If you have selected a .zip/.tgz/tar.gz file, the content is unpacked, and the root directory searched for all .rpm files. The installation command is run against each of these files. The appliance finds all rpm files at the top level of an archive automatically, so you can install more than one package at a time. You can also create an archive containing a shell script and then specify that script name as the full command. The appliance runs that command if it is found, and logs an error if is not.
To change the default parameters, you have to specify this in the Run Parameters field. You can specify wildcards in the filenames you use. If the filename contains spaces, enclose it in single or double quotation marks. The files are extracted into a directory in /tmp and it becomes the current working directory of the command.
To perform these steps, be sure to select your organization from the Organization drop-down list in the top-right hand corner of the page.
On Red Hat Linux, you do not need to include any other files in your archive other than your script if that is all you want to execute.
8 Distributing Software from Your K1000 Management Appliance
If the PATH environment variable of your root account does not include the current working directory, and you want to execute a shell script or other executable that you have included inside an archive, specify the relative path to the executable in the Full Command Line field. The command is executed inside a directory alongside the files that have been extracted.
For example, to run a shell script called installThis.sh, package it alongside an .rpm file, and then enter the command: ./installThis.sh in the Installation Command field. If you archived it inside another directory, the Installation Command field is:
./dir/filename.sh
Both these examples, as well as some other K1000 Management Appliance functions, assume that “sh” is in the root's PATH. If you're using another scripting language, you may need to specify the full path to the command processor you want to run in the Installation Command, like
/bin/sh ./filename.sh
Include appropriate arguments for an unattended, batch script.
If you select the uninstall check box in the MI detail, the agent runs the following command on either your standalone rpm file or each rpm file it finds in the archive, removing the packages automatically:
//usr/sbin/rpm -e packagename.rpm
Removing software in this way is performed only if the archive or package is downloaded to the node. If you select the Uninstall Using Full Command Line check box, specify a full command line in the Installation Command field to ensure the correct removal command is run on the correct package. Because no package is downloaded in this case, specify the path in the installation database where the package receipt is stored.
5. If your package requires additional options, you can enter the following installation details:
Run Parameters (Optional) You do not need to specify parameters if you have an .rpm file.
Enter a value to override (Default -U default).
For example, if you set Run Parameters to: -ivh --replacepkgs, then the command that runs on the computer is:
rpm -ivh –replacepkgs package.rpm
Installation Command You do not need to specify a full command line if you have an .rpm file.
The appliance executes the installation command by itself. The Linux node tries to install this via: rpm [-U | Run Parameters]
"packagename.tgz”
If you do not want to use the default command, you can replace it completely by specifying the complete command line here. If you have specified an archive file, this command is run against all of the .rpm files it can find.
Distributing Software from Your K1000 Management Appliance 8
6. Specify the deployment details:
7. Set user interaction details:
Un-Install using Full Command Line
Click the check box to uninstall software.
If a Full Command Line above is entered, it is run. Otherwise, by default the agent attempts to run the command, which is generally expected to remove the package.
Run Command Only Click the check box to run the command line only. This does not download the actual digital asset.
Notes (Optional) Enter additional information in this field.
Managed Action Managed Action allows you to select the most appropriate time for this package to be deployed. Execute anytime (next available) and Disabled are the only options available for Linux platform.
Deploy to All Machines Click the check box to deploy to all the machines.
Limit Deployment To Selected Labels
Select a label to limit deployment only to machines belonging to the selected label. Press CTRL to select multiple labels.
If you have selected a label that has a replication share or an alternate download location, then the appliance copies digital assets from that replication share or alternate download location instead of downloading them directly from appliance.
Note: The appliance always uses a replication share in preference over an alternate location.
Limit Deployment To Listed Machines
You can limit deployment to one or more machines. Select the machines from the drop-down list to add to the list. You can filter the list by entering filter options.
Deploy Order The order in which software is installed. The lower value deploys first.
Max Attempts Enter the maximum number of attempts, between 0 and 99, to indicate the number of times the K1000 Management Appliance tries to install the package. If you specify 0, the appliance enforces the installation forever.
Deployment
Window(24H clock)
Specify the time (using a 24-hour clock) to deploy the package. The Deployment Window times affects any of the Managed Action options.
Also, the run intervals defined in the System Console, under K1000 Settings for this specific organization, override and/or interact with the deployment window of a specific package.
Allow Snooze This option is not available for Linux platform.
Custom Pre-Install Message
This option is not available for Linux platform.
Custom Post-Install Message
This option is not available for Linux platform.
Delete Downloaded Files Select this check box to delete the package files after installation.
8 Distributing Software from Your K1000 Management Appliance
8. Click Save.