Customizing Scanit

Scanit can be customized by adding tokens to the existing types or by adding new token types.

Adding tokens

Every token type has a file that lists all the tokens for which to scan. The default token files delivered with the tool are:

• tokens_c for IRAPI and C language tokens
• tokens_t for TAS language and external function tokens
• tokens_sh for anything that can appear in a shell script
• tokens_prg for Script Builder text files before they are converted into .t files

To add a new token for which to scan:

1. Add a new line with the new token to the end of the file corresponding to its type.

For example, if IRAPI function irFPlay were found to have a problem, and needed to be flagged by the scanning tool, you would update the tokens_c file (IRAPI calls are found in C programs). The format of tokens_c files is a simple three column file that has the following format:

NAME: token weight

where NAME is fixed text and token and weight must be provided.

2. Update the token_information file (the file that contains a problem description for every token) for that file type.

Note:
When adding new tokens do not leave any blank lines at the bottom of the token_type file.

Adding new types of tokens

To add a new type:

1. Identify a new type identifier.

For example, if you needed to scan java source files, java might be a logical new type identifier.

2. Add the new type to the ext_type file in the installed tool directory.
3. Create a tokens_new type file, and populate it with tokens.

Use the same format as the other token type files.

4. Create a token_information.type file with resolutions and descriptions for each new token in the tokens_new type file.

� 2002 Avaya Inc. All Rights Reserved.