prev 2014. 11 next
1
2 3 4 5 6 7 8
9 10 11 12 13 14 15
16 17 18 19 20 21 22
23 24 25 26 27 28 29
30
 
 

포인트 랭킹 Top 9

  • 1위. 김동영b
    23523점
  • 2위. 아름프로
    6846점
  • 3위. netfer
    1289점
  • 4위. 심플
    829점
  • 5위. 정의의소
    813점
  • 6위. 바이스
    627점
  • 7위. 달마다
    590점
  • 8위. 코디
    577점
  • 9위. 데로드
    448점

counter
 
 
 
   
  
 

Rational solution for Collaborative Lifecycle Management 2012 Deployment Guide

Overview

This guide provides a roadmap to assist you with your deployment of Rational Collaborative Lifecycle Management (CLM) 2012. It is intended to help you navigate to pertinent documentation on Jazz.net, the Infocenter, and other resources that are essential for successfully deploying a new CLM 2012 solution or upgrading to CLM 2012 from a current installed base. It will also answer questions that typically arise during a deployment scenario with pointers to additional information should the reader require it.  As this guide is not intended to replace existing documentation available elsewhere you will note the heavy use of links to tutorials, articles, videos, and product documentation created by multiple contributors from across the Jazz development organization.

The intended deployment scenario should guide you through the material below. If you are not familiar with CLM basics, you should start with the first section Introduction to CLM. If you are already familiar with CLM, and will be installing CLM for the first time, then proceed with New CLM 2012 Installation. If you are upgrading an existing deployment to CLM 2012, then then you should read Upgrade to CLM 2012.

Disclaimer: This guide is an evolving document and incremental improvements will be published on a regular basis. For additional information about the topic presented in this article add your comments or questions directly in the discussion part, or visit the Jazz.net Forum.

Finding information

The following table lists some good sources for information with a brief description of each and links to RSS feeds where appropriate:

Useful Links
Description
Jazz.net library

Jazz Library RSS feed

The jazz.net library contains articles, videos, tips, documentation, and more. All library items have tags associated with them to help you find what you are looking for. For example the tag SCM will get you all the source control topics.
 Jazz Team Blog and  Planet Jazz  on jazz.net

Jazz Team Blog RSS feed

Go to the Jazz Team blog for bogs from the Jazz development team.  Planet Jazz is a new page on jazz.net that aggregates blogs from the broader community of experts, users, and fans of Jazz and related technologies.
 Jazz.net Forum

Jazz Forum RSS feed
The forum allows your to ask questions, get answers from the Jazz experts and post your own answers.
CLM 4.0 Infocenter
Information centers provide a powerful online interface for finding technical information on a particular product, offering, or product solution.

For the latest news, blogs, and tidbits about Jazz from around the Web, you may want to subscribe to the  Jazz Community News RSS feed.

As well, several sections within this article contain links to additional material under "Further Reading" and "Advanced Topics" to facilitate more in-depth study. 


Table of Contents

Introduction to CLM

This section answers the question:

     What are the basics I need to know before I get started with deploying and configuring CLM?

This section briefly explains the basics and provides you with links to more in-depth information and useful tutorials. 

If you would like to experiment with some of the features and capabilities of Rational's solution for Collaborative Lifecycle Management (CLM) and the Jazz platform, you can  create a CLM sandbox. This is a temporary, hosted environment, where you can create your own sandbox project and explore and evaluate the capabilities of RTC, RQM and RRC.

What is CLM?

CLM stands for Collaborative Lifecycle Management.  It is an integrated solution for effective Application Lifecycle Management (ALM). Essentially, it provides integrations between the three core processes at the foundation of an organization's Software Development Lifecycle (SDLC):

  • Change and Configuration Management (CCM)
  • Quality Management (QM)
  • Requirements Management (RM)

CCM, QM, and RM are applications that provide capabilities accessible by product licenses. They are not products - you cannot purchase QM for example, but you can purchase RQM which gives you capabilities that are drawn from all three applications. Building products from applications is a good reference that explains the difference between applications and products.

CLM comprises three products - Rational Team Concert (RTC) , Rational Quality Manager (RQM), and Rational Requirements Composer (RRC) - that provide the capabilities needed by developers, quality professionals, and requirements analysts, respectively. One or more role-based license keys for each product permit access to capabilities provided by deployed applications.  More information on roles and licensing is provided later in this document in the section Roles and Licensing in CLM. For an overview of CLM 2012, refer to Overview of the CLM solution in the Infocenter.

The products in CLM 2012 are Rational Team Concert 4.0, Rational Quality Manager 4.0 and Rational Requirements Composer 4.0.

With the exception of the RM application, which uses the Jazz Team Server repository for persisting data, each of the applications has its own data store. The cross-product integrations in CLM support traceability, web-like navigation, review, commenting, and status tracking across project repositories with the intent to better coordinate the flow of people, processes and information. As an example, a developer can link an enhancement created in CCM to requirements that were created by an analyst in RM. Additionally, a tester may link one or more test cases created in QM to the same requirements in RM as well as the enhancement in CCM. For readers new to CLM, the Money that Matters lifecycle scenario in the Infocenter is a excellent tutorial for exploring these capabilities (here is a welcome page for the scenario).

Components of CLM 

1. Jazz Team Server

The Jazz Team Server (JTS) is a separately deployed web application that provides common services to enable applications to work together.  Services include user and project administration, security, collaboration, query, presentation, process and other generic cross-tool capabilities. An installed instance of an application is affiliated with an installed instance of a JTS by registering it as a Jazz Team Server Extension. Application integration is enabled when multiple applications share the same JTS. Note: While a single JTS can support multiple instances of Jazz applications such as CCM, and QM, only one instance of RM is permitted.

Further Reading:

Advanced Topics:
  • If you want to see how OSLC works, you can do a hands-on workshop called the OSLC Workshop.
  • If you want to learn how to extend the capabilities of Jazz, you can do a hands-on workshop called the RTC Extensions Workshop.

2. Jazz Applications

We discussed applications in What is CLM above. A Jazz application is any application that is deployed to provide some type of service within a family of Jazz tools and is registered as an extension to JTS.

3. Reporting 

CLM 2012 offers two main reporting capabilities:
  • Development Intelligence Reports are used to communicate status, monitor progress, diagnose problems, identify corrective actions, etc. for the purpose of managing projects and programs. A pie chart that shows defects categorized by customer or a graph depicting test case execution over time are examples of this report type.

    CLM ships with a set of predefined reports where you can set runtime parameters for your specific need. However, in order to author new reports or customize existing reports Rational Reporting for Development Intelligence (RRDI) is required.

  • Document-style Reports typically constitute a deliverable used in subsequent phases of a project. An example is a requirements specification which is a compilation of requirements into document format that can be circulated for review and approval.

    RRC, RTC, and RQM users can generate and view document style reports but the ability to author new report templates requires that Rational Publishing Engine (RPE) be installed. 

Rational Insight is required if you want to include data from multiple JTS deployments, other Rational applications, and third party tools, or if you need to customize the underlying reporting data warehouse and schema. Note that CLM 2012 requires Insight 1.1.1 or later.

Further Reading:

Advanced Topics:

Roles and Licensing in CLM

A license (also known as a Client Access License or CAL)  is associated with products - RQM Quality Professional, RTC Developer, or RRC Analyst. These licenses are installed in the JTS and then assigned to the user. Based on the license assigned, the user has access to certain capabilities.

A license (also known as a Client Access License or CAL) permits access to capabilities provided by an application. Role-based licenses are associated with products. For example, the CCM, QM, and RM applications each have an author-class license that permits full read-write access to their capabilities and typically only read access to capabilities provided by other applications. The three author licenses for CLM 2012 are RTC Developer, RQM Quality Professional, and RRC Analyst.  Licenses are installed in the JTS and then assigned to a user ID.  A user ID may have more than one license assigned to it and any user using that user ID will have access to the union of capabilities provided by all the assigned licenses.

Most licenses are available as different types. For example, Authorized User licenses are permanently assigned to a single user ID until they are explicitly reassigned. Floating User licenses are acquired dynamically from a license server when an operation is attempted and released after an inactivity timeout or explicit logout. Token licenses are acquired in a similar manner to Floating User licenses but each license has a token cost and the token pool is managed by a Rational License Server.


Further Reading:


New CLM 2012 Installation

Planning the Installation

The process for a new installation is relatively straight forward and has been made easier with the use of the InteractiveInstallation Guide.  Before you get started, you should get familiar with the CLM installation process by reviewing the installlation process example.

