Individual content files are added or removed from the document root for each top-level help topic. To make the content file available for linking and viewing from the help system, you must also alter the file list, files.js, located at <document root>\wwhdata\common. The files.js file also controls the order of the files in the array for reference by other files. For example, the content of files.js for the using-dk document root looks like the following code:
P.fA("Introducing Actuate Java Component","DKusing-intro.2.01.html");
|
Each file, about-dkreports.html, DKusing-intro.2.01.html, DKusing-intro.2.02.html, and DKusing-intro.2.03.html, is available for linking and display by Java Component help.
|
|
|
The first file in the array is about-dkreports.html, which is referenced by the array number 0. The second file in the array is DKusing-intro.2.01.html and is referenced by the array number 1 and so on.
|
The order of the files in the array always begins with and proceeds from 0. The file array is an internal mechanism that supports referencing these files by number within the help topic.
|
1
|
Copy your content file into the document root directory for the help topic you need to enhance. For example, to add a new file to the Using Actuate BIRT Java Components help topic, the document root is the <context root>\using-dk directory.
|
P.fA("Using Actuate BIRT Java Components","about-dkreports.html");
P.fA("Introducing Actuate Java Components","DKusing-intro.2.01.html");
P.fA("Using Actuate Java Components","DKusing-intro.2.02.html");
|
5
|
Add a P.fA(…); entry for the file to add, placing it where you need it to appear in the file array relative to the other entries.
|
P.fA(…); requires two parameters. The first is a string that describes the file. The second is the name of the file. Both parameter values must individually be within quotation marks and separated by a comma.
