RPE, the RPE 1.2 fixpack, is now available. The list of defects and other useful information can be found here while the the update can be downloaded from FixCentral here.

The main theme of the release is defect fixing and that includes PMRs but also the work we have done to adjust, simplify and make more consistent some of the features we have introduced in 1.2.

We’ve also worked to improve the RPE performance, focusing on the core processing part. The RPE core processing  is the document generation part that lies between data input and writing the output files.

The performance improvement targets templates using JavaScript but since almost all RPE templates use JavaScript one way or another the impact  should be quite large. And the more JavaScript you have in a template ( conditions, scripted filters, scripted content, assignments etc) the bigger the improvement will be.

But the core processing is just one of the document generation stages and so the overall document generation time depends on how fast the other two parts, input and output, take.  Between the two, the input part usually has a greater weight so the slower the data retrieval  is, the more it will weigh in the overall time and this will reduce the impact of the core processing improvements we have made.

In our tests we’ve seen the core part running up to 4 times faster for JavaScript heavy templates but usually that translates to a smaller factor for the end to end docgen. The actual figure depends on the time spent by RPE retrieving the data.

As a first step in improving the input part we read ahead the pages in a paged data feed. Rather than request a page only when needed, RPE will now request the next page in a feed as soon as the previous pages is downloaded and while the RPE core processes it.

There are several other changes in the RPE code that should further boost performance including the ability to use the RPE Remote Generation Web Services  in a load balanced environment.

Author: Dragos Cojocari

Architect for Rational Publishing Engine

2 thoughts on “RPE”

  1. Will the templates generated with this version be compatible with RRDG of Jazz V.4.0.3?
    We use RPE to create templates to generate documents out of RRC and RTC reporting.

    1. RPE supports both template version 1 as well as template version 2. If RRC 4.0.3 supports templates version 2 ( I believe it does but best check documentation or ask this on jazz.net) then you can design them using template version 2 otherwise you need to use template version 1.

      But whenever in doubt use template version 1 especially since you can always update the templates to version 2 at a later time.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s