You can use the Publish Method Configuration wizard to generate
a Web site based on a method configuration.
To publish a configuration as a Web site:
- From the toolbar, use the Configuration menu
to select
Publish. The Publish
Method Configuration wizard opens.
- From the list of available configurations, select the method configuration
that you want to publish. Click Next.
- Indicate if you want all method content of the selected method
configuration to be included in the published site, or if you want only the
method content that is being used by the processes that you can select in
the process list below. Click Next.
- Select options to customize the look and behavior of the published
site:
- Select options for Title and links.
- Title: The title is displayed in the title
bar of the browser showing the published site
- About content: Select a text or HTML file that
contains the text that will be displayed when the user presses About in
the published site
- Feedback URL: For more information about the
feedback URL, see page Changing feedback addresses.
- Select options for Glossary and index. Check
these boxes to generate a Glossary and Index section.
- Select options for Look and feel.
- Publish banner: Check this box to create a
banner on top of the published content. Use the Banner image field
to select a graphic file that contains your banner. If you do not enter anything
here, EPF Composer will use its default banner.
- Select options for Validation.
- Check external hyperlinks: When this option
is selected, EPF Composer checks all hyperlinks before publishing. Clear this
option if you are not connected to the Internet or need to use a Proxy server
(currently not supported).
- Convert broken hyperlinks to plain text: If
the Check external hyperlinks finds broken links and this option is not selected,
EPF Composer prefixes each link with a broken link symbol. The same is true
for links to content elements that are not in the published method configuration.
If this option is selected, all links are converted to plain text instead
and no broken link symbol is used.
- Select options for Diagrams.
- Publish activity detail diagrams that have not been manually
created: When this option is selected, EPF Composer publishes
an Activity Detail Diagram for every activity. It creates these diagrams and
publishes them with a default auto-layout. If the option is cleared, then
only the Activity Detail Diagrams are published that a user has manually created
in the Process editor and saved with a custom layout.
- Publish activity diagrams for unmodified activity extensions:
By default, activities that are extensions of other activities are not published
with an Activity Diagram, but only the Breakdown Structure. If this option
is selected, however, extending activities are published with the diagram
of their base activities if these extending activities do not define their
own sub-elements, that is, are pure pattern applications without providing
its own modifications. If these activities define their own elements, you
should create a local activity diagram for the extending activity that will
then be published.
- Select options for Layout.
- Show relationship sub-folders in navigation trees:
If this option is selected, it will publish elements, such as task with its
related elements (such as input and output work products), in separate sub-folders.
If cleared, it will publish related elements as sub-elements. It will also
list a subset of these related elements in the tree; for example, only output
work products for tasks and not the inputs.
- Show related elements for roles, tasks and
work products in navigation trees: If this option is selected,
it will publish roles, tasks, and work products with their related elements.
- Show task descriptors in navigation trees:
If this option is cleared, EPF Composer creates a breakdown for all activities
for published processes in the tree-browser. If selected, it also includes
the descriptor level into the tree-browser. Selecting this option has an
impact on publication time and performance of the published site.
- Include method content in descriptor pages:
If this option is selected, it hides the distinction between method content
elements and descriptors from the users of the published site. All descriptors
are published without using the word “Descriptor” as their type and all textual
content and guidance relationships of the related method content elements.
- Publish process usage in role, task and work product pages
linking to related descriptors: When this option is selected,
all method content pages include an additional section called “Process Usage”
that lists all occurrences of the method content elements in all processes
of the published configuration. This provides a quick overview to see in which
processes and where in these processes method content elements have been used.
When this option is selected, you can also select the option “Show all indirect
(green) occurrences in extended patterns” which determines how many process
occurrences are shown for a method content element. If the option is not checked,
then only direct usage of the elements is shown (recognizable by using a black
font for these elements in the process editor’s breakdown structure). If the
option is checked, then also all indirect occurrences are shown. Indirect
usage means that the element has not been applied directly to the process,
but indirectly by applying a capability pattern that had this element applied
(recognizable by using a green font for these elements in the process editor’s
breakdown structure).
- Default tab for activity pages: Published activity
pages comprise four tabs. This option allows selecting which of these tabs
is presented first by default.
- To get to the next set of publishing options, click NEXT.
- Enter destination Directory: Decide in which
directory the published site will be created.
- Select options for Website format.
- Static web site: This option creates static
HTML pages in the directory selected above. If this option is selected, search
is supported requiring a Java runtime environment installed on the Web site
user’s machine because it will use a Java Applet.
- Java EE Web application: This option creates
one WAR or EAR file in the location selected above that can be installed on
a Java EE Web server with Servlet 2.3 capabilities. Search will be realized
as a Servlet running on such servers.
- Click Finish. Publishing
is initiated.