1 Declare Customer Networks (CN)
Ensure that the customer network, relevant to the managed systems, is already declared in SAP Focused Run as described in page Preparing Customer Network.
2 Install or verify version of existing SAP Host Agents (SHA)
A SAP Host Agent shall be installed on all hosts that operate managed objects, including also hosts that operate SAP Focused Run related components, like the SLDR or the CA APM EM, as described in page Preparing Outside Discovery. The sapadm password (see point 8 for details) chosen during the SAP Host Agent installation on the host, must be known during the Customer Network Declaration phase and for the SM59 HTTP destination creation between managed Systems and SAP Focused Run.
3 CA APM Enterprise Manager
If you operate CA APM Enterprise Manager (CA APM EM), make sure the CA APM EM instances are known within LMDB of the SAP Focused Run system, before proceeding with the next steps. See page Preparing CA APM Enterprise Manager.
Check for each Managed System the CA APM Enterprise Manager Byte Code Injection Agent (BCIA) Compatibility with JVM Versions and the SAP Netweaver Version. The BCIA version shall also correspond to the CA APM release which is operated in the Customer Network.
|Java Virtual Machine Version||1.4||1.5||1.6||1.7||1.8|
|SAP NetWeaver Version on Managed System||04 / 7.0 / 7.0 EHP1 / EHP2 / EHP3||7.1 EHP1||7.20 / 7.30 / 7.30 EHP1 / 7.40||n/a||>=7.50|
CA APM Byte Code Injection Agent 8
PPMS: WILY INTROSCOPE AGENT 8
CA APM Byte Code Injection Agent 9.7
PPMS: WILY INTRO AGT MIN 9.7 J5
CA APM Byte Code Injection Agent 10.1
PPMS: WILY INTRO AGT MIN 10.1 J5
CA APM Byte Code Injection Agent 10.5
PPMS: WILY INTRO AGT MIN 10.5 J5
4 Prepare the System Landscape Data Router
According to your current landscape situation: if you operate one or more SAP Focused Run and/or you operate SAP Solution Manager in parallel of SAP Focused Run. See page Preparing System Landscape Data Router.
5 Outside Discovery
Enable the Outside Discovery on each relevant for hosts, databases (except for HANA DB), Microsoft IIS, and the Simple Diagnostics Agents following page Preparing Outside Discovery.
7 Check the SLD Data Suppliers Completeness
Before to execute the SSI Automatic Configuration, ensure, given your product that all the SLD Data Suppliers are complete into LMDB. See the Data Suppliers Completeness Checks troubleshooting page.
To review the completeness check, start the Infrastructure Administration / LMDB Object Maintenance, using the Launchpad, Search for the relevant Technical System, press Display and finally select the entry Data Supplier Completeness Check. For more details, see the SLD Data Suppliers Completeness Checks Troubleshooting page.
8 Perform The Simple System Integration (SSI)
Note: Monitoring User and Monitoring Password information which was chosen during the Preparing Managed Systems phase, must be known during the SSI Operations.
Note: Perform Simple System Integration for the CA APM Enterprise Manager first, before you configure any other systems.
Proceed as follow:
Note: In case of failure, refer to the Troubleshooting page Managed System Preparation - Troubleshooting FAQs
9 Finally, execute the listed application relevant preparation steps, as described in Preparing SAP Focused Run Applications page.