It is important to note that CLM is an integrated installation - one download contains all 3 applications and the JTS.  During install you can select what to install so that you have the flexibility to install all applications on one application server or you can choose to spread the applications across systems. 

Supported Topologies

There are 3 basic topologies - for details see Topology examples.
  • Evaluation Topology  - A single server install used for evaluation purposes only and then discarded.  If you are planning to create production level artifacts you should start with either a departmental or enterprise topology.
  • Departmental Topology  - This is a good production topology for a group or department when there may be limited hardware resources, or the projects and teams are relatively small in scope and size and unlikely to expand significantly.
  • Enterprise Topology  - Suitable for medium- to large-sized teams, this is a distributed deployment of Jazz applications meant to scale to support an Enterprise.

The article  Standard Collaborative Lifecycle Management Topologies on jazz.net details standard topologies to assist you with planning your deployment.

Single Sign-On

Single sign-on (SSO) allows users to sign on once to gain access to all servers without having to re-authenticate for each server.  Although Tomcat supports SSO, it limits SSO to applications that are installed on a single server.  WebSphere Application Server is more flexible where SSO can be configured in a distributed environment.    The Infocenter article  deploying with single sign-on provides steps for each of the supported application servers.  Here is a tip for deploying SSO on WAS.

Clustering


Clustering is a new feature for CLM 2012 that provides high availability (HA) support with automatic fail-over and load balancing. One of the goals of the clustering development effort was to deliver High-Availability while not impacting performance. Testing has shown that a cluster of three nodes will deliver the equivalent performance of an un-clustered configuration. At this time, clustering is only supported on AIX and non-virtualized Linux systems.

To enable clustering, you must request a "Clustering Feature Key File" from IBM Support. Refer to Setting up a clustered environment for instructions.

The CLM 2012 clustered solution relies on the following components:

  • WebSphere eXtreme Scale, which is bundled with CLM 2012.
  • WebSphere Application Server Network Deployment (ND), which requires a separate license.

A Reverse proxy should  be used in a clustered topology.  More specifically it is recommended that two instances of IBM HTTP Server be used as the reverse proxy solution for a 3 node cluster. 

If you have more than one cluster, you will also need two load balancers (primary and backup) to manage the load.

Database failover is supported by the database software. CLM in a clustered or non-clustered environment works with database failover.


Further Reading:

Server Rename

Server Rename, new in CLM 2012, can be useful where you want to prepare a test staging environment using production data or when moving a pilot deployment into production.  See supported scenarios for details. It allows you to update the Scheme/Protocol, Host name, Port, and Context Root components of the URI. Server rename is complex, potentially disruptive, and should only be used as a last resort when other approaches to reconfiguring your topology are unworkable. Often the use of DNS aliases or a reverse proxy can accomplish your goals. To enable server rename you must obtain a feature key file from IBM Software Support. It is called a "Server Rename Feature Key File".

Renaming the application server may require that you update the port number  on the application server. There are additional steps for changing the context root.

Before proceeding you need to plan for server rename and review risks and limitations. The following links provide the step-by-step procedure for each of the supported scenarios:


 

URI Planning

Choosing a public URI for long-term stability is very important as the applications and JTS generate absolute URIs to resources that are used for stable resource identification across all applications. In many cases the URIs are persisted in the repository databases and stored resources may contain links between them as well as to resources in other applications. Once resources have been stored in the repository, changing the URI will have serious consequences.

The absolute URI is rooted by a public URI that is declared for the applications and JTS.
Therefore it is imperative that you choose a public URI that is fully qualified, likely to remain stable over time, and is accessible from anywhere in the network where users need to connect. Here are some additional considerations:

  • Use hostnames that can be resolved via DNS (NEVER USE  'localhost' or an IP address).
  • Moving a Jazz application from one server to another (even one with a different IP address) will maintain any links to the data in the repository as long as the domain name remains unchanged and is mapped to the new IP address.
  • You must specify a context root for web applications that are deployed within the application server. The context root appears immediately after the host and port segment of the URL. Default context roots are listed below:
    /jts		-- the Jazz Team Server
    /ccm -- Change and Configuration Management capability (provided by RTC)
    /qm -- Quality Management capability (provided by RQM)
    /rm -- Requirements Management capability (provided by RRC)
    /admin -- Jazz Project Administration capability
    /clmhelp -- Help resources
    Example:  for a server named jazz_ccm.demo.test, with the /ccm capability running on it, the base URI for the CCM resource would be https://jazz_ccm.demo.test:9443/ccm.

  • When planning a new installation, if you do not want to use the default port numbers (9443) for the application servers you can change them.  Changing the port numbers for the application server explains how.
  • Consider using a reverse proxy or DNS aliases (see the next section)

Reverse Proxy and DNS Alias

Using a reverse proxy or DNS aliases will help ensure you have the flexibility to update your topology in the future.

  • A reverse proxy is a type of proxy server that retrieves resources on behalf of a client from the application servers sitting 'behind' the reverse proxy server.  For more information see  Using a reverse proxy in your topology and a recent blog with additional links to articles explaining reverse proxy servers and how to configure them.  Here are  instructions for configuring the IBM HTTP server as a reverse proxy for IBM Websphere Application Server.
  • Another option is to use a DNS alias for each application in your topology so that the public URI can remain stable in the event you need to change the configuration. 


Further Reading
:

Client / Server Compatibility

In release 4.0, client N-1 compatibility is supported, which means that you can upgrade a server to the next release without the need to upgrade the clients. This backward compatibility applies to the following clients and is illustrated in the table below:

  • Client for Eclipse IDE
  • Client for Microsoft Visual Studio IDE
  • SCM command line
  • ISPF client
Eclipse & Visual
Studio Client
Jazz Team Server
4.0      
3.0.1.x
3.0      ,
2.x     
4.0
y
n
n
n
3.0.1
y
y
n
n
3.0
y
y
y
n
2.x
n
n
n
y

When a server/client mismatch occurs, a friendly dialog explains the version mismatch. An option is available for customizing the message to direct users to the location where they can download new clients. How to do this is explained in this article on jazz.net (in the article, search for the string 'Set the client version mismatch messages').


As per the above table, RTC users who require access to both v3.x and v4.0 servers must use a v3.x RTC Eclipse client.  If users need to access both v2.x and v3.x (or v4.0) servers they must use separate RTC Eclipse clients for each since no single client will work with both servers.


Notes:

  1. RTC 4.0 eclipse client can run in Eclipse 3.6 and 3.7 (3.6.2.2 is bundled) and supports shell sharing. 
  2. RTC repository workspace compatible from v2.x or v3.x to v4.0 client.
  3. RQM and RRC 4.0 clients are web-browser based.  There is no Eclipse client for these products.
  4. CLM 4.0 Server Rename feature: you must upgrade all RTC clients (including build engines) to version 4.0 prior to the rename.

Performing  the Installation

For an understanding of the key concepts that are involved in performing the installation, refer to Understanding the deployment and installation process.

For a new CLM installation you will perform the following:

Preparing the Installation

Before starting:
  • Be sure to have properly selected your URI's for your Jazz capabilities.  See URI Planning for more information.
  • Read the release notes available on the product downloads pages.
  • Verify that the system requirements are met.
  • Decide on the user registry to be used.  Your options will depend on the application server you are using.  Tomcat has a default user registry whereas WebSphere offers a range of possible configurations for user registry as described in Selecting a registry or repository.  Both application servers can be configured to use LDAP.  Refer to setting up user management for details.
  • Decide on the database vendor to be used and review the installation instructions in Setting up the database.  Instructions  are provided for DB2, Oracle, and SQL server.  
For an enterprise deployment you will need to install a database server and configure a database for each of the following:
    • Data warehouse database (optional)
    • Jazz Team Server database
    • CCM database (if the CCM application will be installed)
    • QM database (if the QM application will be installed)
    • RRDI content store (if RRDI is installed)

Note: RM does not require its own database as it uses the JTS database.
  • If installing RRDI, make sure that the RRDI application is installed on a separate server instance. This will ensure that heavy reporting loads on the system do not impact the performance of the CLM tools. 
  • Review the Sizing guides to assist you with maximizing system performance. Also review factors that can affect performance.
  • Have your instructions handy. It is strongly recommended that you use the Interactive Installation Guide available from the Infocenter as it compiles installation instructions specific to your scenario.
    • New for CLM 2012:  If you are using Websphere Application Server, you now have the option to configure a cluster of app servers. 
    • If you need to be able to author new reports or customize existing reports be sure to select 'yes' to install Rational Reporting for Development Intelligence.

