Different SMD Agents on a single HANA appliance

Hello,
we've four different HANA instances on our HANA maschine. We have installed a SMDAgents for every instance.
The agents are created with different SID's. The SID's have different instance numbers as well.
Now we are not able to connect all the Agents to the solman. It's only possibel to connect a single agent.
If we stop the agent we are able to connect an other installed agent on an other
HANA instance.
How is it possible to connect all the agents?
Best regards
Roger

1) Create another bin (e.g. test_bin) directory in the oracledi directory. Copy all of the agent related bat files across to the new bin directory i.e. odiparams.bat, agent.bat etc. Make sure your new odiparams.bat file is configured to point at the correct work repository.
2) Yes, multiple agents can be managed via OPMN
3) They will be using the same resources available on the single server but as long as you configure them appropriately it shouldn't lead to unnecessary conflict / performance issues. i.e. don't go changing the java heap size for the agent to some unrealistic threshold if the server resources cannot support it.

Similar Messages

How to add two different page numbers in a single page

How to add two different page numbers in a single page? One is for page number of the whole article, the other one is for page number for each chapter in the article.

It's quite complicated, see
Two Page Numbering Schemes in the Same Document.
Regards, Hans Vogelaar (http://www.eileenslounge.com)

SMD agent communication channel

Hi All,
I am configuring SMD for our landscape.
I have successfully installed Wily Introscope Enterprise Manager 7.2 on our solution manager system.
from what i understand i need to install SMD agent in satellite system to connect to SMD server in Solman system. fyi, my satellite system reside in different segment of solman system. Whats port do i have to use to connect the SMD agent(satellite) & SMD server(Solman system)? Thanks
Ridhwan

The following ports have to be opened up in your firewall prior to End-to-End Diagnostics
installation. It is recommended to place the SAP Solution Manager within the same subnet or
DMZ of your managed landscape. In case you are managing systems in different subnets you
have to adapt your security settings and firewall accordingly.
Connection established u201CServiceu201D on dest. host / Protocol Service port example /from host(s) Format Src. Host to host
Dest. Host
Outside Diagnostics
Server
J2EE engine / HTTP
Ex: 50100 /
5<InstanceNb>00
DMZ Diagnostics Server
ITS / HTTP Default: 8000
Outside Diagnostics Server
Introscope Manager/ HTTP
Default: 8081
Diagnostics Server
IGS / HTTP Ex: 41080 /
4<InstanceNb>80
ALL Managed systems
(Diag. Agent)
Diagnostics Server
J2EE engine / P4 Ex: 50104 / 5<InstanceNb>04
ALL Managed
Diagnostics Server
Message srv. / HTTP
Ex: 8101 / 81<InstanceNb>
Hope this helps,
Thanks
Aditya.

ASCS on SAP HANA Appliance

Hi All,
I am planning to install the ASCS of SAP BW 7.4 in the same Sap HANA Database Appliance .
I read some notes, including the central note and found nothing related to the Central Services on the appliance.
This scenario is supported by SAP?
Regards,
Fabio Nassar

Issue resolved,
This scenario is not supported, ASCS cannot be installed on HANA Appliance!
Even if you try installing ASCS on HANA host with SWPM sapinst,it will give an error message after
providing the DB host details.
" The SAP HANA database must installed on a remote host.Please enter a
different host name".

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)]

SMD Agent 7.00 or Diagnostics Agent 7.11

Hello,
Our managed systems are running on NetWeaver 7.00.
We are currently implementing SAP Solution Manager Diagnostics using SOLMAN_SETUP guided procedure.
In https://service.sap.com/swdc -
Support Packages and Patches - Entry by Application Group" SAP Technology Components" SAP SOLUTION MANAGER" SAP SOLUTION MANAGER 7.0 EHP 1" Entry by Component" Agents for managed
there are 2 kinds of Diagnostcis Agents :
1. SMD Agent 7.00
2. Diagnostics Agent 7.11
Question :
Can we install a Diagnostic Agent 7.11 on our managed systems running on NetWeaver 7.00 or must we install SMD Agent 7.00 ?
Are Diagnostics Agent 7.11 supported for managed systems running on NW 7.00 ?
Best regards
PC

