Publish to a Folder
We started with testing the publication process to a folder, as this seemed the simplest way to start with CoRePublisher. A set of reports was generated and published to a file location. The reports are PDF outputs from a bursted report. Each report is generated and placed in the output directory as a PDF and accompanied with the report description file in XML format.
The report itself is a simple list report.
When you open CoRePublisher Configurator there is little to see. You can see two tabs, the Monitor tab and the Publication tab. The Monitor tab contains all the report output folders that you want to monitor. The Publication tab contains the target systems and the logic to publish. When you open CoRePublisher Configurator for the first time both tabs are empty (here already 1 entry is shown).
The first step is to add the Cognos report output folder we want to use to the Monitor tab. This is done by clicking the + button. Then the “Add New Monitor Folder” wizard appears.
The fields “ Main group”, “Group” and “Sub group” serve a free to choose categorization to define a structure in your different Cognos report output folders. The “Uri” field must contain the Cognos report output folder file path. When you set “Active?” to “Yes”, CoRePublisher will actively monitor and if required process the contents of the folder.
When you click the “Add” or “Update” button the Monitor tab will show a new entry.
The next step is publishing the reports to another target, in this case a Folder. Select the “Publication” tab and click the + button to add a new publication. The “Publications” wizard will appear.
In the first step you can choose a name for the publication and you have to select a Cognos report metadata file. This is the XML file published with each report. Note that selecting the file of a single report does not limit the publication to that report. Still all the reports in the selected monitor folder will be processed. But it will be the criteria available in this XML file that you will be able to use for conditional and dynamic logic further on. You also have to select a target system. In this case File/Folder is chosen. Next are a couple of options that are all straightforward. The last option allows you to load custom VBScript (which we did not test).
This was the list of available target connectors in the tested version:
The second step in the wizard only shows when you selected the mail option. On the left you can see all items that are included in the selected XML report definition file. Any item can be used in any field of the e-mail form to create dynamic mails. Including is done by selecting a mail form field and then selecting and double clicking a field on the left. Drag and drop would have been nice.
Below you can see the XML report definition file, all field defined in the report definition file can be used. It is also possible to create a generic report definition file that can be used universally.
Step 3 in the wizard is to define the conditions on which a report is picked from the monitored folders and published to the target. Each condition contains … a condition, an operator and a condition value. All 3 fields can use the report definition fields and can also contain custom VBScript logic. So it’s simple but also flexible at the same time.
The last step contains the target configuration. In this case a target folder, a report file name format, and custom credentials if different from the CoRePublisher Monitor service. Just as before the report definition fields can be used to format the target folder and file names dynamically.
When you click finish an entry is added to the “Publication” tab. If the CoRePublisher Monitor service is running the publication definition will immediately be evaluated.
And the resulted publication should be visible in the defined target folder.
Ok that went well, so now let’s crank it up a bit.
NEXT: Publish to a SharePoint Directory