Runtime Merging Server-Based HTML5 Output

This is an easy way to merge the output from multiple HTML5 Flare targets into one Help system. These targets can be originated from the same Flare project or from different Flare projects. You simply place the output files in the correct location on the server (i.e., within your parent project's AutoMerge folder). Flare then automatically merges the output from all of the targets when users access the Help. From the end user's perspective, the results are seamless, appearing as one large Help system. All of the TOCs, browse sequences, indexes, glossaries, and search capabilities for the projects are merged.

Note Flare's HTML5 Side and Top Navigation skins do not support runtime project merging.

For a complete scenario that illustrates these and other HTML5 server-based output steps in a real-life situation, see HTML5 Server-Based Output Scenario.

The following information is necessary only for server-based output. If you do not require server-based HTML5 output, see Runtime Merging Flare Projects Using Targets instead.

  1. Enable HTML5 Server-Based Output If you want to take advantage of the advanced server-side features of HTML5 (i.e., automatic runtime project merging, server-side search, searching of non-XHTML files), you must enable HTML5 server-based output. This includes performing the following tasks: (1) installing Microsoft Internet Information Services (IIS) and ASP.NET, (2) setting up the HTML5 target and generating/publishing, (3) configuring IIS on the production server, (4) starting Microsoft Indexing Service or Microsoft Windows Search (depending on the operating system), and (5) enabling HTML5 search.See Enabling HTML5 Server-Based Output.
  2. Determine Parent Output Decide which of your project outputs will serve as the parent. This is the main output that users will open. All other outputs will be accessed from that output, although it will appear as one large Help system to end users.
  3. (Optional) Specify TOC and/or Browse Sequence Locations for Automerge By default, the TOCs and browse sequences from the child outputs will be appended at the end of the parent output's TOC and browse sequence. However, if you want them to be appended somewhere within the parent output's TOC or browse sequence, you can specify the exact location.See Specifying the Automerge Location in a TOC for HTML5 and Specifying the Automerge Location in a Browse Sequence for HTML5.
  4. (Optional) Specify Order of Merged Outputs When you automerge HTML5 outputs, the secondary outputs are merged to the parent project's table of contents (TOC) and/or browse sequence in alphabetical order. However, you can override this default configuration and merge the secondary outputs in any order that you like.See Specifying the Order of Automerged HTML5 Outputs.
  5. Generate Outputs Build the output for each of the targets to be included in the automerge. You must use HTML5 for all of the targets. See Step 5: Building and Publishing Output.

Note If you are testing HTML5 server-based output on your local machine, you need view the output at least one time. When you view HTML5 output on your local computer, you need to create a special folder called "MCPreview" within your "C:\Inetpub\wwwroot" folder. Place a copy of your HTML5 output files in it. This enables you to test the advanced features of HTML5 on your local machine. When testing the automerge feature on your computer, you need to place the secondary ("child") outputs in the AutoMerge subfolder at this location (as opposed to the output folder that was generated where your Flare project is located).

Note If you are testing HTML5 server-based output on your local machine, you may need to wait a few minutes after viewing the output for the Indexing Service to fully scan your files. Otherwise, you may not immediately see the effects of the scan (e.g., searches of non-XHTML files, incorporation of merged output files) in the output. If you avoid performing other tasks during this period, the scanning of the files will be completed more quickly.

Note If you want to test HTML5 server-based output on your local computer, the advanced search features of HTML5 are not operable.