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 Help

Hi,
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

Similar Messages

Why SMD agent on ABAP only?

OK. I don't get it. Why install SMD Agent on ABAP only systems???
Isn't SMD Agent used primarily for Java???
I have 37 systems of which only 8 have a java component. If I install SMD Agent everywhere I'll
need a much bigger SolMan server!!!
What is SAP policy on SolMan 7 Enh 1 OS/DB migration???
Can I migrate from this little Intel Linux box to a serious AIX LPAR?
Will SAP give me a migration key???
Ken Chamberlain
University of Toronto

About the migration, you can migrate without problems. You'll need study the following process "Heterogeneous system copy".
There's a component that checks just this kind of problems related with migration. BC-INS-MIG.
Check the documentation below.
http://www.sapdb.info/homogeneous-and-heterogeneous-system-copy/
http://www.fulleffectsolutions.co.uk/Html/technical-sap-hetero.html

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

Introscope Host Agent for ABAP only instance, fails with java.lang.NullPoin

Hello,
I'm trying to configure the Introscope Host Agent Adapter for ABAP 7.02 instance.
Solman Version is 7.1 ST 4, BASIS SP9.
I did created the Trust relationship between DAA and hostctrl and
also the same setup working find for Java Instance or ABAP+java Instance,
I'm not sure whether IS Adapter can be installed for ABAP only Instance.
Log file from Solman:
java.lang.NullPointerException
at com.sap.smd.server.manager.SMDPluginProperties.setProperty(SMDPluginProperties.java:119)
at com.sap.sup.admin.wily.hostagent.config.AgentConfigWriter.setJCoUserAndPwd(AgentConfigWriter.java:1085)
at com.sap.sup.admin.wily.hostagent.config.AgentConfigWriter.setLogonData(AgentConfigWriter.java:1075)
at com.sap.sup.admin.wily.hostagent.config.AgentConfigWriter.createJcoDestinationVO(AgentConfigWriter.java:677)
at com.sap.sup.admin.wily.hostagent.config.AgentConfigWriter.prepareSapAgentConfiguration(AgentConfigWriter.java:284)
at com.sap.sup.admin.wily.hostagent.Setup.setupAgentConfiguration(Setup.java:272)
Thanks
Srikanth M

Hi
I am sure, it is logically incorrect, how you deploy byte code agent in abap only instance
Introscope Bytecode Agent runs on managed systems based on J2EE engines to report data to the Introscope Enterprise Manager, so it has to be setup only for Java Stacks.
Please check with the wily config guide again.
I am watching this thread for further view from others.
Thanks,
Jansi

Error while installing SMD agent

Hi ,
1) Can any one please justify/brief the need of installing SMD agent on ABAP stack?
2) When I tried to install the SMD 711 agent on ABAP stack I could see the below error when i click sapinst.exe.
    " Running msiexec failed with return code 1063: undefined
      command line was :
       msiexec.exe /norestart /L vcredist_x64.log /i vcredist_x64.msi /qn "
I tried with Changing the environment variable of Temp and tmp to C:\usr\sap\<sid>\tmp and also tried with directory c:\temp but in vain .
enivronment:-   Windows 64-bit.
Note:- SMD agent was successfully installed on Development systemn
Please suggest.
Thank you
Jayanth

Hi ,
Log from vcredist_x64.log. Please have a look
" Product: Microsoft redistributable runtime DLLs VS2005 SP1(x86_x64) -- Error 1719. The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.
Error 1719. The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.
Action ended 2:47:00: SxsInstallCA. Return value 3.
Action ended 2:47:00: INSTALL. Return value 3.
MSI (s) (FC:38) [02:47:00:489]: Windows Installer installed the product. Product Name: Microsoft redistributable runtime DLLs VS2005 SP1(x86_x64). Product Version: 8.0.50727.762. Product Language: 1033. Installation success or error status: 1603.
Does this mean that , I should download new sapinst file for service market place and try again ??
Thank you
Jayanth

Connection between SMD Agent and SMD server via SAProuter

In our scenario, we have to setup the connection between SMD agent and SMD server(solution manager server) via saprouter. But during the installation of SMD agent, we can only specify the hostname of the managing system, we have no place to add saprouter string(/H/..../H/). I I am not sure if we could connect the agent and server via saprouter, if so how to do it?
Hope someone can give us your precious advices on this issue.
Karl

