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.
Similar Messages
-
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,
ArindamHi 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 -
SMD agent for VMW-based SAP systems
SAP talents:
We have hard time to configure SMD agents for VMW-based SAP systems.
We have followed some SAP documents for non-VMW-based SAP systems, but seems that SMD agent cannot
differentiate the individual system on VMW.
Our SMD agent has no problem for non-VMW-based systems.
Thanks!Sorry to reply late because we have attempted a lot of fixes but all failed
For example, we have QAX, QAY and QAZ on VMW.
On Wily Introscope:
1) QAZ simply does not show up even we deployed/configured the agents as the procedure specified;
2) under the node QAX, we see QAY's entry as a sub-entry.
Does each SAP system need an agent OR only one agent is enough? We have tried both ways but
seems not working properly either way.
Please help, thanks a lot! -
MS Word for iPad won't connect to OneDrive
I just downloaded MS Word for iPad (and I have a subscription to MS Office 365). The install went fine, but when I log in, it doesn't access my OneDrive folders. It shows two generic folders (Documents and Public), but if I click on Documents, for example, it grinds for a while and then returns with the message "Cannot Connect to Server." My internet connection is fine, and if I simply go to OneDrive, it works fine too. It's just the new Word for iPad app that won't connect to OneDrive.
Any ideas?Not a direct answer but you might try posting to the MSFT OneDrive forum for possible help...
http://answers.microsoft.com/en-us/windows/forum/windows8_1?tab=Threads&status=& mod=&modAge=&advFil=&postedAfter=&postedBefore=&threadType=All&tm=1382788071583
Good luck... -
SMD Agent for ABAP Only Systems
Everything I have read states that the SMD Agent is only for JAVA Stack. Then I read a post here stating to install the SMD on the ABAP systems. Can anyone clear this up? I have a mix of Java only, Abap only and dual stack systems. Can anyone help clear this issue up for me?
Hello Donna,
SMD Agent can be installed on Java Stack, Java-ABAP Stack and ABAP Stack. It is not there only for Java as it can be used with ABAP and Dual stack also. Hope this answers the question that you have brought up.
Thanks,
Mark -
SMD agents for Solaris X86_64
According to PAM Solaris X86_64 is released generally for WebAS 7.00 ABAP + Java (NW2004s SR1 to be exact).
However, there are no SMD agents available for that platform. Any idea why those will be published?
Regards,
MarkusHi Dolores,
thanx - did that - and they told, that they "do not exist" (that's what I know already).
I'll update the thread as soon as I get some information.
Markus -
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 -
X-box receiver for Windows won't connect to controller
Hello,
I have recently restored my computer, and before that point my wireless xbox controller connected to the PC fine via the Official Microsoft receiver. After the restore, I reinstalled the drivers for the receiver and when plugged in the light on the receiver
didn't light up. I did some research prior to posting this to see if I could find a solution, and I got it to light up by doing the following:
1.Right click on Computer
2.Go to Properties
3.Click on Device Manager
4.Right click on the Unidentified Device
5.Go to Properties
6.Go to the Drive tab
7.Click on "Update Driver"
8.Browse my computer for driver software
9.Let me pick from a list of device drivers on my computer
10.Microsoft Common Controller for Window Class
11."Xbox 360 Wireless Receiver for Windows"
12.Update Driver Warning
13.Click Yes
I heard by doing the above, it cured the problem for others, but it didn't work for me. Now, when I try to hook up my controller, I hold the large X in the middle of the controller, and all four quarters blink. I hold down the sync button on the receiver,
then the controller, and the receiver blinks, and the controller does its swirling connecting thing. The receiver then stops flashing and goes back to being static, and the controller resumes the four quarters blinking. Normally, the top left quarter should
stay lit and the connection would be successful, but it isn't doing that for some reason. Anyone know how to get them to complete the process of syncing?
Thanks,
- Nathanbump.
-
SMD Agent application - Explanation
Hello,
I have installed SMD. By startind "Agent Administration" from SMD, I get the application list of SMD Agent.
I am editing a guide to explain each application of this SAP SMD Agent. I get an explanation for 10 of 22 applications.
But I miss details regarding the other ones :
Do you have any help or guide which explain me what these SMD applications are used for ?
1. com.sap.smd.agent.application.e2emai
2. com.sap.smd.agent.application.eem
3. com.sap.smd.agent.application.flightrecorderdumpscan
4. com.sap.smd.agent.application.navigation.links
5. com.sap.smd.agent.application.remoteos
6. com.sap.smd.agent.application.runtime
7. com.sap.smd.agent.application.tracing
8. com.sap.smd.agent.application.wily
9. com.sap.smd.agent.application.wily4duet
10. com.sap.smd.agent.application.wily4java
11. com.sap.smd.agent.application.wilyem
12. com.sap.smd.agent.application.wsclient
Thanks
Best regards
PCHello,
I have finally foudn an explanation for each SMD Agent application :
1 .com.sap.smd.agent.application.connectors
Provide P4 or JMX connection to the monitored SAP J2EE engine.
2. com.sap.smd.agent.application.database
Access to the DB of the remote system to return table information to the SMD SQL Command Console application.
3. com.sap.smd.agent.application.datacollector
Collects XML based data from monitored systems (replaces the tool u201CComponent Analyzeru201D download feature)
4. com.sap.smd.agent.application.filesystem
Provides access to the remote file system for the u201CSMD File System Browser applicationu201D, and the Gather/Upload functionality.
5. com.sap.smd.agent.application.global.configuration
Global configuration of the SMD Agents.
6. com.sap.smd.agent.application.ldap
Provides remote access to connect to a LDAP server for the SMD LDAP browser application.
7. com.sap.smd.agent.application.logviewer
Provides an access to the file system of a monitored system. Files can be displayed or downloaded.
8. com.sap.smd.agent.application.remoteos
Enables to start remote OS commands console.
9. com.sap.smd.agent.application.remotesetup
Enables to setup the J2EE engine of a monitored system for SMD usage, from the smd/admin application.
10. com.sap.smd.agent.application.telnet
Provides remote access to the J2EE telnet console for the SMD J2EE command console application.
11. com.sap.smd.agent.application.tracing
It is used by the application E2E Trace Analysis (tools of RCA).
12. com.sap.smd.agent.application.wily
It is used by the application Introscope Setup.
13. com.sap.smd.agent.application.wily4duet
It is used by the application Introscope Setup for managed system running on duet.
14. com.sap.smd.agent.application.wily4java
It is used by the application Introscope Setup for managed system running on java.
15. com.sap.smd.agent.application.wilyem
It is used to store the data about Introscope Enterprise Manager (EM) for SMD.
16. com.sap.smd.agent.application.wilyhost
A: The agent application "com.sap.smd.agent.application.wilyhost" contains the HostAgent.
HostAgent = Host-Level Introscope Agent.
The following SMD Agent applications are not for a specific application but for the
general runtime of Root Cause Analysis :
- com.sap.smd.agent.application.e2emai
- com.sap.smd.agent.application.eem
- com.sap.smd.agent.application.wsclient
- com.sap.smd.agent.application.flightrecorderdumpscan
- com.sap.smd.agent.application.runtime
- com.sap.smd.agent.application.navigation.links
Best regards
PCuennet -
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
RidhwanThe 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. -
Hi
Our Solution Manager is on SP14 and Managed System is on SP15. I want to install the SMD Agent. As per the note 1126895 it is possible and suported. LMSERVICE is SP14.
I used note 1170855 to install it and it was successfull but the status is "in Progress" in http:////<hostname>:<port>/smd page. It says "DEPLOYING APPLICATION". It never finishes.
I checked the log file jvm_SMDAgent.out and it says that
Starting SMDAgent ...
Running SMD Agent ...
Establishing connection to server 'ms://<hostname>:8177/P4
[ms://<hostname>:8177/P4] Waiting for connection ...
[ms://<hostname>:8177/P4] Checking server availability...
[ms://<hostname>:8177/P4] Authentication in progress ...
[ms://<hostname>:8177/P4] Connection established .
[ms://<hostname>:8177/P4] Registering agent on server ...
Exception occured. Please check log files.[Exception ID:1219178405804 ]
[ms://<hostname>:8177/P4] Waiting for connection ...
[ms://<hostname>:8177/P4] Checking server availability...
[ms://<hostname>:8177/P4] Authentication in progress ...
[ms://<hostname>:8177/P4] Connection established .
[ms://<hostname>:8177/P4] Registering agent on server ...
It never finishes.
It is failing at deployment application.
The log file SMDSystem.0.log states following -
Aug 19, 2008 4:30:04 PM [Thread[Thread-2,5,main]] Info
[AgentContext.offlineDeployApplication] ENTERING - deploying file
com.sap.smd.agent.application.runtime_7.0014.20080429115048.0000.war
Aug 19, 2008 4:40:05 PM [Thread[SMDAgent connection thread,5,main]]
Error [Exception ID: 1219178405804 ] java.rmi.RemoteException -
error counter: 1
[EXCEPTION]
java.rmi.RemoteException: Agent Registration failed: Time out occurred
when calling method 'offlineDeployApplication' on object
[com.sap.smd.api.IAgentContext_Stub@1de64fc2] after 600000 ms.
possible cause: com.sap.smd.server.util.concurrent.TimeoutException
at com.sap.smd.SMDServerHandle.internalRegisterAgent
Anybody has experienced it.
Please let me know.
Regards.
SSHello,
Would you kindly share the solution?
Think I run into a similar issue.
Many Thanks,
Jan -
Urgent!! Setup of SMD Agent failed due to Remote Error....
I am getting the following error when i tried to Setup the Smd agent using setup wizard:
<b>The assignment of server frces4153 to SMD Agent failed
Remote error occurs during the connection to the smd agent for agent frces4153</b>
Can you please give me the solution for this...
<b>Reward points of all the replies....</b>
Ajay KandeThnx for ur suggestions, Now i colud see the following error "[Setup]Failed to assign SMD Agent to frces4146/EP7 (frces4146)
[EXCEPTION]
Time out occurred when calling method 'getService' on object [com.sap.smd.api.IAgentContext_Stub@7fc07fc] after 10000 ms.... [siehe Details]
from the logs....
Ajay Kande -
Hi everybody,
anyone seen this before?
I have installed a new SMD Agent for a newly installed system.
I chose the message server connection to my SolMan System (connection is available, I check on OS level).
When starting the Agent I get:
[EXCEPTION]
Time out occurred when calling method 'configure' on object [com.sap.smd.api.IAgentContext_Stub@36423801] after 10000 ms.
possible cause: com.sap.smd.server.util.concurrent.TimeoutException
at com.sap.smd.server.exec.asio.AsioInvocationHandler.invoke(AsioInvocationHandler.java:130)
at $Proxy23.configure(Unknown Source)
at com.sap.smd.local.AgentContextWrapper.configure(AgentContextWrapper.java:188)
at com.sap.smd.SMDServerHandle.registerDeprecatedConfiguration(SMDServerHandle.java:424)
at com.sap.smd.SMDServerHandle.internalRegisterAgent(SMDServerHandle.java:222)
at com.sap.smd.SMDServerHandle.registerAgent(SMDServerHandle.java:147)
at com.sap.smd.SMDServerHandlep4_Skel.dispatch(SMDServerHandlep4_Skel.java:196)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Any ideas?
Thanks in advance and best regards,
JochenHi David,
thanks for all your suggestions. Obviously it was only a load problem on the SolMan system. This monday the agent was suddenly connected....
Best regards,
Jochen
Edited by: Jochen Spieth on Jan 20, 2011 8:52 AM -
Not able to find SMD Agent in SMP
Hi,
I need to install SMD agent in all the NW2004s servers, but i am not able to find the SMD agent for NW2004s in Service Market Place.
SMD agent is not available in the below mentioned path:
service.sap.com/swdc --> Download --> Support Packages and
Patches --> Entry by Application Group -> SAP Technology Components --> SAP
SOLUTION MANAGER --> SOLUTION MANAGER 4.0 --> Entry by Component -->
Agents for Satellite Systems --> SMD AGENT 7.00 --> <choose OS>
Regards,
RanjithHi Shyam,
Thanks for your reply.
I already tried downloading the SMD Agent from the OS independent, but after extracting the SAR file, i am unable to see the sapinst in it.
I have all the monitored systems of version NW2004s SR1/SR2, in this version of installation master, will i be able to install the SMD agent?
Regards,
Ranjith -
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)]
Maybe you are looking for
-
How do i move my itunes library to a different drive
i underestimated the space i needed for my itunes library. at the time, i thought 75gb is more than enought for my 60gb ipod, then the videos and movies came along. although i cannot put them on my 4th gen ipod, but i did downloaded a bunch of free t
-
How do I add DxO 9 as a lightroom external editor?
I posted this in the beginners section but was recommended to move it to more advanced viewers. I have lightroom 5.3 I want to use DxO 9 from within Lightroom as an external editor, to both convert raw to tiff and make use of the lens corrections.
-
Is there a way to turn off Faces, or otherwise disable the facial recognition function in iPhoto?
-
I am going to replace my internal HD with a 120 GB HD. After I install it I want to transfer stuff from the old HD to the new HD. Is there any cable that will connect the old HD, (now outside the computer) to a USB or Firewire port? Mark
-
Updating more than one table in the same region
Hi all, I have a header and detail relationship created between to entities. I created an association between them. I have 2 views and a view link based on the 2 entities. I have built an update page and I'm able to display the detail and header fiel