Creating the OSGi lifecycle

If you enabled the Open Services Gateway initiative (OSGi) model library, you can activate a preconfigured lifecycle for your community. The lifecycle enables support for generating attributes, package and service assets and their relationships with the bundle asset.

Before you begin

Before you can use the OSGi lifecycle, a repository administrator must enable the OSGi model library. For more information, see Enabling the OSGi model library.

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

Products can integrate with Rational Asset Manager by using the OSGi bundle repository. Products must use the following URL: http://hostname:port/context-root/BundleRepository. This URL is the OSGi bundle repository (OBR). For more information, see OSGi Bundle Repository (OBR).

Procedure

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

What to do next

You can modify the OSGi 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 OSGiBundle assets in the community, follow these guidelines:
  • Submit one asset per bundle and include a .jar file with a manifest.mf file.
  • Enter a name, version, and short description in the asset. These values are overwritten with the values that are specified the manifest file.
  • When you submit the bundle, prevent the web client from extracting the content of the .jar file. In the Expand Compressed File window, click More options, select Upload, and click No.

Feedback