Profile Files

Profile files are saved in the path\Config folder, where path is the directory where PASS-Web G3 is installed. Profile files are named name.profile, where name is the application name that appears in the title bar of the Service and Client shells.

The Service shell must know its profile. There are several possible cases that may happen during the shell start-up.

If the shell is started with profile=<ProductName> command line argument, the value is going to be used as profile. If there is no profile.ini file found in the startup folder, the default configuration is used. If the shell is executed as NT service, the “profile” command line argument must be present.
If “profile” command line argument is missing and the shell is not executed as NT service the shell looks for profile_name.ini files. If none of them is found, the profile set as the default is used (“Trapeze6”). If only one profile is found, the shell uses that profile. If multiple profiles are found, the Service shell prompts the user to select a profile.

As a result, the Service shell loads or sets the configuration as the default into the context properties and sets the profile context property (set of system settings).

Profile file paths must be set up as follows: ([ drive ] \ [ path] are user-defined. (The path examples are shown in bold text. )

<directory name="Hw" path="[ drive: ]\[ path ]\Reference_Responsive-V1.0"/>

<directory name="$\" path="..\Modules;..\Modules\Core\UI;[ drive: ]\[ path ]\Reference_Responsive-V1.0"/>

Common

(Required for all products)

<directory name="public\common" path="[ drive: ]\[ path ]\Reference_Responsive-V1.0\Apps\Public\Common"/>

For PASS-Web

<directory name="public\paratransit" path="[ drive: ]\[ path ]

\Reference_Responsive-V1.0\Apps\Public\Paratransit"/>

Example

For Client specific markups, the following is an example of how the path can be set for PASS-Web G3:

A client markup folder has the following subfolders: Reference and Override

<directory name="Hw" path="C:\svn\solutions\Customers\NA\PT\USA\JTA\JTA_PASS_WEB_ANGULAR\Reference"/>

<directory name="$\"path="..\Modules;..\Modules\Core\UI;C:\svn\solutions\

Customers\NA\PT\USA\JTA\JTA_PASS_WEB_ANGULAR\Reference"/>

<directory name="public\paratransit" path="C:\svn\solutions\Customers\NA\PT\USA\JTA\JTA_PASS_WEB_ANGULAR\

Override \Apps\Public\Paratransit;C:\svn\solutions\Customers\NA\PT\USA\JTA\JTA_PASS_WEB_ANGULAR\Reference
\Apps\Public\Paratransit"/>

The last line provides the variable "public/paratransit" for the two locations. The File service will use the first location if it exists, otherwise, it will use the second one.

The two paths are similar with "Override" and "Reference" being the only subfolders different between them.

Note: File permission should not be granted to Anonymous users and is not needed so long as the above configuration is used.