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 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.

Data Source Configuration conflicts detected

If you notice “Data Source Configuration conflict detected” error in problems view upon opening a template in RPE studio, you should fix it immediately to avoid undesired results. The document generation might go through successfully for some case. However, for some cases the document generation could fail as well.

The data source configuration conflict happens when you use a schema normally and then use the same schema to configure the DSC element as in the below screen capture.


How to fix the conflict

Duplicate the conflicting schema either by using “Duplicate Schema” option from the outline. If the duplicate option is not available, go through the normal Add Schema operation to add the  schema with a different name again.


Once the schema is duplicated as _resources (or any unique name), use this schema to configure the DSC element and make sure to configure rest of the properties like URL, inherited data source, etc for the DSC element as earlier.


After you fix the issue, re-opening the same template should NOT result in “Data Source Configuration conflict detected” in the problems view.

Plan Ahead and Act Proficiently for Reporting

The material Einar Karlssen and I created for the Interconnect 2016 Plan Ahead and Act Proficiently for Reporting session is available on Slideshare in addition of being available via Interconnect Mobile Application

This alongside the best practice articles Kumar just posted can be used as a frame of reference for building documents with RPE.

Using JavaScript Objects/Arrays during iteration

When a JavaScript Array is populated with attributes within query on a container, you will notice that the Array object holds data for future iterations of the query while in the current iteration. This is because of how RPE processes the data and write to the output document in separate threads.

The solution here is to use additional variable called _arrayLength, which should be incremented for every query iteration and any operation on the Array should be through _arrayLength RPE variable.


Continue reading “Using JavaScript Objects/Arrays during iteration”

Can RPE work with Product X?

Publishing Engine is supported with a number of IBM products as described in the RPE System Requirements. What this means is that we’ve tested the integration and we will support users running into issues with those products.

However RPE is designed to work with any product that meets the following 3 rules:

  1. the product’s API provides data in XML format
    • it’s preferable that the API is Web based but that is not mandatory as long as you can automate the process of obtaining the XML.
  2. an XML schema exists for the data
    • the XSD can be provided by the API or it can be manually created
  3. RPE can handle the authentication* used to protect the API.
    • RPE currently supports Basic authentication, Form based authentication and the Jazz flavour of OAuth

There are further details like rich text, binary file attachments and more but if the above  conditions are met RPE should be able to at least produce documents with raw data from your product.

So when you don’t see your product on the support page my advice is to give it a try and if you run into any issues raise them on the RPE DevWorks forum.


3 minute videos

We’ve recorded a number of short videos showing how to deploy RPE. They are just long enough to keep you entertained while boiling eggs for breakfast.


How to troubleshoot document generation in DNG

When starting with DNG and document generation or when deploying new reports on the server the RRDG log is an invaluable resource for troubleshooting problems on the RRDG server.  As expected the log provides detailed information on errors and additional information including performance data.

Click to enlarge

All the DNG logs can be access at https://server:9443/rm/logs.  The log for document generation is rrdg.log which is located towards the end of the list.

By default the RRDG log is set on WARN level which means only warnings and errors will be logged. This is the recommended setting for most production servers but if you need to troubleshoot document generation you should increase the level and set it to INFO.

Changing the log level is done in the logger configuration page https://server:9443/rm/logs/config by setting the INFO/DEBUG level  to the logger

Click to enlarge