SSLHandshakeException in RPE 2.1.2

SSLHandshakeException exception is noticed with RPE 2.1.2 while connecting to DNG, RTC, RQM in few environments. This is happening due to the mismatch in ciphers.

One way to fix it is to add cipher supported in RPE into CLM. See http://www-01.ibm.com/support/docview.wss?uid=swg22007595 for details.

Another way is use swap JRE directory from RPE 2.1.1 to RPE 2.1.2. The jre direction is found in RPE_INSTALLATION_PATH directory.

Advertisements

Sample assets in RPE Document Builder

Out-of-the-box sample assets have been available in the Rational Publishing Engine (RPE) Desktop installation of RPE Document Studio and RPE Launcher for many versions. These sample assets are now included within RPE Document Builder 2.1.1.

Find details at https://jazz.net/blog/index.php/2017/01/19/sample-assets-in-rational-publishing-engine-document-builder/

 

Generate documents from fine-grained components

Rational Publishing Engine (RPE) 1.3 and above was already capable of configuration-aware document generation. With Collaborative Lifecycle Management (CLM) 6.0.3, we can use configurations of separate components in the project area to achieve re-usability. Rational DOORS Next Generation (RDNG) and Rational Quality Manager (RQM) offer the reusable solution. With RPE 1.3 (yes, 1.3) and above, we can generate documents by selecting the configuration of a component through RPE Launcher (desktop application) and also from RPE Document Builder (Web application) while configuring the template data source.

Find more details at https://jazz.net/blog/index.php/2017/01/16/generate-documents-from-fine-grained-components/

 

Reporting Labs at IBM ICE-IoT 2016

Reporting Labs are scheduled at ICT-IoT.

  • November 16 – 18, 2016 8:30AM to 5 PM.
  • Labs are self-paced with workbooks
  • SMEs will be present to answer any questions

Report Management Labs

  • Lab IOT9667 – Cross lifecycle project analysis with RELM and JRS
  • Lab DEV9311 – Insightful Reporting Using IBM Collaborative Lifecycle Management
  • DMT 3722 – Learn to Use Rational Publishing Engine to Create Custom Reports from Rational DOORS Next Generation
  • Publish Your Rational DOORS Requirements with RPE

Configuration Aware Document Generation

RPE 1.3 and above is capable of generating configuration-aware document from CLM environment with Configuration enabled.

My colleagues Sunil and Dragos have put a video that explains document generation from RPE desktop client and RPE Web document builder.

Find documentation related to configuration-aware below.

Setting up data source with config-aware

Discovering OSLC resource for GC Continue reading “Configuration Aware Document Generation”

Understanding type of the model from DM

While building a cross product template from DNG to Design manager, the derived by attribute links to model diagram from Design Manager. How do you know whether it is a use case diagram or sequence diagram or something else?

If you make a GET request to DM model OSLC  / permanent URL (https://server:9443/dm/models/_Eea40KY8EeWtTLergOJe7g~OLDID__6018453__1) with Accept header as application/rdf+xml, you get OSLC representation of the resource. Looking at RDF/Description/type@resource attribute mentions whether the model is a use case or sequence diagram or etc. Continue reading “Understanding type of the model from DM”

OSLC API and POX Profile simplifies CLM traceability

Further to OSLC + POXProfile post, RPE 2.1 with CLM 6.0.2 simplifies the data source configuration; especially while configuring dynamic data source for traceability reports.

Use OSLC / Permanent link for configuring the data source URL without having to modify the URL manually or through JavaScript. This simplifies the data source configuration to a great extent as the Permanent / OSLC links are available to the user from the product UI.

Watch video, created by Dragos, on requirement (DNG) to use case design (DM) traceability document generation using Permanent / OSLC links from DNG and DM without having to go through building Rest URL. Continue reading “OSLC API and POX Profile simplifies CLM traceability”