BiLog: X...Request Page XML
PamDenny 270000BXV7 Visits (3970)
X is misunderstood. It can drive some to hold up a plane’s takeoff. Others may celebrate with unusual sounds or squirm in agony when faced with it on their tile board. Second only to Q and Z with its 8 point value, X should be recognized as a critical alphabetical character.
Report request page xml is also often misunderstood. Misconceptions exist on what the request page xml is, when it needs to be generated and when it doesn’t need to be generated. To minimize that confusion, a listing of questions and answers on the request page xml are presented below.
What is the Request Page XML?
Report request pages enable a user to input parameter, schedule and email inputs for reports. Report request pages vary by the type of report that is used (BIRT, Cognos or Custom) and by the types of parameters that are used.
The report request page information, including the parameter input dialogs, for all reports is held in one XML structure in a library called REPLIBRARY. This REPLIBRARY presentation is often referred to as the Request Page xml.
How is the Request Page XML generated?
The request page xml is generated with the Report Administration application. To do this, an administrator, with security privileges, accesses application. Then, on the bottom right hand side of the page, the administrator clicks on the ‘Generate Request Page’ button. This creates the REPLIBRARY presentation in the database.
Before the request page xml is generated, the REPLIBRARY presentation in the database has no values. After it is generated, the REPLIBRARY is created, and reports can then be executed.
What happens if the Request Page XML is not generated?
If the request page xml has not been generated from the Report Administration application, you will be unable to execute reports. Specifically, what will occur is that the list of available reports will display to a user. However, if they select a report, an error will display as the request page is unavailable. The error is: BMXAA3515E – The report is not available because its request page has not been generated.
When do you need to generate Request Page XML?
The request page xml should be generated under any of the following conditions
1. When you perform a new Maximo installation
2. When you apply a Maximo Fix pack
3. When you add a new enterprise report. This could be a BIRT, Cognos or any other external reporting tool you use through a Integration.
4. When you modify any of the report’s parameters or parameter settings. These settings include: Parameter name, attribute name, lookup, Display name, Display Sequence, Required, Multi-lookup enabled, default value or Operator
5. If you change the settings for a report including: Schedule Only, Priority, No Request Page
6. If you add or delete Reserved Processing Times for a Schedule Only Report
7. If you have a multi-language environment, please see the requirements for these environments in the section below.
When do you NOT need to generate Request Page XML?
The request page xml does not have to be generated in these conditions
1. If you add a new JVM to a clustered environment. In this case, the JVM will take the request page xml (REPLIBRARY) from the database.
2. If you modify any of the Browser View, Direct Print or Direct Print with Attachments settings.
3. If you modify the Use Where Clause setting
4. If you modify existing Reserved Processing Times for a Schedule Only Report
5. If you modify the report design file.
Additional details on the Request Page XML, including where it is located, and its creation requirements in a clustered and multi-language environment are detailed here. This location also contains a pdf file download with the complete information. Thank you!