Previous Topic: ProfilesNext Topic: Testing


Format of a Build Tool Profile File

When a Build Tool Profile is modified (either the default profile or a user profile), only the modified tokens are saved to disk.

The file is formatted in token/value pairs, using the following format:

<PROFILE_NAME>.<PROFILE_TREE_SECTION>.<PROFILE_SUBTREE_SECTION>.<KEY>=<value>

Note: All data to the left of the ‘=’ must be in uppercase. The value to the right of the ‘=’ can be mixed case.

All keys have a preface of one of the following:

OPT.

This preface is for option tokens.

LOC.

This preface is for location tokens.

The following example shows a profile file format for the OPT.DBUSER option key set to dbuserid in the MYPROFILE profile with the DBMS profile section tree name and the ORACLE subtree section name

MYPROFILE.DBMS.ORACLE.OPT.DBUSER=dbuserid

Note: For more information about the list of available tokens, according to their profile tree section and subtree section, see the appendix "Profile Tokens."

The location of the default profile file is a fixed location. You can find the file that is named System.profile in the following location:

You can find the user-specific profile files, named using the format user.<PROFILENAME>.profile, in the following location: