2.3. Installing and Configuring Enhanced Reporting

Subscription Asset Manager includes an optional reporting module which can pull in cross-organization (within Subscription Asset Manager) and even cross-subscription service (Subscription Asset Manager and Satellite 5.6) data to generate reports about subscription status on systems.
The reporting module requires additional packages to create a reporting database and a sync service.
When using enhanced reporting, there are some additional system requirements:
  • The crond service must be running.
  • An additional 4 GB of disk space must be available for the reporting database journal.
  • Additional packages
    • splice
    • ruby193-rubygem-splice_reports
    • spacewalk-splice-tool

Important

If enhanced reporting will be used with a Satellite 5.6 instance, the Subscription Asset Manager instance must be dedicated only as a reporting server for that Satellite 5.6 server. It cannot be used to manage other systems.
To install Subscription Asset Manager with enhanced reporting configured:
  1. Register the host system. Use the --auto-attach option to attach the required subscriptions for the operating system immediately. 
    [root@server ~]# subscription-manager register --auto-attach
Username: jsmith@example.com
Password:
  2. Wait several minutes for the updated content repositories to be added to the system configuration.
  3. Enable the rhel-6-server-sam-rpms repository.
    If the Enhanced Updates (EUS) repository is enabled, then disable it, either as part of the yum configuration (as in this example) or when running yum to install packages. There are conflicts in the Ruby packages between the EUS repository and the Subscription Asset Manager repository. 
    [root@server ~]# subscription-manager repos --enable rhel-6-server-sam-rpms --disable rhel-server-rhscl-6-eus-rpms
Loaded plugins: product-id, refresh-packagekit
========================= repo: rhel-6-server-sam-rpms =========================
[rhel-6-server-sam-rpms]
bandwidth = 0
base_persistdir = /var/lib/yum/repos/x86_64/6Server
baseurl = https://cdn.redhat.com/content/dist/rhel/server/6/6Server/x86_64/subscription-asset-manager/1/os
cache = 0
cachedir = /var/cache/yum/x86_64/6Server/rhel-6-server-sam-rpms
cost = 1000
enabled = 1
enablegroups = True
exclude =
failovermethod = priority
...
  4. Install Subscription Asset Manager and reporting packages: 
    [root@server ~]# yum install -y katello-headpin-all splice ruby193-rubygem-splice_reports spacewalk-splice-tool
  5. After installing the packages, run the Subscription Asset Manager configuration script, katello-configure.
    The required parameters for the basic installation are the deployment type, which is sam, and an administrator password.
    While not required, it is useful to specify an initial organization name for your deployment. If this is not set, then the first organization has a default name of ACME_Corporation.
    This sets up the Subscription Asset Manager instance with the default user and database settings. 
    [root@server ~]# katello-configure --deployment=sam --org=Example_Org --user-pass=admin
Starting Katello configuration
The top-level log file is [/var/log/katello/katello-configure-20130904-210539/main.log]
The Reports Menu Item

Figure 2.1. The Reports Menu Item

Using reports with Subscription Asset Manager is covered in Section 8.6, “Creating Subscription Asset Manager Usage Reports”. Using Subscription Asset Manager as a reporting server for Satellite 5.6 is covered in Section 8.7, “Using Subscription Asset Manager to Generate Satellite Usage Reports”.