If you want to install the product as a non-root user on UNIX systems or as a non-administrator on Windows, in the Select user mode for Installation Manager, select Non-Administrator.

Use the Interactive Installation Guide

The Interactive Installation Guide takes you through the following main steps:

  • Planning checklist
  • Installing the server using IBM Installation Manager - you have 2 options - a web based install or a local install.
     
  • Install and configure databases. You can use Derby which is included with the installer but its use should be limited to trial and demo deployments.  And note that RRDI does not support Derby - although you can configure a data warehouse on Derby, you will not be able to migrate your data to another database vendor. 

    For any other deployment, instructions are provided for DB2, Oracle, and SQL Server.  
  • Install, set up, and start the Application Server(s) - Tomcat Application Server v7.0 comes with the installation but if you are planning to use Websphere Application Server then you should not install Tomcat. During installation, you will be asked to provide the directory where the webbapps are to be placed (the default location is JazzInstallDir/server/webapps). Later in the install process you will deploy these web apps to the application server.

  • If you selected to install Tomcat v7.0 you are good to go.  To start the server(s) refer to Starting the Apache Tomcat Server. Websphere Application Server (WAS) is a separate install -  you can set up WAS using the  Integrated Solutions Console or using Jython scripting. Depending on your desired topology, you may be installing one or more application servers (eg. one app server for each of JTS, CCM, QM, RM).

  • WAS includes some addition steps to configure the server to use LDAP (this is optional) and to deploy the web applications and start the server. In addition to the web archives for JTS, CCM, QM, and RM, you will also be deploying web archives for the following applications:
    • Lifecycle Project Administration (LPA) - admin.war
    • Information Center (IC) - clmhelp.war
    • RM view mode version of the graphical artifacts - converter.war

  • Install the RTC client for Eclipse IDE. Refer to Install the Eclipse Client later in this article.
  • If you selected to install RRDI, the installation package consists of Rational Report Server and optional sample reports (the samples are not related to CLM data). Review the planning checklist, installation requirements, and deployment scenarios- for a departmental or enterprise deployment, RRDI is installed on a separate application server with its content store created on the database server. The installation procedure is described in installing RRDI.
  • Now that the servers are started run the setup wizard as described next.

Run the Setup Wizard

The Setup Wizard walks you through some final configuration steps to connect the applications and database to JTS v4.0.  The Setup Wizard helps you to:

  • Configure the public URI
  • Configure database connections
  • Configure email settings
  • Register applications
  • Configure the user registry
  • Configure the data warehouse
  • Finalize Setup for each application

After ensuring the application server(s) have been started launch the wizard.  In a browser window type:

    [fully qualified hostname]:[port number]/jts/setup

The default port number for the application servers is 9443. It is recommended that each of the application servers and applications have their own unique port numbers. This makes it easier to debug any potential performance issues and allows for implementation of a reverse proxy server at a later time. You can change the port number by referring to the following procedure: Changing the port number for the application server. You should also select a unique context root.   Note that you should change the port number and context root before setting the public URI for your applications. 

The JTS, along with the applications registered to the JTS, is called an application group. In a single server configuration, the applications that need to be registered are found automatically. In a distributed system, where the applications are installed on different machines from the JTS  (we call these 'remote' applications), registering the applications with the JTS can be done when you initially set up your CLM environment by running the setup wizard for enterprise deployments or you can run the setup on the command-line.

If you have an existing Jazz CLM environment, and you are adding a new server and/or capability, then you will need to register the new application with the JTS by following to these instructions.

Install and configure the build system

The Jazz Build System Toolkit contains the Jazz Build Engine (JBE) and a toolkit of Ant tasks that processes manual and scheduled build requests, executes builds, and publishes logs. You can use any build engine to run Jazz Team Builds (such as the Build Forge build engine).  For details on variations refer to Jazz Team Build setup variations.

The Build System Toolkit can be be installed using the IBM Installation Manager  or it can be installed from a .zip file. If you will be using the Build Forge build engine, refer to Installing the Rational Build Agent

For an overview of the steps involved in setting up and running a typical Jazz Team Build, refer to A typical Jazz Team Build setup. The detailed procedure for performing the build tasks can be done using the Eclipse client or using the Web client. If you intend to use the Eclipse client, refer to Install the Eclipse Client below.

Further Reading:

Install and configure a license server

If you plan to use floating CALs or Token services for your licensing scheme then you will need to install and configure a license server.

Floating CALs are managed as a pool that are shared by multiple users who acquire a license when they need it and return it to the pool when they are done. You can either have a dedicated JTS that serves floating CALs or you can use an existing JTS. See Installing and managing floating client access license keys for instructions on configuring a floating license server and to point other jazz team servers to the license server.

A floating CAL server can also distribute Rational Common Licensing (RCL) tokens. Jazz services have a predetermined 'token cost' associated with them and when a user invokes the service, the required number of tokens are checked out from the license server. Token services requires an additional license server called the IBM Rational License Key Server. Please refer to the RCL information center for installation instructions.

For more information on Jazz Licensing and some background on how it works, check out the CLM 2011 Licensing Article.  Some of it may be out of date, but the core concepts hold true.

Install and configure RPE

Refer to the Rational Publishing Engine 1.1.2.2 Infocenter for instructions on Installing RPE and integrating CLM data sources (integrating RTCintegrating RQM, and  integrating RRC) with RPE.

Install the Eclipse Client

There are three ways to install the client. Refer to Client Installation Overview for details.


Upgrade to CLM 2012

Before proceeding: If you have Insight in your current deployment, you should wait for Insight version 1.1.1 before proceeding with the upgrade to CLM 2012. If you are upgrading from CLM 2010, you can proceed with the first step (upgrade to CLM 2011) and then hold off until Insight 1.1.1 is available.

Also, note that if you have RRDI in your current deployment, you will need to upgrade to RRDI 2.0 before upgrading to CLM 2012.

CLM 2012 is backward compatible with the 3.0.x clients and servers providing you with more flexibility in planning and executing your upgrade. You can execute the upgrade in stages, say by starting with the JTS and one application, such as CCM, and upgrading those applications first. Then, at a later time you can  upgrade the remaining applications as well as the Eclipse and Visual Studio clients. 

Although a mixed 3.x and 4.0 environment is supported, for compatibility with JTS 4.0 you will need RQM 3.0.1.3 and RRC 3.0.1.4.

If you are upgrading from CLM 2010, you will need to perform a 2-step upgrade process by first upgrading to CLM 2011 and then finally to CLM 2012.

Two-Step Upgrade from CLM 2010 to CLM 2012

Upgrading from CLM 2010 to CLM 2012 is a 2-step process:
  1. Upgrade from CLM 2010 to CLM 2011:  refer to Understanding the deployment and upgrade process in the 3.0.1 Information Center. As well, review the  Upgrade process examples and Upgrade topolgy example and then use the Interactive upgrade guide to perform the upgrade to CLM 2011. Note all these links are on the 3.0.1 Information Center. For a summary of the tasks you should complete in preparation for the upgrade, read the article  Upgrade reference for CLM 2011. The CLM 2011 Upgrade Workshop provides a hands-on walk through of the CLM 2011 upgrade process.  The CLM 2011 Upgrade FAQ is also a great source of information.

  2. Upgrade from CLM 2011 to CLM 2012 - see the next section below.
If the upgrade is planned such that step 2 is to be done at a later time, the eclipse and visual studio clients should be upgraded to be compatible with the 3.0.1 server at the same time step1 is done. If it is acceptable that the client upgrades can wait until the upgrade is complete, it would be wise to inform users that only the web client should be used in the interim.  Here are instructions for upgrading the clients to v3.x.

Upgrade from CLM 2011 to CLM 2012

For an understanding of the key concepts that are involved in performing an upgrade, refer to Understanding the deployment and upgrade process. You should also review Deployment and upgrade considerations, Upgrade process example, Upgrade topology example, and the CLM 2012 Upgrade Guide

A CLM 2011 to CLM 2012 upgrade requires a full installation of CLM 2012  followed by an upgrade script (one for each application) which migrates and updates configuration files, adds tables to the various database repositories in place, and upgrades the data warehouse. The upgrade should be staged with the JTS being upgraded first, followed by the applications, which can be done in any order. Use the interactive guide, Upgrading to version 4.0, to generate upgrade instructions specific to your deployment topology, application and database servers, data warehouse configuration, product integrations, etc. It is important to note that you should not run the setup wizard during the upgrade process.

