Those of you interested in learning more about extending, integrating and adopting Systems and Software Engineering solution should check out my colleague’s blog. Stefan is in IBM Services and writes about his experiences here. http://rtcpractise.wordpress.com
Rational Engineering Lifecycle Manager has just EGA’d v4.0.6!
You can learn more on the following Web Sites:
1. Shutdown DWA, Derby, Interops and Broker (user desktop shortcut)
2. You must stop the DOOR DB server, kill it from the task manager
3. Backup folder C:\Program Files (x86)\IBM\Rational\DOORS\9.5\certdb
4. Update and replace the 4 server_* and 4 client_* files into the C:\Program Files (x86)\IBM\Rational\DOORS\9.5\certdb folder the following files:
5. From Services start the DOORS DB server again.
6. Start Broker, Derby, Interops and DWA (use desktop shortcut)
If you don’t have updated keys above you can also solve this issue by setting the secure key (on regedit) to “off” instead on “on”.
Rational SPARQL Gateway
SPARQL is a querying language for RDF databases analogous to SQL for relational databases. Its power lies in being able to query across RDF artifacts and their relationships that span multiple repositories. RELM supports SPARQL v1.1. Many of the SSE customers are interested in reporting on or exporting cross domain artifact reports in PDF, Excel or CSV format. One of RELM’s core capabilities is to provide near real-time reporting across tools and repositories. The SPARQL Gateway component included with RELM allows you to create reportable XML data sources the from the RDF results returned by the RELM SPARQL queries. Additionally RELM allows you to deploy Rational Publishing Engine (RPE) templates that format these XML data sources into reports that can be easily printed or exported to CSV, Excel or PDF formats.
Tip: For historical or trending reports consider Rational Insight. Also consider existing reporting technologies within each SSE product
Tip: When configuring SPARQL_Gateway for the RELM (https://hostname.com:9443/relm) you get the following error when trying to generate a RELM Report
500 (null):CRCPD1006E The LQE endpoint is not defined in SPARQL Gateway
Problem is probably caused by not having Endpoint URL set. Go into LQE and set the end point URL. It should look like https://yourhostname.com:9443/lqe/sparql
I am happy to share the availability of the Tracked Resource Set Software Development Kit that supports Rational Engineering Lifecycle Manager (RELM) V4.0.3. which support TRS v1 draft specification plus errata. There is a technical article on Jazz.net that shows how to use the reference implementation TRS provider for Bugzilla. The article is titled
Setup Rational Engineering Lifecycle Manager, Lifecycle Query Engine,
Jazz Team Server and Tracked Resource Set Provider for Bugzilla
Anyone who uses TRS SDK can get support from the Eclipse Lyo Community. IBM Customers and partners who have purchased RELM and use the TRS SDK can also use the Jazz.net forums to get assistance.
Both the TRS SDK workshop and the Jazz.net article don’t include references to or implementations for Access Control Protocal which describes how to control access to the data and resources published to RELM/LQE. The ACP specification is still in draft and requires additional review.
Many of your product lifecycle resources are locked away in vendor proprietary databases. This often prevents them from being reused and often results in wasted duplication and as a results longer times to market. I think IBM and Rational have come up with an interesting way to make these resources be available in an open and scalable way using OSLC, Tracked Resource Set (TRS) Provider using a Linked Data approach and standards. To accomplish this resources must be exposed using Web Application/Sever. So traditional client only or file based tools require a Web Server be build or these files be hosted on a one that supports being a Tracked Resource provider like Rational Asset Manager that can do that for Word, PDF, Excel and other file based artifacts. Or you can build your own using this TRS Software Development Kit (SDK) Many of the IBM Rational Tools already provide support for Tracked Resources. I recently published which ones here. The same rules apply though so for DOORS you must utilize DOORS Web Access to expose your as searchable tracked resources. For Rhapsody you must utilize Rhapsody Design Manager to expose your Design Elements as searchable tracked resources.
Here are the high level steps to expose these different servers as TRS providers.
- If the Rational Team Concert, Rational Quality Manager, etc. project area is on a separate RTC application on a separate JTS server you must create a JTS OAuth Friends relationship between the two JTS servers, using Oauth keys.
- Create a project area association between RTC and RELM
- Create a LQE Data Source for RELM server for the new RTC instance.
- Create user ids and roles that can access the data on both JTS instances.
- Ensure there is a lqe_user license on the new RTC instance to work with the LQE indexer.
- Create the the Data Source for the TRS provider in Rational Engineering Lifecycle Manager (RELM) Query Engine.
- Use RELM to search, reuse and do impact analysis on your product lifecycle resources.
Here are some recent bumps I hit setting it up. I hope this can help others in case they hit the same issues which are being addressed. There were two problems and two work arounds.
1. Error WARN com.telelogic.festival.generalservices.util.UriUtils – [Message:Unable to convert to legacy format because the doors resource url <doors://>” DWA installation was failing because InfoCenter command example didn’t work in dbadmin example below. The reason that the dbadmin fails silently when a copy and paste of the command was done was because some of the characters when copied and pasted do not end up as the right ASCII characters that the command expects for switches. For example, the double quote (“) character surrounding the dcnChannelName value ends up to be the wrong ASCII character when pasted and has to be replaced with a (“) character to make it work. It does not return an error message when the wrong character is encountered. . Work around was to enter or type quotes in and one dbadmin command at a time.
2. DOORS TRS Authentication using JTS OAuth was failing because DOORS TRS was returning mixed case in server token names back to LQE. Work around was to create all data sources in RELM LQE for token and authorization URLS using lower case.
I am pleased to announce the availability of a DOORS Next Gen Technical Article on Jazz.net https://jazz.net/library/article/1243 The article is titled “Exporting from Rational DOORS and importing to Rational DOORS Next Generation by using ReqIF” and is for users of IBM Rational DOORS 9.5 and later who want to adopt either IBM Rational DOORS Next Generation 4.0.1 and later or IBM Rational Requirements Composer 4.0.1 and later for selected new projects.
For certain projects, you might want to seed a Rational DOORS Next Generation or Rational Requirements Composer project with information from a Rational DOORS project. To do so, you can export modules from Rational DOORS to Rational DOORS Next Generation or Rational Requirements Composer by using Requirements Interchange Format (ReqIF).
Shiv Kumar Singh is a member of the SSE Jump Start Team, and leads the early adoption program for Rational DOORS Next Generation. The SSE Jump Start Team assists ISSR, CTPs, and IBM partners and customers with PoC and PoT related to SSE Solutions, including the Rational solution for Collaborative Lifecycle Management (CLM) products, Rational DOORS, Rational DOORS Next Generation and Rational Engineering Lifecycle Manager. Prior to this role, he helped several IBM customers adopt many SDLC processes and IBM Rational tools. He can be contacted at firstname.lastname@example.org