Perfect; and thanks for your response. I found this help page for developers to implement P4 support over SAP router: http://help.sap.com/saphelp_nw73/helpdata/en/48/2992d7ad8758d7e10000000a421937/content.htm
But in the SM Diagnostics Setup options I can set up only a direct HTTP adresses and have no options to set up connections over a sap router to P4 ports directly. I can at the moment only solve my problems with NAT or firewall rules.
And also the diagnostic agent setup has no options to config a proxy or sap router. I found yesterday a blog on sdn side with screenshots of the setup with all available connection opetions to SLD... sry I can not post this link today.
This is an official statment of SAP from the current version of SMD guide; it is also possible but why not from the beginning???:
In some network conficurations, the Diagnostics agent has to connect to the Managing system though a SAP router.
This feature will be fully supported in Solution Manager 7 Ehp2 (7.02).
In order to enable this feature in Ehp1, please contact the Diagnostics Agent support team to get information on how to
setup the agent and on which patch level you can perform the installation.
This thread were a long time not answared; proxy and routing connections are mostly stepmotherly handled by SAP; this is also a problem by set up of automatic RFC generations in SMSY; why there are in the setup assitents no options to set up the router string.
I have absolutly no comprehension for this in year 2011. All this technics are good known and long time tested.
In this case the f**k has provoked an answare to this thread and this is what I expected; but sorry for my style You are right I could also writh why the heck
FAQ:
SMD root side on SDN: http://service.sap.com/diagnostics
SM FAQ: http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/4e49dbea-0c01-0010-91bd-f0b61388c9ae
SM Setup Home: http://wiki.sdn.sap.com/wiki/display/SMSETUP/Home
SM Diagnostic Troubleshooting Guide: https://websmp201.sap-ag.de/~sapdownload/002007974700000409092009E/DiagAgent_TroubleShooting.pdf
SMD Candidate Setup: http://wiki.sdn.sap.com/wiki/display/SMSETUP/Diagnostics+Agents

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

Error when registering CCMS agent SAPCCMSR on ECC 6.0 ABAP only system

I need to start the agent sapccmsr on SAP ECC 6.0 system to monitor ABAP proxies for separate MDM system.
I already have the sapccm4x agent running.
When I try to register using:
CALL PGM(<kernel_lib>/sapccmSr) PARM('-r' '-f' '/usr/sap/<sid>/<inst>/log/sapccmsr/csmconf' 'pf=/usr/sap/<sid>/SYS/profile/<inst_host>')
I get the error message:
ERROR: cannot open Config
File /usr/sap/D12/DVEBMGS12/log/sapccmsr/csmconf fo
r registration
I cannot see any issue with authorizations. I have modified the csmconf file with the appropriate passwords. The sapccmsr.install.logs are empty.
Has anyone run into this issue? Can I start the agent on an ABAP only system? If so has anyone done this successfully & have the cmd to do so?
There is probably a very simple solution to this but I just have not been able to find it!
Any information would be greatly appreciated.
Regards,
Diane Szmurlo

Hello Nish,
Have you done SGEN already?
Anyways first try this out Check through SE11 if the tables exist in the new client. For example check for A001. If it shows up there try to activate the table and see if you get any errors. Let us know the results.
Regards.
Ruchit.

Migrate dual stack to ABAP only

We have a dual-stack NW700.
We only want to export its ABAP portion and then use the export to build a new NW700 ABAP only.
1) is this feasible (i.e. the traget system will run? It's OK run without JAVA functionality as long as it runs)
2) if so, on sapinst , should select "system copy-> oracle->central system->system based on ABAP"
OR
"system copy-> oracle->central system->system based on ABAP + JAVA" ?
Thanks!

Hi Jessica,
You don't have to export the database.. Removing the java schema from the database is sufficient.
The installation guide explains how to remove a java add-in from a dual stack system.
Basically you do a drop user cascade from the java schema, remove the java software and delete the java specific parameters from the instance profile.
Kind regards,
Mark

Problems with SMD and Non-ABAP EW Alerts

Hi,
Iu2019m installing Solution Manager Diagnostics EhP1. Iu2019ve installed SMD Agent at my satellite systems and created the system and the solution at Solution Manager EhP1 SP21 (SMSY and DSWP transactions), but when I try to execute at Solution Manager Diagnostics (http:<server>:<port>/sld) managed systems -> setup wizard for my managed systems, I got the following error:
u201CNo instances or servers are defined for this system. Please check its definition in SMSY before proceeding to setupu201D
If I try to open up the system I realise that the Landscape collumn is red-rated and shows:
Start checking Technical System 'EPD~JAVA'. (green-rated)
No Hosts found! (red-rated)
The Technical System is not well defined! (red-rated)
Iu2019ve maintained properly SMSY transaction, and defined servers and instances for Application Server Java, EP Content, EP Core and Enterprise Portal.
On the other hand, Iu2019ve followed SAP Note 976054 and itu2019s attached file, which types that I can schedule an EW Alert for Non-ABAP trhough DSWP transaction -> Solution->Solution Reporting->Services->Activities->Scheduling Reporting.
If I schedule the job and try to execute, the job is cancelled and the job log types this:
Date       Time     Message text                                                               Message class Message no. Message type
18.11.2009 14:03:30 Job started                                                                     00           516          S
18.11.2009 14:03:30 Step 001 started (program RDSWP_REP_SERVICES, variant , user ID SOLMANADM)      00           550          S
18.11.2009 14:03:30 Table (22x9) exported as attachment 1000000000005; 1.570 bytes                 DSWP          857          S
18.11.2009 14:03:30 No layouts found                                                                0K           017          E
18.11.2009 14:03:30 Job cancelled after system exception ERROR_MESSAGE                              00           564          A
At the same word file, it shows that I can download an XML file wich contain all data required for the service in question and upload it into a service session for direct evaluation.
When I try to go to Managed systems->Scheduler, I notice that this section doesnu2019t appear at my Solution Manager Diagnostics. I only have setup options for Diagnostics system and managed systems.
So I resume my main problems:
1 When I try to setup an managed system I get a pop up u201CNo instances or servers are defined for this system. Please check its definition in SMSY before proceeding to setupu201D
2 When I try to execute SM_REP:XXXXXXX job itu2019s cancelled
3 When I try to get an XML file for direct evaluation, Iu2019m unable to get to the option to execute it.
Please, could you help me?
Thanks in advance and regards,
Tomas.

Hello,
When you are clicking on the System in SMSY, do you get a message that this is a dual stack system and gives you a
choice with a dialog that has two buttons to select 'EPD~JAVA' or 'EPD-ABAP'?
Just if you are then you have not defined the system correctly in SMSY
Let me knwo if you get this dialog when you seelct the SID in SMSY.
Did you use the System Landscape Setup Guide to define your technical system?
Regards,
Paul

How do I populate 0CCMSATPH for ABAP only instance

Hi All,
I have inherited a SAP Solution Manager installation and I am trying to configure the system correctly.
In an Early watch report for one of our ABAP only systems (ERP6) it states
Reading performance data from BW returned neither data nor an error code. A timeout may have occurred.
Infocube: 0CCMSMTPH used in section 'Workload Overview <SID>'.
So I determined that this related to End to End Analysis and configured SOLMAN accordingly and am now getting data for SOLMAN itself in this cube but nothing else. I also determined that the Extractor WA (STATISTICAL RECORDS SECONDARY EXTRACTOR-0CCMSATPH) from Extractor FWK Administration is responsible for this data.
So my question is this, where does this extractor come from as I don't appear to have this extractor for the ABAP system it's complaining about?
SMS uses SMDAgent but that's because it's a dual stack system but for an ABAP only system surely this isn't required, if this is where the extractor comes from?
Also a related issue, in the log for this extractor for SOLMAN it has the following message "DL: Warning: Component not found in Target Structure:0INFOPROV". What is this and should I be concerned?
Thanks
Craig

Does this topology/configuration make sense? Yes.
To set up "agent only" instance:
1] Install MDEX,
2] Install PlatformServices (answer N for running EAC),
3] On Central server update AppConfig.xml (add definition for new dgraph),
4] On Central server "runcommand.sh --update-definition"
5] Install Deployment Template by running deploy.sh (answer N for integrate with Workbench),
6] Start ECA, which starts dgraph - $ENDECA_ROOT/tools/server/bin/startup.sh (Make sure you don't have eca.xml in $ENDECA_CONF/conf/Standalone/localhost)
7] On Central server "initialize_services.sh",
8] On Central server "runcommand.sh DistributeIndexAndApply"
Is the agent only server suppose to also have Workbench and/or our application (configuraitons)?No and no.
How does the Control server know there is another instance which is running with just an EAC agent?The AppConfig.xml on the Central server instance needs to be updated. Don't use the Workbench EAC admin console to do this. Only use that interface for stop/start and monitoring. Any permanent config changes you should make to AppConfig.xml by hand.
How is the dgraph process on the agent only instance started?$ENDECA_ROOT/tools/server/bin/startup.sh
How do I "turn on" an EAC agent only instance/server?
Edited by: EndecaJoe on Nov 9, 2012 8:55 AM

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]

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

SMD Agent SR3 on NW2004s SR2

Hi all,
We are running NW2004s SR2 on our Solution Manager system. We upgraded component ST-SER to 700_2008_1. The older SMD agent appears to not work correctly with this level according to SAP.
My question is, is it possible to install the standalone engine for SMD Agent SR3 without upgrading our entire system to SR3? (kernel, installation, Java)
We tried doing the SMD SR3 standalone install but are seeing some strange issues.
If anyone has an answer for me on whether I have to upgrade the entire system or not that would be much appreciated.
Thank you.

Solution Manager is a combined ABAP + Java installation, components of both must be in sync. It's not advised to install separate support packages or updates for certain components only, there are dependencies between them.
Why don't you upgrade t the latest service pack - for both ABAP + Java? This will avoid lots of compatibility problems...
Markus

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 Piotrowsky

Hi 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

SMD Agents on ABAP only stacks

Similar Messages

Maybe you are looking for