Preparing CA APM Introscope Enterprise Manager
For more information on Introscope, please check the respective pages in the SAP Solution Manager Application Operations Expert Portal here.
| Task | Actions |
|---|---|
| Run Outside Discovery on the Host | As prerequisites, you shall install the SAP Host Agent and run Outside Discovery as described in page Preparing Outside Discovery. |
Install CA APM EM Use CA APM EM 10.8 | Situation until/including SAP Focused Run 2.0 FP01 Note: Only one CA APM EM system per Customer Network must be installed. Having multiple CA APM EM is an unsupported scenario. Since SAP Focused Run does not yet support an Introscope EM cluster a workaround must be applied to connect a MoM as a "faked" Standalone EM to SAP Focused Run. To do so the property com.sap.sldds.override.type=EnterpriseManager has to be added in file <EM_HOME>/config/IntroscopeEnterpriseManager.properties. Restart EM and as a result the MoM appears as Standalone EM in LMDB. Situation per SAP Focused Run 2.0 FP02 Note: Per Customer Network, either one Enterprise Manager Standalone or one Enterprise Manager Cluster (aka MoM) is supported. Having multiple of these systems in one Customer Network is an unsupported scenario. Due to SSI reconfigurations based on background LMDB events, the last configured Enterprise Manager system, would take-over the role of “leading” Enterprise Manager system in the respective Customer Network. In case you install an Enterprise Manager Cluster, you can install an arbitrary number of Enterprise Manager Collector Instances in the same Customer Network. If you have the applied the workaround to connect a MoM as a "faked" Enterprise Manager Standalone to SAP Focused Run, you should revert this workaround. To do so the property com.sap.sldds.override.type=EnterpriseManager has to be deleted from file <EM_HOME>/config/IntroscopeEnterpriseManager.properties. Restart EM and as a result the MoM appears as IS_MOM in LMDB. In LMDB:
As root or Administrator, upgrade the SAP Host Agent to the latest 7.21 Patch Layer Level version. Check Global SAP Note 797147 for installation procedure of CA APM EM, CA APM EM Agents and Webview. As sapadm (and part of group sapsys), install one CA APM EM, typically on the customer management server. Follow the CA APM installation guide, referenced by SAP Note 3247270. If you cannot run the EM as user sapadm then you have to make sure that the Simple Diagnostics Agent (running with user sapadm) has write permission into the folder /sap of the EM installation: The agent writes the central configuration file for pushing system monitoring metrics into this folder. The CA APM EM Management Module (MM) Packages shall have version:
No CA APM EM is required in a given Customer Network, if no BCI Adapter are installed on managed systems that belongs to this Customer Network. Note: If you have upgraded the SAP Host Agent before to Install the CA APM EM, you must restart it after the Data Supplier execution. |
| Check if an SLD Data Router (SLDR) is needed | As a prerequisite, you need to choose, according to your landscape, if an SLD Data Router is required see page Preparing System Landscape Data Router. |
Configure SLD DS CA APM EM creates an SLD DS payload, sent to SAP Focused Run by the SAP Host Agent. If host name virtualization is in use, this name must be provided as part of the SLD payload. | This user must have Administration permissions (Automation possible via OS script) Update IntroscopeEnterpriseManager.properties file, setting: A restart of the CA APM EM triggers: -payload file registration to the SAP Host Agent (saphostctrl -function ConfigureOutsideDiscoveryPath -register <file>) -payload file sending (saphostctrl -function ExecuteOutsideDiscovery -xmlfromconfig -sldreg) |
| Create a Technical User | A Monitoring User is required if the Trace Analysis feature is enabled (use-case AUM – Advanced User Monitoring) as described in the Security Guide. The Monitoring User must be entered in the “Edit Configuration” dialog in Simple System Integration. |