An upgrade in a Tomcat environment is straight-forward and essentially involves shutting down each of the servers hosting the JTS or CLM application, installing the JTS or CLM application, running an upgrade script on each server to update configuration files and tables (and the data warehouse in the case of JTS), and lastly, starting the servers. Note that for the RM application, there is an online migration phase after the server has been started.

An upgrade in a WAS deployment involves additional steps to backup the server profile, uninstall the 3.0.1.x JTS/CLM apps from WAS, clean up some directories, update properties, etc. and then running an upgrade script on each server to update configuration files and tables (and the data warehouse in the case of JTS). After starting the server, the last step is to deploy the 4.0 war files and start the applications. Note that for the RM application, there is an online migration phase after the server has been started.

To review an upgrade scenario in a fully distributed WAS deployment refer to the article  CLM 2012 Upgrade Guide on jazz.net. The CLM 2012 upgrade guide also provides troubleshooting and FAQ sections as well as other information to help guide you through the upgrade process.

Notes:

  1. 3.0.1 did not require 64bit OS - whereas a 64 bit OS is a requirement for 4.0
  2. The 2011 Eclipse and Visual Studio clients are compatible with CLM 2012 and can therefore be upgraded at a later time. Here are instructions for upgrading the clients.
  3. For RRC you still need to perform an online migration. Instructions are provided in the interactive upgrade guide Upgrading to version 4.0.

Upgrade an existing Jazz environment to CLM 2012

In this scenario you already have a Jazz-based product (RTC, RQM, RRC) in your network and now you would like to upgrade to CLM 2012. 

If you are starting with a 2.x product, you will have to upgrade the product to 3.0.1 first by following the Interactive upgrade guide in the 3.0.1 Information Center. As you select the options that describe your environment, you will choose your deployment topology. This is where you can specify that you want to begin distributing your applications on multiple machines if you have not already installed a separate JTS.

If you are starting with 3.0.1 products or have just finished upgrading to 3.0.1, the next step is to upgrade to version 4.0 using the Interactive upgrade guide in the 4.0 Information Center. 

Now that you have upgraded to version 4.0, the next step is to install the remaining applications to make up a full CLM 2012 offering. For this, use the Interactive installation guide.


Administration

Before we start,  a few definitions would be useful.

A repository is a central location for tool-specific information. It is a data store containing top level objects called items that have a Universally Unique Identifier (UUID). Some item types maintain a history of changes for audit purposes, while other item types do not. APIs are provided for creating, retrieving, updating and deleting items as well as running queries on the repository. 

Each CLM application (CCM, QM, RM) uses a project area to organize a software project. A project area is a top level or root item in a repository that defines the project's deliverables, team structure, process, and schedule. There can be many project areas in a repository. In a CLM deployment, artifacts across application projects can be linked to support cross-application traceability.

A project area can contain multiple teams and team areas are the mechanism for organizing them. A team area includes team members, the timeline to which the team is assigned, and the process to which the team has subscribed. Team areas are optional - they may not be needed for small projects or project teams.

In CLM, each of the applications has their own project area. A lifecycle project groups multiple project areas so that the project areas can be managed from a central location. The application that is used to administer project areas is called Lifecycle Project Administration (LPA). In
Run the Setup Wizard during a new CLM installation you may recall registering  LPA with the server.

Common Project Administration

There are several administrative tasks that are common to CCM, QM, and RM such as creating project areas and team areas, creating timelines and iterations, adding users to a project area, and adding and modifying roles and permissions. These common administration tasks are described in Administering project areas: Tasks for all applications (web client). Alternatively, you can use the Lifecycle Project Administration (LPA) application to create and manage project areas across applications, which is what we will be doing in the next section.

Setting up projects

To create a lifecycle project and project areas, log into Lifecycle Project Administration and either create a lifecycle project from a template or, if you have existing project areas, then you can create a lifecycle project and add existing project areas.

When you create a project area you will need to specify a process template to use. Process specifies
the roles, practices, rules, and guidelines that are used to organize and control the flow of work in a project. It defines permissions for performing operations within the project, and can be used to define project reports, queries, and work item types. Jazz includes process templates for common processes that you can use as-is or customize to suit your organization.

If users have not yet been created, follow the instructions to create users in the Jazz Team Server repository. Once created, users can be added to projects (see add members to projects) and assigned roles (see assigning roles).  Roles identify the functions of team members and determines which operations a user can perform. If email notification has been enabled, the newly added user will receive a team invitation with instructions on how to accept it.  

Once you have your project areas created and have added members the next steps are to create timelines,  iterations, and iteration types and optionally create team areas for organizing project teams. For a complete set of common administrative tasks refer to Administering project areas: Tasks for all applications (web client).

Enabling email notification

You can modify the server configuration properties such as database connections, feed settings, OAuth consumers, etc. from the admin page of the JTS or the admin page of an application registered with the server. See Configuring the Server for a complete list but for now, if you want to send email notifications to work item owners and subscribers to inform them of changes then you need to configure e-mail settings since the default is that email notifications are disabled.

Managing users

User information is stored in the JTS database where it is shared by the server and by all applications registered with the JTS. User information is also stored in an external registry such as LDAP. A task can be scheduled to run regularly to synchronize data in the two locations. For details refer to Managing users - when getting started with CLM 2012, the key user administration functions are  creating users and assigning licenses.


Additional Administrative Tasks

The above description focused on the administrative tasks that are common to CCM, QM, and RM. Additional administration tasks specific to these applications can be found in Administering change and configuration management project areas, Administering quality management project areas, and Administering requirements projects


Further Reading:
  • Jazz Administration Guide (3.x) - While this was written for 3.x, it provides a template for the important information and tasks that you need to be aware of as a jazz Administrator.


profile
조회 수 :
4531
등록일 :
2012.07.13
22:18:23 (*.168.242.88)
엮인글 :
http://jazzlab.net/jazz/teamblog/21457/14a/trackback
게시글 주소 :
http://jazzlab.net/jazz/21457

아름프로

2012.07.13
22:18:50
(*.168.242.88)
profile

https://jazz.net/library/article/832

How to author and use a Process Description for a Process Template in CLM 2012

This article gives step by step instructions for extending process templates with readable process descriptions in CLM 2012. For more information on CLM 2012, see the CLM Infocenter topic in the online help.

Overview

CLM 2012 allows users to compose a process description for a process template in place using the web UI. The new process description will be available for viewing and editing in both the web UI and the Eclipse client, and will be part of the process template that can be shared via export and import. When you create a new project area using a process template with a process description, a copy of the process description from the process template will be created for that project area. If you extract a process template from a project area, the process description will also be extracted as part of the extracted process template.

In CLM 2011, the process description for a process template had to be created outside of the Jazz application as static content (usually HTML) and zipped up in a zip file. The zip file was then attached to the process template as an attachment, and the process description made available only in an Eclipse client (e.g. the Rational Team Concert client). The description was not visible in the web UI, and could not be modified. Even when creating a new project area, the process description was still only visible from within an Eclipse client, and was read-only.


Prerequisites

This topic assumes that you have installed CLM 2012 and have deployed the process templates in the CLM applications. If you have not, follow the directions in the online help to run setup and deploy templates before continuing. This topic also assumes that you know the basic concepts of project area, team area, process description and practice, and are familiar with project area management in the CLM web UI. You can refer to How to author and use a Process Description in CLM 2011 to familiarize yourself with process description and practice.

Glossary

The Process Template provides a starting point and guide for a project area by providing a process configuration and iteration structure that can be applied to a new project area to define the initial runtime process of the new project area and its team areas.
The Process Description is used to capture how a project or team works. It describes all of their routines and methods.
The Practice is part of a process description. It is a routine or method that is used by members of the project or team (e.g. practice "Continuous Testing" describes how to perform testing during development).


