The Byte Code Adapter, also known as IS Agent, is started, but it doesn't generate any logs nor connects to the Enterprise Manager.
In the dev_server* files, found under /usr/sap/<Managed System Java ID>/J<instance number>/work/dev_server<number> of the managed system, it is possible to see it was loaded with the JVM in the arguments list:
F arg = -javaagent:/usr/sap/ByteCodeAdapter/<Managed System ID>/J<instance>/BytecodeAgent/ISAGENT.220.127.116.11-2013-07-23/wily/Agent.jar=-Dcom.wily.introscope.agentProfile=/usr/sap/ByteCodeAdapter/<Managed System ID>/J<instance>/BytecodeAgent/ISAGENT.18.104.22.168-2013-07-23/wily/core/config/<managed system ID>_IntroscopeAgent.profile
Even so, upon checking the Introscope Agent logs folder, it is not possible to see any logs, in the std_server files, the following information is seen:
8/07/17 10:40:05 PM NZST [INFO] [IntroscopeAgent.Agent] Trying to load agent profile based on the working directory at: /usr/sap/<Managed System ID>/J<instance>/j2ee/cluster/server0/wily/IntroscopeAgent.profile
8/07/17 10:40:05 PM NZST [INFO] [IntroscopeAgent.Agent] Unable to load agent profile because of: java.io.FileNotFoundException /usr/sap/<Managed System ID>/J<instance>/j2ee/cluster/server0/wily/IntroscopeAgent.profile (No such file or directory)
In this case, the path provided for the IS Agent profile doesn't exist or is wrong.
- Solution Manager 7.1
- Java managed system
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.