Word macros allow document creators to correct document errors and fine tune the document formatting. Running the macros programatically through Word automation allows to automate the process for added benefits. There are a number of tools and processes that do this with RPE being one of them.
Running macros is limited to the Windows platform and it’s subject to additional limitations such as Word automation not being supported from NT Services ( as it’s the case for running RPE/RRDG running in WAS or Tomcat in Service mode).
To enable macros to run in situations where Word or Word automation is not available the solution is to execute the macros remotely by a dedicated service. Microsoft offers such a service in the form of Word Automation Services. Another solution, the one described in this article, is to a service that runs the macros through Word automation. The caveat of this service is that it cannot run as an NT service, it must run in an interactive desktop ( Apache Tomcat in console mode or node.js).
DISCLAIMER: The solution described in this article is provided as-is without warranty of any kind, express or implied. The service is not part of RPE and it is not supported by IBM.
Continue reading A node.js service for running Word Macros remotely
One of the most common problems I’ve seen reported for RPE 2.0 is setting up the shared license library required for RPE WebService 2.0 to function. You access http://server:8080/rpeng/, login and you are greeted by the following error
Error 400: Cannot obtain a RPE License. Please contact the system administrator.
For the RPE WebServices 2.0 to work properly you need to configure a shared library in the application container you are using. The procedure is described in the Infocenter in detail for all supported application containers but there are a couple of errors that can cause the deployment to fail. For this I have listed the key missing/incorrect points in our docs.
NOTE: we are working to simplify this procedure considerably in the next RPE release.
Continue reading Setting up the the licensing for RPE Web Services 2.0
The RPE Web Services 2.0 document store is designed to clean old documents after a time interval set by the admin. Out of the box this interval is of 30 days but you can modify this from the administrative settings.
To disable the document clean-up you need to set the value of this flag to 0.
RPE 2.0 report designers have the ability to test and review reports before making them generally available to all end-users.
When a report is created the “Make available for Document Generation” is unchecked by default which makes it visible only to the other designers. These reports are marked by the (draft) word next to their title.
The draft reports allow designers to review&test the report in the exact conditions the end users will run it without being concerned with end users inadvertently running an unfinished report.
Once the tests and reviews are complete the designer can make the report public by ticking the check-box.