Hi
To avoid libraries conflicts it is highly recommended to install a Diagnostics agent which has the same kernel release
that the SAP systems already installed on the host.
Refer the doc in this [link|https://websmp205.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_HIER_KEY=701100035871000526434&_OBJECT=002007974700000409092009E&_SCENARIO=01100035870000000112&] Section 2.3 Managed system page no:8
Hope this helps you
regards
Naveen

Diagnostics Agent 7.11 vs SMD Agent 7.00

Hello,
In our SAP System environment, most of managed systems are running under SAP NW 7.0 platform.
We are currently installing SMD Agent 7.00. The installation is not finished and I was wondering if we can install Diagnostics Agent 7.11 on managed systems running on SAP NW 7.0 ?
In other terms :
SMD Agent 7.00 have to be installed only on SAP NW 7.00
Diagnostics Agents 7.11 have to be installed only on SAP NW 7.11 or also on SAP NW 7.00 ?
Thanks in advance for your feedback
Best regards
P. Cuennet

Yes you can install diagnostics agent 7.11 for a managed system 7.00
It's even possible for a managed system 6.40
Prerequisite is that your Solution Manager stack verison is 20 or higher (EHP1)
You can find the details in the installation guide for diagnostics agent 7.11 on SAP service marketplace:
[https://service.sap.com/diagnostics]

Start of SMD agent fails!

Hi!
After the installation of SMD AGENT 7.00 SP09 we've got some problems starting the agent.
The errorlog says: (/usr/sap/SMD/J98/SMDAgent/log/SMDSystem.0.log)
Oct 11, 2006 2:11:26 PM [Thread[SMDAgent connection thread,5,main]] Error Exception ID: 1160572286256
Registering agent on server myhost.de:50004failed:
com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.Nested exception is:
java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException
However, the manual setup of the agent succeeds:
./smdsetup.sh /usr/java14_64 myhost.de 50004 j2ee_admin PASSWORD
SAP Solution Manager Diagnostic - SMD Agent Setup - Copyright (c) 2005 SAP AG
SMD Agent Setup is in process ...
- STEP 1: checking JDK location
JDK location is consistent: /usr/java14_64/bin
- STEP 2: checking JDK Version
JDK Version is correct: 1.4.2
- STEP 3: checking Connection to SMD Server
SMD Server check completed successfully
- STEP 4: generating Runtime Properties
runtime.properties has been created.
- STEP 5: generating Launcher
smdagent.bat has been created.
smdagent.sh has been created.
- STEP 6: generating SecStore
secstore.properties: has been created.
secstore.properties: user has been set.
secstore.properties generation completed successfully.
- STEP 7: checking P4 Connection and SMD Agent Registration
SMD Agent Registration succeeded
SMD Agent Setup completed successfully
During the start process of the agent, the agent appears in the agent administration tab in SMD/admin, but it disappears after the erroneous shutdown.
What can we do?
Thanks for all hints solving our problem!
Greetz,
André Richter

Hi Rahul,
please try SMD Agent 7.00 SP10! We had no problems with this version!
Also make sure that the OSUser has enough privileges. We use the "sidadm" to start the agent.
Regards
André

Install SMD agent on EP6 fails

Hi,
I get an error when installing SDM agent on EP6 (HP-UX):
STEP 7: checking P4 Connection and SMD Agent Registration
External Command Executed:
/opt/java1.4/bin/java -DP4ClassLoad=P4Connection -Dsap.p4.remote_classloading=false -cp ":/usr/sap/SMD/J97/SMDAgent/lib/sapxmltoolkit.jar:/usr/sap/SMD/J97/SMDAgent/lib/smdagent.jar:/usr/sap/SMD/J97/SMDAgent/lib/tc_sec_secstorefs.jar:/usr/sap/SMD/J97/SMDAgent/lib/iaik_jce_export.jar:/usr/sap/SMD/J97/SMDAgent/lib/launcher/logging.jar:/usr/sap/SMD/J97/SMDAgent/lib/smdserver.jar:/usr/sap/SMD/J97/SMDAgent/lib/exception.jar:/usr/sap/SMD/J97/SMDAgent/lib/sapj2eeclient.jar:/usr/sap/SMD/J97/SMDAgent/lib/launcher/smdagentlauncher.jar:" com.sap.smd.setup.Setup /p4connection
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
P4 Connection succeeded but SMD Agent Registration failed
Root exception is: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of smdserver.
I couldn't find anything on SAP Market Place but a similar thread here advised to check if SDM servers is not in maintenance mode.
Well, it's not.
Can someone please help?
Thx
Bert

Hi,
Did you connect to smd server http://host:port/smd and desactivate maintenance mode in Agent Administration page?
This should solve your issue.
Regards,
Frederic

Configuration check error: The SMD Agent is not able to connect the Satellite System (J2EE stack)

Hi friends,
Getting the below error in step 10 (configuration check) in managed system configuration.
The SMD Agent is not able to connect the Satellite System (J2EE stack).
Please check the JAVA Connect Parameters provided in the Managed System Setup Wizard for this
System.
java.rmi.RemoteException.P4 Connection failed -
P4AuthorizationException -
com.sap.smdagent.plugins.connectors.p4.exceptions.P4AuthorizationException:
Access is denied to SAP System sid [XYZ/null]: check the connection
credentials.More details about the error in agent 'xyz' log file
(SMDAgentApplication.X.log).; nested exception is:
com.sap.engine.services.security.exceptions.BaseLoginException: Cannot
authenticate the user.
The SMD log file referred to in the log above gives the same information and not anything much useful.
Any idea what could be the reason for the above error?
Thanks,
Arindam

Hi All,
Thaks for your suggestions. I chcked the note 182020, but the issue described in the note is for error byte code adapter installation whcih is not my case. The byte cde adapter intallation has been successful in our solman system All the steps from 1 to 9 are green. Only in step 10, check cniguration I am getting the above error.
The logon test wth the user id in step 3 "Enter system parameters" is successful. The message server port is also correct.
Hi Khaja,
I went to the links as suggestedby you but there its about a ifferent error message "Invalid Response Code: (401) Unauthorized.". I am not getting any such kind of error.
All I am getting is this -
The SMD Agent is not able to connect the Satellite System (J2EE stack).
Please check the JAVA Connect Parameters provided in the Managed System Setup Wizard for this System.
java.rmi.RemoteException.P4 Connection failed -
P4AuthorizationException -
com.sap.smdagent.plugins.connectors.p4.exceptions.P4AuthorizationException:
Access is denied to SAP System sid [XYZ/null]: check the connection
credentials.More details about the error in agent 'xyz' log file
(SMDAgentApplication.X.log).; nested exception is:
com.sap.engine.services.security.exceptions.BaseLoginException: Cannot
authenticate the user.
Thanks,
Arindam

Ability to display data in Different Page Sizes in a Single RTF

We have a requirement to show different page sizes in a Single RTF file .
Please let me know you have worked on such a functionality as part of earlier assignments.
Requirement Detail:
We have 2 templates (One Legal (8.5*14) and One Statement ( 5.5*8.5)) as part of the same report in 2 different pages.
Conditionally we need to show xml data in either the Statement or the Legal Format .
Issues Currently faced:
1.     When the Statement is chosen as a user parameter: (Attachment : ReportoutputforStatement.pdf)
-     The data is super-imposed on the Legal layout instead of showing it on the Statement layout . Hence the page dimensions are not as expected in the report.
-     There is a extra last page in the report which is blank with the Statement Layout.
2.     When the Legal option is chosen as a user parameter: (Attachment : ReportoutputforLegal.pdf)
-     The Data is appropriately shown on the legal layout
-     There is a extra last page in the report which is blank with the Statement Layout.
Regards:
Nagaraj.s

Have you tried creating two subtemplates and conditionally calling them based on the parameter chosen?
If I understand correctly,currently you have a single RTF template (2 pages) that includes the two different layouts..
Thanks,
Bipuser

SMD Agent doesn't work

Hello,
I have been trying to install SMD Agent in my BI system but Solution Manager can't check it, this is the message in Solman_setup
Wilyhost Agent configuration finished without errors, but on Enterprise Manager (sapl917.intra.banesco.com:6001) no Wilyhost Agent was detected from host svs978. Please check the log file jvm_smdagent.out whether the Wilyhost Agent could connect to the Enterprise Manager. If the Enterprise Manager configuration has been changed recently please restart the SMD Agent on OS level.
Step Wilyhost Agent Details
Created destination QBB|svs978_QBB_01
Created action QBB - QBB AbapSystem
Created action QBB|svs978_QBB_01 - QBB|svs978_QBB_01 AbapInstance
Created 2 action(s).
0 Wilyhost Agent(s) from host svs978 are connected to the EM.
Wilyhost Agent configuration finished without errors, but on Enterprise Manager (sapl917.intra.banesco.com:6001) no Wilyhost Agent was detected from host svs978. Please check the log file jvm_smdagent.out whether the Wilyhost Agent could connect to the Enterprise Manager. If the Enterprise Manager configuration has been changed recently please restart the SMD Agent on OS level.
do you know something??? i restarted the agent but nothing happens
Thanks!!!!

Hello...
For JAVA
Software Components
Vendor Name Version Provider Location Applied
sap.com ADSSAP 7.01 SP4 (1000.7.01.4.0.20090417021200) SAP AG SAP AG 20091103161136
sap.com BASETABLES 7.01 SP4 (1000.7.01.4.0.20090417015900) SAP AG SAP AG 20091103153957
sap.com BI_MMR 7.01 SP4 (1000.7.01.4.0.20090417021807) SAP AG SAP AG 20091103161215
sap.com BI_UDI 7.01 SP4 (1000.7.01.4.0.20090416221700) SAP AG SAP AG 20091103162333
sap.com CAF 7.01 SP4 (1000.7.01.4.0.20090417194106) SAP AG MAIN_NW701P04_C 20091103163937
sap.com CAF-UM 7.01 SP4 (1000.7.01.4.0.20090417194111) SAP AG MAIN_NW701P04_C 20091103161325
sap.com CORE-TOOLS 7.01 SP4 (1000.7.01.4.0.20090417021948) SAP AG SAP AG 20091103154019
sap.com ISAGENT 8.1 SP0 (8.1.0.0.20090605095817) SAP AG SAP AG 20091210142716
sap.com JLOGVIEW 7.01 SP4 (1000.7.01.4.0.20090417020000) SAP AG SAP AG 20091103154104
sap.com JSPM 7.01 SP4 (1000.7.01.4.2.20090918151100) SAP AG SAP AG 20091201201543
sap.com KM-KW_JIKS 7.01 SP4 (1000.7.01.4.0.20090514115300) SAP AG SAP AG 20091103161349
sap.com LM-SERVICE 7.01 SP5 (1000.7.01.5.2.20091211060559) SAP AG SAP AG 20091224192630
sap.com LM-TOOLS 7.01 SP5 (1000.7.01.5.3.20091208123420) SAP AG MAIN_NW701P05_C 20091228135344
sap.com SAP-JEE 7.01 SP4 (1000.7.01.4.1.20090612152648) SAP AG SAP AG 20091103154150
sap.com SAP-JEECOR 7.01 SP4 (1000.7.01.4.0.20090417015900) SAP AG SAP AG 20091103154414
sap.com SAP_JTECHF 7.01 SP4 (1000.7.01.4.2.20090612144700) SAP AG SAP AG 20091103154520
sap.com SAP_JTECHS 7.01 SP4 (1000.7.01.4.2.20090612152905) SAP AG SAP AG 20091103162132
sap.com SWLIFECYCL 7.01 SP4 (1000.7.01.4.0.20090511115334) SAP AG MAIN_NW701P04_C 20091103151458
sap.com UMEADMIN 7.01 SP4 (1000.7.01.4.0.20090417195012) SAP AG MAIN_NW701P04_C 20091103165828
For ABAP
SAP_BASIS     701     0004     SAPKB70104
SAP_ABA     701     0004     SAPKA70104
ST-PI     2008_1_700     0001     SAPKITLRD1
PI_BASIS     701     0004     SAPK-70104INPIBASIS
CRMUIF     500     0003     SAPK-50003INCRMUIF
SAP_BW     701     0004     SAPKW70104
SAP_AP     700     0016     SAPKNA7016
BBPCRM     500     0015     SAPKU50015
CPRXRPM     400     0015     SAPK-40015INCPRXRPM
ST     400     0021     SAPKITL431
BI_CONT     704     0004     SAPK-70404INBICONT
ST-A/PI     01L_CRM570     0000          -
ST-ICO     150_700     0022     SAPK-1507MINSTPL
ST-SER     701_2008_2     0005     SAPKITLOQ5
LM Components were updated for EHP1 SPS21, I installed SMD Agents in DEV and some QA servers and they work, but this one specially works as a fail over for a PRD cluster enviroment, and for that reason I'm using logical name, in SMSY it is configure with the same name, do you have any ideas?
Thanks!!!

Use cases for the SAP HANA Appliance for SAP FI-Accts.Payable

Hello SAP HANA friends:
Are there any compelling use cases for the SAP HANA Appliance for SAP FI-AP Accounts Payable module?
CO-PA and CRM have many immediate use cases, but I'm looking for the use case for Accounts Payable,
either from a cash flow perspective or performance.
Any and all comments are appreciated.
Regards,
Joe Gonzales
856 912 1136

Hi,
In SQL console please execute below query .
GRANT SELECT ON SCHEMA <schema Name> TO "_SYS_REPO";
BR
Sumeet

SMD agent passowrd issue

Hi Experts,
In our solution manger system, we forgot the SMD agent password. without i can't able to do EWA for java stack. So kindly help me to how to reset the password for this.
Thanks & Regards,
Sampath.

Hi
when you performed the SMD Setup Wizard in the managing system, created the SMD_ADMIN user and the enter the passowrd
please reset the password for the smd_admin user in the managing system (satelite system and try)
else use the section 4.9.2 in the diagnostics setup guide 7.11 on [https://websmp108.sap-ag.de/diagnostics|https://websmp108.sap-ag.de/diagnostics] > media library as below
4.9.2 Change the Diagnostics Agent credentials
This section provides information about how to change the credentials (login and/or password) of the J2EE user used to connect the Diagnostics Agent to the Managing System.
Prerequisites
All the Diagnostics Agents must be connected to the Managing System before updating the password of the J2EE user used by these Diagnostics Agents
Procedure
1. You can either change the password of the J2EE user used by the agents or create a new J2EE user in User Management.
2. Open the Agent Administration application
In the Agent Credentials panel, fill the previous login of the Diagnostics Agents and enter the new one (or enter the same login with a new password). Click on the Update all agents button.
3. All the agents are disconnected and reconnected with the new credentials
jansi

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

Different SMD Agents on a single HANA appliance

Similar Messages

Maybe you are looking for