Create a process description for a process template

  1. Navigate to the application administration page (e.g. https://clmwb.ibm.com:9443/ccm/admin for the Rational Team Concert application).
  2. Open the Templates menu.
  3. Hover over the Scrum template, and click the Edit Process Description button to create a new process description.
  4. Name the process description "Process Description for Scrum", and input some text in the description field.
  5. Save. A process description for the process template is created.
  6. You can now create or import practices following the instructions in How to author and use a Process Description in CLM 2011.

See screen shot for the Edit Process Description button in the process template list page:

Edit Process Description

See screen shot for a example of a completed process description in Scrum template:

Template Process Description


Import, export, or delete a process template with a process description

  1. Create a process description for the Scrum template as explained above.
  2. Navigate to the application administration page (e.g. https://clmwb.ibm.com:9443/ccm/admin for the Rational Team Concert application).
  3. Open the Templates menu.
  4. Hover over the Scrum template, and click Export Scrum to export the process template with its process description. You will find a file named processdescription.zip in the exported archive.
  5. Hover over the Scrum template, and click Delete Scrum to delete the Scrum template as well as its process description.
  6. Click the Import Template button to open the dialog for importing a process template. Select the exported archive created in step 4 to import the Scrum template.
  7. After the import is finished, hover over the Scrum template, and click Edit Process Description to see that there is already a process description for the Scrum template.

Create a project area using a process template with a process description

  1. Navigate to the application administration page (e.g. https://clmwb.ibm.com:9443/ccm/admin for the Rational Team Concert application).
  2. Open the Project Areas menu, and then open the Active Project Areas sub-menu.
  3. Click Create Project Area to create a new project area.
  4. Name the project area "My Project".
  5. Select Scrum Process in the Process section (make sure that the Scrum template contains a process description).
  6. Save.
  7. Open the Process Description tab. You will see that there is already a process description created for this project area.

See screen shot for the process description in the newly created project area:

Process Description Tab


Extract a process template from a project area with a process description in the Rational Team Concert client

  1. Start the Rational Team Concert client, and create repository connection (e.g. https://clmwb.ibm.com:9443/ccm/) to the Rational Team Concert server in CLM 2012.
  2. Connect to the project area My Project, which contains your process description (created above).
  3. In the Team Artifacts view, right-click My Project and choose Extract Process Templates... to open the Create Process Template dialog.
  4. Rename the new template name "My Project Template", input a process ID, then click OK. This will extract the process template from the My Project project area.
  5. After several moments, a new process template will be created and opened. In the Process Templates view, there is now a new process template named "My Project Template".
  6. In the process template editor, switch to the Links tab, click the web client link in the Process Description section, and log on to the web client. You will see a process description for the new template "My Project Template".

For more information


About the author

ShaoMin Xing is a software engineer in Process team of Jazz Foundation project. You can contact him at xshaomin@cn.ibm.com.

Phong Nguyen Le is the Process Authoring component lead in Process team of Jazz Foundation project. You can contact him at pnle@us.ibm.com.

profile
태그 :
조회 수 :
5087
등록일 :
2012.07.13
22:14:41 (*.168.242.88)
엮인글 :
http://jazzlab.net/jazz/teamblog/21449/436/trackback
게시글 주소 :
http://jazzlab.net/jazz/21449

아름프로

2012.07.13
22:14:53
(*.168.242.88)
profile

https://jazz.net/library/article/963

Rational solution for Collaborative Lifecycle Management 2012 Administration Workshop

This workshop assists CLM administrators with configuration and setup of CLM applications within different topologies and middleware applications. You should do the workshop if you want to learn how to:

  • Move a CLM installation to Departmental or Enterprise topologies.
  • Install a reverse proxy to better manage CLM servers.
  • Adopt enterprise middleware such as DB2, WAS or LDAP services.
  • Rename CLM servers to create a staging environment.
  • Create CLM clusters to support High Availability.

The workshop contains the following labs:

  • Lab 1: Workshop setup
  • Lab 2: Departmental Topology (migrate to WAS, DB2, and LDAP)
  • Lab 3: Configure Reverse Proxy
  • Lab 4: Enterprise Topology (migrate to a clustered topology)
  • Lab 5: Create a Staging Environment (server rename)

There is a cloud image available that completes most of Lab 1. This will save you significant time in setting up the workshop.

Lab Material:

  • Workbook (workshop labs)
  • Introductory slides
  • IBM SmartCloud Image: Launch the SmartCloud Dashboard and select Add Instance from the Instances portion of the Control Panel. Select the Raleigh data center, and select Shared Images for the View. The CLM 2012 Admin Workshop image is in this list.
profile
태그 :
조회 수 :
5540
등록일 :
2012.07.13
22:12:29 (*.168.242.88)
엮인글 :
http://jazzlab.net/jazz/teamblog/21440/881/trackback
게시글 주소 :
http://jazzlab.net/jazz/21440

아름프로

2012.07.13
22:12:44
(*.168.242.88)
profile

https://jazz.net/library/article/831

March 11, 2009

Finding your changes - using releases, builds, and snapshots

Tags: , , --- By Jean-Michel Lemieux @ 2:24 pm

It has been a busy fall and winter for the Rational Team Concert (RTC) development teams. We shipped 1.0.1 in October, followed by 1.0.1.1 in February, and we are working on 2.0. It’s probably not uncommon to have many releases on the “go” at the same time, but I must admit that it has been a bit mind bending.

On the plus side, it has really put our tools to the test. In particular, we’ve had to port changes from one development stream to the next and closely track what changes went into which releases. I’d like to walk through how we do this.

Streams, builds, and releases

First though, let’s review the Team Concert development stream structure. We have an integration stream for the current release, in our case 2.0, that we call “Weekly Jazz Integration”, and an integration stream for the maintenance release 1.0.1.X. Each component team has their own parallel stream structure to isolate their changes. Note that the stream structure in Figure 1 was created from within the Eclipse RTC client by clicking on the “Weekly Jazz Integration” stream from the Team Artifact navigator and selecting “New > Flow Diagram…” then adding the streams of interest to the flow diagram.

Figure 1: Work Item and Source Control teams flowing changes to 2.0 and 1.0.1.1

The stream structure gives teams and developers the isolation needed and the ability to integrate using a regular rhythm. When we show this instead in a time line view of the stream hierarchy, in Figure 2 below, you can see how the levels of integration allow team isolation with continuous integration. Each stream gets a build to ensure continuous health and also that each developer has their own private builds. It’s all about running continuous builds and flowing changes between different integration levels.

Figure 2: Timeline view of the stream hierarchy (Click for full-size)

The first thing of interest to most teams is to track what changes happened between two releases. Let’s take 1.0.1 (October) and 1.0.1.1 (February) and see the changes made by the Build and Dashboard teams in 1.0.1.1. There are two key practices we use to help us track exactly what we’ve shipped.

  1. We keep all the build results for milestones and releases. The build result allows easy navigation to the snapshot that was taken of the build workspace when it was built.
  2. When a build is blessed, we create a release description that is shown in the project area and links the release with the build and provides values for the “Found In” field of a work item.  We bless builds by creating a work item linked to the build with a set of approvals for each component lead.
  3. We promote the snapshots for blessed builds to the main integration stream so that we keep a common list of the blessed snapshots.

Finding what changed between 1.0.1.1 and 1.0.1

To find the changes between two releases, we start from the project area editor and open the “Releases” page, as shown in Figure 3. From here we can open the build that produced this release and open the snapshot. The snapshot is the Source Control artifact which references a list of component baselines. It’s like a read-only copy of a repository workspace. When a build is run, a snapshot is created automatically by the build engine.

Figure 3: The releases for Rational Team Concert

We start by opening the 1.0.1 build and then clicking the snapshot linked from the build result. Now that we hav found the 1.0.1 snapshot, from the snapshot editor we click the “Compare with snapshot” action, as shown in Figure 4.

Figure 4: Snapshot editor for 1.0.1

Now to find the 1.0.1.1 snapshot, we simply select the “Weekly Jazz Integration” stream into which we promote all the snapshots from the blessed builds. When the comparison runs we get a summary of the changes between 1.0.1 and 1.0.1.1 grouped by component. You’ll also notice that because of the process we enforced for the maintenance stream, all change sets have an associated work item which allow traceability for each change made in the release. In this case, we can confirm that most teams focused on TVT or globalization fixes to enable Team Concert to be translated into 13 languages.

Figure 5: Change Explorer showing the snapshot comparison (Click for full-size)

An alternate way of finding if a change set in another stream is to run the “Locate Change set” action from a work item or the history view. As an example, let’s try and see where the change set for work item 68677 has flowed. First, select this change set from the history view, run “Locate Change set”, you’ll get a search dialog as shown below.

Figure 6: Locate change set dialog

In this case let’s search in the flow targets for our repository workspace and see where the change set has flowed.

Figure 7: Search results from locate change sets

This confirms that the change set has flowed to both the 1.0.1.1 and 2.0 streams.

Forward porting the changes from 1.0.1.1 into 2.0

In the last section we saw how to find the changes and see if a change has flowed to several streams. Now let’s see how to actually get changes to flow from 1.0.1.1 into 2.0. The best way to forward port changes is to use the Pending Changes view to accept the changes from the maintenance streams into the current development stream. Take the example below. It shows the Pending Changes view with the latest code from the 2.0 release, and I’ve changed the flow target to accept from the “Weekly Integration 1.0.1.X” stream for the Filesystem and AgilePlanning components.

Figure 8: Merging changes in Pending Changes

As with most feature releases, a lot of files can get modified. This is highlighted above with the orange potential conflict markers which indicate that files have been modified in both 1.0.1.1 and 2.0 and merging will be required when they are accepted. Notice that the Filesystem component has ported all the change sets from 1.0.1.1 into the current release, whereas the AgilePlanning team still has a couple left to port forward.

Note: In general you don’t want to flow baselines between development streams. Since the baselines are used to mark interesting points in time along a history, when histories are merged between two streams those points are less interesting if they are mixed. In the case of backporting or forward porting changes, focus on flowing the changes and not the baselines. There is a setting in the Pending Changes view preferences which allow hiding empty baselines.

Although there are several techniques to track work in two releases (for example, creating a work item for each release in which the fix must be made), it’s still very useful to merge the change sets into each release, even if the changes are redone differently. This allows the SCM system to be used to its potential and make it easier to track which changes still need to be ported.

When changes have to be completely re-written to be forward ported, it is still good practice to accept the change set from the previous release. When conflicts occur, resolve them using the “Resolve with Mine” action to mark the changes as merged although you won’t actually take any of the file changes. The changes are marked, and the change set is now part of the component’s history. From now on you can easily track which change sets need to be merged forward.

“Why would I have to re-write a fix? Can’t I just merge it?”. In most cases when changes between your streams are small, text merging will work fine. However, there are other cases when classes are refactored, someone fixes the bug already in another way, or too many conflicting changes exist, that it’s just easier to make the a one liner fix instead of figthing with a very busy text merge editor.

Conclusion

I have shown a lot here, so let me try to wrap up with a quick summary:

  1. The combination of Releases, Build Results, and Snapshots allows your teams to create traceability between official releases and the code you ship.
  2. Use the compare tools to compare snapshots, streams, and baselines to find out the differences between releases or at different points of time in your release cycle.
  3. Use the locate change set action to find where changes have flowed.
  4. Merge your changes forward to make is easier to track the fixes that need to be forward ported.

Happy parallel development!

Jean-Michel Lemieux
Team Concert PMC
Jazz Source Control Lead

profile
조회 수 :
8489
등록일 :
2009.03.12
19:18:22 (*.109.178.9)
엮인글 :
http://jazzlab.net/jazz/teamblog/3477/aa6/trackback
게시글 주소 :
http://jazzlab.net/jazz/3477
원본 : 바로가기

Integrating Visual Studio builds with Team Concert

By Jean-Michel Lemieux @ 12:08 pm

Many of you have asked if we support integrating automated Visual Studio builds with Rational Team Concert. The short answer is yes, but you’ll have to use the Eclipse Team Concert client to control and view the results.

When talking about build, it helps a lot to look at a picture. The following diagram taken from the build examples shows the different parts involved in a build. For integrations with the Team Concert client for Visual Studio you can use the continuous integration engines, integrate with the build toolkit, and store your results in the repository. Then use the Eclipse client to control and view the results.

Let’s see how this works in practice. As you would expect, as we were developing our client in Visual Studio we needed to automate our builds. We started by doing the following:

  • We wrote a set of MSbuild based batch files, calling devenv and other tools.
  • We tested the scripts locally, checked that the installer was created and that tests were being run. We used the Visual Studio test infrastructure, but you could easily of used NUnit instead.
  • After the scripts were in place, we figured out how to have them called from a command line build engine. This basically simulates what we did in the first step, but invoked from the build engine instead of manually from the command line. The command line output is automatically attached to the build result. Of course, you have to ensure that your batch files are parameterized as you can see is the following build definition screenshots:


  • At this stage we have automated builds running, but we don’t have the install being uploaded or the individual test files available from the build. To further integrate, we used the Jazz Build toolkit Ant tasks, as shown in the C++ build example. From the batch file, you can call into the Ant tasks that ship with Team Concert:

:StartActivity
java -cp %CLASSPATH% %ANT_LAUNCHER% -f “%DEST_DIR_PATH%\RTC.NET Client\jazzBuildTasks.xml” -lib %JAZZ_TOOLKIT% -DuserId=%BUILD_USER_ID% -DpasswordFile=%JBE_PASS_FILE% -DrepositoryAddress=%REPOSITORY_URL% -DbuildResultUUID=%BUILD_UUID% -DactivityLabel=%1 startActivity
GOTO :EOF

:PublishFile
java -cp %CLASSPATH% %ANT_LAUNCHER% -f “%DEST_DIR_PATH%\RTC.NET Client\jazzBuildTasks.xml” -lib %JAZZ_TOOLKIT% -DuserId=%BUILD_USER_ID% -DpasswordFile=%JBE_PASS_FILE% -DrepositoryAddress=%REPOSITORY_URL% -DbuildResultUUID=%BUILD_UUID% -Dfile=%1 -Dlabel=%2 -Dtype=%3 publishFile
GOTO :EOF

To track the progress of the builds and browse the results you’ll have to use the Team Concert Eclipse client. The following screenshot shows the build activity and downloads that have been attached to the builds.

So the good news is that you can integrate your Visual Studio based builds. Over time we will try and provide more control and visibility from within the Visual Studio IDE. Before getting started with your builds, start by reading the build documentation and the examples. Then chime in to our forums if you need more help.

Cheers,
Jean-Michel


profile
조회 수 :
7256
등록일 :
2008.11.24
18:52:54 (*.168.242.42)
엮인글 :
http://jazzlab.net/jazz/teamblog/3132/601/trackback
게시글 주소 :
http://jazzlab.net/jazz/3132

원본 : First Look: IBM Rational Quality Manager


Yet again hats off the Jazz folks for making something consumable. With no effort involved I was able to download and install a Beta 2 of Rational Quality Manager (RQM) and login and get a default empty dashboard with no configuration at all 8)

RQM is a web based tool “for test planning, workflow control, tracking and metrics reporting capable of quantifying how project decisions and deliverables impact and align with business objectives.” It’s also Jazz based. A couple of weeks ago I did a First Look analysis of Rational Requirements Composer (here) so I thought I’d have a look at RQM today. I should caveat this by saying I’m not a QA/Test expert! :)

This being a Beta there are some bugs hanging around like the horizontal tabs having a higher z-order than the pop-up menus from the left navigation bar so you’ve got to be precise with the mouse to open the “My Test Plans” tab at the moment and it’s a little hard to create a new test plan :S If only the left menu bar auto scrolled down like the “related sites” links on the far right! Eventually I worked around this by constructing the URI to create a new test plan - https://localhost:9443/jazz/web/console/QM#action= com.ibm.rqm.planning.home.actionDispatcher&subAction=newTestPlan and just typing it into the browser address bar. I had this problem in FF and IE, anyway I’ve got a work around so off I go.

Here’s the blank empty GUI:

Once I got into the Test Plan editor I was able to start creating a structured Test Plan. I like this idea, as instead of a huge Word document with no structure here there are discreet sections with potentially seperate ownership. Obviously in my demo repository there are no requirements to hook into a test plan so I clicked the button to create one, this led me into the Rational Team Concert web interface 8)

Unfortunately I got quite a few errors in trying to save sections of my test plan, and also none of the editors for the various sections would let me type in them no matter how many times I hit the “Edit” link. The idea of structured test assets continues in the Test Case editor, although I had the same problems as with Test Plans here in terms of editing some of the content. I was however able to generate work items (which naturally I did twice) based on my test case and configured environments using the excellent lab management interface :D

Upon executing my generated work item the problem I found was that my test failed. There were no doughnuts to be had! :(

This being based on the Jazz platform there is of course a lot of reporting available (I shifted over to the sample Java PetStore test plan since there wasn’t enough data in my dummy project).

Conclusions

RQM gives you a fully web based quality management portal. The structured nature to managing test assets is a major improvement, and since this is Jazz based I’m sure it’s all deeply configurable for different ways of working and approaches to quality management and testing.

The integration of information from Team members, Test Plans, Test Cases, Test Scripts, Execution, Reports and Defects is seamless and intuitive, with requirements and defects being managed through the Rational Team Concert interface and of course the data is easily reported on.

I’d like to dig more into the integration with other tools such as Rational Team Concert, possibilities with Rational Requirements Composer and the relationship between process templates in these various tools. Not to mention migration paths from other QM/Test tools like the “classic” Rational tools and those from other vendors.

All in all it looks like an impressive, intuitive and powerful product but it’s an early access Beta and has quite a few bugs that can make playing with it a bit frustrating at the moment.

More info

See my first look at IBM Rational Requirements Composer here

See more stuff about Jazz in general here: What’s all that Jazz?


profile
조회 수 :
7206
등록일 :
2008.10.02
23:00:28 (*.168.242.42)
엮인글 :
http://jazzlab.net/jazz/teamblog/2922/f09/trackback
게시글 주소 :
http://jazzlab.net/jazz/2922

원본 : First Look: IBM Rational Requirements Composer


So I downloaded and installed IBM Rational Requirements Composer (RRC) today. I’m not very good at reading instructions so typically I didn’t read them but I still managed to set up RRC server and connect a client within an hour :D Excellent job yet again Jazz people, in the past with the “classic” tools this sort of thing wouldn’t have been possible in such a short time. It even co-exists (but isn’t integrated) with my Rational Team Concert installation. At the moment I’ve got two Jazz server instances which is a shame, but this is only a Beta.

Anyway, I used the configuration utility and with only referring to the instructions once or twice I quickly got RRC setup and working. Having said that the config utility uses an embedded IE instance to access the Jazz Admin console and for me that wasn’t working so I gave up on the config utility and just used trusty FireFox.

The client is Eclipse based but isn’t shell sharing with my other eclipse shell at the moment. I’ve created a Test Project and thought about creating some artifacts to go along with it. I can’t see where to edit templates but since this is Jazz based I’m sure that everything is customisable. I’ve got a bunch of errors showing in my logs and in the Jazz admin web UI so I’m not sure if I’m seeing everything anyway. Perhaps reading the instructions is a good idea!

Overview

It’s clear that it’s an early Beta as there’s still a lot of simple UI bugs but the point of these releases is not to provide a finished product but to give people that are interested a chance to get to grips with the functionality and look and feel. So here’s some of my thoughts and screenshots (clicky piccies):

I set about creating a process diagram

Then a glossary that supported some of the terms that I identified in thinking about the business process

I also played around with creating a Use Case diagram

Because I’ve got a software development background I immediately decided to mock up a UI and screen flow rather than consider any of those pesky requirement things :P

At this point it seemed like a good idea to think about writing an initial Use Case specification, this was cool because I could integrate the various things I’ve done already such as embed the UI mockup, link to the business process and have glossary management done for me too :)

All of which left me with some cross linked integrated stuff to do with capturing my requirements as regards eating doughnuts

Conclusions

It’s quite easy to start setting up a set of integrated stuff including storyboards, process diagrams, use cases, UI mockups etc. and is very non-technical to use. Personally I found the UI mockup functionality to be limited, I’d prefer more free form drawing capability when I create a “sketch” it would take me longer to mock up a UI here than it would for me to build it in Visual Studio - but then again this is aimed at analysts that may not be able to use IDEs. The UI seems very windows based as well, what about trusty web widgets!

I’d like to get at the project template and see what can be done in terms of the elements and strucutre of the project, not to mention document templates for things like Use Cases.

Does this replace RequisitePro? No. Although it’s got requiremetns authoring, marking and linking RRC doesn’t yet provide full traceability management and (at least at the moment) I can’t see where I’d go about attributing and managing requirements attributes. That’s why RRC has integration into ReqPro to provide these things.

Personally I’d like to see versionable requirements artifacts, more flexible UI sketching, traceability management, attribute management and more integration into other Rational tools such as Rational Software Architect and Team Concert.

This is a good start in terms of providing a single tool to support requirements elicitation and elaboration, all the diagrams and docs in one place, easily distributed and collaborated on. I’ll look forward to seeing more of it as time goes by :)


