Now that all of the necessary components are in place, you may use RHN Bootstrap to generate the required scripts. Log into your RHN Satellite Server or RHN Proxy Server as root and issue the rhn-bootstrap command followed by the desired options and values. If no options are included, a bootstrap.sh file is created in the bootstrap/ subdirectory that contains the essential values derived from the server, including hostname, the SSL certificate, it if exists, SSL and GPG settings, and a call for the client-config-overrides.txt file.
At a minimum, Red Hat strongly recommends your scripts also accommodate activation keys, GPG keys, and advanced configuration options in the following manner:
Use the --activation-keys option to include keys, taking into account the entitlement requirements identified in Section 5.1 Preparation.
Use the --gpg-key option to identify the key path and filename during script generation. Otherwise, use the --no-gpg option to turn off this verification on client systems. Red Hat recommends retaining this security measure.
Include the --allow-config-actions flag to enable remote configuration management on all client systems touched by the script. This feature is useful in reconfiguring multiple systems simultaneously.
Include the --allow-remote-commands flag to enable remote script use on all client systems. Like configuration management, this feature aids in reconfiguring multiple systems.
When you're done, your command will look something like this:
rhn-bootstrap --activation-keys KEY1,KEY2 \ --gpg-key /var/www/html/pub/MY_CORPORATE_PUBLIC_KEY \ --allow-config-actions \ --allow-remote-commands
Obviously, include the actual key names. Refer to Section 5.4 RHN Bootstrap Options for the complete list of options.