You can define Rational® Requirements Composer as
a data source in Rational Publishing Engine.
Tip: The
Rational Publishing Engine installation
includes a set of sample reports. Before you begin to publish documents,
you can explore this example document generation scenario. See
Creating a template with the REST sample data.
Before you begin
- Get familiar with the Rational Requirements Composer REST
service and the various URLs needed in order to extract data from Rational Requirements Composer when
you are using Rational Publishing Engine.
To locate the information center for your version of Rational Requirements Composer,
seeAbout the Rational Requirements Composer information
center.
- Connect to a data source schema. See Adding data source schema.
- The schema can be on the local file system. For example, https://server:port/jts/service/com.ibm.rrc.project.artifacts.xsd is
a schema file that uses artifacts argument. You can
use this schema to add specific data pieces from your Rational Requirements Composer project.
- The schema can be any URI that is accessible from the computer.
Open the data source schema and, from the XML file, take the URI for
a particular resource. Add ?metadata=schema at
the end of the URI. A typical URI is: https://server:port/jts/service/com.ibm.rrc.project.artifacts?metadata=schema.
- You can use the elements in the data source schema to add queries
in your template. These queries specify which pieces of information
are generated in the report.
- After you connect to the data source schema, you can create or
import a template design. With the Rational Publishing Engine Document
Studio, you can build a report template design. This design determines
the layout of the report. See Designing templates with Document Studio.
- After you connect to the data source schema, you can plan the
structure of your document and define the content to extract data.
See Template development process to
get an overview of the template development process. For large documents,
you can create separate templates for each document block.
- You can use filters, which are more specific versions of the general
data source URI, to point to specific subsets of data so that Rational Publishing Engine
does not attempt to retrieve more information than necessary from
the Rational Requirements Composer repository
during report generation. These filters must be broad enough to retrieve
all of the necessary data referenced by the template or it cannot
include a complete set of data. See Extracting
data using native filters.
- After you create the report template and populate it with Rational Requirements Composer data
points, you can generate a report in various formats. When you generate
a report, you must connect to the data source that contains the information
by specifying a URI that points to the Rational Requirements Composer repository
that contains the relevant data. See Creating a document specification.
- If data source schemas are added to a template after
the template is assigned to a document specification, the document
specification becomes out of sync. You can manually
synchronize the document specification or select a preference
option to automatically synchronize the document specification with
the current template. See Setting the Document Studio preferences for information about how to set
the Keep Document Specification synchronized with the current
Template? preference.
- Before you publish your document, see the Specifying output properties topic
for more information about the available output options that you can
choose from and which one is best to use for the elements you are
using in your template.
- You are now ready to publish your document. See Publish
your document.
Note: You create and publish documents from the Rational Requirements Composer.