Guided Configuration - RFC Destinations
The Guided Configuration screen allows Administrators to configure LiveCompare for its first use, and to maintain an essential set of LiveCompare resources. It is displayed when an Administrator logs in to LiveCompare; and may be accessed by Administrators via the 
tool button in the LiveCompare Dashboard, or the 
tool button in the LiveCompare Studio.
RFC Destinations store the connection parameters that allow LiveCompare to connect to your SAP systems. The RFC Destinations tab lists the RFC Destinations defined on the LiveCompare server and allows you to create, maintain and test them. Note that RFC Destinations stored in subfolders in the LiveCompare hierarchy are also shown.
LiveCompare supports connections to the following:
-
Custom application servers
-
Secure Network Communication (SNC) servers
-
Load balanced SAP instances (by allowing a group of application servers to be specified)
Create RFC Destinations
To create an RFC Destination, click 
to display the RFC Destination screen. Complete the fields as follows:
| Field | What to do |
|---|---|
| Name | Enter a unique name that will identify the RFC Destination. |
| Description | Enter a description for the RFC Destination. |
| Connection Type | Select the type of connection to create, either ‘Custom Application Server’ or ‘Group/Server Selection’. |
Custom application servers
To specify a custom application server, complete the fields in the Custom Application Server section as follows.
| Field | What to do |
|---|---|
| SAP Router | Enter an SAP router string if required. |
| Application Server | Enter the DNS name, domain name, or IP address of the SAP Application Server. |
| Instance Number | Enter the application instance number of the SAP system to be used for the connection. |
| Client |
Enter the SAP client number to be used for the connection. |
| Language | Enter the SAP code for the logon language (for example, EN for English). |
| User | Enter the SAP user ID to be used for the connection (required). |
| Password | Enter the SAP password for this user ID (required). |
Group or server selections
To specify a group of Application servers, complete the fields in the Group/Server Selection section as follows.
| Field | What to do |
|---|---|
| Sysid | Enter the SAP system ID. |
| SAP Router | Enter an SAP router string if required. |
| Message Server | Enter the DNS name, domain name, or IP address of the SAP Message Server. The Message Server provides a list of groups on the specified SAP system. |
| Message Server port | Enter the SAP Message Server port (if required). |
| Logon Group | Enter a logon group defined on the SAP Message Server. |
| Instance Number | Enter the application instance number of the SAP system to be used for the connection. |
| Client | Enter the SAP client number to be used for the connection. |
| Language | Enter the SAP code for the logon language (for example, EN for English). |
| User | Enter the SAP user ID to be used for the connection (required). |
| Password | Enter the SAP password for this user ID (required). |
SNC connections
For Secure Network Communication (SNC) connections, complete the fields in the SNC Parameters section tab as follows.
| Field | What to do |
|---|---|
| My Name | Enter the LiveCompare domain account that has been used to authenticate an SNC connection to your SAP server, prefixed with p:, for example, p:CN=livecompare@domain.com. |
| Partner Name | Enter the partner name to be used for the connection, prefixed with p:, for example, p:CN=SAPService<SID>@domain.com. |
| Qop | Enter the Quality of Protection level to be used for the connection. The default value is 8 (Apply Default Protection). |
| X.509 Certificate | Paste in the contents of a certificate file created by the SAPGENPSE.EXE program. See the Create secure RFC Destinations help topic for details. Note that when the contents a certificate file are pasted into this field, the BEGIN CERTIFICATE and END CERTIFICATE lines are removed automatically. |
External connections
An RFC Destination may be associated with a HANA Database External Data Source to allow HANA data to be used when performing an impact analysis for BW objects. To associate an RFC Destination with a HANA Database External Data Source, select the HANA Database External Data Source in the HANA Database field.
An RFC Destination may be associated with a Fiori Launchpad Content Aggregator External Data Source to allow Fiori data to be retrieved by the Convert SAP Objects Test Search action. This allows the Search Test Repository action to find test assets that match the Fiori data in the specified Test Repository. To associate an RFC Destination with a Fiori Launchpad Content Aggregator External Data Source, select the Fiori Launchpad External Data Source in the Fiori Launchpad External Data Source field.
After completing the appropriate RFC Destination dialog fields, click ‘Save’ to save your changes.
Use downloaded performance history data only
To create an RFC Destination that uses performance history data uploaded to an External Data Source, complete the Add RFC Destination screen’s ‘Name’ and ‘Description’ fields only. When the RFC Destination has been created, use its PHD tab to specify an External Data Source of type ‘Performance History Data’.
The Read Performance History Data action may be used to read application statistics from an RFC Destination which does not have any RFC connection parameters, but which does have an associated External Data Source.
Test RFC Destinations
To test an RFC Destination, click the 
icon in the Actions column for the corresponding row in the RFC Destinations tab.
Edit RFC Destinations
To edit an RFC Destination, click the 
icon in the Actions column for the corresponding row in the RFC Destinations tab. The RFC Destination screen is displayed. Modify the fields as required and click ‘Save’ to save your changes.
Delete RFC Destinations
To delete an RFC Destination, click the 
icon in the Actions column for the corresponding row in the RFC Destinations tab. A confirmation dialog is displayed.
Note that when an RFC Destination is deleted, it is removed from all resource groups of which it is a member.