Please follow the steps below, if you want to use a centralized software distribution instead of an installation in a central folder or individual local installations:
Run the setup on your local machine,
...
In the setup process you can set the used central database, name the respective systems – this can all be adjusted later again, since all the information is stored in the central database.
After you have installed it locally, you can take the whole folder and package it. There are no additional registries or path and variable settings needed.
...
e.g. into C:/PerformerSuite.
(the setup is more of an 'archive to be unpacked')Follow the guided configuration process and enter your central database parameters (SQL Server or Oracle. SQLite is only for testing purposes).
Load your license XML file into the central database (needs to be done only once for a centralized DB).
Start the Performer Suite, and connect once for testing purposes to all your Systems (BW, BO, HANA) to confirm all your connection parameters to your SAP Systems are correct.
Package this installation folder (there are no additional registries, nor path or variable settings needed).
Roll out the package to your desired destination.
The Performer Suite Users now have only to execute the PerformerSuite.exe from the configured rolled-out folder.
The same PerformerSuite.exe can be started multiple times, as long as a different PS-User is logged in.
All the needed configuration information is stored in subfolders and stored in the database.
Please make sure all Windows-Users have write rights to the complete Performer Suite folder and its subfolders.
Keep in mind, you need the respective .NET Framework on the target clients (.NET 4.8.
...
x)
All the needed information can be found in the User Manual: How to get started
| Info |
|---|
|