Before creating and managing channels, you should note the differences between the various tools and repositories at your disposal. This is especially important if you will be deploying both a RHN Satellite Server and RHN Proxy Server, as this increases the utilities and storage locations available. Further, a Proxy-Satellite combination offers certain best practices for optimal performance.
First, become familiar with these package management tools:
RHN Package Manager - This application is used to push custom packages into custom channels on an RHN Proxy Server.
RHN Push - This application is used to push custom packages into custom channels on an RHN Satellite Server.
RHN Satellite Synchronization Tool - This application is used to import and synchronize standard packages on an RHN Satellite Server with Red Hat Network. either via the Internet or CD-ROM.
Each of these tools has a corresponding package repository. Both the RHN Package Manager and the RHN Push require the creation of a temporary staging directory for placement of custom packages that will be uploaded to the Proxy or Satellite. The RHN Satellite Synchronization Tool may also necessitate a temporary directory to hold channel ISOs, if the Satellite is not synchronized over the Internet. All three of these repositories should be deleted after use. Red Hat recommends first archiving the custom packages used by RHN Package Manager and RHN Push.
Customers using both RHN Proxy Server and RHN Satellite Server should be using only the RHN Push (as well as the RHN Satellite Synchronization Tool for importing and syncing) because this combination requires custom packages and channels be uploaded to the Satellite only. From there, the Proxies will obtain the packages and distribute them to client systems.