Anisat Simmons 060000HJHP Visits (13152)
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
Sizing recommendations for planning migration of data from Rational DOORS to Rational DOORS Next Generation
paulellis 270001KTVW Visits (11058)
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.
AcdntlPoet 2700019V2G Visits (8946)
Continuous Engineering for the Electronics Industry- See how IBM continuous engineering solutions can help you tackle the challenges and opportunities of Mobile, Internet of Things and Software and help you Define better, Design Faster, Develop Smar
Learn more about the IBM Internet of Things Continuous Engineering Solution: Tools, best practices and services to help organizations create the connected products at the heart of the internet of things. The IBM Internet of Things Continuous Engineering Solution is designed to help manufacturers create smart, connected devices for the Internet of Things. This solution helps teams adopt continuous engineering practices to address cost, time and quality challenges in delivering complex, connected products. IBM is now adding new product line engineering (PLE) features to help engineers streamline the design of product lines while reducing data duplication and the chance of design errors.
And don't miss the featured white paper: The
dmmckinn 1200006SCS Visits (3543)
Do you need extra assistance deploying IBM software that has been sitting on the shelf? Need assistance with managing your upgrades? Would it help to have a single point of contact within IBM Support who can help you connect with a team of subject matter experts? If you are struggling to manage your IBM Software deployment with limited resources, the Accelerated Value Program (AVP) may be able to help.
So, what’s in it for me you ask?
If you plan on attending the upcoming TRIRIGA University event on November 28-29, you can learn more by attending the Accelerated Value Program session hosted by our AVP Program Director, Betsy Autry. Further information and registration details are available in
dmmckinn 1200006SCS Visits (5560)
New videos are available for the latest 6.0.6 version of IBM Jazz Reporting Service.
mccarron 060001KYG9 Visits (6285)
CLM 6.0.5 iFix002 was made available for download on January 26. This iFix contains fixes for 71 defects broken out for the following products:
For information about downloading this fix (and fixes available for other versions) please go here.
AcdntlPoet 2700019V2G Visits (6123)
CLM configuration management: Adoption guidance and practices - After you determine whether your organization would benefit from configuration management, you need to evaluate your existing processes and determine how they will change to reflect the new concepts and operations. This article guides you through important considerations for adopting configuration management. See the related articles for additional details about practices and decisions points.
CLM configuration management: Defining your component strategy - Components typically represent physical or logical subdivisions of your product or system. A
CLM configuration management: Patterns for stream usage - This article introduces several patterns of stream usage, or stream strategies, which are described in more detail in additional linked articles. You should already be familiar with the configuration management capabilities, and have decided to investigate further. For the introduction to this series, see Adoption guidance and practices. As part of planning your adoption of configuration management you need to determine your stream strategy.
CLM configuration management: Single stream strategy - Use the single stream pattern for basic change management that’s only in a single domain application (that is, requirements or tests or designs). Typically you use this pattern with the Requirements Management (RM) or Design Management (DM) appl
CLM configuration management: Multistream variant strategy - This article discusses patterns of stream usage for situations where multiple variants of lifecycle artifacts need to be maintained in parallel for each of several releases. This is a common need of product-centric organizations. These and other patterns – including several that these patterns build on – are introduced in the companion Patterns for stream usage article. Read about these base patterns before you read this article. You’ll also find links there to the other stream pattern articles in this series.
CLM configuration management: Multistream concurrent release development strategy - This article explores patterns of stream usage for situations where you work on multiple releases of a product concurrently. Many organizations find these patterns useful on their own. These patterns also form the basis of the more complex multistream variant patterns, as explained in the Multistream variant strategy article. Many patterns are introduced in the companion Patterns for stream usage article. That article in turn points to the other stream details articles in this series. We suggest you read about the more basic patterns, such as the single stream strategy, before you read the current article. The patterns we present here are relatively complex. If an opportunity to “go simpler” presents itself, even for a single component, we encourage you to do so. For example, if you can build and maintain a reusable component of regulatory requirements using a single-stream pattern, rather than one of the multistream patterns, by all means use the simpler pattern.
What else did we improve in Collaborative Lifecycle Management 6.0.5 - key updates for client experience
paulellis 270001KTVW Visits (7414)
On December 4th 2017, we announced Now
The list below focuses not on the new product features, but instead, the key wins in the 6.0.5 release which will make life better for users and administators in particular.
There were two main focuses to address the complexity of backup strategies. There is now an inte
Typically, like buses, two articles are now available. We wrote a specific article on back
We now strongly encourage you to backup your DOORS Next Generation indices so as to lessen the likelihood of needing to run a repotools reindex.
Windows VM users can now consider using alternative performance settings for DOORS Next Generation
We have focused on DNG backup strategy mentioned above, so as to ensure that we do not need to run repotools reindex. This was in part prompted by the desire for Windows Virtual Machine(VM) users to be able to use a DNG
Guidance on adopting IBM CLM configuration management across the lifecycle
During the same time frame, there was a large intiative to provide guidance on adopting CLM lifecycle configurartion management. Tim Feeney's blog explains the new Bes
Validating and documenting on WebSphere Liberty Profile and Jazz Authorization Server (JAS)
It is now possible to authenticate using Smart Cards, or certificates (.p12) with Liberty:
and with JAS, see related article: Conf
We have also improved the formal IBM Knowledge Center on these topics, cross-linking so you don't need to find these additional resources: Conf
Last but not least, Mul
In a preview, an expert guides you step-by-step through the various products in the IBM IoT continuous eng
Jazz Community sharing site:
A big thank you to the German User Group for creating a new public sharing site available to everyone - see Rolf Nelson's Intr
Romain_Barth 2700076HKB Visits (8397)
Links between DOORS 9 and DNG use Link Discovery.
The link is stored in the source application and is discovered by the target application so :
You should see the "discovering Links" indicator during the process