Directory structure of the Infront Portfolio Manager

During the installation of the Infront Portfolio Manager, the two directories <program directory> and <local directory> are created. The <program directory> is the target directory of the Infront Portfolio Manager installation and essentially contains the application. The <Local directory> is used to store data and configuration files that are only relevant for users of this client.

Read authorization for all Windows users of this client is sufficient for the <program directory>. For the administrator who installs the Infront Portfolio Manager or carries out updates, write rights are also required.

Read and write permissions are required for the <Local directory> for all Windows users of this client. It is installed below CSIDL_COMMON_APPDATA (usually <C:\ProgramData\> under Windows 10).

In the custom installation of the Infront Portfolio Manager, you can specify not only the <program directory>, but also the <local directory> individually. Please note that the directories must not be identical, otherwise there will be overlaps in the "sys" directory. We therefore recommend leaving the default setting for the <Local directory>. The same applies to the <shared directory>, although there are no direct collisions due to identical files.

Programm-Verzeichnis

<6>

<bin>

<help>

<jre>

<bin>

<lib>

<erl>

<queue>

<sys>

Directory	Description
Infront Portfolio Manager	Structure
am	Essentially executables, DLLs and other binary files
help	Application help folder (currently only contains files for the program start intro since the introduction of the Help Center)
intros	Files for the program start intro
jre	Java Runtime Environment for using the server component
am (jre)	Executables, DLLs and other binary files for the Java Runtime Environment
lib (jre)	Java libraries for the Java Runtime Environment
lib	Java libraries that are required when using the server component
server	Structure
appsrv	The required structures for the <Application Server>, which are required for the server component, are created here.
attain	Erlang Runtime Environment for using the server component
queue	Required structure for the server component
websrv	The structures for the <Webserver> (Apache), which are required for the "Infront Advisory Solution" component and the cloud services, are created here.
sys	Unchangeable configuration files

Lokales Verzeichnis

<Local directory> (CSIDL_COMMON_APPDATA)

<6>

<local>

<there>

<mdp>

<psi>

<log>

<queue>

<sys>

Directory	Description
Infront Portfolio Manager	Structure
local	Structure
download	Files downloaded from the Internet for data updates or , which are processed further
there	Structure
mdp	Data update via Market Data Pool
psi	Data update
log	Log files
server	Structure
appsrv	The required structures for the <Application Server>, which are required for the server component, are created here.
queue	Required structure for the server component
websrv	The structures for the <Webserver> (Apache), which are required for the "Infront Advisory Solution" component and the cloud services, are created here.
sys	Configuration files for local settings that are only valid for the users of this client
upload	Files for uploading to the Internet (cloud services)
dashboard	Files from the Infront Portfolio Manager for uploading to the

To work with the Infront Portfolio Manager without restrictions, Windows users need write access to this <local directory> and all its subdirectories.

System administrators can configure the paths (<local directory> and <shared directory>) for different environments via a corresponding environment variable in the system properties. You can use this configuration option to manage your test and production environments, for example.