IBM Rational Publishing Engine Fixes in 1.1.1.2

®

IBM Software Group

© 2008, 2009 IBM Corporation

IBM Rational Publishing EngineFixes in 1.1.1.2

Dragos CojocariSeptember 2010

IBM Software Group | Rational software

Agenda

Installer

Documentation

Memory consumption

Licensing

Data Source paging support

Miscellaneous

PMRs fixed

DOORS 9.3 Secure Mode

2


Installer

“lib” folder Contains all the jar files required to use RPE through its Java API

“utils” folder Refreshed rpe_signed.dot

DOORS Integration Creates “addins” entry in the DOORS registry

If DOORS is installed after RPE than RPE modify/repair installation must be performed and RPE and DOORS restarted

3


Documentation

Content restructured for better role based documentation

Work in progress to add RPE documentation to CLM online help Each point product will contain information on the specifics of integrating with RPE

4


Memory Consumption

Fixed a memory leak affecting Dynamic Data Sources (PM14189)

Console size limit Defined in rpe-launcher.ini and rpe-studio.ini

-Dcom.ibm.rational.rpe.console.limit=100000

If flag removed the entire log is kept in the console view

Does not affect the content of rpe.log

Output buffering default queue size reduced to 20000 from 500000

Various internal optimizations

5


Licensing

TPE_PUBLISH license no longer supported

Supported license servers IBM Rational License Server Telelogic V2.0.0 Multiplatform English eAssembly

(CR8X2EN)

IBM Rational License Key Server V8.1.1 Multilingual Multiplatform eAssembly (CRC6CML)”

6


Data Source Paging Support

Pages in ATOM feeds are automatically recognised and processed by RPE Example: RQM test case feed etc

Pages for OSLC data sources are automatically recognised and processed by RPE Example: RTC workitems list

7


WAS time-out

Feed time-out Can occur on WAS for RQM feeds. RPE will report a “Premature EOF” error

http://www-01.ibm.com/support/docview.wss?uid=swg21320747

Procedure

Start WebSphere Process Server

Launch the administrative console

Set the property

Expand Application Servers

Click on server Name

Click on Configuration Tab

Under Server Infrastructure, expand Java & Process Management

Click on Process Definition

Click on Java Virtual Machine

Click on Custom Properties

Create a new property with

key = com.ibm.ws.security.cacheCushionMax

value = 24

8


Miscellaneous

Java 5 backport RPE ships with IBM JRE 5

Nested containers in tables/rows/lists These containers can now contain other containers

Caching for XML Data Sources Recommended data source type to use for RRC, RQM and OSLC data sources

Dynamic Data Source inheritance DDS can inherit from other DDS now

DOORS 9.3 Fixes for empty lines

Fix for Symbol support

Improved scalability for OLE intensive modules

9


Miscellaneous (continued)

OSLC data sources Can be used if schemas are created manually. Ex: RTC 2.x

Embedded RPE Focal Point 6.5.1

DOORS 9.3 – OOTB templates

Customers using DOORS 9.3 need to upgrade to RPE 1.1.1.2 support for secure mode ( RPE 1.1.1.1 and older cannot work with DOORS 9.3 in secure

mode)

DRML changes - DOORS 9.3 DRML is not handled properly by older RPE versions ( empty lines will be introduced in the output or lines will be incorrectly merged)

enhancements in RPE 1.1.1.2 to better support DOORS

improved scalability for OLE intensive modules

support for symbols

installer fixes

10


PMRs Fixed

11

APARs Description CommentsPM18416 Digital signature for the macros in style sheet rep_signed.dot has expired.

PM19722 DOORS Passwords with special characters will not work with Rational Publishing Engine.

PM19205 Memory exhausted error message while running an extraction from an OLE intensive Rational DOORS module.

Requires DOORS 9.3

PM14075 Header information combined from style sheet and master page.

PM07242 Date pattern property does not work at element level.

PM13545 Inserting a field element adds a space in output.

PM19630 Paragraph or Text border is not applied correctly if there is CR in the object text.

PM13634 Include file page orientation not applied.PM14189 Rational Publishing Engine document generation aborts with error Out of Memory. See “Memory conusmption”

PM10698 Standard doors-structure.dta template when used on a complex Rational DOORS DB Structure, results in errors.

Limit in XSL-FO removed

PM09795 Rational Publishing Engine should not allow the use of variables in master page and style definitions.

PM15586 Performance issues with IBM Rational Requirements Composer schemas and template while using a proxy server

Eclipse networking plugin added to ini files


