Versions Compared

Old Version 50

changes.mady.by.user Alexej Hinz

Saved on

compared with

New Version 51

changes.mady.by.user Alexej Hinz

Saved on

Key

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

...

  1. Run the setup on your local machine, e.g. into C:/PerformerSuite.
    (the setup is more of an 'archive to be unpacked')
  2. Follow the guided configuration - process and enter your central database parameters (SQL Server or Oracle. SQLite is only for testing purposes).
  3. Load your license XML file into the central database (needs to be done only once for a centralized DB).
  4. 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.
  5. Package this installation - folder (there are no additional registries, nor path or variable settings needed).
  6. Roll out the package to your desired destination.
  7. 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.6.1)
  • All the needed information can be found in the User Manual: How to get started
Info
  • Every PS-User needs to have an individual 'Named User License' to work.
  • The same PS-User can only be logged in once.
  • A PS-User is a named license and should only be used for one assigned individual.

...