profile
조회 수 :
6902
등록일 :
2008.10.02
22:56:59 (*.168.242.42)
엮인글 :
http://jazzlab.net/jazz/teamblog/2918/86e/trackback
게시글 주소 :
http://jazzlab.net/jazz/2918

원본 : Screenshot of Visual Studio Client for Jazz Rational Team Concert


VS Client for RTC

Excellent news! Some info about the Visual Studio client for Rational Team Concert! Apparently early builds may  be available as early as November. Sign up for jazz.net and read more info here.



profile
조회 수 :
6879
등록일 :
2008.10.02
22:49:55 (*.168.242.42)
엮인글 :
http://jazzlab.net/jazz/teamblog/2913/fd4/trackback
게시글 주소 :
http://jazzlab.net/jazz/2913

원본 : Screenshots of new IBM Rational Jazz products


I recently put together a presentation for IJI on IBM Rational Jazz and the new, and future, Jazz -based products. Rather than present bullet points about products I like to show demos where possible and screenshots otherwise as like many people I find that I need to see a tool to gain an understanding of it. This presented me with a bit of a problem because most of these tools aren’t released yet, and some are only ideas from Rational Labs rather than actual listed products. But I managed to get screenshots or at least spy shots for the presentation so I thought I’d share.

You can download the whole presentation here, it’s in PDF form though so you don’t get the animation or Rational Team Concert demo vids (if you’re an IJIer just drop me an email if you want the full demo videos) Download

