By default, PPM Customizing Toolkit stores the configuration files and applications for your PPM Customizing Toolkit client in the custom directory of your PPM installation.
This structure has been developed from many years of project experience and has proved its suitability on many occasions. We advise you not to change this directory structure.
Advantages of the standard PPM Customizing Toolkit directory structure
Clarity
The data is stored in different folders so that you can find the information you are looking for faster.
Standardization
A standard structure helps you handle different projects and shortens familiarization time. A wide range of applications can access this common standard.
Portability
All the information required to create a PPM client is stored in one coherent directory structure. This structure can be copied to any computer, allowing you to completely reproduce a PPM client.
Data archiving
The only archiving needed is backing up the client directory, which contains all the necessary information for your client.
Layout of the standard PPM Customizing Toolkit directory structure
The client data directory is stored under <PPM installation directory>\server\bin\work\data_ppm\custom and has the same name as the relevant PPM client. Below is a folder structure with the configuration contents.
Example: Directory structure for umg_en client in the custom directory
The following list describes the contents of the standard PPM Customizing Toolkit directory structure.
bat directory
This directory contains all the utilities for managing and configuring your client. The utilities are in the form of batch scripts that you can call up from PPM Customizing Toolkit. The directory is mandatory.
cockpits directory
This directory contains the Performance Cockpit definition and configuration files. The directory is optional and only required if you use performance cockpits.
config directory
This directory contains the *_settings.properties files for your PPM client's properties. All the files in this directory are copied from the bat directory to the corresponding config directory for the PPM installation when you run runinitdb.bat. This applies in particular to InitDb_settings.properties and InitSystem_settings.properties, which are used to initiate the database.
If you specify settings in the settings files of your PPM client (<PPM installation directory>\server\bin\work\data_ppm\config\<client>), e.g., Keyindicator_settings.properties, we recommend that you copy the modified files to the config directory of your corresponding PPM Customizing Toolkit client (<PPM installation directory>\server\bin\work\data_ppm\custom\<client>\config) to ensure complete archiving.
data directory
This directory contains the extracted source data of the PPM client. We recommend a separate subdirectory for each data source with the same name as the data source in question, e.g., CustomerServices or Sales in the PPM demo database. A corresponding directory is created automatically when you extract data.
In addition to the process data, we recommend separate subdirectories for the process instance-independent measures (piki folder) and dimension data (dimdata folder). The default batch applications supplied use this structure to import data.
docu directory
This directory contains any documentation for a client. By default, the expert and technical documentation that PPM Customizing Toolkit generates for a client is written to this directory. The directory is optional and is created automatically when documentation is generated.
dump directory
This directory contains any database dumps that may have been produced. The directory is optional.
log directory
This directory contains the log files produced by the CTK applications. The log files for the default batch applications have a name with the form <batname>_<Date>_<Time>.log. <batname> represents the name of the batch application, <Date> is the date and <Time> is the time at which the application was run. The directory is deleted when runinitdb.bat is called up. Server log output is not written to this file, but to <PPM installation directory>\server\bin\work\data_ppm\log\<client>.log. This directory is mandatory and is created automatically during installation.
managementviews directory
The directory is optional and only required if you want to use Management views.
The performancedashboards directory
This directory contains the Performance Dashboard definition and configuration files. The directory is optional and only required if you use Performance Dashboards.
patch directory
This directory contains the client-specific JAR files. These are always needed when specific Java classes are used, e.g., to calculate a measure or define a merge rule. When create_demo.bat is called up, all JAR files in the directory are automatically copied to the PPM patch directory and the PPM Customizing Toolkit patch directory. The directory is optional and only required if you use patches.
reportdefinitions directory
This directory is optional and only required if you want to use reports.
xml directory
This directory contains the PPM client configuration files in XML format. All files in this directory should observe the convention <client>_<configmodule>.xml. We recommend storing all the configuration files for PPM in this directory.
Each data source defined has its own <client>_<data source>.xml files and other files it requires, such as the fragment definition or mapping definition. The files are stored in a mandatory subdirectory with the same name as the data source.