Target Application-Specific Configuration Settings

For target applications that support help integration, there are three possible feature sets to configure: Application Help, Multi-Language Content, and Advanced Options.

Application Help Options

The options in this feature allow you to configure a page to launch which has links to both the developed content and the original help. This feature is only available for those applications in which the link to the developed content replaces or suppresses the link to the original application help.

Help URL: If you enter the application's Help URL, it is displayed in the gateway page. If this URL is not present, the Player content launches without displaying the gateway page.
Display Help As: The application's help link can appear as a link in the gateway page, or as a frame embedded at the top or bottom of the gateway page. If you choose to display the help as a link, the Help Link Text field is available for you to supply text for the link.

Multi-Language Content Options

The options in this feature allow you to configure the help to launch the appropriate content if you have developed content in multiple languages. This feature is only available for certain target applications.

Content URLs by Language: This option has two fields, Language and Content URL. Use the Language list to select a language, and then enter the URL to the content developed in that language in the Content URL field. You can add new rows as necessary to support all available languages.
Default Content URL: This is a URL to the content to be launched if the language is not defined in the Content URLs by Language list. For example, if you have defined English, Spanish, French, and German, and someone logs on in Italian, you can specify that the English content should be launched.

Advanced Options

The options in this feature allow you to control how the outline appears when the content is launched, and point to the content if the scripts folder is moved.

Outline Display: If you have configured the content to launch with context-sensitivity, then the outline will only contain the items which are related to the task the user is performing in the target application. This is called applicable content, and it is the default setting. If you want the entire content outline to display instead, you can change this option to show all content.
Special Content Location: If the configuration file folders, [application name]/hemi and /stdhemi are copied from their default location from within the published content, you must enter a URL in this field which points to the content location. This option should only be used on the advice of Technical Support.

Special Options

Certain target applications have special options. Most of these appear under Advanced options as necessary. If there are special options for the target application you are configuring, see the section below for more information.

Each target application that supports help integration has its own page in the IAS Configuration Utility. However, every target application does not support all of the features. The table below displays the features each target application supports.

Target Application	Application Help	Multiple Languages	Advanced Options	Special Options
Agile PLM			X
CA Clarity PPM	X		X
JD Edwards EnterpriseOne	X	X	X
JD Edwards World			X
MicroSoft Dynamics CRM	X		X
Oracle CRM On Demand			X
Oracle E-Business Suite	X	X	X	X
PeopleSoft Enterprise	X	X	X
SAP GUI for HTML		X	X	X
SAP GUI for Windows		X	X	X
SAP NetWeaver Portal	X	X	X	X
Siebel CRM Applications			X

To configure application-specific options:

Launch the IAS Configuration Utility.
Click the target application link that you want to configure.
Change settings as appropriate.
Save the configuration.