Here’s some screenshots and spy shots of some of the new tools:

Rational Team Concert

Rational Team Concert (RTC) is a collaborative project execution environment providing source control, work item tracking, build management and reporting capabilities as well as supporting agile planning. RTC is the first Jazz based product and at the moment the best known. The demo includes some early integration between Esswork and RTC.

Early access packages of RTC are available now from jazz.net

Rational Quality Manager

Rational Quality Manager (RQM) is a business-driven software quality portal for people seeking a collaborative and customizable solution for test planning, workflow control, tracking and metrics reporting capable of quantifying how project decisions and deliverables impact and align with business objectives.

RQM should be available around the 7th of July

Rational Requirements Composer

Rational Requirements Composer (RRC) is a requirements definition solution that enables organizations to enhance their requirements processes with easy-to-use elicitation and definition capabilities and provides various visualisation, documentation and collaboration capabilities.

Open Beta pre-registration (Available in July hopefully)


The following are currently Rational Labs projects and may not make future products in their current form

Rational Tempo

Improve estimation through:
  • Tracking probabilities
  • Schedule extrapolation
  • Risk management

Rational Ensemble

Improve team collaboration
  • Awareness of similar work
  • Tracks historic assignments
  • Links team members

There is also business partner collective called IBM Rational Ensemble which is not the same thing as this Rational Labs project!

Rational Governor

Improve Governance
  • Specify Governance Solutions
  • Manage Roles and Decisions
  • Automate processes

Rational Financier

Improve Financial Management
  • Specify Governance Solutions
  • Manage Roles and Decisions
  • Automate processes


profile
태그 :
조회 수 :
5198
등록일 :
2008.10.02
22:43:56 (*.168.242.42)
엮인글 :
http://jazzlab.net/jazz/teamblog/2909/784/trackback
게시글 주소 :
http://jazzlab.net/jazz/2909
Tags: , , --- By Kim Peter @ 5:40 am

Normally the term “polish” makes me wince a little. For a long time now I have equated that term with the pejorative notion or belief that user interface design, often specifically visual design, is something that you can stick on at the end. However, as the Jazz Project team recently finished Beta 3, its third major end-of-cycle round for Rational Team Concert, I have come solidly around to understanding the value and purpose of “polish” as a way to refine the product UI --- quickly.

What has changed my thinking is the realization that so much can be done in this phase. It doesn’t trump any of the more intensive design and development work done in the regular milestones, but it does provide an opportunity to take care of a number of niggling things that were on the wish list but got supplanted by more significant development pieces.

The following lists represent a sample of the polish items completed or underway. Some are arguably not polish in that they involve more significant code changes but, big or small, all represent refinements we have deemed important and doable for the first release and are being handled in this last push before we finalize.