DOORS 9.3 SECURE MODE

Configuring RPE to run with DOORS 9.3 in secure mode

12


Overview

DOORS 9.3 DXL Security Restriction on the location of include files

Restrictions on the location of DXL files ( batch mode only)

RPE 1.1.1.2 Objectives Run with all previously supported DOORS versions

Run with DOORS 9.3 in unsecure mode

Run with DOORS 9.3 in secure mode

13


Changes in RPE

RPE 1.1.1.1 and older DXL scripts are generated in the user’s temp folder to configure the DXL execution

The temp DXL contains information such as module path, view name, baseline version and the name of the attributes that are to be extracted from DOORS

These scripts will no longer work with a DOORS 9.3 in secure mode

RPE 1.1.1.2 All RPE’s DXLs are static ( deployed by the RPE installer)

RPE provides the runtime details to the DXL environment through an XML file

The path of the XML file is defined in the RPE_DXLARGUMENT system variable

The DOORS addins registry value is updated by the RPE installer to include the path to RPE_HOME

If DOORS is installed after RPE the addins registry key will not be created. You need to create it manually or re-run the RPE installer in “repair” mode and then restart DOORS and RPE.

14


RPE_DXLARGUMENT

When accessing DOORS though COM ( new_instance=false) only one user can run a document generation as there is a unique value for RPE_DXLARGUMENT Accessing DOORS though COM is not supported for concurrency in RPE. This is why

RPE WebService always access DOORS in batch mode

The variable is not used for COM access as the Java code and DXL code assume that the path is %TEMP%\RPE\rpe_doors.xml. This removes the need of creating a new system variable in the user’s ebvironment.

When accessing DOORS in batch mode ( new_instance=true) RPE will generate a unique value for the RPE_DXLARGUMENT for each DOORS process it spawns. This allows concurrent requests to be processed as before. The variable is automatically created by RPE for batch mode (new_instance=true)

The generated value is in the form: %TEMP%\RPE\rpe_doors_<UNIQUESTRING>.xml

The variable “lives” only for the duration of the spawned DOORS process

15


Default installation

Will work as is for DOORS 9.2 and older and for DOORS 9.3 in unsecure mode

Will work with DOORS 9.3 in secure mode if RPE_HOME is in the list of trusted addins location

RPE_HOME is a trusted “batch files path” location

RPE can handle different scenarios as the above is not guaranteed to be the situation in a production environment. A set of 1 time tasks must be performed by the System Admin.

16


Custom installation for DOORS 9.3 in Secure Mode Server side: copy the “Source” subfolder from the RPE Installation folder in one of the “Addins Path”

locations specified in DOORS DB – DXL Security property. As RPE references its included files using relative paths the DOORS DXL runtime will be able to retrieve them.

The folder structure must be preserved. The source folder cannot be renamed

Server side: copy the “Source” subfolder from the RPE Installation folder in the location specified by “Batch files path” property in DOORS DB – DXL Security property

The folder structure must be preserved. The source folder cannot be renamed

Define the RPE_DXLLOCATION ( double L) variable to point to the “Batch files path value”. RPE will then use this location as startup location for its DXLs instead of the default RPE_HOME.

This value can be set through the RPE silent installer

17


RPE_DXLLOCATION

Silent installer example msiexec.exe /i “<path to msi>" /qn INSTALLDIR=“<install dir>" LAPAGREE="Yes"

RPE_DXLLOCATION=“<TRUSTED DXL LOCATION PATH>“

The <TRUSTED DXL LOCATION PATH> Example: \\Arakis\DOORS\trusted_dxl

Must be the same path as the one in the DOORS DB properties

Must be an absolute path ( cannot contain system variables)

Example of bad value: %DOORS_SERVER%\DOORS\trusted_dxl where DOORS_SERVER = \\Arakis

Must be an UNC path. It cannot be a mapped drive letter as drive mappings are user specific and will not work from all user accounts including the Local System account used by NT Services such as the Tomcat service

Example of bad value: Z:\trusted_dxl where Z: = \\Arakis\DOORS

The path must not end with a “\”

18


Running as a WebService

Install RPE 1.1.1.2 on the machine hosting the RPE WebService Define the RPE_DXLLOCATION variable if installation is manual

Deploy the RPE WebService

19


Test Environment

a standard user that has no “Edit DXL” powers

all DOORS DXL security options used

20

IBM Rational Publishing Engine Fixes in 1.1.1.2

Documents

Transcript of IBM Rational Publishing Engine Fixes in 1.1.1.2