Ralph Schoon has posted a great reference, tutorial, and code on his personal blog which provides for A Rational Team Concert WorkItem Command Line! He provides code for a simple Work Item Command Line Client and explains the usage in a detailed but easily understood manner. Of course, noting that the post contains published code derived from examples from Jazz.net as well as the RTC SDK, we need to state that the usage of code from that example source code is governed by this license andas stated in the disclaimer, this code comes with the usual lack of promise or guarantee.
Since we have seen many requests to be able to create and update work items from a command line in the forum, as well as enhancement requests and a story for it in the RTC development repository, we wanted to highlight Ralph's work as a great starting point for creating these solutions. This WorkItemCommandLine should provide access for most of your automation needs when creating work items, as well as standing as a resource for the RTC work Item API.
So, go ahead and check out Ralph's blog post; we think you may find it stands as a hugely valuable resource as you move forward with your own RTC work!
Stéphane Leroy (Unleash the Labs CLM, IBM Software Engineer) has created a wonderfully simple table to outline the Test Lab managementcapabilities of IBM Rational Quality Manager (RQM). The table shown below and discussed further on his blogshould help speed up your understanding of the currently available capabilities in RQM, and facilitate the decision of the mapping between your own testing shop terminology and RQM terminologies:
I suspect I could get DOORS Web Access (DWA) installed and running on Windows in 5 minutes. But I hear grumbling about it so I am sharing and timing a DWA 18.104.22.168 install in a rush. I’m usually in a rush.
[Start the stopwatch]
Download it, usually from Fix Central. 22.214.171.124 is current and is here
If necessary, install the DOORS client. The DOORS client must be the exact same version as DWA. If there is already a client installed of a different version, uninstall it. I do this uninstall while the download is going on. If it is already installed and the same exact version as your DWA, skip this.
Start the DOORS client - make sure it works and connects to your database
Establish the database ID - run Tools - Edit DXL - print databaseID
Save that value (5304e5790e4b2eef for me)
Run the dbinfo commands. I never copy them from webpages that may include tab and quotes that break it. I make sure I see a “–I- DBADMIN” for every parameter I set, i.e. I need to see 6 of these. If I’m just upgrading, I skip this step as they are already set in my database. But if I am not upgrading and I need to set them, I refer to the help for the syntax Configuring the Rational DOORS database server
Stop the DOORS client
Restart the DOORS database server
Install DWA (I usually do this in parallel to the above)
Replace REPLACE_THIS_WITH_YOUR_REPOSITORY_ID with the database ID we found using DXL
Insert location of the license server
Put in the DOORS_PATH and DWA_PATH and if the database is not on the same machine or default port, edit DOORS_HOST.
Run dwa.start.bat as Administrator and take this opportunity to practice patience (i.e. throw paper airplanes at Fiachra)
It is important to wait for it to start, as the first time you start it, it is uncompressing the .war files and putting them in different places - this can take minutes. If you interrupt it, you get partly deployed war files which will cause problems later.
When in the Tomcat window you see the message 'INFO: Server startup in xx ms', it should be done
Open a web browser and go to https://<hostname>:8443/dwa and login. The first very login tends to be a bit slow to load the login page. And as we have used self-signed certificates, the browser will ask if you want to proceed.
[Stop the stopwatch]
24min 11sec. This included downloading and first draft of this blog. So 5 minutes is not in fact possible for me, I stand corrected. Downloading and starting are the slowest parts.
Avoid problems by having the DOORS client and DWA at the same version level and make sure that the client can start and that you don’t interrupt the tomcat start. If the database server is on the same machine, it is usually best to also upgrade it in order to avoid any DLL compatibility issues.
These are ten of the most recent How-To technotes for IBM Rational Team Concert (RTC). We know you will find them as helpful as we do, especially since they were all created based on client calls/ emails that have come in to our Support Engineers and the answers from which have been reused to solve even more PMRs than just the initial call...
IBM Rational DOORS: Common Mistakes and Misconceptions- In this video Afsheen Khan, an experienced DOORS user, takes you through the various common mistakes and misconceptions made by novice DOORS users as well as what powerful and useful DOORS functions most often go unused or underutilized.
Table of Contents:
00:40 - Agenda 03:00 - Background 04:26 - Objects vs. Attributes 06:37 - Columns vs. Attributes 09:43 - Object heading vs. Object text 16:00 - Misinterpreted warnings 18:00 - Object identifiers 21:09 - Mitigating issues with object identifiers 22:00 - Copying modules vs. Archiving modules 25:10 - Input/Output to/from DOORS 28:40 - OLE objects 38:42 - If links are deleted incorrectly 41:26 - Links, link modules, linksets 46:04 - Default Link Module 48:00 - Linkset pairing 49:28 - Putting it all together 52:20 - DXL deficiency 54:10 - Maintaining the database 59:00 - E-mail notifications 1:00:26 - Group access rights
IBM Rational DOORS 101: Basics- In this video Senior Systems Engineer Rick Learn takes you, as a beginner, through everything you need to know to get started with IBM Rational DOORS.
Table of Contents:
01:05 - How do you get started? 01:40 - Import all of your data and create documents 03:19 - Create a document based on a standard or template 04:10 - Document import and export 05:49 - Is DOORS easy to use? 06:39 - DOORS database view 08:46 - DOORS document views 11:25 - Traceability is the key to compliance 13:14 - Traceability drag-and-drop 14:32 - Multi-level traceability 17:13 - Traceability verification or 'completeness' 18:38 - How can I manage change? 19:12 - Change proposal system (CPS) 20:21 - Integration with RTC 21:29 - What are suspect links? 22:47 - Can I use DOORS to help with testing? 23:14 - Test Cases 24:44 - History and Baselines, Compare 26:10 - MS Word Export 26:34 - Printing with standard layouts 27:13 - Discussions 29:50 - DOORS Interface demonstration! Starting with new document (new Formal Module)
Rational Developer for System z (v9.0.1): Integrated Debugger- This video features the new Integrated Debugger that is part of Rational Developer for System z, version 9.0.1. This debugger is much more than your typical debugger. In this video you'll become familiar with the debug perspective, learn how to submit a job in debug mode or code coverage, access the full feature editor, step through a program, add, monitor, filter, label and search for variables and breakpoints, work with complex variables, easily navigate large programs using the Outline or Program Code Flow views, and use Monitor memory to display results in different formats.
After the wizardry of my previous post, where you learned how to install the Rational License Key Server Administration and Reporting Tool by using the IBM Installation Manager wizards, let’s now slay some demons! In this post, I will help you understand how a typical licensing model works and how, specifically, the Rational licensing model is designed, complete with daemons!
A licensing model generally consists of:
an application that needs a license, and
a license file that contains the license information.
The license file defines what software or features the license is for, how long it is valid for, how many users can use the software, the computers on which the software can be used, and so on. The license file can be stored locally on the same computer as the application, or on a remote license server. In a served license model, where licenses are stored and served from a common license server, the applications that require a license connect over a TCP/IP network to obtain the licenses from the license server. Rational Common Licensing supports both options local license file deployment and the served license model.
The Rational Common Licensing model consists of the following components:
Rational client application – the application under use that requires a license, for example, a Rational product such as Rational Focal Point or Rational Functional Tester
Rational License Key Administrator – GUI-based client application to import and install licenses, and to configure license servers
Rational License Key Server – server application to host license files
Optional: Rational License Key Server Administration and Reporting Tool – use to remotely administer your Rational License Key Servers and to generate reports on license usage data from the license servers.
When you purchase an IBM Rational product, you receive a license entitlement that authorizes you to generate and download license files from the Rational License Key Center. The Rational License Key Center is an online service that you use to create license files (.dat, .upd, .txt) for the application or applications that you have purchased, or in IBM parlance, “have entitlement for”. As I mentioned earlier, the license file:
contains license data for one or more products or product features
specifies the period of use or validity of the license
applies to the machine where your Rational License Key Server or your licensed application is hosted. If you change the computer where your license key server is hosted or your client application is installed, you must get an updated license file that is configured for use on the new host machine.
Tip: Do not change the host name when you migrate your license server from one computer to another. If you do change the host name, be sure to log into the Rational License Key Center, return your existing license and regenerate licenses for the new host computer.
For single desktop applications, you can store the licenses on the same computer as the application. You also have the option to run multiple instances of the application on the licensed computer. For applications that are used on several computers by different users, you can use a served license model. The licenses are held centrally by the Rational License Key Server and served up to requesting applications and users.
Let’s take the help of an illustration to clarify the concept of a served licensing model.
Fig 1: Rational Common Licensing process
Log in to the Rational License Key Center to generate and download your licenses. After you download the license files from the Rational License Key Center, you can use the Rational License Key Administrator (LKAD) to import and deploy the license files to the license server. Depending on your product type, you will need to use different mechanisms to point to the license server:
For Rational products, such as Rational ClearCase and Rational ClearQuest, use LKAD to deploy products for Rational products.
For products belonging to the former Telelogic company, such as Rational Rhapsody and Rational Change, configure the environment variables in the Telelogic license file to point to the license file.
For Software Delivery Platform products such as Rational Functional Tester and Rational Performance Tester, use the IBM Installation Manager > Manage Licenses option.
See the daemons in the illustration? Those two daemons - the lmgrd manager daemon and the ibmratl or telelogic vendor deamon - manage licenses on the license server. The lmgrd daemon runs on the license server. The vendor daemon information is supplied for each application in the license file for the application. The lmgrd deamon handles the initial contact with the client application or the IBM Rational product. It reads the license file, identifies and starts the appropriate vendor daemon, and then passes on the connection to the vendor daemon. The vendor daemon tracks how many licenses are checked out and who has the licenses. An application that requires a license connects to the license server and requests a license. The license server provides a license based on the availability of the license. The daemons write information about license usage to the lmgrd.log file. The License Key Server Administration and Reporting Tool uses the information in this log file to generate reports on license usage.
That, in a nutshell, is an overview of the Rational Common Licensing model. In my next post, I will pick up from where I ended here, and describe how the License Server Administration and Reporting Tool uses the log data and works with the license servers to generate reports.
Additional reading: If you are interested in more information on Rational Common Licensing, read my previous posts on the subject #licensing:
Here's a great new tutorial from TheOnDemandDemoGuy covering theRational Developer for System z (v9.0.1): Integrated Debugger- This video features the new Integrated Debugger that is part of Rational Developer for System z, version 9.0.1. This debugger is much more than your typical debugger. In this video you'll become familiar with the debug perspective, learn how to submit a job in debug mode or code coverage, access the full feature editor, step through a program, add, monitor, filter, label and search for variables and breakpoints, work with complex variables, easily navigate large programs using the Outline or Program Code Flow views, and use Monitor memory to display results in different formats.
Did you know : about a unit of measure defined by IBM to streamline their licensing policies and contracts, IBM define a processor (for the purposes of PVU licensing) as each core on a socket. Specific processor families carry individual weights per core - E.G. a single core Intel or AMD CPU is assigned a weight of 50, while a small Power 7 processor is assigned a weight of 70. As an example, a quad core Power7 chip on a PS700 blade server would constitute 4 x 70 PVU's. The Licensee can deploy software either using Full Capacity licensing or Virtualization Capacity (Sub-Capacity) licensing.
Lets elaborate this, a "Processor Value Unit" (PVU) is a unit of measure used to differentiate licensing of software on distributed processor technologies (defined by Processor Vendor, Brand, Type and Model Number). IBM continues to define a processor, for purposes of PVU-based licensing, to be each processor core on a chip (socket). Each software Program has a unique price per PVU. For a complete definition of PVU licensing, please see description of PVU full-capacity and sub-capacity licensing below. For more information about PVUs, see the links under 'Essentials' on the right hand navigation bar.
Processor value unit (PVU) licensing :
You apply the IBM URBANCODE DEPLOY MANAGED CAPACITY PVU LIC license to the IBM UrbanCode Deploy server. Then, the server can run processes. In this case, the agents do not require a license; instead, each PVU license allows the server to use a certain number of agents concurrently. The number of concurrent agents may be limited or unlimited, depending on the terms of the PVU license. If you are using this license scenario and the license server does not have any PVU licenses for a IBM UrbanCode Deploy server, the server cannot run processes.
You can see the type of license that the server is using by logging in to the IBM Urban Code Deploy server, clicking Settings > System Settings and looking at the Server License Type field.
For PVU licensing, the Server License Type field shows Managed Capacity.
For example, in the case of IBM Urban Code Deploy Managed PVU licenses, when the Deploy server is started up it retrieves a PVU license. The number of PVU licenses required to run Deploy is dependent on the Machine/underlying server on which the deploy server is running . For example, if the Deploy server has been installed on a Quad code(4cores) processor, then the calculation would be based on the type of processor multiplied by the value required for each core (Note: The value for each core would be dependent on the processor manufacturer and model, refer the data-sheet for full listing).
This model of licensing is best suited for CLOUD and Virtualized environment, where there is a huge deployment of servers, and multiple servers are running same application. In such a environment the control of how many cores a application would use would be regulated by the relevant virtualization technology. For example :- Hyper V for Microsoft based Virtualization, and V-center for ESX based Vmware virtualization. However, if there is lesser number of cores being used than the full capacity, the licensing administrator should refer the table to ascertain how many PVU units are required to be deployed on the license server.
For example:- If on a Server machine, there are 10 Server sockets, each capable of handling a Quad core processor, the effective number of cores which the server machine can handle is 10x4=40. However, 40 cores may not be fully dedicated to one single application, and the licensing administrator may use the relevant virtualization console to cap the number of cores required for running the application, lets say 20 cores for Urban Code. In such a case, the administrator shall look up the table to find the relevant value for each core against the model of processor in use and then decide the number of PVU units required for the entire application.
Now once we have ascertained the number of PVU units required for running a specific application, we could deploy it on the IBM Rational license key server(RLKS).
Table of Processor Value Units [PVUs] per core :
The tables below list existing generally available processor technologies only, as of the published date. PVU requirements for future processor technologies may differ.
Processor Technologies for IBM,
Processor Technologies for HP/Intel, Sun/Fujitsu,
Processor Technologies for Intel,
PVU full-capacity and sub-capacity licensing :
Processor Value Unit (PVU) is a unit of measure by which the Program can be licensed. The number of PVU entitlements required is based on the processor technology defined within the PVU Table by Processor Vendor, Brand, Type and Model Number and by the number of processors made available to the Program. IBM continues to define a processor, for the purpose of PVU-based licensing, to be each processor core on a chip. A dual-core processor chip, for example, has two processor cores.
The Licensee can deploy the Program using either Full Capacity licensing or Virtualization Capacity (Sub-Capacity) licensing according to the Passport Advantage Licensing Terms. If using Full Capacity licensing, the Licensee must obtain PVU entitlements sufficient to cover all activated processor cores* in the physical hardware environment made available to or managed by the Program, except for those servers from which the Program has been permanently removed. If using Virtualization Capacity licensing, the Licensee must obtain entitlements sufficient to cover all activated processor cores made available to or managed by the Program, as defined according to the Virtualization Capacity License Counting Rules .
Advantages of Processor Value Units [PVUs] :
- As simple a licensing structure as possible, understanding that simplicity needs to be balanced against precise measurements of the potential value that a customer receives from their middleware.
- Greater flexibility in deploying middleware licenses on servers that use multi-core chip technologies, using sub-capacity licensing where they have partitioned those systems more granularly.
Continued middleware price performance improvements as the underlying hardware performance improves.
One of the queries that I received, while working on IBM Rational Team Concert (RTC) is this:
I would like to change the configured Active Directory (AD) location (domain controller) of the Jazz Team Server.
Can we just change the LDAP Registry Location setting in the Advanced Properties in JTS and do we have to restart the server?
Firstly, I asked the user to confirm that by changing the configured AD location, it does not involve a change in the public URI for the Jazz team server.
(i.e. change in either the fully qualified domain name in the URI or the hostname).
He did confirm that they only want to change to another domain controller running Active Directory and containing the same user information.
No changes in the Jazz Team server location or the hostname.
==> Essentially to achieve this, you must do the following:
1. Change the LDAP location in the Jazz Server properties.
Login to JTS as admin: https: //<host_name>:9443/jts/admin
Go to server --> Advanced Properties;
Look for these two services and update with the latest parameters: -----
2. Change the LDAP host in Websphere Application Server (WAS).
3. Redo the Security role to user/group mappings in WAS because of the realm change.
While working the front lines in support over the past 16 years of my career, a small handful of issues always seem to crop up as the most requested items when clients call in. One of those items was consistently in depth question on how to setup SSL for any of the products I was supporting. So, of course I'm going to highlight an SSL article when it comes across my plate, as I know how important these types of setups are to you, or clients, with a focus on ensuring your environment's security.
Luckily, John Chewter, Chief Architect for Green Hat Technologies in IBM has written a wonderfully detailed article on developerWorks outlining this process for IBM Rational Integration Tester:
Using SSL within Rational Integration Tester- Overview of key material, the SSL handshake, and its use in Rational Integration Tester transports. Learn how to configure SSL and use the key material in IBM® Rational® Integration Tester to test and virtualize secure services.
Summary: This article explains the various key material types and how they are used within Rational Integration Tester so that it can connect to and test applications secured using SSL. In Part Two we explore how to use the HTTP(S) proxy server to record and re-route secure traffic by using existing key material, or by using the certificate and key that is included in the HTTP proxy server, within the Rational Integration Tester Platform Pack.
Over the course of 10 weeks in Q4 2013, developerWorks Rational featured a modeling tip for systems engineers each week from Bruce Douglass. Undeniably, Bruce's 35 years of experience and credentials make him the perfect person to provide this information, and he does so with humor- which makes it all the more fun. We think these are some fabulous hints and tips and hope you find these tips helpful in your daily work as well:
#4 Design patterns reuse proven solutions- In hint #4 of Bruce Douglass' top 10 modeling hints series you'll learn about the importance of leveraging the experience and knowledge of other designers through abstraction or design pattern reuse.
#5 Only 4 (+1) diagrams are required- Your article abstract goes here. Put the main points and key phrases at the beginning of the abstract, because it will be truncated in search results. Make your abstract enticing yet succinct. Aim for three to five sentences that express why the reader would care about the content (motive) and what he or she can gain from reading the content (benefits).
#9 All models are abstractions but some are useful- System engineers have responded to the need for more rigor by adopting the UML and SysML standards. The standards are complex, and don’t provide guidance on how best to apply modeling techniques with these languages to effectively specify requirements and architectures, nor how to use modeling to perform trade studies and the various kinds of analyses required by systems engineering. Dr. Douglass has spent more than 30 years consulting on hundreds of project. He shares his observations and deep experience in this list of his top ten hints for model-based systems engineering.
#10 Forget 7 ± 2- System engineers have responded to the need for more rigor by adopting the UML and SysML standards. The standards are complex, and don’t provide guidance on how best to apply modeling techniques with these languages to effectively specify requirements and architectures, nor how to use modeling to perform trade studies and the various kinds of analyses required by systems engineering. Dr. Douglass has spent more than 30 years consulting on hundreds of project. He shares his observations and deep experience in this list of his top ten hints for model-based systems engineering.