DOORS Next Generation (19)
Introduction At Softacus, we constantly strive to improve products and services. A very important part of the services offered for your infrastructure is monitoring. In addition to monitoring the basic system parameters of servers/VMs/ESXi, we offer the possibility of monitoring the IBM Jazz platform and its individual applications. This page aims to provide you with information about monitoring options for your IBM ELM applications and infrastructure. By being our customer, you have a unique opportunity to start monitoring your infrastructure at a high level. We can monitor the infrastructure that we manage - Softacus (local), or we can even set up the monitoring in the infrastructure that is deployed in your internal environments.
DOORS Next provides great functionalities for managing requirements within your team, but as your project grows sooner or later you need to export and import the data using external formats. For DOORS Next data the first format to think of is project template (or component template, in case if configuration management feature is enabled in RM). Content of template can be set up to include different types of data but all items of included types will be included to a template (e.g. you can include artifacts to a template - and it means that all folders will be added to a template). Another option is the ReqIF package - it allows interchange requirements between requirements management platforms which are compatible with ReqIF, with more data selection options (e.g. you can include only certain artifacts or modules). CSV/spreadsheet format is also an option to export and import data to DOORS Next,…
Introduction The history is an important part of the requirements management tool and the purpose of this article is to explain functions and capabilities of DOORS Next for working with history of requirements. Artifact revisions On the very basic level history of requirements management items in DOORS Next is organized on artifacts level and is presented as revisions and audit history. This information is accessible for artifacts via ‘Open history’ action in the menu (Figure 1). Figure 1 The first tab you see when you open history is ‘Revisions’, it is splitted on ‘Today’, ‘Yesterday’, ‘Past week’, ‘Past month’ and ‘Earlier’ sections which include different versions of an artifact and baselines of project area or component. When you switch to the ‘Audit history’ tab you see only versions of a current artifact with explanation of actions performed on it and changes which were created with information on date…
Introduction IBM® Rational® DOORS® Next Generation is consistently one of the best requirements management tools out there. One of its biggest strengths is the opportunity to expand its capabilities by the people using it, so that they can utilize it to its fullest. Whether you are someone who already uses IBM® Rational® DOORS® Next Generation on a regular basis or someone who is considering using it, the knowledge of how you can optimize your work environment is the key to peak productivity in the workplace. Purpose of the article - OS Gadgets This article will be delving into how you can extend IBM® Rational® DOORS® Next Generation behavior with JavaScript, in particular we will be focusing on OpenSocial gadgets (widgets that are created following OpenSocial standards), as DOORS Next offers its users a JavaScript API which enables OpenSocial gadgets to automate intricate operations and work with the requirement data. Here…
Introduction The history is an important part of the requirements management tool and the purpose of this article is to explain functions and capabilities of DOORS Next for history maintenance. The Challenges to Managing History in DOORS Next Generation On the very basic level history of requirements management items in DOORS Next is organized on artifacts level and is presented as revisions and audit history. This information is accessible for artifacts via ‘Open history’ action in the menu. The first tab you see when you open history is ‘Revisions’, it is splitted on ‘Today’, ‘Yesterday’, ‘Past week’, ‘Past month’ and ‘Earlier’ sections which include different versions of an artifact and baselines of project area or component. When you switch to ‘Audit history’ tab you see only versions of a current artifact with explanation of actions performed on it and changes which were created with information on date and time and…
DOORS Next provides great functionalities for managing requirements within your team, but as your project grows sooner or later you need to export and import the data using external formats. For DOORS Next data the first format to think of is project template (or component template, in case if configuration management feature is enabled in RM). Content of template can be set up to include different types of data but all items of included types will be included to a template (e.g. you can include artifacts to a template - and it means that all folders will be added to a template). Another option is the ReqIF package - it allows interchange requirements between requirements management platforms which are compatible with ReqIF, with more data selection options (e.g. you can include only certain artifacts or modules). Excel/CSV format is also an option to export and import data to DOORS Next,…
So you have applied the latest iFix as that is the best praticse for your CLM/ELM environment just to find out your widgets have stopped working and you cannot find what could be the cause of the problem? With the new iFixes starting from versions ELM 7.0.2 iFix004, ELM 7.0.1 iFix009, CLM 6.0.6.1 iFix018, and CLM 6.0.6 iFix022 the IBM has implemented new security measures to prevent Server-Side Request Forgery (SSRF) vulnerabilities.This measure has changed the behavior of all OpenSocial gadgets and RSS feeds that fetch content from an external service or location which results in errors when trying to add widgets to your side-panel or dashboard that worked flawlessly before. Solution? In order to fix this issue and get your widgets working again you need to add the location (URLs) of your extension hosting servers into jazz "allowlist" first.You can find the allowlist in JTS application in Admin menu.…
For completeness, the DNG public API's that are available are: RDNG Reportable API - extracting read only information from RDNG generally for creating custom reports to be run from DNG or RPE. As well, it can be used in a lot of custom applications interacting with RDNG. Big advantage of this API is its simplicity and great performance if you need to work with big amounts of data. Sometimes it's called as RDNG Reportable REST API. OSLC RM V2 API - the open standard way to programmatically integrate with DOORS Next Generation, there is an elaborate workshop to get you started here OSLC Workshop article. These programs can be from any language that supports various HTTP methods of requests, e.g. Java, C# etc. Hence these are more flexible to run and can read and update DNG data, as part of a web server, or standalone, but have some limitations set by the current OSLC standard, for example…
Tracked-resource setsThe tracked-resource set (TRS) specification allows a server to expose set of resources in a way that allows clients to discover the exact set of resources in the set, to track all additions to and removals from the set, and to track state changes to all resources in the set. This specification is HTTP-based and follows RESTful principles. It is suitable for dealing with large sets containing a large number of resources, as well as highly active resource sets that undergo continual change. When project areas are enabled for configurations, for team members to see, use, create, or remove links across project areas, a Jazz administrator must install the Global Configuration Management (GCM) and Link Index Provider (LDX) applications. Use TRS v2.0 as a data source to create the linked lifecycle data index. When project areas are not enabled for configurations, to ensure that Lifecycle Query Engine (LQE) can access…
You can enhance the Requirements Management (RM) application by authoring extensions for it. The extensions can enhance productivity and are useful for analysis. You can add the extensions to your mini dashboard and remove them as needed. Extensions are authored by using a combination of JavaScript, HTML, and CSS files. The extensions access data within the RM application by using an RM API. This article aims to help you with enabling and uploading the widget extensions in Engineering Requirements Management DOORS Next. Widget Extensions
In Doors NG there are three types of templates - Project Area Template, Module Template, and Artifact Template. All of these templates can be managed on the project administration Templates page. Config. Management enabled = Manage Component Properties --> Templates --> Component or Artifact Templates (in the left sidebar)Config. Management disabled= Manage Project Properties --> Templates --> Project or Artifact Templates (in the left sidebar)
The purpose of this article is to make an overview of options you have when you have a need for reuse of artifacts like requirements, specifications, contracts or event full lifecycle management projects in IBM Rational Collaborative Lifecycle Management Platform (IBM Jazz). This article will be improved several times but the intention is not to describe everything since this is done in the consulting engagement.
This article describes the possibilities you have for the underlying database for Jazz Platform. Compared are advantages and disadvantages between the following databases: IBM DB2 Oracle DB MS SQL Derby (only for non-productive trial use)
This article aims to help the user with the process of deploying templates to the DOORS Next Generation. The official procedure is described by IBM here:https://jazz.net/wiki/bin/view/Main/RRCCustomRRDGReportsWalkthrough In brief, you can deploy the template to DOORS NG easily steps:
Option 1: Project Area or Component Template How to: In the current project go to Project or Component Properties > Templates Create New Click on data which you want to copy (if you click on Artifact then all artifact will be part of the template Create a new project area or component and use a template for creation (template must be downloaded and uploaded if you are porting to a new server) Advantages: Works also for porting to a new server Links between artifacts are kept project area properties are automatically saved Are links within the project area/component are kept
