Creating the SOA lifecycles collection

If you have enabled the sample SOA best practices library, you can activate a preconfigured collection of lifecycles for your community that support a service-oriented architecture environment for asset development.

Before you begin

Before you can use the SOA lifecycles, a repository administrator must have enabled the SOA model library. For more information, see Enabling the service-oriented architecture (SOA) model library.

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

To configure the lifecycles to work with IBM WebSphere® Service Registry and Repository, you must have configured a connection to WebSphere Service Registry and Repository. For more information, see Connecting to WebSphere Service Registry and Repository.

Procedure

  1. Log in to the web application.
  2. Click Administration.
  3. Click the name of the community.
  4. Click Master Lifecycles.
  5. In the Lifecycles section, click Import SOA Lifecycle.
  6. Optional: Configure a connection to WebSphere Service Registry and Repository:
    1. In the Websphere Service Registry and Repository Configuration section, select Configure policies with lifecycles to work with Websphere Service Registry and Repository.
    2. In the Connection list, select the WebSphere Service Registry and Repository connection to use. If you have not configured a connection, click New Connection. For more information about configuring a connection to WebSphere Service Registry and Repository, see Connecting to WebSphere Service Registry and Repository. This will apply the included ALE policy to every action such as Entrance to State to every state in the lifecycles. For more information on the ALE policy, see Policies for lifecycles.
  7. Click OK.

Results

The SOA lifecycle collection will create and configure six lifecycles:
  • Business Solution: A workflow to identify, propose, and revise charters for new assets of the Business Solution type.
  • Release: A one-way workflow for assets of the Release asset type.
  • Specification: A workflow for assets of the Specification asset type, with policies to require .wsdl and .xsd artifacts.
  • Business Case: A workflow for assets of the Business Case asset type to review the merits for starting a project.
  • Implementation: A workflow for assets of the Implementation asset type to realize or execute projects, designs, or standards.
  • Document of Understanding (DoU): A workflow for assets of the DoU asset type for agreements between providers and consumers.

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


Feedback