With contributions from Adrian Cho and Jazz Jumpstart team members: Jorge Diaz, Boris Kuschel, Rosa Naranjo, Jim Ruelin, Stepane Leroy, and Daniel Toczala
Last updated: June 26, 2012
Build basis: Rational solution for Collaborative Lifecycle Management 2012 (4.0)
All deployment guidance and best practice will be published in the Deployment wiki rather than as Jazz.net articles going forward.
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.
|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.
- Introduction to CLM
- New CLM 2012 Installation
- Planning the Installation
- Performing the Installation
- Upgrade to CLM 2012
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.
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).
- Jazz Team Server article – a brief description.
- JTS is based on RESTful web services and is considered the center of the Jazz Integration Architecture(JIA)
- Lifecycle resources (test cases, work items, requirements, etc) that are exposed by these RESTful services comply with the Open Services for Lifecycle Collaboration standard.
- 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.
- 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.
- What’s New in Rational solution for Collaborative Lifecycle Management reporting
- Introduction to Rational Reporting
- What’s New in Rational Reporting For Development Intelligence 2.0
- Setting up Reporting – this link provides steps to install and configure RRDI for CLM 2012
- Using RPE with CLM – contains tutorials for using RPE with RTC, RRC, and RQM.
- Tips for Deploying Rational Insight in a large Enterprise – this developerWorks article walks the reader through installing a version 188.8.131.52 of Insight that is currently available.
- Get things clear about CLM 2011 reporting capabilities – A mind map that summarizes the basic reporting capabilities in CLM.
- CLM 2011 Reporting Workshop – a hands-on workshop that guides you through some of the basics of using the CLM reporting capabilities.
- CLM Framework Manager Data Model Details – for the low level details and data dictionary associated with each of the CLM capabilities.
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.
- For a good discussion of the types of licenses and roles, and the functionality available, read Client access license management overview and Floating client access license management overview in the Infocenter.
- Licensing in the Rational Solution for CLM 2012 – Jazz.net article for What’s new in Licensing for CLM 2012
- Licensing in the Rational Solution for CLM 2011 – Jazz.net article with some discussion of licensing, as well as some how-to for setting up your CLM licensing.
- Jazz Licensing in Ten Minutes with RTC 3.0 – An older video on Jazz.net, but a lot of the concepts still hold true.
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.
- 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 (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 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.
- CLM Standard Topologies article on jazz.net
- High Availability with Rational solution for Collaborative Lifecycle Management – 2012 Clustering article on jazz.net
- Clustering for High Availability wiki on jazz.net. Information on setup and troubleshooting.
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 your Rational solution for Collaborative Lifecycle Management server
- Setting up a test staging environment using production data
- Moving a pilot deployment into production using server rename
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 ServerExample: 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.
/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
- 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.
- Moving Jazz Servers and URI Stability with CLM 2011 – A Jazz.net article on the topic of URI stability.
- You Can’t Change the Public URI. Really. You can’t – Another perspective on URI stability from the Jumpstart team.
- What’s the Deal with the CLM Public URI? – blog about the importance of selecting an appropriate public URI
- Solving Real World Problems using Rational Technologies – developerWorks article that provides some guidance on selecting a public URL.
- CLM Reverse Proxies, Part 1 – Covers the idea behind using reverse proxies for your CLM environment.
- CLM Reverse proxies, Part 2 – A “how-to” guide on how to set up a reverse proxy for your CLM deployment.
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 |
|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.
- RTC 4.0 eclipse client can run in Eclipse 3.6 and 3.7 (184.108.40.206 is bundled) and supports shell sharing.
- RTC repository workspace compatible from v2.x or v3.x to v4.0 client.
- RQM and RRC 4.0 clients are web-browser based. There is no Eclipse client for these products.
- CLM 4.0 Server Rename feature: you must upgrade all RTC clients (including build engines) to version 4.0 prior to the rename.
For a new CLM installation you will perform the following:
- Prepare for the installation – see Preparing the installation.
- Use the Interactive Installation Guide to guide you through the installation steps. You can choose various options to define your topology including whether you want to install RRDI.
- Run the setup wizard to connect the applications and database to JTS v4.0.
- You probably don’t have a build system installed so refer to Install and configure the build system.
- If you plan to use floating CALs or Token services for your licensing scheme then you must install and configure a license server.
- If you want the ability to author new document style report templates you will need to install and configure RPE.
- 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.
- 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)
- 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.
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.
- Once RRDI has been installed, you will need to create the database for content store, Initialize the reporting server and then run the RRDI set up wizard to configure RRDI. Finally integrating RRDI with CLM data requires that you load the Cognos archive files from the JTS as described in Integrating RRDI with CLM data sources.
- Now that the servers are started run the setup wizard as described next.
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.
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.
- Getting Started with Setting up Jazz Builds
- Continuous Integration Best Practices with RTC
- Using the Hudson Build Integration with RTC
- How To Do Maven Releases with Jazz SCM
- RTC Plugin for Jenkins
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.
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 220.127.116.11 and RRC 18.104.22.168.
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.
- 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.
- Upgrade from CLM 2011 to CLM 2012 – see the next section below.
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.
- 3.0.1 did not require 64bit OS – whereas a 64 bit OS is a requirement for 4.0
- 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.
- For RRC you still need to perform an online migration. Instructions are provided in the interactive upgrade guide Upgrading to version 4.0.
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.
Before we start, a few definitions would be useful.
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.
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.
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).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.
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.
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.
- 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.
Copyright © 2012 IBM Corporation