Refer to the following information when you are specifying parameters
in the custom script for generating UML reports with Extensible Stylesheet
Language Transformation (XSLT) report templates, com.ibm.xtools.publish.CLLegacyXSLTReportPublish.
Note: - If an attribute is optional, you can specify it or not. If you do not
specify the attribute, the default value is assumed. A required attribute
must have a valid value for the task to work.
- Write all paths as fully qualified paths, as in these examples: /root/myoutput/myModelProject1 (Linux®)
or c:\output\myModelProject1 (Windows®).
The script includes the following attributes:
- modelPath
- Required. Specify the fully qualified path of the model to publish.
- To find the fully qualified path, right-click the model in the Project
Explorer view; then click Properties.
- You can specify more than one model. Use a semicolon (;) to separate the
entries.
- targetOutputFolder
- Required. Specify the fully qualified path of the location to send the
report. The folder must be accessible before you run the script.
- targetOutputFile
- Required. Specify the output name of the report, for example, myReport.
All reports generated from XSLT templates are in PDF format.
- xsltReportTemplateFile
- Required. Specify a valid URL path to an XSLT report template file.
- To find the fully qualified path, right-click the report design in the
Report Explorer view and then click Properties. The report design file must
be registered; for information see the topic "Registering XSLT report templates
for the current release."
- overwriteExisting
- Optional. Specify whether the contents of the output directory should
be deleted before a report is generated to this directory. The values are true (the
default) and false.
- autoShowPublishedOutput
- Optional. Specify whether to display the report automatically after it
generates. The values are true and false (default).
- errorHandling
- Optional. Specify how to handle errors. The values are ignore (the
default), which ignores any errors that might occur and continue processing,
and abort, which stops processing immediately and exits the
task.