Introduction
Simple System Integration (SSI) is a guided, largely automated procedure for integrating managed systems into FRUN for monitoring purposes.
SSI can be used for:
- Integration and configuration of technical systems for monitoring with SAP Focused Run applications
- Searching for technical systems and displaying configuration status and possible issues
- Changing configuration parameters and triggering reconfiguration
Within the SSI workflow, the “Edit Configuration” function is the critical first step — it is where you supply the connection parameters and credentials that FRUN needs to establish communication with the managed system. Without completing this step correctly, the subsequent “Configure Automatically”/ “Configure manually” step cannot succeed.
https://support.sap.com/en/alm/sap-focused-run/expert-portal/frun-ssi-main.html?anchorId=section
The Edit Configuration dialog differs slightly depending on the system type being integrated:
- For ABAP systems: You enter the credentials of the dedicated FRUN user (RFC user) created on the managed system's production/main client.
- For JAVA systems: You provide the FRUN user credentials along with the HTTP and P4 ports required for the SDA agent to connect to the Java managed system.
Once the parameters are saved via Edit Configuration, triggering Configure Automatically will initiate the full automated configuration of the managed system for SAP Focused Run monitoring.
Prerequisites
Before using the “Edit Configuration” function in SSI, ensure all of the following prerequisites are in place:
Managed System Side
- Simple Diagnostics Agent (SDA) deployed on all hosts of the managed system. SDA is installed as an add-on to the SAP Host Agent, so the SAP Host Agent must be installed on each host first.
- Managed system registered in LMDB with the Data Supplier Completeness check showing green status.
- FRUN RFC/technical user created on the managed system:
- For ABAP systems: Monitoring User (the SDAGENT or a comparable user) must be created in the managed system's production/main client. This user is required for the RFC connection.
- For JAVA systems: Monitoring User (the SDAGENTJ or a comparable user), and the HTTP and P4 ports of the Java managed system must be known.
- The user must have all required roles and profiles as specified in SAP Note 2450740 — Roles to authorize access in managed systems to collect data for FRUN.
- The user must not be locked and must not be in use elsewhere with an incorrect password.
SAP Focused Run System Side
- Host registered on the FRUN system via Outside Discovery.
From hostctrl\exe as administrator or <sid>adm user:
./saphostctrl -function ConfigureOutsideDiscovery -enable -sldusername FRN_LDDS_<CID> -sldpassword <Password> -sldhost <Reverse Proxy FQDN> -sldport <Reverse Proxy Port>
https://support.sap.com/en/alm/sap-focused-run/expert-portal/managed-systems-maintenance-guide/preparing-outside-discovery.html?anchorId=section
- SDA installed and configured via the Agent Administration app in the FRUN launchpad (Infrastructure Administration block). After installation, the agent must also be configured to receive monitoring definitions from FRUN and to enable self-monitoring.
- Appropriate SSI authorization schedule assigned to the user performing the configuration. SSI supports the following authorization schedules: Display, Execute, Expert, and Administrator. Refer to the SAP Focused Run Security Guide for details.
For JAVA Systems — Additional Prerequisites
- Introscope Agent installed and configured on the Java managed system.
- Java VM parameters set via SAP J2EE Configtool, including:
- com.wily.introscope.agent.agentName
- com.wily.introscope.agentProfile
- -javaagent:/usr/sap/ccms/wily/Agent.jar
- SAP instances restarted after Configtool changes.
- Wily Enterprise Manager connected to the FRUN system by updating IntroscopeEnterpriseManager.properties and restarting the Wily EM.
For more information, please refer to https://support.sap.com/en/alm/sap-focused-run/expert-portal/frun-supported-products/frun-setup-nw-java.html
How to Execute Edit Configuration
Once all prerequisites are met, follow these steps:
- Navigate to the Infrastructure Administration section of the SAP Focused Run launchpad (transaction FRUN).
- Open the Simple System Integration app.
- Search for the relevant technical system using the Go button.
- Select the row for the target system.
- Click Edit Configuration — a dialog/pop-up will appear.
- Enter the required parameters depending on system type:
- ABAP: Enter the SDAGENT user credentials (username and password).
- JAVA: Enter the SDAGENTJ user credentials plus the HTTP and P4 ports.
- Save the configuration.
- Click Configure Automatically to trigger the full automated configuration.
Note: If the system has previously been configured and its Lifecycle Status is Active, saving parameters via Edit Configuration will automatically trigger a new configuration run.
Common Issues & Troubleshooting
Issue | Cause | Resolution |
|
“Authentication did not succeed” / P4 connection check failed | The SDAgent/FRUN monitoring user on the managed system has an authentication problem — user may be locked, have an incorrect password, or be missing required roles. | 1. Verify the FRUN user exists on the managed system. 2. Confirm all roles/profiles per SAP Note 2450740 are assigned. 3. Check if the user is locked and reset the password if necessary. 4. Ensure the user is not being used elsewhere with an incorrect password. |
|
Edit Configuration saved but Configure Automatically does not start | The automatic configuration only triggers if the system's Lifecycle Status was previously Active (i.e., it has been configured before). If the system is new or in a non-Active state, it will not auto-trigger. | Check the Lifecycle Status of the system in SSI. If the status is not Active, manually click Configure Automatically after saving the Edit Configuration parameters. Also check for any messages about invalid parameter values. |
|
SSI configuration step fails with an error | Various causes — could be connectivity issues, missing prerequisites, or system-specific configuration errors. | 1. Rerun the SSI step that generated the error. 2. Go to transaction SLG1, enter Object: AI_SSI, and select the relevant Subobject: AMA (Agent Management), CLEANUP (System Cleanup), or CONFIGURATION (SSI Configuration). 3. Review the detailed error message. 4. If the error persists, raise a case under component SV-FRN-INF-SSI and attach the error message. KBA 3573699 – How to troubleshooting on errors during SSI execution — SAP Focused Run |
|
SDA installation or configuration issues | SDA binary not uploaded to FRUN, host not registered via Outside Discovery, or agent configuration incomplete. | 1. Upload SDA binaries to FRUN using report SRSM_AMA_UPLOAD_BINARY (transaction SA38). 2. Verify host registration via Outside Discovery commands. 3. Use the Agent Administration app to install/update the agent and configure it post-installation. 4. Refer to SAP Note 3210747 — Guided Answer for FRUN Simple Diagnostic Agent Troubleshooting for known SDA issues. |
|
Managed system not visible in SSI after host registration | Outside Discovery not executed, or LMDB Data Supplier Completeness check is not green. | Re-execute the Outside Discovery commands on the managed system host. Verify in LMDB that the system is registered and the Data Supplier Completeness check is green before proceeding with SSI. |
|
Configuration triggers database configuration unexpectedly | Technical systems rely on an underlying database; FRUN configures them together as a functional unit. | This is expected behavior. Databases affiliated with a technical system are configured together with it. Standalone databases without such affiliation must be configured explicitly as separate technical systems. |
|
Configuration takes a very long time | The configuration involves many steps including exchange of communication parameters and configuration data for all hosts and affiliated databases, which is inherently time-consuming and depends on overall system workload. | Use the Refresh Selected action to get the latest known status of the system. Do not interrupt the process prematurely. |
|
Additional Resources
For further guidance, refer to the following resources:
- SSI UI User Guide: SAP Focused Run Expert Portal
- Managed System Preparation Troubleshooting: Available on the SAP Focused Run Expert Portal
- Simple System Integration Troubleshooting: SSI Troubleshooting Guide
- SAP Note 2450740 — Roles to authorize access in managed systems for FRUN data collection
- SAP Note 3210747 — Guided Answer for FRUN Simple Diagnostic Agent Troubleshooting
- SAP Note 3573699 — How to troubleshoot errors during SSI execution
- SAP Note 3537607 — Corrections for SSI in Focused Run 5.x
