How SapAgentConfig.xml gets constructed?

[Former Member]

Hi All,

Does anyone know how this SapAgentConfig.xml get constructed? I keep getting waning about invalid property sysno for a destination. This happens during the configuration of a managed system. It seems that this file SapAgentConfig.xml gets recreated during the setup. When it is created, it truncated the sysno.

Here is the error in the log:

Error com.sap.smd.wily.hostagent.config.AgentConfigVO - finalizeDestination(): Initialization failed

[EXCEPTION]

com.sap.smd.wily.hostagent.PermanentException: Configuration Error: invalid property sysno for destination SapStartSrv_SAPDZSMP_SMP_

Any suggestions is greatly appreciated.

Thanks,

Garry

[former_member220077]

You need to setup the agent, here's a copy of the instructions

Start the Diagnostics administration tool named u201CIntroscope Agentu201D:

Logon as an admin user (URL http://<host>:<port>/smd --> Diagnostics Setup --> Managed Systems --> Introscope Agent)

This tool requires several settings, which are used to perform this remote-deployment and configuration for one or several Introscope Bytecode Agents.

These settings are:

The Introscope Bytecode Agent must report to an Introscope Enterprise Manager (IS EM). Therefore provide the hostname and port number to be used by the Bytecode Agent to connect to the dedicated Introscope Enterprise Manager.

Select the managed system, in the dropdown list, for which you would like to remotely setup or upgrade an Introscope Bytecode Agent. The Introscope Bytecode agents are activated (installed) per managed system J2EE engine SERVER NODE. Be aware that the managed system J2EE engineu2019s Dispatcher node(s) is not listed, as it is not necessarily relevant to instrument those nodes.

Note: In case you do not see the system / server nodes that you defined in SLD / SMSY, double check your system definition in SLD / SMSY and run the managed system setup wizard again.

Choose the adequate profile (instrumentation) associated to the type of managed system. By default use the IntroscopeAgent.profile. Whereas for XI systems, select the IntroscopeAgent_xi.profile.

In very specific situation (like 3rd party product) you may require that additional metrics are collected and will therefore choose extended instrumentations. This could be done within the Autoprobe Directives selection.

FOR AIX SYSTEMS ONLY:

An additional setting will be required. Please make sure whether the managed system is running within u201CJ9 modeu201D (JVM parameters u2013Xj9 or at managed system J2EE engine OS level) before you complete this setup! Providing a wrong information at this level will prevent your managed system from u201Ccoming-upu201D again after the system restart.

Find hereafter some more details on the various u201Csectionsu201D displayed by this setup tool.

[rkresha]

I too am having this problem. Any help would be appreciated.