Creating the Red Hat Package Management lifecycle

If you enabled the Red Hat Package Management (RPM) library, you can activate a preconfigured lifecycle for your community. The lifecycle enables the support for generating attributes and their relationships with the package asset.

Before you begin

Before you can use the RPM lifecycle, a repository administrator must enable the RPM model library. For more information, see Enabling the Red Hat Package Management library.

To import and manage the lifecycle, you must be a repository or a community administrator.

The yum client can integrate with Rational Asset Manager by using the RPM package repository. The yum client is installed by default on typical Linux operating systems. Products must use the following URL: http://hostname:port/context-root/yum. This URL is the RPM package repository URL.

Procedure

  1. Log in to the web application.
  2. Click Administration.
  3. Create a community to store the RPM packages.
  4. Click the Lifecycles tab. In the Lifecycles section, click Import RPM Lifecycle.
  5. Click Roles and specify the community user roles to manage which users can search for, view, and download package assets. The packages that are visible are based on a user's role. To ensure package assets are visible and to allow users to download packages, users must be able to search and download assets. You can use the Asset Consumer role. To allow anonymous users to have search and download capabilities, you can assign the Asset Consumer role to All Users.
  6. Click OK. The RPM lifecycle is created and configured for the RPM asset types.

What to do next

You can modify the RPM lifecycle to align with the processes of your community or organization. For more information about configuring custom lifecycles, see Creating master lifecycles.

When you submit RPM Package assets in the community, submit only one file for each asset.


Feedback