LiveCompare resources
You’ll need the following LiveCompare resources to perform most types of analysis.
RFC Destinations
RFC Destinations allow LiveCompare to connect to each of the systems in your SAP landscape. When creating an RFC Destination, you’ll need to specify its name and description, the hostname of the SAP system, and the client number, system ID, username, and password that LiveCompare will use for the connection. An RFC Destination’s name should reflect the system’s hostname and client number, and its role within your SAP landscape. For example, SAP23_00_DEV.
LiveCompare classifies RFC Destinations according to their role in an analysis.
-
Analysis systems provide the SAP objects that apps and workflows will analyze.
-
Comparison systems contain SAP objects that LiveCompare compares with objects from an analysis system.
-
Usage systems provide SAP usage data for analysis, including performance history data and daily usage audit data
-
SAP Solution Manger systems provide changing ChaRM objects that LiveCompare uses in an impact analysis.
LiveCompare needs the following data from each type of RFC Destination to run impact analysis or test audit, and to perform other types of analysis.
| Type of RFC Destination | What does LiveCompare need? |
|---|---|
| Analysis system | Object links cache data, IMG data |
| Comparison system | Daily usage audit data, IMG data |
| Usage system | Performance history data |
| SAP Solution Manager system | - |
Object links cache databases
Object links cache databases store links between objects retrieved from an analysis systems RFC Destination. LiveCompare stores these on LiveCompare server, and the Smart Impact app uses them to find objects that one or more changing objects have impacted.
You can use the Create Object Links Cache workflow to create object links cache databases for your RFC Destinations. LiveCompare also creates them using a schedule as part of the Commit Configuration process.
Usage data
Many LiveCompare analyses use usage data retrieved for an RFC Destination in its PHD and DUA tabs. For example, the Smart Impact app uses performance history data retrieved for the usage system, and the Test Audit app uses daily usage data retrieved for the usage system.
You can set a schedule in an RFC Destination’s DUA and PHD tabs to retrieve the most recent N months of usage data on the first day of each month, or use the Update Cache button to retrieve usage data immediately This allows apps and workflows that read usage data from the RFC Destination to have access to current data.
IMG data
The Compare IMG app and the Compare IMG Configurations workflow use downloaded IMG data.
Test Repositories
Test Repositories allow LiveCompare to connect to testing tools such as Tosca and qTest. For example, the Smart Impact app uses:
-
Search Test Repositories to find test cases for most-at-risk objects.
-
Execute Test Repositories to create and run Tosca test cases that match most at risk objects.
-
A Requirements Test Repository to store test requirements for most-at-risk objects that don't have matching test assets.
LiveCompare stores data retrieved from Search Test Repositories in Test Repository cache databases on the LiveCompare server. You can use the Create Test Repository Cache workflow to create Test Repository cache databases for your RFC Destinations. LiveCompare also creates them using a schedule as part of the Commit Configuration process.