When a SAPRouter string is used by the SMDAgents to connect to the SAP Solution Manager system, the Introscope Host Adapters and the Byte Code Adapters must also be configured to use the same SAPRouter string to connect to the Enterprise Manager. It might be the case where the SMDAgents are configured to use SAPRouter string to connect to the Solman, however after run the activity Byte Code Adapter Installation the 'Byte Code Adapters' (Introscope JAVA Agents) are not configured to use SAPRouter string. Then in the Introscope Investigator, the node 'SAP Netweaver' will be missing for the target system servers.
In the IntroscopeAgent.profile for the affected Byte Code Adapters it is possible to see that they are configured to use the default connection settings, the following connection properties are active in the IntroscopeAgent.profile:
In the IntroscopeAgent.log file it is also possible to confirm that the Byte Code Adapter is not using the SAPRouter string to connect to the Enterprise Managers, the following connection error will be shown:
|5/31/15 11:35:17 PM CEST [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at myenterprise.manager.com:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (10).|
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
- SAP Solution Manager 7.10
- SAP Solution Manager Diagnostics
KBA , SV-SMG-DIA-WLY-BCA , Byte Code Agent Setup , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.