Some of the Eclipse-based UI changes include:

  • Updating the color palette for feeds in Team Central so there are more colors to choose from, each having been tested to work well as a foreground color. This palette was previously composed of the core system colors, which are not all ideal, or aesthetically pleasing, as foreground colors. To access this new palette to color code your feeds, choose “Configure…” from any feed section’s local menu, then select a feed item from the list and choose “Edit…”. This will surface the following dialog with the updated color options:

    Feed color palette

    Here is an example of a section with feed items that have been color-coded with the new palette:

    Feed color example in Team Central

  • Using adaptable color labels in form-based editors so they change with the OS theme. This is something the Work Item editor does already. It allows for a nice visual distinction between what is a label and what is content, as well as being accessible across all themes, including high contrast. These were updated recently in the CQ editors and will also eventually be updated in the Builds editors:

    Form labels will be updated to adaptable color

  • Improving consistency between the Quick Filter bar instances in My Work view, Iteration Plan editor, Work Items explorer, and Search view. This included mainly icon updates so far, ensuring all use the same ‘Filter’ scope icon and the same ‘Close’ control. You can access the Quick Filter bar using Ctrl + F from any of these UI contexts.
  • Refining the Getting Started message areas in the My Work view, Iteration Plan editor, and User editor. The updates here included adjustments to the message wording, what words were hyperlinks, the alignment of the ‘Information’ icon and ‘Close’ control to the top instead of centered, the use of Eclipse-style ‘Close’ control instead of the more agressive OS-based one, and refinement of the graphical rendering of the message box. The following example is from My Work view:

    Getting Started message area in My Work view

  • Improving the presentation of, and distinction between, “Load” and “Progress” bars in Iteration Plans. Previously the coloration and labeling of these two bars was very similar --- they both had green and red colors and used “Hours” as the initial label. Now the color for Load shows as blue on the left for hours booked and red on right if the team member is overbooked. The Progress bar continues to use green on the left side to show progress. When ahead the bar on the right is green, and when behind the bar on the right is red. The labels for each of the bar types is now explicitly called out with “Load” and “Progress”, respectively. In both cases, more detailed information about the nature of the content in each bar is available on hover, as shown here:

    Load bar in the Agile Planning Toolkit

    Progress bar in the Agile Planning Toolkit

  • Improving the input experience on estimate controls in Work Items and Iteration Plans. The polish updates included refining the look and position of the overlay image; adding more information to the tooltip text for clearer guidance on how time units can be input, e.g., showing an example with 1w, 2d, 3h, 4m, where w = week, d = day, h = hour, and m = minute, and noting the “h” is the default time unit; and adding the default “h” if the field is left without a unit having been input, as in the example below. Also, now with the automatic input of the default time unit, errors are only shown if there is an obvious input error, not if a time unit has been left out. This is a friendlier approach and means most times errors should not show on these estimate controls:

    Estimate input, showing initial control focus

    Estimate input, showing tooltip with description and example of units

    Estimate input, showing a number entered but no time unit

    Estimate input, showing the automatic insertion of the default unit ‘h’ for hour when the user leaves the control

  • Showing validation markers for required fields only after ‘Save’ in the Build Definition editor. The following screen is a snapshot of how the markers previously showed on first interaction with the editor, but now these markers only show on ‘Save’ --- a pattern we try to follow in editors, dialogs, and wizards:

    Build Definition editor showing validation markers for required fields only after Save.

  • Using the “Show More” action link in dialogs with long lists, such as the Baseline dialog and History view in Source Control, to allow for expanding the list incrementally on demand
  • Reordering and sizing of the default column in the History view to aid its discoverability
  • Adding the CQ Synchronization status to the Quick Information area of work items that are synchronized with the CQ Connectors:

    CQ Synchronization status entry in Work Item Quick Information area

  • Adding or replacing a number of UI graphics (icons and wizard graphics) that were either missing or needed improvement. Of course I keep coming across more to do! ;-)

Some of the Web UI changes include:

  • Improving navigation between Project Areas; the regular application pages like Dashboards, Work Items, Iteration Plans, Reports, and Source Control; and Admin. These improvements included making “Project Areas” a first-class page on the global navigation bar for ready access to all Project Areas from any point in the UI. It also included introducing a Project Areas switcher on the far right of the banner, that is scoped to “My” project areas to allow for quick access to the project areas you are part of:

    Global navigation now includes access to Project Areas and maintains context across the pages

    Project Areas switcher

  • Adding quick navigation to “All Dashboards” from the left sidebar. We’ve long had the challenge of how to show all the Team Areas within a project with the potentially deep levels of nesting on the left sidebar. Showing them all was overwhelming and difficult to navigate through, particularly in such a constrained space. The “one-link” solution here removes the hierarchy from the sidebar, replacing it with a single link that when clicked, shows the full content on the right in the main page area. So simple, and yet it took a few tries to arrive at. We have a similar approach in Iteration Plans with the break down of plans into “My”, “Current”, and “All”, and will reuse this approach in other components over time where there are deep hierarchies:

    All Dashboards link on left sidebar with a selection of its content on the right in the main page area

  • Introducing breadcrumbs in Dashboards and other components to aid context and traversal of paths to and from a given artifact:

    Breadcrumb showing the hierarchical path to Source Control from All Dashboards

  • More consistent load and busy indication across the UI. Previously we had a mix of graphical animation and text used in different ways and in different locations across components. Most loading or busy indication now uses a text-based “Loading …” information string either in-line or at the page-level in the upper-right corner, as shown in this example of loading an iteration plan:

    Loading message area in upper-right of page area

    The exception is in Dashboards where we continue to use an animation in the title bar in a couple of ways: First to provide an additional layer of feedback as the viewlet is loading, and second, when there is content already in the viewlet and we need a place to show that additional information is coming in. This example shows the first case of the loading viewlet, then that same viewlet once the content is in. The animation was recently updated from a bar-style to the circular one shown here:

    Viewlet loading animation

  • Moving away from dialog-based error messages in favor of contextual in-page messages for issues that occur at the page level. If you do encounter a page-level error, such as a ‘Save’ problem in the Work Item editor due to a required field not being filled in, it will now show in the editor header area, much like on the Eclipse client. These in-page messages are also used in the Jazz Team Server Setup wizard, and in the Admin area with the Web UI.
  • Introducing an “Unsaved Work” section in the Work Items sidebar to support an unlimited number of new and modified work items. This image shows one new unsaved Defect:

    Unsaved Work section in the left sidebar

  • Adding Quick Search type-ahead in Work Items and Dashboards, so far. This example shows type-ahead for Connectors in the Dashboards area:

    Type ahead in Quick Search within Dashboards

  • Tweaking some layout and color issues in Work Items, Reports, and Iteration Plans, including updating the color of static titles in the Overview pages of Iteration Plans so the text doesn’t look clickable and adjusting the spacing of the Quick Information area within the Work Item editor so it is easier to read

(You might also have noticed an evolving look and feel in the Web UI, most notably in the banner and global navigation areas. I’ll tell you more about these and related changes in an upcoming blog post.)

The most recent New & Noteworthy for M6a and Beta 3 will also showcase some UI polish items mixed in with a great many more recent implementation updates. If you want to see these changes live, the Rational Team Concert Beta 3 client download is available, as is the same level of the product’s Web UI.

Once you’ve had a chance to check out some of the changes, I’d be interested in hearing what changes you find useful, what you don’t find useful, and even what you are indifferent to. And if you have any niggling UI points of your own to make, don’t hesitate to let me know about those as well! We might not be able to tend to them immediately but they are likely to get on the polish list in one of the post 1.0 cycles to come.

---
Kimberley Peter
Jazz UI Design Team

  1. Excellent overview of some of the polish items. Great work, team!

    Comment by Jennifer Hayes --- May 29, 2008 @ 4:02 pm

  2. Kim, this all looks fantastic! Great improvements and your usual subtle artfullness.

    Wrt your opening comments, I always think of it as “fit and finish”. When a house is built, there is much design that occurs all along the process. But the last touches that the craftsmen make around fit and finish go a huge way to making that first “wow” impression when you walk in the door. The tiles well chosen, fitted perfectly, the walls smooth, the paint even, hardwood gleaming, the doors fit nicely in the jams… If that polish isn’t there, a well designed house just won’t come across at all and the good design was for naught. By the same token, the polish won’t turn a badly designed house into something of value. They’re both needed for the object to be fully realized as something worth wanting.

    Comment by Kevin McGuire --- May 30, 2008 @ 2:14 pm

profile
조회 수 :
2835
등록일 :
2008.05.31
23:50:26 (*.168.242.42)
엮인글 :
http://jazzlab.net/jazz/teamblog/2035/ffe/trackback
게시글 주소 :
http://jazzlab.net/jazz/2035