Skip to end of metadata
Go to start of metadata

After perform the Byte Code Adapter (ISAgent) Installation in the Managed System Configuration and restart the managed system, you noticed that the ISAgent didn't start. The node SAP Netweaver that should be created by this agent is missing for the target managed host in the Introscope Investigator (Workstation or webview). The following picture shows an example of the Introscope Investigator:

 

If the entries 'SAP Netweaver' + <SID_of_managed_system>_<instance>_<servernode> are NOT available in the invstigator, this means that the Byte Code Adapter (ISAgent) could not connect to the Enterprise Manager or it is not running. In this case, check the IntroscopeAgent.log that is usually located in the temp folder of the SMDAgent or managed system folder:

  • \usr\sap\SMD\SMDA97\SMDAgent\temp
  • \usr\sap\<ManagedSID>\<InstanceID>\<ByteCodeAdapter> (If Ensure HA virtualization compatibility=true)

If the IntroscopeAgent.log does not exist or is not being updated for a long period, this means that the Byte Code Adapter (ISAgent) is not running. In this case, check the results of activity Byte Code Adapter Installation in the Managed System Configuration for the target system. The activity Byte Code Adapter Installation is responsible to deploy the ISAgent files and configure the ISAgents JAVA parameters in the managed system.

If the managed system runs on a UNIX server, ensure that the OS permissions are correctly configured as described in note 1163751. In most of the cases the Byte Code Adapter cannot start due to wrong permissions at OS level.  The easiest configuration to make it work is to give 775 (e.g: chmod 775) permissions to the Managed System OS user in the Byde Code Adapter folder.

It is possible to check the managed system startup files dev_server* and std_server* to search for issues related to the Byde Code Adapter:

  • dev_server*: In this file it is possible to see if the JAVA Server node has been started using the ISAgent JAVA parameters. If the parameters are not shown in the file, repeat the Byte Code Adapter Installation for the affected system.
  • std_server*: This file might provide details about the start of the ISAgent. If the ISAgent could not be started for some reason, usually the std_server* shows the root case (where is the permisison problem).

Finally, to start the Byte Code Adapter (ISAgent) it is required to restart the managed system, there is no other way to start the Byte Code Adapter.

 

 

 

 

 

  • No labels