SMD agent on Sol Man 4 instance?
Quick question. Would/should one install the SMD agent on the Solution Manager 4 J2EE instance (as well as on satelite J2EE instances)?
Hi,
of course you may want to diagnose the monitoring system itself. Especially for the Java part of SolMan 4 this is useful.
Kind regards,
Bernie
Similar Messages
-
SMD Agents for Dialog Instances and Distributed Systems
Hi,
We are planning to install SMD agents in our landscape.
Is it sufficient if we install SMD agent on the central instance Host to monitor all the instances ( CI + Dialog Instances)
or
Do we need to install SMD agents individually for all the Instances each for CI and Dialog Instances.
Also , If we have CI and DB on a separate host (Distributed Environment), Do we need to install SMD Agent on DB host also.
Thanks,
TanujHello Tanuj,
Please refer to note 1365123 - Installation of Diagnostics Agents and check the attachments (AgentInstallationStrategy.zip) for this note.
BR,
SAPFan -
Failed to connect to server - Please make sure SMD Agent is up and Running
Hi All
I am getting this message in SMD when trying to set up the SMD agent on one of our JAV servers - this is possibly a really simple problem to solve but I have no idea how to start the SDM Agent.
Can anyone give me instructions on how to do this (Windows / SQL)?
Thanks in advance
PhilHi Phil,
The SMD Agent gets installed as an instance & can be started/stopped via the SAP MMC.
Have a great day,
-S. -
Sol Man 4 - data transfer to SMD - what is installation path?
In Solution manager 4, transactio SOLUTON_MANAGER then select menu path goto > Solution Manager Diagnostics > Solution Data Transfered. It says "This wizard senden the configuration data of solutions to the Solution Manager Diagnostics.". Select continue. Next I select a Solution Landscape and press continue. It seems to select all the servers with a basis level >= 640 and in my case find red opposit the server. If you double click on the server and expand the resulting display to the "SYSTEM - main instance" attribute Installation Path is blank.
What is Installation Path? Nothing I try to enter is valid. Any idea what is supposed to go here?Before you attempt to publish a landscape to SMD there must be an SMD agent on each host running SAP BASIS 640 or higher that has sucessfully connected to the SMD. The wizard takes your specified path and asks the agent on that host to verify that it exists. If there is no agent you get that same cryptic error message.
I suggest you use SM trans SOLUTION_MANAGER to create landscapes comprising of systems you have sucessfully deployed a SMD agent there-on. As you deploy more SMD agents you can either create more landscapes or add those systems to your existing landscape that you have used for "publish to SMD".
Summary:
Step 1) Install SMD
Step 2) Install SMD agent(s)
Step 3) verify http://smhost:smport/smd/admin > Agent administration > Agent tab lists your server(s)
Step 4) create landscapes for publishing wizard
Step 5) publish lanscape expressly tailored for SMD -
SMD agent not starting correctly FAIL: NIECONN_REFUSED (Connection refused)
I am getting the following message when I start the agent. I don't see any errors except for this, and when I try to connect it in agent_adminstration, it never connects. Just eventually times out after 30 mins.
FAIL: NIECONN_REFUSED (Connection refused), NiRawConnect failed in plugin_fopen()
cat jvm_SMDAgent.out
LoadBalanceRestricted=no
P4ClassLoad=P4Connection
SAPDBHOST=
SAPINFO=SMD_98_server
SAPMYNAME=ssmsap_SMD_98
SAPSTARTUP=1
SAPSYSTEM=98
SAPSYSTEMNAME=SMD
application.home=/usr/sap/SMD/exe
com.ibm.cpu.endian=little
com.ibm.oti.configuration=scar
com.ibm.oti.jcl.build=20080922_1143
com.ibm.oti.vm.bootstrap.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
com.ibm.oti.vm.library.version=23
com.ibm.util.extralibs.properties=
com.ibm.vm.bitmode=64
file.encoding=UTF-8
file.separator=/
ibm.signalhandling.rs=false
ibm.signalhandling.sigchain=true
ibm.signalhandling.sigint=true
ibm.system.encoding=UTF-8
j2ee.dbhost=
java.assistive=ON
java.awt.fonts=
java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
java.awt.printerjob=sun.print.PSPrinterJob
java.class.path=/usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar:../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
java.class.version=48.0
java.compiler=j9jit23
java.ext.dirs=/opt/IBMJava2-amd64-142/jre/lib/ext
java.fullversion=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
J9VM - 20080922_23329_LHdSMr
JIT - 20080815_1845_r8
GC - 200809_04
java.home=/opt/IBMJava2-amd64-142/jre
java.io.tmpdir=/tmp
java.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/classic:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SMD/exe:/usr/lib:/usr/sap/SMD/exe:/usr/sap/SMD/exe
java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
java.runtime.version=2.3
java.specification.name=Java Platform API Specification
java.specification.vendor=Sun Microsystems Inc.
java.specification.version=1.4
java.util.prefs.PreferencesFactory=java.util.prefs.FileSystemPreferencesFactory
java.vendor=IBM Corporation
java.vendor.url=http://www.ibm.com/
java.version=1.4.2
java.vm.info=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
J9VM - 20080922_23329_LHdSMr
JIT - 20080815_1845_r8
GC - 200809_04
java.vm.name=IBM J9 VM
java.vm.specification.name=Java Virtual Machine Specification
java.vm.specification.vendor=Sun Microsystems Inc.
java.vm.specification.version=1.0
java.vm.vendor=IBM Corporation
java.vm.version=2.3
jstartup.debuggable=yes
jstartup.mode=JCONTROL
jstartup.ownHardwareId=F2143454721
jstartup.ownProcessId=17393
jstartup.whoami=server
jxe.current.romimage.version=9
jxe.lowest.romimage.version=9
line.separator=
memory.manager=256M
os.arch=amd64
os.name=Linux
os.version=2.6.9-89.ELsmp
path.separator=:
sun.boot.class.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm/jclSC14/classes.zip:/opt/IBMJava2-amd64-142/jre/lib/core.jar:/opt/IBMJava2-amd64-142/jre/lib/charsets.jar:/opt/IBMJava2-amd64-142/jre/lib/graphics.jar:/opt/IBMJava2-amd64-142/jre/lib/security.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmpkcs.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorb.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorbapi.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjcefw.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjssefips.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjgssprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjsseprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjaaslm.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmcertpathprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/server.jar:/opt/IBMJava2-amd64-142/jre/lib/xml.jar
sun.boot.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
sun.io.unicode.encoding=UnicodeLittle
sun.java2d.fontpath=
sys.global.dir=/usr/sap/SMD/SYS/global
user.country=US
user.dir=/usr/sap/SMD/J98/SMDAgent
user.home=/home/smdadm
user.language=en
user.name=smdadm
user.timezone=
user.variant=
Running SMD Agent ...
[p4://ssmsap:50004] Agent ready.
Initialization done.
cat jvm_SMDAgent.out
LoadBalanceRestricted=no
P4ClassLoad=P4Connection
SAPDBHOST=
SAPINFO=SMD_98_server
SAPMYNAME=ssmsap_SMD_98
SAPSTARTUP=1
SAPSYSTEM=98
SAPSYSTEMNAME=SMD
application.home=/usr/sap/SMD/exe
com.ibm.cpu.endian=little
com.ibm.oti.configuration=scar
com.ibm.oti.jcl.build=20080922_1143
com.ibm.oti.vm.bootstrap.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
com.ibm.oti.vm.library.version=23
com.ibm.util.extralibs.properties=
com.ibm.vm.bitmode=64
file.encoding=UTF-8
file.separator=/
ibm.signalhandling.rs=false
ibm.signalhandling.sigchain=true
ibm.signalhandling.sigint=true
ibm.system.encoding=UTF-8
j2ee.dbhost=
java.assistive=ON
java.awt.fonts=
java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
java.awt.printerjob=sun.print.PSPrinterJob
java.class.path=/usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar:../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
java.class.version=48.0
java.compiler=j9jit23
java.ext.dirs=/opt/IBMJava2-amd64-142/jre/lib/ext
java.fullversion=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
J9VM - 20080922_23329_LHdSMr
JIT - 20080815_1845_r8
GC - 200809_04
java.home=/opt/IBMJava2-amd64-142/jre
java.io.tmpdir=/tmp
java.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/classic:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SMD/exe:/usr/lib:/usr/sap/SMD/exe:/usr/sap/SMD/exe
java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
java.runtime.version=2.3
java.specification.name=Java Platform API Specification
java.specification.vendor=Sun Microsystems Inc.
java.specification.version=1.4
java.util.prefs.PreferencesFactory=java.util.prefs.FileSystemPreferencesFactory
java.vendor=IBM Corporation
java.vendor.url=http://www.ibm.com/
java.version=1.4.2
java.vm.info=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
J9VM - 20080922_23329_LHdSMr
JIT - 20080815_1845_r8
GC - 200809_04
java.vm.name=IBM J9 VM
java.vm.specification.name=Java Virtual Machine Specification
java.vm.specification.vendor=Sun Microsystems Inc.
java.vm.specification.version=1.0
java.vm.vendor=IBM Corporation
java.vm.version=2.3
jstartup.debuggable=yes
jstartup.mode=JCONTROL
jstartup.ownHardwareId=F2143454721
jstartup.ownProcessId=17393
jstartup.whoami=server
jxe.current.romimage.version=9
jxe.lowest.romimage.version=9
line.separator=
memory.manager=256M
os.arch=amd64
os.name=Linux
os.version=2.6.9-89.ELsmp
path.separator=:
sun.boot.class.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm/jclSC14/classes.zip:/opt/IBMJava2-amd64-142/jre/lib/core.jar:/opt/IBMJava2-amd64-142/jre/lib/charsets.jar:/opt/IBMJava2-amd64-142/jre/lib/graphics.jar:/opt/IBMJava2-amd64-142/jre/lib/security.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmpkcs.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorb.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorbapi.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjcefw.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjssefips.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjgssprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjsseprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjaaslm.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmcertpathprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/server.jar:/opt/IBMJava2-amd64-142/jre/lib/xml.jar
sun.boot.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
sun.io.unicode.encoding=UnicodeLittle
sun.java2d.fontpath=
sys.global.dir=/usr/sap/SMD/SYS/global
user.country=US
user.dir=/usr/sap/SMD/J98/SMDAgent
user.home=/home/smdadm
user.language=en
user.name=smdadm
user.timezone=
user.variant=
Running SMD Agent ...
[p4://ssmsap:50004] Agent ready.
Initialization done.cat dev_SMDAgent
trc file: "/usr/sap/SMD/J98/work/dev_SMDAgent", trc level: 1, release: "701"
node name : smdagent
pid : 17393
system name : SMD
system nr. : 98
started at : Wed Oct 7 08:56:32 2009
arguments :
arg[00] : /usr/sap/SMD/J98/../exe/jlaunch
arg[01] : pf=/usr/sap/SMD/J98/../SYS/profile/SMD_J98_ssmsap
arg[02] : -DSAPINFO=SMD_98_server
arg[03] : pf=/usr/sap/SMD/J98/../SYS/profile/SMD_J98_ssmsap
JStartupReadInstanceProperties: read instance properties [/usr/sap/SMD/J98/profile/smd.properties]
-> ms host :
-> ms port : 36
-> OS libs : /usr/sap/SMD/exe
-> Admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Used property files
-> files [00] : /usr/sap/SMD/J98/profile/smd.properties
Instance properties
-> ms host :
-> ms port : 36
-> os libs : /usr/sap/SMD/exe
-> admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Bootstrap nodes
Worker nodes
-> [00] smdagent : /usr/sap/SMD/J98/profile/smd.properties
[Thr 182894174624] Wed Oct 7 08:56:32 2009
[Thr 182894174624] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 182894174624] JLaunchRequestQueueInit: create pipe listener thread
[Thr 1074792800] JLaunchRequestFunc: Thread 1074792800 started as listener thread for np messages.
[Thr 1085282656] WaitSyncSemThread: Thread 1085282656 started as semaphore monitor thread.
[Thr 182894174624] SigISetDefaultAction : default handling for signal 17
[Thr 182894174624] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
[Thr 182894174624] CPIC (version=701.2009.01.26)
[Thr 182894174624] [Node: SMDAgent] java home is set by profile parameter
Java Home: /opt/IBMJava2-amd64-142
[Thr 182894174624] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/SMD/J98/../exe/jvmx.jar
JStartupIReadSection: read node properties [smdagent]
-> node name : SMDAgent
-> node type : server
-> node id : 1
-> node execute : yes
-> java path : /opt/IBMJava2-amd64-142
-> java parameters : -DP4ClassLoad=P4Connection -Xj9 -Xmn50m -Xgcpolicy:gencon
-> java vm version : J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
-> java vm vendor : IBM J9 VM (IBM Corporation)
-> java vm type : server
-> java vm cpu : amd64
-> heap size : 256M
-> init heap size : 256M
-> root path : ../SMDAgent
-> class path : ../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
-> OS libs path : /usr/sap/SMD/exe
-> main class : com.sap.smd.agent.launcher.SMDAgentLauncher
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : /usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar
-> parameters : run jcontrol
-> debuggable : yes
-> debug mode : no
-> debug port : 58981
-> shutdown timeout : 20000
[Thr 182894174624] JLaunchISetDebugMode: set debug mode [no]
[Thr 1086335328] JLaunchIStartFunc: Thread 1086335328 started as Java VM thread.
JHVM_LoadJavaVM: VM Arguments of node [SMDAgent]
-> stack : 1048576 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -DP4ClassLoad=P4Connection
-> arg[ 4]: -Xj9
-> arg[ 5]: -Xmn50m
-> arg[ 6]: -Xgcpolicy:gencon
-> arg[ 7]: -Dsys.global.dir=/usr/sap/SMD/SYS/global
-> arg[ 8]: -Dapplication.home=/usr/sap/SMD/exe
-> arg[ 9]: -Djava.class.path=/usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar:../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
-> arg[ 10]: -Djava.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/classic:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SMD/exe:/usr/lib:/usr/sap/SMD/exe:/usr/sap/SMD/exe
-> arg[ 11]: -Dmemory.manager=256M
-> arg[ 12]: -Xmx256M
-> arg[ 13]: -Xms256M
-> arg[ 14]: -DLoadBalanceRestricted=no
-> arg[ 15]: -Djstartup.mode=JCONTROL
-> arg[ 16]: -Djstartup.ownProcessId=17393
-> arg[ 17]: -Djstartup.ownHardwareId=F2143454721
-> arg[ 18]: -Djstartup.whoami=server
-> arg[ 19]: -Djstartup.debuggable=yes
-> arg[ 20]: -DSAPINFO=SMD_98_server
-> arg[ 21]: -DSAPSTARTUP=1
-> arg[ 22]: -DSAPSYSTEM=98
-> arg[ 23]: -DSAPSYSTEMNAME=SMD
-> arg[ 24]: -DSAPMYNAME=ssmsap_SMD_98
-> arg[ 25]: -DSAPDBHOST=
-> arg[ 26]: -Dj2ee.dbhost=
[Thr 1086335328] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [SMDAgent]
-> arg[ 0]: run
-> arg[ 1]: jcontrol
[Thr 1086335328] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 1086335328] Wed Oct 7 08:56:35 2009
[Thr 1086335328] JLaunchISetState: change state from [Initial (0)] to [Initial (0)]
[Thr 1086335328] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 1086335328] Wed Oct 7 08:56:38 2009
[Thr 1086335328] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 1086335328] JLaunchISetState: change state from [Starting (2)] to [Running (3)]
[Thr 1101334880] Wed Oct 7 08:56:43 2009
[Thr 1101334880] JLaunchISetState: change state from [Running (3)] to [Starting applications (10)]
[Thr 1101334880] Wed Oct 7 08:56:48 2009
[Thr 1101334880] JLaunchISetState: change state from [Starting applications (10)] to [Running (3)] -
Does solution manager 4.0 require SMD Agent?
we have solman 4.0 abap+java with sp11.we are in the process of configuring sol mananager diagnostics for sattlite systems.
for monitoring solution manager java stack it self from solution manager do we need to install SMD AGENT even thogh solution manger it self has SMD server ? still solution manger need SMD AGENT ?Hi,
SMD Agents are mandatory to run Diagnostics on sattelite systems.
Each Agent is connected to SMD Server and is able to run task or collect information from central request (SMD Server).
If you do not have them, you will not be able to run any tools in Diag.
SMD Server is one sub-component of Solution Manager 4.0.
Regards,
Frederic -
Hello All,
In order to install Wily Introscope Agent, initially I have installed
a SMD Agent on managed system host.
After the installtion of SMD Agent , while starting the SMD agent I am getting below error .
Starting SMDAgent ...
Establishing connection to server '[host is empty]' on port [port is
empty]
Smd connector is disabled because no SLD association and no credentials
found.
Smd connector is disabled because no SLD association and no credentials
found.
Waiting for connection ...
Checking server availability...
Warning :
Connecting to SMD server null failed - error counter: 0 -
com.sap.engine.services.jndi.persistent.exceptions.NamingException: No
InitialContext can be created because the java.naming.provider.url
property is no specified in the jndi environment.
Next try to push instance data in SLD is Tue May 19 14:36:31 CDT 2009
I have given user SLDAPIUSER in SLDAPICUST transaction. This user
which is not locked and I have also reconfirmed the password of this
user.
Kindly request your suggestion!!!!
Regards,
SuhasSantosh Asuthkar
I am receiving the same error in my SMD agent log:
Starting SMDAgent ...
Dec 8, 2009 1:43:48 PM [Thread[main,5,main]] Info Establishing connection to server '[host is empty]' on port [port is empty]
Dec 8, 2009 1:43:51 PM [Thread[SMDAgent connection thread,5,main]] Info Smd connector is disabled because no SLD association and no cred
entials found.
Dec 8, 2009 1:43:51 PM [Thread[SMDAgent connection thread,5,main]] Info Smd connector is disabled because no SLD association and no cred
entials found.
Dec 8, 2009 1:43:51 PM [Thread[SMDAgent connection thread,5,main]] Info [null] Waiting for connection ...
Dec 8, 2009 1:43:52 PM [Thread[SMDAgent connection thread,5,main]] Info [null] Checking server availability...
Dec 8, 2009 1:43:53 PM [Thread[SMDAgent connection thread,5,main]] Warning Connecting to SMD server null failed - error counter: 0 - com.sa
p.engine.services.jndi.persistent.exceptions.NamingException: No InitialContext can be created because the java.naming.provider.url property i
s no specified in the jndi environment.
Dec 8, 2009 1:43:54 PM [Thread[SLD-Registration,1,main]] Info [SLDReg] Next try to push instance data in SLD is Wed Dec 09 01:43:54 EST
2009
Dec 8, 2009 1:46:52 PM [Thread[SLD-AssocWatcher,1,main]] Info [SLDManagingConnectionMonitor] Next time to check Managing System Associat
ion is Tue Dec 08 14:01:52 EST 2009
Can you please provide details if you found a solution?
Thanks!!!!!
Jeff -
Monitoring SMD Agent with CCMS
Hi gurues, I need to know if there is any way to monitor SMD Agent installed in an application server via CCMS CEN system on a Solution Manager.
Right now we have CEN Monitoring define on Solution Manager, and several SMD Agents over the whole landscape, and it is critical for us to get alerted when this SMD goes down, so we are thinking about monitoring through Solutin Manager, isthat possible or we must do it in another way?
Regards
GustavoIt's so typical SAP; I was looking for exactly the same question. SAP changed from 7.1 the OSCOL to run by the host agent instance and will not install the OSCOL to the SAP instance. You also will not be able to download OSCOL separatly.
But OSCOL is needed to monitor processes on host side. If the host agent don't starts also the OSCOL will not start (on LINUX side) and so you are not be able to monitor the SMD process.
The only chance is to start the SMD via init script.
A better way would be to implement a GRMG availability monitoring; this can be implemented in the CEN system independent from the monitored host. In the first solution the host has to be create itself the basis to monitor itself... that's nonsense.
I absolutly don't understand why SAP always and everywhere ignore his own design concept and reinvent the wheel. It would be so easy to design and implement the availability moniroring on SAP development side but they don't have a focus on that. It is the same with SAP router connection via host agent to the CEN system. It was implemented as very last feature after a lot of disgruntled customers (administrators). -
Change the Standard Installation Directory of SMD Agent
Hi Everyone,
Standard Installation Directory of SMD Agnet is /usr/sap/SMD which I want to change & Install the SMD Agent
under /usr/sap/<SID>/SMD directory
I dont want maintain soft link way
Is it possible , If yes then How ??
Thanks in advance
Regards
Deepak GosainDear Deepak Gosain
Keep in mind that Diagnostics Agent 7.11 is the new version for SAP Solution Manager EHP1 > SP20. Depending on your current version of Solution Manager you might want to start installating the new version.
The new version has it's own unique SID and acts like a SAP system: for example for stop/start it uses stopsap and startsap commands, instance profiles and SAP JVM instead of OS JVM.
Structure in new version is /usr/sap/<SID>/SDMA<instance no> where SID needs to be unique (so not your existing SAP system SID).
Kind regards
Tom -
How to install SMD Agent on a MSCS?
Hello helpers,
we have installed a PI 7.1 (double stack) on a MSCS environment. The next step is to connect the PI 7.1 SAP system to our SolMan and to install the diagnostics agent. Unfortunately I wasn't able to find any documentation explaining an installation of the SMD Agent in a MSCS environment.
Does anybody know what has to be done? Do I have to install 3 agents, one on every MSCS node and one in the SCS/ASCS cluster resource group, or is only one agent needed in the SCS/ASCS cluster resource group?
Looking forward for any answers,
Sascha PiotrowskyHi Sascha,
To distribute a solution to the diagnostics the install path must be verified in TC SMDIAG_WIZARD. To verify the install paths an installed SMD-AGENT is neccessary.
Yes
Another point is that we like to monitor the J2EE Servers and Dispatchers from the 2 instances on "nodeA" and "nodeB". So in my opinion at least 2 SMD-Agent should be installed, one on every node. Do you agree?
No, you need one SMD Agent, this agent can then monitor multiple instances on one virtual host. The connection is only between virtual host and agent, not between instance and agent.
But what shall I do with the ASCS00/SCS01 instance. Does an SMD-Agent installation bring any effort on "clusterSID" or is it a must?
It's not a must, only relevant if you want to receive host metrics from this host. As this is only virtual, I would not install one here.
Best regards
Michael -
Solution Manger Diagnostics setup (SMD Agent)
Hi All
I have managed to setup Solution Manager Diagnostics and Deploy on of the agents to out DEV BI Server (JAVA), however I keep getting the message:
"Failed to connect to server: bidevdb - Please make sure SMD Agent is up and running"
Now I can see in the SAPMSC that the SMD agent is running - so I am not sure why this is the case. Does SMD require SAPCCMS setup as a windoes service on the BI Server?
Or what else can I check to find out what the issue might be?
Thanks all in advance (will award points for helpfull answers)SMDSystem.x.log
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[SMDSystemLog]/>
<!PATTERN[SMDSystem.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%t] %10s %m)]/>
<!ENCODING[Cp1252]/>
<!FILESET[0, 10, 1000000]/>
<!PREVIOUSFILE[SMDSystem.9.log]/>
<!NEXTFILE[SMDSystem.1.log]/>
<!LOGHEADER[END]/>
Mar 25, 2010 2:23:08 PM [Thread[main,5,main]] Info Starting SMDAgent ...
Mar 25, 2010 2:23:09 PM [Thread[main,5,main]] Info ===> Establishing connection to server '[host is empty]' on port [port is empty]
Mar 25, 2010 2:23:11 PM [Thread[Connector,5,main]] Info Smd connector is disabled because no SLD association and no credentials found.
Mar 25, 2010 2:23:11 PM [Thread[Connector,5,main]] Info Smd connector is disabled because no SLD association and no credentials found.
Mar 25, 2010 2:23:12 PM [Thread[SLD-Registration,1,main]] Error Cannot retrieve saposcol hardware info for SLD data instance.
[EXCEPTION]
java.io.IOException: CreateProcess: ..\..\exe\saposcol -b error=2
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.<init>(ProcessImpl.java:85)
at java.lang.ProcessImpl.start(ProcessImpl.java:30)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
at java.lang.Runtime.exec(Runtime.java:591)
at java.lang.Runtime.exec(Runtime.java:429)
at java.lang.Runtime.exec(Runtime.java:326)
at com.sap.smd.agent.util.RunExec.exec(RunExec.java:78)
at com.sap.smd.agent.util.RunExec.exec(RunExec.java:55)
at com.sap.smd.agent.util.RunExec.execAndWaitFor(RunExec.java:158)
at com.sap.smd.agent.util.RunExec.execAndWaitFor(RunExec.java:148)
at com.sap.smd.agent.connection.sld.SLDAgentDataBuilder.getSAPOSColHostInfo(SLDAgentDataBuilder.java:254)
at com.sap.smd.agent.connection.sld.SLDAgentDataBuilder.addAgentHostMember(SLDAgentDataBuilder.java:195)
at com.sap.smd.agent.connection.sld.SLDAgentDataBuilder.addGroupAgentInstance(SLDAgentDataBuilder.java:132)
at com.sap.smd.agent.connection.sld.SLDAgentDataBuilder.addSLDInfoNodeForAgentRegistration(SLDAgentDataBuilder.java:498)
at com.sap.smd.agent.connection.sld.SLDAgentDataBuilder.writeAgentInstanceData(SLDAgentDataBuilder.java:597)
at com.sap.smd.agent.connection.sld.SLDQueryBuilder.registerAgentInstanceData(SLDQueryBuilder.java:604)
at com.sap.smd.agent.connection.sld.process.SLDReg.run(SLDReg.java:68)
at java.lang.Thread.run(Thread.java:664)
Mar 25, 2010 2:23:12 PM [Thread[SLD-Registration,1,main]] Info [SLDReg] Next try to push instance data in SLD is Fri Mar 26 02:23:12 GMT 2010
Could not find the SMDAgentApplication.X.log
Does that help? -
Sol Man HP QC Integration -Install TAO Client
Hi Team,
I am having the requirement to integrate SAP Sol Man with HP QC. In the process, it has been mentioned that, "Install TAO Agents in the SAP Backend systems".
What is TAO clinet? Why this is to be installed?
Backend system means , all the satellite systems which have been conneted with sol Man?
Thanks in advance
KumarHi Kumar,
What is TAO clinet? Why this is to be installed?
This is just another type of application. The SAP Test Acceleration and Optimization application supports customers in automating their business process tests by automatically generating draft test cases and test components. Its tight integration with SAP Solution Manager helps in identifying the impacted test cases and components when there are changes in the landscape. The SAP Test Acceleration and Optimization application creates modular test cases, which are easy to maintain, when the test cases are damaged due to functional changes.
The SAP Test Acceleration and Optimization application supports customers in automating their business process tests by automatically generating draft test cases and test components for SAP GUIu2013based transactions. Using this application in combination with the SAP Quality Center application by HP, you can modify, compose and execute automated business process tests in SAP software development and test systems. The SAP Test Acceleration and Optimization application also provides a lot of reusable library components, which could be used for test composition.
Backend system means , all the satellite systems which have been conneted with sol Man?
It might be all the systems or the system through which you want to perform, or the systems that you want to test the Business Processes
For more details please check these SAP Notes.
Note: 1391728 SAP TAO 2.0 Release and Upgrade Information.
Note: 1404715 SAP TAO 2 Installation Information.
SAP TAO Agent will be available with the SAP Solution Tools Plug-In ST-PI which has to be implemented on all the managed systems that we are planning to connect to the SolMan and SAP TAO systems.There is a compatibility matrix which you can find in the Note: 1404715.
Also you can find some materials and demos under http://service.sap.com/testing Test Management and Media Library.
Hope this is helpful.
Thanks & Best Regards,
Raghavendra.
Edited by: Raghavendra B Deshpande on Jul 2, 2010 6:42 AM -
The SMD Agent 'slcxemw04vu' hasn't been found!
Hi,
We are have problem with SMD agent.
We are executing Setup wizard ( for managed system ) but getting following message
The SMD Agent 'slcxemw04vu' hasn't been found!
Thing is SMD agent is running on host slcxemw04vu but somehow it is not able to detect.
System Install Path: /usr/sap/<Agent SID> :Is this correct Path?
Instance Path:/usr/sap/<Agent SID>/<AgentSID97>Is this correct Path?
Please let me know if you have any information for message'
The SMD Agent 'slcxemw04vu' hasn't been found!
Best Regards,
Tushar
Edited by: TusharC Chavan on Oct 21, 2009 5:44 PMHi Rahu,
Now Remark are "
Setup data must be entered for with servers : server0 (running EM Core, Application Server Java) (ITS port number must be provided)"
Now AS Java system will not have ITS . So entered solution manager ITS info.Then I got
"with servers : server0 (running EM Core, Application Server Java)
No setup or configuration steps performed yet"
By the way I can't find Diagnostics Administration --> Diagnostics System --> Self Check. Select your Solution and start a Self Check.Can you please explain it in detail.
Best Regards,
Tushar -
Standalone SMD Agent for EEM won't connect to SLD
I have installed a standalone SMD agent, which was configured properly (logs verify this) and starts up successfully, but I don't ever see it register in the SLD. Does anyone know of a guide which tells how to manage a standalone SMD agent? I want to get it connected to the SLD in Solution Manager so that I can use it as an EEM robot, but the connectivity so far is not working.
For instance, if there is a way to get something like SM59 in an ABAP system on my SMD agent to change and test connectivity parameters, this may help.
Cheers,
David.OK, thanks for the reference to the troubleshooting guide, I had not seen that before. Using it, I found the following procedure:
How to check if the Diagnostics agent is registered in SLD?
␣ Go in SLD with the url: http://sldhostname:port/sld
␣ Logon with a J2EE user having the role SAP_SLD_ADMINISTRATOR
␣ Go in the section u2018Administrationu2019
␣ Click on link u2018Content Maintenanceu2019
␣ Select the subset u2018All with Instances and class u2018Diagnostics Agent Instanceu2019
If the class u2018Diagnostics Agent Instanceu2019 does not appear in drop down list, No Diagnostics agent is registered
␣ In column Name of table, check if the Diagnostics agent is present.
This procedure verified that my diagnostics agent is in fact in contact with the SLD, but for some reason, the agent does not show up in the SLD when I go to Home > Technical Systems, nor does it show up when I go to the EEM Administration screen > Robots > Check Agents.
So I'll have to keep researching.
Cheers,
David. -
SMD Agents on ABAP only stacks
Hi
Is is possible to install the SMD Agent on ABAP only satellite systems.
Or does it require a J2EE instance.
What would that gain?
Thanks for your HelpHi,
Yes you can and you must do it for E2E Root Cause Analysis. It does not need J2EE but as it is Java based you need to install JDK.
Regards,
Stephan
Maybe you are looking for
-
HT1338 adding text to iPhoto pictures
I would like to ad captions or text to my iPhotos, can this be done? If so, how?
-
SAP Kernel release - Difference between SM51 and System- Status ?
Dear SDN colleagues, I am a ABAP developer, and have been told by our Basis department that our SAP Kernel is 640. When I check the following, I get different values: 1) System -> Status : SAP_BASIS is 620 2) Transaction SM51 -> Release Notes: I see
-
Hi peoples, This is probably a stupid question, but what is the icon in the bottom left hand corner of Finder? It's only there in certain windows, like Documents and Pictures. It looks like four diamonds/parallelograms in a grid. Here's a screenshot-
-
Photoshop CS4 quits responding when using 3D
Photoshop CS4 quits responding when selecting new texture in materials section under opacity in 3D. I have not had this happen till just a few weeks ago. It was working just fine. I run an IMac with 2 gig of ram. My graphics card is a ATI,RadeonX1600
-
Need a little help with this factory pattern thing..
Evening all, I have an assignment to do over easter, before i start i will say i dont want any code or anything so this isnt 'cheating' or whatever.. This was the brief: A vending machine dispenses tea and coffee, to which may be added milk, and 0, 1