Anisat Simmons 060000HJHP Visits (12477)
IBM Watson IoT Support Lifecycle Resources
IBM provides advance notification of End of Support (EOS) dates allowing customers reasonable time to complete software upgrades or to refresh application products. EOS announcements are made in April and Sept.
Announcement letter dates are U.S. only. Information for other country announcements is available on the IBM Offering Information page. Select the date to view the announcement letter. Note that some product versions may not have online announcement letters.
View all IBM Software EOS announcements for 2016 and 2017.
This section describes some of the standard and enhanced IBM Software Support Lifecycle Policies and common questions. Additional details and answers to commonly asked questions regarding the Support Lifecycle Policy can be found on our Frequently Asked Questions page.
Q: What are the major Support Lifecycle milestones?
A: The major Support Lifecycle milestones are:
Q: How do you determine if your installed software is still supported?
A: Search by product name or keyword using the Supp
Q: What happens when EOS is announced?
A: Often, there is a newer version of the software available for download. In most cases, you’ll have sufficient time to plan for and install the latest version. For more information on the lifecycle stages, including EOS, view this short YouTube video on the IBM
Q: What is the standard version format for IBM Software products?
A: The full product version is expressed by a four-digit code known as the IBM Version, Release, Modification and Fix Level structure, or VRMF. View this Technote for additional information and description of each element. You may also find this Glossary of product support and maintenance terms helpful.
Q: How can you connect with Watson IoT on social media?
Q: Where can you find more information on IBM Support policies?
A: You can view and download the IBM
Romain_Barth 2700076HKB Visits (12254)
From DOORS 126.96.36.199 and RQM 6.0.1, it is possible to use link discovery instead of back linking.
With link discovery, links from RQM to DOORS are only stored in RQM. When opening a module in DOORS, it will query RQM to display the links.
With this feature, RQM does not need to acquire a lock on requirements to create a link, so it reduces conflict between RQM users and DOORS users.
In this article, you will learn how to enable this feature.
1-Case of a new installation
You just installed DOORS/DWA 188.8.131.52 and RQM 6.0.1.
2- Case of an upgrade
After upgrading DWA to 184.108.40.206 or/and RQM to 6.0.1, you have to perform the following steps :
AcdntlPoet 2700019V2G Visits (11286)
Highlights of CLM 6.0.3 - I’m pleased to announce that Collaborative Lifecycle Management (CLM) 6.0.3 is now available for download — along with IBM Internet of Things continuous engineering solution 6.0.3, which is a superset of CLM. Our largest focus area this release has been improving simplicity and productivity for practitioners. You’ll see that in these highlights [Read more...]
What’s new with SAFe® in CLM 6.0.3 - It’s official. IBM’s support for Scaled Agile Framework® (SAFe) 4.0 is now “in the box”! You can read more about the highlights of the Collaborative Lifecycle Management (CLM) 6.0.3 release in Daniel Moul’s blog: Highlights of 6.0.3. We’ve been working diligently with several early adopters who have provided great feedback since we posted the first beta templates back in March. That early feedback has led to some great improvements — thank you all for contributing to make the SAFe support better. Next up: reports and videos. [Read more...]
What’s new in Rational DOORS Next Generation 6.0.3 - IBM Rational DOORS Next Generation (DNG) 6.0.3 introduces a new dimension to configuration management a simpler way to interact with requirements information and more. [Read more...]
What’s new in Rational Team Concert 6.0.3 - We’ve been busy with key enhancements to IBM Rational Team Concert 6.0.3 including enterprise agile planning with SAFe® 4.0, improved work item collaboration with rich text support and enhanced usability for the Jazz SCM. For more details, see New & Noteworthy. [Read more...]
What’s new in Rational Quality Manager 6.0.3 - In this post, I am going to highlight three key enhancements to IBM Rational Quality Manager 6.0.3 that will make a difference for many of you: customization of manual test scripts, artifact comparison, and components. For a complete enhancement list and more details about the content of this release, please see the New & Noteworthy. [Read more...]
What’s new in Rhapsody Design Manager 6.0.3 and Rhapsody 8.2 - IBM Rational Rhapsody Design Manager 6.0.3 and IBM Rational Rhapsody 8.2 are here! As usual, there are many exciting things that have taken place in the area of modeling, or as many call it today, architecture and design management. For a complete list, see the New & Noteworthy for Rhapsody Design Manager and what’s new for Rhapsody. [Read more...]
What’s new in Rational Publishing Engine 2.1.1 - Many organizations must produce documentation from their systems along with software engineering data that meets complex style and format requirements. These requirements might be imposed by clients, business partners, government or industry regulatory bodies. IBM Rational Publishing Engine automates the generation of these types of documents from your data in Collaborative Lifecycle Management (CLM) and other products. In the 2.1.1 release of Rational Publishing Engine, we’ve continued to simplify the user experience with a focus on both template designers and report designers. You can watch demos of these and other new features at the Rational Publishing Engine 2.1.1 YouTube playlist. For more details, see New & Noteworthy. [Read more...]
AcdntlPoet 2700019V2G Visits (11103)
In this two-part blog series, Bruce Powel Douglass, Ph.D.(Chief Evangelist, IBM Analytics) discusses security in the Internet of Things world, both in terms of the connection and well as the devices themselves.
Securing the Internet of Things. Part 1 – Security in a world of connected devices: Time was when smart embedded devices needed little or no security. They were, for the vast majority, disconnected devices that performed simple dedicated functions. Now, as we hear ever more about the Internet of Things (IoT), it seems everything is connected over the web. Washing machines are connected over the web. This allows unprecedented capabilities for both consumers to connect and manage their lives and for vendors to improve services, monitor usage patterns, deliver updates, and address emerging markets. It is not, however, without risk. [Read more]
Securing the Internet of Things. Part 2 - Securing the ‘Things’ of the IoT: In my last post I discussed the overall challenges of securing the Internet of Things. In this post I focus primarily on the "Things" of the Internet of Things. Certainly securing the cloud end is important as well, but there has always been far more emphasis on cloud security than on device security. I think there are a number of essential aspects of a development environment for designing secure systems [Read more]
paulellis 270001KTVW Visits (10579)
On April 25th 2016, IBM released Collaborative Lifecycle Management 6.0.2. In Moshe Cohen's blog
One of those highlights was:
And Moshe said:
Maybe it's a coincidence, but a lot of upgrades have occurred in the last few months.
Unfortunately, not all of them have gone as smoothly as they could have done.
Why are people finding that their upgrades are not wildly successful?
This, for me, is particularly frus
We also published a useful blog post "Planning your CLM upgrade?" to help find information about the latest available fixes and system requirements; and Dan Toczala wrote a
All of which was great, but do we just have too much information in too many places?
What we have missed all this time is a single entry point to our expansive library of information relating to your specific upgrade - in a single page!
In order to have a positive upgrade, where success is planned in from the start, a simple, handy checklist is required.
One, simple, must
This checklist includes simple links to assist with obtaining all the information required for each of the key areas of an upgrade:
* Upgrade Testing
* Software Licenses
* Server, infrastructure and performance considerations
* Latest Upgrade flashes and news per CLM application
* Ways to contact us so we can help
* Additional pertinent links/information
We are strongly recommending that this be the starting point of every CLM upgrade. Please also give us your feedback if you believe something is missing.
AcdntlPoet 2700019V2G Visits (10543)
Getting started with reporting by using Lifecycle Query Engine data sources in version 6.0.3: You can use the Report Builder in the Jazz Reporting Service to create and run reports about artifacts across projects or versioned data in configurations. Using indexed data from the Lifecycle Query Engine (LQE) data sources, you can, for example: Create a multi-project report that shows test cases, the requirements that they validate, and related defects. You can include designs from Design Manager by editing the SPARQL query in the Advanced section of Report Builder. Run this report, scoping the results by choosing a configuration (stream or baseline). Learn how to set up your environment and understand some of the limitations when you use either the LQE or LQE using Configurations data source. Consider the limitations described here before you use LQE data sources for production reports. If you are interested only in document-style reports, you can export Report Builder reports as Rational Publishing Engine templates to make document authoring easier. [Read more at Jazz.net...]
Authors: Catherine Trinkwon, Information Developer, with contributions from the Jazz Reporting Service team at Persistent Systems Ltd.
Sizing recommendations for planning migration of data from Rational DOORS to Rational DOORS Next Generation
paulellis 270001KTVW Visits (10468)
Are you considering migrating your data from Rational DOORS to Rational DOORS Next Generation(RDNG)?
Are you looking for guidance and best practice before you begin to be successful first time?
If so, then your starting point is definitely the detailed guidance on developerWorks on how to Migr
New Sizing and Best Practice Guide on Jazz.net's Deployment wiki
Since the developerWorks article was published, we realized that more detailed sizing information was required prior to executing the migration of data packages from DOORS 9 to RDNG. We collated pertinent sizing information from the Rati
There are significant improvements to the import timings with RDNG 6.0.2 release, so please refer to this article if you are evaluating an existing or future migration as this could indeed be an influencing factor.
The document details:
Sizing Guidelines for Rational DOORS Next Generation 6.x
Recommendations on the maximum sizes of your modules, projects and repositories so as to maximize your success when importing your packages and working in the future within RDNG.
The considerations for hardware are simplified from guidance published elsewhere in the Deployment wiki, but here they are explained within the context of how to plan for your new world.
Guidance on how to convert your Rational DOORS modules prior to migration
Invariably there will be modules and projects within DOORS 9 which will not match up to the guidance prescribed for RDNG. Use this section to understand how to easily manipulate your data before migrating.
What if the data to be migrated exceeds the recommendations?
The guidance is clearly aimed for the general use cases and is very much our strongest recommendation.
It is understood that there are very large enterprise requirements management estates out there. It is recommended that you contact IBM if this applies to you.
Romain_Barth 2700076HKB Visits (10384)
DOORS 9 - RQM integration : How to update link properties in DOORS after renaming a test case in RQM
After creating a link from RQM artifact to DOORS requirement, if you change the name of the RQM artifact (test case or step of test script), this change is not updated in DOORS : the link description and title in DOORS are still referring to the old name of the RQM artifact.
This is working as designed when the integration between DOORS and RQM uses back-linking (in other words: 2 links are created, 1 in DOORS and 1 in RQM)
There are 2 ways to correct this issue :
- Manually edit the link description in DOORS
- Run a DXL script on your DOORS module that will query RQM to gather the name of the RQM artifact for each link to RQM in the module. Then it updates the description and title of those links.