Appendix B. RHN API Access
200
follows the "=" symbol, as part of a string that resembles the following: "details.pxt?sgid=334958".
Note that the member parameter within the
set_group_membership
method requires only
yes
or
no
as input to make the association.
B.6. Channel Labels
The architecture of a channel is not always clear from the channel label. Below is a list that shows the
correspondence between channel labels and the official title of the architecture they serve.
Channel Label
Platform
channel-i386-sun-solaris
i386 Solaris
channel-ia32
IA-32
channel-ia64
IA-64
channel-sparc
Sparc
channel-alpha
Alpha
channel-s390
IBM S/390
channel-s390x
IBM System z
channel-iSeries
IBM eServer System i
channel-pSeries
IBM eServer System p
channel-x86_64
AMD64 and Intel EM64T
channel-ppc
PPC
channel-sparc-sun-solaris
Sparc Solaris
Table B.1. Channel Labels
This is particularly necessary to know for the channel.software.create method.
B.7. Sample API Script
The following sample script depicts how to construct an RHN API client. Review the comments and
links for a full discussion of the calls made.
#!/usr/bin/perl -w
use strict;
use Frontier::Client;
use Data::Dumper;
############################################################################
# This is a sample script for use of the experimental RHN Management
APIs. #
# The API is currently available using XMLRPC only, which is described in
#
# depth at:
#
#
#
# http://www.xmlrpc.com/
#
Summary of Contents for NETWORK SATELLITE 5.2 - CHANNEL MANAGEMENT
Page 1: ...Red Hat Network Satellite 5 2 Reference Guide Red Hat Network Satellite ...
Page 10: ...x ...
Page 30: ...Chapter 2 Red Hat Update Agent 18 Figure 2 11 Available Package Updates ...
Page 46: ...34 ...
Page 68: ...56 ...
Page 162: ...150 ...
Page 174: ...162 ...
Page 186: ...174 ...
Page 259: ...247 Appendix D Revision History Revision History Revision 1 0 ...
Page 260: ...248 ...
Page 268: ...256 ...