RPE 188.8.131.52 contains an experimental feature called “Fast OAuth” which can provide a very consistent performance boost to reports that need to make multiple requests , via Dynamic Data Sources, to retrieve resources from the same application that uses OAuth for authentication.
NOTE: it is possible that applications use multiple authentication methods for their different components/APIs. For example you can have applications that use OAuth for their Web UIs and Form/Basic Authentication for the Reportable REST APIs. For this feature it’s the Reportable REST APIs authentication that has to be OAuth.
The time gains you can achieve depend on the number of resources you need to retrieve and the network speed. The more requests RPE has to make to the server and the farther the server is from the RPE machine the larger the gains will be. In our tests a 3+ hours report was finished in ~1 hour after enabling the fast authentication.
NOTE: This applies to running reports from RPE and not to RRDG reports as in that context the authentication is already a 1 step process.
You need to opt in this feature and you do this by defining the com.ibm.rational.rpe.fastauth Java property. If you are running your reports through Launcher/Studio this can be done by adding the following line in the rpe-launcher.ini and rpe-studio.ini files:
With this feature enabled RPE will go through the authentication process only once for a given data source within a single document generation process. Once the initial authentication is done RPE will use the OAuth authentication cookies obtained with each subsequent request.
To better understand the impact on performance you need to know that each OAuth authentication takes several distinct GET requests to complete. Assuming your report requires to retrieve 1000 resources ( to take all test cases for example) from the same application this translates into 3000 or more actual GET requests made to the server. With com.ibm.rational.rpe.fastauth enabled the number is reduced to ~1000 GET requests.
|Fast Auth Disabled||Fast Auth Enabled|
For now this feature is limited to the OAuth authentication method but we plan to be extend it to Form authentication in the future as internal tests show very consistent gains for that authentication type as well.
In conclusion if your report retrieve data from applications that use OAuth for their Reportable REST APIs you should enable this feature as it can provide consistent performance boosts to your reports.