Whether you are configuring content for SmartHelp or help integration or both, you use IAS Configuration documents in the Developer. These documents contain options that allow you to associate the configuration with specific content, control launch behavior, and set up rules for the context search. The configuration document is dynamic; as you select options other options may be hidden or may appear.

A configuration document can be stored anywhere in the Library. It is recommended that the configuration be stored in the same folder as the root outline item, and when saved, saved with the same name as the root outline item. This makes it easier to select the correct configuration document when the content is published. Also, the configuration document is not automatically selected as a related document if you export the outline into an odarc. If the IAS Configuration document is stored in the same folder as the root outline item, the document and the outline item can be easily selected to be exported together.

In an IAS Configuration document, you create a configuration and associate it with content in the Library. When you publish the content, you select the IAS Configuration document in the Publishing Wizard, and the appropriate files are published with the content.

To create a new IAS Configuration document:

1. Open the Developer.
    
2. On the File menu, point to New and choose IAS Configuration.

Configuration Overview

When you create a new configuration document, there are two main sections, Sources and Application Instances. The Sources section allows you to "enable" content for use with SmartHelp and define different types of content for help integration. The Application Instances section allows you to configure specific applications to use SmartHelp and/or Help Integration, and define which Sources can be used for either one.

The examples below are for different situations to help you understand how the options in a configuration document relate to each other. Each example assumes you have started by creating a new configuration document. Refer to the sections that follow for more information about each of the options in the Configuration document.

Example 1: Configure a single application for SmartHelp.

1. In the Sources section, choose the Player content in the Library and be sure that the Allow SmartHelp option is selected. If you are deploying the content on web server and not through Knowledge Center, enter the URL where the content is deployed.
    
2. In the Application Instances section, choose the application from the Type list, enter a name, and select the source from those available in the SmartHelp Sources list.
    
3. Define the SmartHelp URL Rules.

Example 2: Configure a single application or multiple applications to use multiple SmartHelp sources. You can define as many SmartHelp Sources as you need for an application.

1. In the Sources section, choose the Player content in the Library and be sure that the Allow SmartHelp option is selected. If you are deploying the content on web server and not through Knowledge Center, enter the URL where the content is deployed.
    
2. Still in the Sources section, add a new source, choose the Player content, and enable it for SmartHelp. Repeat for as many different outlines as you need.
    
3. In the Application Instances section, choose the application from the Type list, enter a name, and select the sources in the SmartHelp Sources list.
    
4. Define the SmartHelp URL Rules.
    
5. If you want to configure multiple applications, add a new application and repeat steps 3 and 4.

Example 3: Create a configuration document for an application that supports help integration.

1. In the Sources section, define a source or sources as necessary. Content can be from the current Library, content from another Library, the original application help (for certain applications), or any URL, although one of the sources must be Player content from the current Library.
    
2. In the Application Instances section, choose the application from the Type list, enter a name, and select the Help Integration option.
    
3. For the first tab for the integrated help, choose a Player content from the current Library.
    
4. If desired, segment the content, for example for different languages.
    
5. Add tabs or links as desired to include additional sources of help, such as more Players, the original application help, or any URL.

Table of Contents  Back