Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Summary

Overview of all important folders which the Performer Suite is using.

Tip

You can move the Working Directory with a Command Line Argument to

...

the desired location.

...

Related article:

Current folder tree

Directory
Path exampleDescriptiontype of contained filesclass of datarecommended Write rightssecurity relevanceperformance relevance
Proposed default InstallDirectory
C:\Users\

...

<USER>\

...

Documents\

...

PerformerSuiteLast used install pathInstallationSettings.xmluser

...













WorkingPath

=

...

<PerformerSuite Installation directory> or <command line argument> 

...

C:\

...

PerformerSuite

Install path

...


All files belowapplication

...

(star)

...



Database= WorkingPath + "Databases"C:\

...

PerformerSuite\Databases

SQLite Database location

Database.dbapplication

...

(only for SQLite DB)

(red star)(green star)
ImagesPath= WorkingPath + "Images"C:\PerformerSuite\ImagesIcons used within the Performer SuiteSAP iconsapplication(star)
(only for 3rd Party Objects)

(green star)
Logo= WorkingPath + "Logo"C:\

...

PerformerSuite\LogoYour company logoLogo.pngapplication

...

(star)




Template= WorkingPath + "Templates"C:\

...

PerformerSuite\Templates

...

Contains templatesWord Templates (*.dotx)application

(star)

...

(star)












...

AppData= WorkingPath + "AppData"C:\

...

PerformerSuite\AppData

application(star)
(only for local installations)


AutomationTool= AppData + "AutomationTool"C:\

...

PerformerSuite\AppData

...

\AutomationTool\AutomationToolData.xmlAutomationTool setting fileAutomationToolData.xmluser(star)
(only for local installations)
(red star)
Backup=

...

AppData + "Backup"C:\

...

PerformerSuite\AppData\Backup

application

...




ConnectionData=

...

AppData + "ConnectionData"C:\

...

PerformerSuite\AppData\ConnectionData

...

Files for the DB connection (incl. documents path) and proxy settings
  • ConnectionData.xml

...

  • ProxyData.xml
application

...

(star)
(only for local installations)
(red star)
Generated

=

...

AppData + "Generated"

Note

...

This export path can be changed within the PerformerSuite (Settings)


C:\

...

PerformerSuite\AppData\Generated

...

Generated and exported

...

SAP documentations
  • Word

...

  • Excel

...

  • PDF
  • Powerpoint

...

user

...



(green star)

...










UserPath

=

...

"

...

Documents\PerformerSuite"

C:\

...

Users\

...

<USER>\

...

= "MyDocuments\BI Docu Performer"

Note

WebEdition: UserPath = LogPath = TempPath = WorkingDirectory

...

Documents\PerformerSuite
User-dependent files and encrypted credentials for SAP connection
  • AppBackup.data*
  • AppLoginCredentials.xml*
  • InstallationSettings.xml
  • SacLoginCredentials.xml*
  • SapLoginCredentials.xml*
  • SettingPathAndFilenameLocal.xml*
    * MOVED INTO THE DATABASE AS OF V23.1
user(star)(red star)
LogPath= UserPath + "Log"C:\Users\

...

<USER>\Documents\

...

PerformerSuite\Log

...

Log file (

...

PerformerSuite)

...

PerformerSuite.log

application

...

(star)

...


(green star)

= Log + "

...

BoConnectionTrace"C:\Users\

...

<USER>\Documents\

...

PerformerSuite\

...

Log\BoConnectionTraceIn-depth analysis logs for BO
application



= Log + "BwConnectionTrace"C:\Users\

...

<USER>\Documents\

...

PerformerSuite\Log\BwConnectionTraceIn-depth analysis logs for BW
application



= UserPath + "

...

Settings_off"C:\Users\<USER>\Documents\PerformerSuite\Settings_offConfig file to perform BO in-depth analysisTraceConfig.xmlapplication


TempPath= UserPath + "Temp"C:\Users\<USER>\Documents\PerformerSuite\TempUsed for temp install files during installation and temporarily generated files
application(star)










Services= WorkingPath + "Services"C:\PerformerSuite\Services\Log\PerformerSuiteServices.logLog file (AutomationTool)PerformerSuiteServices.logapplication(star)
(green star)