Enabling the service-oriented architecture (SOA) model library

IBM® Rational® Asset Manager includes a small collection of asset types, categories, asset attributes, and relationships that represent the best practices for managing and developing business assets in a software-oriented architecture environment.

To enable the SOA model library, you must be a repository administrator.

You can use, modify, or duplicate the contents of the SOA best practices library however you want.

The SOA model library also allows you to activate a pre-configured collection of lifecycles that support service-oriented architecture workflow for assets. With the SOA lifecycles, you can also closely integrate the assets in a community with a connection to IBM WebSphere® Service Registry and Repository. For more information, see Creating the SOA lifecycles collection.

  1. On the Rational Asset Manager web client home page, log in with an account that has master administrative permissions for the repository.
  2. Open the Administration page.
  3. On the sidebar, click Libraries.
  4. Click Import Existing Library.
    The Import Library window opens.
  5. Select Select a built-in library, and then select SOA Model Library from the list.
    Note: If the SOA Model library is already enabled on the server, you will not be able to import it again. SOA Model Library will not be available in the list, and you can continue to the next lesson.

    If the SOA model library has been imported but not enabled, find SOA Model Library under the list of libraries, click the latest version number of the SOA Model library, and then click Enable

  6. On the page for the IBM SOA Model library, in the Library Actions sidebar click Enable.
  7. Confirm that the information in the SOA library does not conflict with existing assets or metadata on the repository or with assets and metadata that are controlled by other libraries, and click Enable.
    The assets, asset types, categories, asset attributes, and communities for the SOA library will be enabled on your repository.
  8. Click Administration to return to the list of communities on the repository.

After you activate the SOA model library, you will see the following new elements on your repository:

Communities:
  • Sample Application Development
  • Sample Open Source

These communities contain assets that demonstrate an environment to develop internal applications and services.

Assets

The communities contain assets that demonstrate how a web application for customer service called Customer Care Web Application updates from version 1.0 to 2.0 by incorporating a web service (Eligibility Service) that automatically verifies the eligibility of customers. The assets include releases and business cases for the applications, design documents, a case for change, and a Document of Understanding between the Eligibility Service and Customer Care Web Application.

The Eligibility Service uses an open source utility (log-4j) to create applications logs.

Asset types:
  • Business Case
  • Business Solutions
  • Common Component
  • Design
  • DoU (Document of Understanding)
  • Documentation
  • Implementation
  • Open Source Software
  • Release
  • Specification
  • Test Plan

The assets in the Sample Application Development and Sample Open Source community demonstrate how to use and relate these asset types.

The SOA model library also includes one asset type (ALE Configuration) that internally stores a mapping configuration file for connecting Rational Asset Manager to IBM WebSphere Service Registry and Repository.

Category Schemas:
  • Software Development

This category schema helps you further categorize and organize common asset types. It contains categories for programming languages, kinds of applications, licenses, and formats for documentation.

Relationship Types:
  • business case / business case for
  • consumer / consumer dou
  • design / design for
  • documentation / documentation for
  • implementation / implementation for
  • mediator / mediator for
  • provider / provider dou
  • release / release for
  • specification / specification for
  • test / test for

These relationships provide common ways to create further connections between the asset types in the repository.

Asset attributes:
  • Addressed Defects
  • Availability Date
  • Build ID
  • Business Owner
  • Certificate of Originality
  • Charter
  • Defects
  • End Date
  • End of Life
  • License URL
  • Line of Business
  • Manufacturer
  • Operations
  • Project URL
  • Quality Certificate
  • Release Plan
  • Requirements
  • Start Date
  • Support Contact
  • Target Namespace

These asset attributes describe the asset types with types of metadata that are frequently needed when developing software applications. You can inspect the included asset types and the sample assets to see how these are used and assigned.