EWA on Non-ABAP System with Solution Manager EHP 1

Hi Experts,
We have recently updated our solution manager from SP Stack 16 to EHP1 (sp 18). we are now planning to set up EWA for non-abap components (EP 7.0). however, the only SAP note that i have been able to find is "976054 - Availability of EWA for Non ABAP components" but this is only limited up to SP 17. I have not been able to find any guides relating to EWA thru Solution Manager EHP1.
I would greatly appreciate if anyone can refer any documents or SAP notes that would enable setting up EWA for non-abap components thru Solution Manager EHP1.
We have also gone through the note 1332428, but we have'nt found it useful. We are still struggling to generate EWA report on Non-ABAP system.
Looking forward to your kind help.
Thanks and Regards,
Sarthak Syal

Hi Sarthak,
Good!!
Please do the following:
1) include the system in the Solution and scheduled the EWA session.Logical component should refer to the Non-ABAP System with no ABAP instance as relevant under the SID definition in SMSY-systems.
2) Is the Non -ABAP ( assuming its java) has the Software component defined and is mentioned as relevant under the SID with the component name and type.
3) Having said that SMD - Root cause Analysis functionality is configured-> check whether you are getting the Details for the Non-ABAP systems in the analysis Tabs of Root Cause Analysis.
This should be good to go. Wait for the session to get completed.
Thanks,
Jagan

Similar Messages

How to setup EWA for non-ABAP system with SM 4.0 ?

Hi, we are running SM 4.0 with the support-stack 06. I have set-up a solution for monitoring which includes a NW04 WebAS 6.40 Java only system. Has anyone set-up EWA reports for this type of non_ABAP system who can advise of the steps necessary for this ?
It seems like you need to define RFC destinations for where the monitored system data should be collected from , but there doesn't appear to be anywhere to do this for non-ABAP systems ?
I have looked at Note 738676 - Service Data Download for Non-ABAP Components but it hasn't helped and it seems to be SDCC specific, rather than SDCCN.
Thanks.

Hi Andrew,
we are just developing it, at the moment you have the following option, your java system has to send by ccms agends its data to an ABAP 640 system or higher, there you can see its alerts in ccms, then you have to make both system available in SMSY. Then important you have to assign the java system as a system component, then we collect also the java data and shows them in the EWA of the ABAP system. There for go to the main instance tab and set a java main instance to relevant and assign your java system.
This is the old, available standard solution. At the moment we develop it also for java stand alone.
I think it will be available with the new ST-SER in autumn
Regards,
uDo

EWA for non-ABAP systems

Hi,
We are planing to implement EWA for Java systems. Currently EWA is active for all ABAP systems. Do we need Wily Introscope in order to setup the EWA for non-ABAP systems? Or just we can use the SMD to generate EWA reports for Java systems?
Any idea?
Thanks,
Kris

Thanks Paul
We are on SM 7.0 EhP1. But I see following info in note 976054. It says data sources for EWA are different on 7.0 EhP1, does it mean we don't need wily from 7.0 EhP1 onwards?
Data sources in Solution Manager Diagnostics up to SP17 used for EWA for non-ABAP components analysis are:
                      - Introscope (SAP Note 797147),
                      - Garbage Collection (SAP Note 1079125) and
                      - Portal Activity Reporting (SAP Notes 936612 to know how to activate PAR and 914791, 1075276 to configure SQL
                        Command Console).
Starting with Solution Manager 7.0 EHP1 (SP18) the data sources are:
                      - Solution Manager BI for performance data
                      - Configuration and Change DB(CCDB) for configuration data
Thanks,
Kris

Transport Management System with Solution Manager

Dear all,
Do you know the function transport management system(TMS) with solution manager, I already search in SAP document but not found this function.
Do you know how to config solution manager for TMS and documents related with this function please guide for me!
Thanks all very much !

Hi,
Check this link.
https://websmp103.sap-ag.de/~sapdownload/011000358700000508502008E/ChangeRequestManagement.pdf
Hope this answers your questions.
Feel free to revert back.
-=-Ragu

Evaluation system with Solution manager

has anyone added an evalaution system where a user who logged a support message can evaluate the Solution given, with Solution manager. Basically the same thing like SAP have. When you close a call you have to rank the messageeg in regards of qaulity of answer etc etc..,
Anyone that might have any ideas how to do this, could you please give me some direction to how I can implement an evaluation system.
I thought of having a URL added to confirmation message, where the user can click on to take him to some area where he could evalaute the message. This systems is then linked to Solution manager so that I can report on these messages and the evealuation received for these support answers.
I will appreciate any feedback and any ideas would be most welcome to help me to get to a method of implementing such a evaluation system or developing such a system.

Dear Johan,
Firstly the kind of scenario that you are trying to implement is not possible via the standard configuration of Support Desk.
What I can think of is probably creating an action while closing the message which generates a form for the user to be filled and saves the values into an custom table for questions based on evaluation of the solution.
Later you can generate reports based on this table.
Regards
Amit

Configuring EWA for non Abap System

Hello to everybody.
I am configuring EWA in Portal System 7.01and SOLMAN 7.01 too. It's a new installation and i have a question:
- Which is the order to start to configure SMD?
- Is Necessary configure the CCMSR agent?
I configured EWA in a old system that had installed the agents, but they could not to connect to SMD Server.
I Fixed this problem, but now I need configure the SMD since start.
By the way, I'm new configuring EWA for Java
Thanks.
Esteban G.-
Edited by: Esteban Gutierrez E. on Jan 11, 2010 8:48 PM

Hi Sailesh
Here is related blog fr your issue. Hope this will help you.
setup EWA for portal
Thanks
Jignesh

Monitoring a non-SAP satellite system in Solution Manager

Hi Folks,
I have two quick questions.
1.) What is the proper procedure/tool for monitoring a non-NW system in Solution Manager? Should I be able to use sapccmsr and saposcol on these systems?
2.) What is the proper way to connect a non-NW system to the SLD? Should I be able to use saposol and sldreg for these?
Background:
- My Solution Manager system is a NW70 EHP1
- Solution Manager Diagnostics is installed and monitoring my ABAP and Java systems
- I have my CCMS agents registered back to my CEN for the ABAP and Java systems
Satellite systems:
- Multiple Wintel servers (both IA32 and x64) that are running;
o standalone SQL server databases
o BOE/BOBJ
o BPC for Microsoft
Section 4.8 of the Monitoring Setup Guide (CEN SAP Netweaver 7.0 SPS18) states that I should be able to monitor a standalone database.
My confusion isu2026 in the absence of an SAP filesystem (kernel) and the standard SAP environment variables that get set during an install, how do I register the agents? The executables do not want to launch.
Thank you,
Bill

Dear William,
Monitoring of NON-SAP systems is not actually done on the solution manager system itself. The solution manager system gets its feed of alert information from the satellite, specifically CCMS. For SAP systems, alerts from CCMS are set up and activated by default. For Third-Party systems you have to be ablke to set up the interface to feed monitoring information from your non-SAP software to SAP's CCMS infrastructure.
You can get more information on CCMS agents via the website at http://service.sap.com/monitoring.
Go to "system Monitoring and Alert Management" > "Monitoring in Detail".
I hope this information is helpful.
Regards,
Paul

Add sap R/3 enterprise system in solution manager SLD

Dear All
Required solution manager configuration documents.
We have DEV QAS and PRD server on SAP mySAP ERP 4.7 ( SAP R/3 Enterprise )
And during the installation of solution manager I select u201CConfigure a Local SLD u201C
Which steps I follows to connect or configure my sap system with solution manager ( SLD ) then I will configure central monitoring, TMS management, Helpdesk etc
Who to Configure SLD Bridge ( in SLD Server ) ?
in which system Run Transaction RZ70 ( In SAP R/3 Enterprise ) ?
and how to Verify that my system is connected and working fine With SLD
Please help me regarding u201C configuration solution manager u201C
Regards
Shahid

Hi
Visit for step by step details of Standard Configuration of Basic Settings
http://service.sap.com/rkt-solman-->SAP Solution Manager 7.0->Technology Consultants & System Administrators->Technical Configuration->just drill out there you can find lot of simulator how to install and configure solution manager
http://www.wilsonmar.com/sap_solution_manager.htm
/people/federico.babelis2/blog/2006/04/14/service-desk-configuration-guide-for-dummies
Regards
Uday

Monitoring of Non ABAP System

Hi,
I posted this thread at the Solution Manager forum.
I need to confirm what i understood there.
I want to monitor portal (Non ABAP) components in Solution Manager 3.2 .
I was advised that it is not possible in Solman 3.2 and i have to upgrade it 4.0.
Could anyone please confirm this.
Juan , Awaiting your comments.
Others are welcome too.
Regards,
Ashish .A. Poojary

Hi,
You have to install solman diagnositic tools to monitor stand alone java stack, But if you want to monitor java stack of abap+java then you have to first register the ccms agent through visual admin. Then you can add the java stack as logical component. But 4.0 has be the better options.
There are many posts in the forum so for adding the java stack .
Regards,
Vamshi.

System Monitoring with Solution Manager Ehp1

Hi,
I'm Tomas Piqueres, and I'm working in a VAR SAP with Solution Manager.
Recently, we installed Solution Manager Ehp1 and we are trying to configure it for System Monitoring. When I worked with Solution Manager SP17 I used to go to transaction RZ21 to add the system I wanted to monitoring and then put the SID and RFCs of the system.
Now with Solution Manager Ehp1, when I create the system in transaction RZ21, first I have to set the Component Type to Be Monitored and then the SID, Message Server Logon Group, the client and user are set automatically, and the password I've set to user CSMREG.
when I fill all the entries, I can see the RFCs used for the monitoring of the system. Those RFCs are set automatically:
<SID>_RZ20_COLLECT
<SID>_RZ20_ANALYZE
I can't edit those RFCs, so I have to create it manually. I check that RFCs destination works fine and both pass the authorization test, so when I try to save the system at transaction RZ21, I see the following errors:
<SID>_RZ20_COLLECT_123539Error when opening an RFC connection
Error during remote call of SAL_MS_GET_LOCAL_MS_INFO function: Error when opening an RFC connection
Error during remote call of SALC function: Error when opening an RFC connection
Error during remote call of RFC1 function: Error when opening an RFC connection
I've been looking for information about those errors and how to monitoring with Solution Manager Ehp1, but I haven't found anything usefull.
Please, Could you help me?
Thanks and regards,
Tomas.

Tomas,
I need to configure EWA from my Solman system and I completed the steps (defining and creation of RFC destinations to the target systems from my Solman system). I downloaded the lates ccmsagent file from the market place based my target system configurations.
Herewith attaching the logs while I'm trying to check the profile parameter.
tqaadm@saptqa01:/usr/sap/TQA/SYS/exe/run 5> sappfpar check pf=/usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
================================================================================
==   Checking profile:     /usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
================================================================================
***WARNING: Unexpected parameter: DIR_EPS =/usr/sap/trans/EPS/----
***WARNING: Unexpected parameter: SAPSECULIB =/usr/sap/TQA/SYS/exe/run/libsapsecu.o
***WARNING: Unexpected parameter: abap/buffersize_part1 =1200000
***WARNING: Unexpected parameter: auth/auth_number_in_userbuffer =5000
***WARNING: Unexpected parameter: dbs/io_buf_size =100000
***WARNING: Unexpected parameter: rsau/local/file =/usr/sap/TQA/DVEBMGS30/log/audit/audit_++++++++
***WARNING: Unexpected parameter: rsau/selector1/class =35
***WARNING: Unexpected parameter: rsau/selector1/severity =2
***WARNING: Unexpected parameter: rsdb/rclu/cachelimt =0
***ERROR: Size of shared memory pool 40 too small
================================================================
SOLUTIONS: (1) Locate shared memory segments outside of pool 40
               with parameters like: ipc/shm_psize_<key> =0
SOLUTION: Increase size of shared memory pool 40
          with parameter: ipc/shm_psize_40 =1472000000
Shared memory disposition overview
================================================================
Shared memory pools
Key:   10 Pool
            Size configured.....:   642000000 ( 612.3 MB)
            Size min. estimated.:   637597428 ( 608.1 MB)
            Advised Size........:   640000000 ( 610.4 MB)
Key:   40 Pool for database buffers
            Size configured.....: 1048000000 ( 999.4 MB)
            Size min. estimated.: 1468229308 (1400.2 MB)
            Advised Size........: 1472000000 (1403.8 MB)
Shared memories inside of pool 10
Key:        1 Size:        2500 (   0.0 MB) System administration
Key:        4 Size:      523648 (   0.5 MB) statistic area
Key:        7 Size:       14838 (   0.0 MB) Update task administration
Key:        8 Size:    67108964 ( 64.0 MB) Paging buffer
Key:        9 Size:   134217828 ( 128.0 MB) Roll buffer
Key:       11 Size:      500000 (   0.5 MB) Factory calender buffer
Key:       12 Size:     6000000 (   5.7 MB) TemSe Char-Code convert Buf.
Key:       13 Size:   200500000 ( 191.2 MB) Alert Area
Key:       16 Size:       22400 (   0.0 MB) Semaphore activity monitoring
Key:       17 Size:     2672386 (   2.5 MB) Roll administration
Key:       30 Size:       37888 (   0.0 MB) Taskhandler runtime admin.
Key:       31 Size:     4806000 (   4.6 MB) Dispatcher request queue
Key:       33 Size:    39936000 ( 38.1 MB) Table buffer, part.buffering
Key:       34 Size:    20480000 ( 19.5 MB) Enqueue table
Key:       51 Size:     3200000 (   3.1 MB) Extended memory admin.
Key:       52 Size:       40000 (   0.0 MB) Message Server buffer
Key:       54 Size:    20488192 ( 19.5 MB) Export/Import buffer
Key:       55 Size:        8192 (   0.0 MB) Spool local printer+joblist
Key:       57 Size:     1048576 (   1.0 MB) Profilparameter in shared mem
Key:       58 Size:        4096 (   0.0 MB) Enqueue ID for reset
Key:       62 Size:    85983232 ( 82.0 MB) Memory pipes
Shared memories inside of pool 40
Key:        2 Size:    31168040 ( 29.7 MB) Disp. administration tables
Key:        3 Size:   114048000 ( 108.8 MB) Disp. communication areas
Key:        6 Size: 1064960000 (1015.6 MB) ABAP program buffer
Key:       14 Size:    28600000 ( 27.3 MB) Presentation buffer
Key:       19 Size:    90000000 ( 85.8 MB) Table-buffer
Key:       42 Size:    13920992 ( 13.3 MB) DB TTAB buffer
Key:       43 Size:    43422392 ( 41.4 MB) DB FTAB buffer
Key:       44 Size:     8606392 (   8.2 MB) DB IREC buffer
Key:       45 Size:     6558392 (   6.3 MB) DB short nametab buffer
Key:       46 Size:       20480 (   0.0 MB) DB sync table
Key:       47 Size:    13313024 ( 12.7 MB) DB CUA buffer
Key:       48 Size:      300000 (   0.3 MB) Number range buffer
Key:       49 Size:     3309932 (   3.2 MB) Spool admin (SpoolWP+DiaWP)
Shared memories outside of pools
Key:       18 Size:     1792100 (   1.7 MB) Paging adminitration
Key:       41 Size:    25010000 ( 23.9 MB) DB statistics buffer
Key:       63 Size:      409600 (   0.4 MB) ICMAN shared memory
Key:       64 Size:     4202496 (   4.0 MB) Online Text Repository Buf.
Key:       65 Size:     4202496 (   4.0 MB) Export/Import Shared Memory
Key:     1002 Size:      400000 (   0.4 MB) Performance monitoring V01.0
Key: 58900130 Size:        4096 (   0.0 MB) SCSA area
Nr of operating system shared memory segments: 9
Shared memory resource requirements estimated
================================================================
Nr of shared memory descriptors required for
Extended Memory Management (unnamed mapped file).: 64
Total Nr of shared segments required.....:         73
System-imposed number of shared memories.:       1000
Shared memory segment size required min..: 1472000000 (1403.8 MB)
System-imposed maximum segment size......: 35184372088832 (33554432.0 MB)
Swap space requirements estimated
================================================
Shared memory....................: 2050.4 MB
..in pool 10 608.1 MB,   99% used
..in pool 40 999.4 MB, 140% used !!
..not in pool:   34.4 MB
Processes........................: 716.8 MB
Extended Memory .................: 8192.0 MB
Total, minimum requirement.......: 10959.2 MB
Process local heaps, worst case..: 1907.3 MB
Total, worst case requirement....: 12866.5 MB
Errors detected..................:    1
Warnings detected................:    9
After checking the profile parameter I tried to run sapccm4x in /run directory but got the below error and I'm not able tomove further.
Pls have a look at these two and let me know what could I do to proceed further.
tqaadm@saptqa01:/usr/sap/TQA/SYS/exe/run 5> sapccm4x -R pf=/usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
INFO: CCMS agent sapccm4x working directory is /usr/sap/TQA/DVEBMGS30/log/sapccm4x
INFO: CCMS agent sapccm4x config file is /usr/sap/TQA/DVEBMGS30/log/sapccm4x/csmconf
INFO: Central Monitoring System is [SMP]. (found in config file)
      additional CENTRAL system y/[n] ?   :
INFO: found ini file /usr/sap/TQA/DVEBMGS30/log/sapccm4x/sapccmsr.ini.
INFO:
      CCMS version 20040229, 64 bit, multithreaded, Non-Unicode
      compiled at   Jun 28 2010
      systemid      324 (IBM RS/6000 with AIX)
      relno         6400
      patch text    patch collection 2010/1, OSS note 1304480
      patchno       335
INFO Runtime:
      running on    saptqa01 AIX 3 5 00069A8FD600
      running with profile   /usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
INFO profile parameters:
      alert/MONI_SEGM_SIZE = 200000000
      alert/TRACE          = 1
      SAPSYSTEM            = 30
      SAPSYSTEMNAME        = TQA
      SAPLOCALHOST         = saptqa01
      DIR_CCMS             = /usr/sap/ccms
      DIR_LOGGING          = /usr/sap/TQA/DVEBMGS30/log
      DIR_PERF             = /usr/sap/tmp
INFO:
      pid           4165682
INFO: Attached to Shared Memory Key 13 (size 200141728) in pool 10
INFO: Connected to Monitoring Segment [CCMS Monitoring Segment for application server saptqa01_TQA_30, created with version CCMS version 20040229, 64 bit single threaded, compiled at Oct 3 2008, kernel 6400_20020600_254, platform 324 (IBM RS/6000 with AIX)]
        segment status     ENABLED
        segment started at Tue Sep 14 09:35:56 2010
        segment version    20040229
ERROR: Shared Memory misconfiguration ==> can not monitor SAP application server saptqa01_TQA_30
       Dispatcher Admin Shared Memory (Key 01) and CCMS Shared Memory (Key 13) both in pool 10.
       Please change configuration with profile parameters
           ipc/shm_psize_01 = -<different pool nr>
       xor
           ipc/shm_psize_13 = -<different pool nr>
EXITING with code 1

EWA for non-abap not triggering with SDCCN session

Hi
I can manually download the session and generate EWA for java stack but its not automatically generated with SDCCN report. Its a double stack system, i am getting EWA for abap stack but not for java stack. Guide on note 976054 do not clearly mention what to do.
Any suggestion

I JUST got this working after months of End-to-End Diagnostics Setup ...
You've run the SMD wizard to set up the managing system?
You've deployed smdagents everywhere you have a non-abap system? Use the SR3 install .. lets you register from SLD ... works when ping of your soulution manager host hasn't a chance.
You've deployed the wily agent? Use the absolute latest hostagent 7.2.3 or use the binary agent
You're running Wily Enterprise manager outside of sap
You've run the SMD wizard to set-up you non-abap systems
You've doubled the size of the host that runs SM/SMD 7.0
You've run the Diagnostics Admin > Diagnostics system > self check and got the reds down to an absolute minimum?
If the SMD wizard for the managing system had problems creating the WEBADMIN RFC,
there is an IMG activity (Solution Manager > Configuration > Basic Settings > Earlywatch Alert > Early Watch Alert for non-abap > Check RFC connection) that says to copy RFC SOLMANDIAG as WEBADMIN. This works where the wizard didn't.
/Ken Chamberlain
University of Toronto

EWA report for non-abap systems

Hi Gurus,
Good day.
I would like to ask, what are the steps that I'm going to do when configuring an EWA report for non-abap systems i.e portal. Do Ineed to install SMD agents on my non-abap systems and connect to diagnostic agent of solman?
Or do I need to install wily introscope agents on my non-abap systems and connect to diagnostic agent?
It is both? Which one?
It would be also great if you can provide me links/documents in relation to my queries.
Please do note that the current version of solman system is 7.1
Thanks in advance for the help
Virgilio

Hi Virgilio,
To generate an EWA report for Java stack system,
you need to do following:
1. install smd agent (diagnostics agent) on Java stack system
you can install this agent standalone, details see note 1234384.
The installation Guide is also attached in note 1234384.
2. finish Initial Config and Basic Configuration in solman_setup for
solman system, the setting about Enterprise Manager is also included
in these configurations, please ensure EM is running properly.
3. start managed system configuration for the EP system in solman_setup
after selecting the system type 'Java', please finish all steps as
suggested in which step. The Step 'Wily Introscope Configuration' is to
install Introscope Agent which is used for Java stack system. More infor
please read the installation Guide of Enterprise Manager and note
797147.
4. You should be able to see data in Wily Introscope and Workload
analysis via
Root Cause Analysis->End-to-End Analysis->select the system->Workload
Analysis
5. If the EP system is added in a solution, the EWA task for this system
should be shown up in solman's SDCCN.
Also check note: 976054"
Thanks
Regards,
Vikram

SAP NW 7.4 as java system sync with solution manager system 7.1 issue

Dear all,
I have installed SAP NW 7.4 system SP level is SP5 ,after that i have cheked in service marlket palce Now service market plkace latest SP level SP7.
For manula downlowd( directly from service market place) is difficult for java system and i have started sysnc with solution manager system to download patches through MOPZ.
Below are the activities completed:
1) Through template installed I have rgeisterd the system into Solman SLD.
2) Sync completed succfully exact product version is shwoing in solman SLD
3) after that I have checked in SMSY and LMDB its showing prefectly
4) But in SMSY its shwoing only under technical system,not showing product systems
5) I have assigned in product system in LMDB
Now the issues while selecting the system group and logical componensts I have created one logical componnets -but in that SAP NW 7.4 is not showing and I have assumed SAP NW 7.3 EHP1 after creating my newly create dsystem is not shwoing in drop down.
I ma getting belwo error.
No system found for this product/product instance
Message no. SOLAR_SPROJECT110
Please sugegst how to reslove the error ,and a;lso please let me know is there any way to download latest pathces to dpownload from service market place .
Advance Thanks

Hi,
re-check if the 7.4 system is correctly registered in the solman SLD system.
Re-check LMDB definition for your 7.4 as JAVA system. you have to manually created the Product system. Ensure all the Component and definitions are correct.
Also do a verrification run within the LMDB. This will confirm whether all the information is correctly defined.
Please note - SLD -> LMDB -> SMSY.
So, if the first 2 don't have the correct information, you wont have much joy with smsy.
Rgds
Deepak

EP 7 systems in Solution Manager 7 for EWA activation

Dear Expert,
Greetings from Partha.
I need to include our EP 7 systems in Solution Manager 7 for EWA activation. Current lanscape scenario
Solution Manger 7.00 Installed
EP 7.00 Installed
No central SLD configured and all the system have local SLD.
1. As per the installtion guide & SAP notes we need to install
a> SM Diagnostics Agent & Wilo Introscope in Solution Manager (manging system).
b> Diagnostics Agent in every manged system(s).
For managing system we can download Diagnostics Agent installation DVDs from SAP Service Marketplace
at: http://service.sap.com/swdc --> Download --> SAP Support Packages --> Entry by Application Group
--> SAP Technology Components --> SAP SOLUTION MANAGER --> SAP SOLUTION MANAGER 7.0
--> Entry by Component --> Agents for Managed systems --> DIAGNOSTICS AGENT 7.11
--> <choose operating system of managed>
Our Solution Manager 7 is already installed and @SPS 17. My question is
1. Can we use the same file for SMD installtion in Solution Manger or we need to download it from some other area ?
If it is different then kindly let me know what are the DVDs to be downloaded and from where?
2. In our Managed System SMD installtion we have decided for
--> Installation Strategy as Direct Solution Manager Registration
But what strategy we should take for SMD installation on Sol Man 7 that is
Local SLD (wrt Sol Man) Registration or Direct Solution Manager Registration
3. What is the need for the SAP Host Agent Installattion ? Is it mandatory ?
Help will be appreciated.
Regards,
Partha

1. As per the installtion guide & SAP notes we need to install
a> SM Diagnostics Agent & Wilo Introscope in Solution Manager (manging system).
b> Diagnostics Agent in every manged system(s).
For managing system we can download Diagnostics Agent installation DVDs from SAP Service Marketplace
at: http://service.sap.com/swdc --> Download --> SAP Support Packages --> Entry by Application Group
--> SAP Technology Components --> SAP SOLUTION MANAGER --> SAP SOLUTION MANAGER 7.0
--> Entry by Component --> Agents for Managed systems --> DIAGNOSTICS AGENT 7.11
--> <choose operating system of managed>
Our Solution Manager 7 is already installed and @SPS 17. My question is
1. Can we use the same file for SMD installtion in Solution Manger or we need to download it from some other area ?
If it is different then kindly let me know what are the DVDs to be downloaded and from where?
Check the pdf attached in note 1234387 - Inst. 7.1 EhP1 - Diagnostics Agent installation
If you have SP17, you must follow note 1357812 and install Diagnostics Agent 7.01 SR1
2. In our Managed System SMD installtion we have decided for
--> Installation Strategy as Direct Solution Manager Registration
But what strategy we should take for SMD installation on Sol Man 7 that is
Local SLD (wrt Sol Man) Registration or Direct Solution Manager Registration
It doesn't matter what strategy you'll decide. You could decide Direct Solution Manager registration
3. What is the need for the SAP Host Agent Installattion ? Is it mandatory ?
As you have solution Manager SP17, you can't install Saphostagent 7.11 and for this reason you can't use SAphostagent.
Agent 7.01 => No Saphostagent
Agent 7.11 => Must install saphostagent
Agent 7.20 => Already have SAPhostagent installed

EWA for NON-ABAP

Hi,
I configured SMD in solman, installed SMD & IA agents in Java systems(portals). But not able to generate report.
EWA setup was already done, i installed the agents recently. Even downloaded the service xml from solman SMD and tried to generate report manually, but not able to generate it.
In SDCCN the session log shows as follows.
         07/07/2008     04:53:59     Transfer of session data completed to destination NONE
         07/07/2008     04:53:59      > transfer completed
         07/07/2008     04:53:59      > transfer for server XXXXX completed
         07/07/2008     04:53:58     > transferring 000005 functions, 0000204676 bytes, RFC block size = 0000320000 for server bs1pa01z
         07/07/2008     04:53:58      > transfer for server XXXX started
         07/07/2008     04:53:58      > transfer data to mapped session ID 0000003416 100 destination NONE
         07/07/2008     04:53:58     Transfer of session data started to destination NONE
         07/07/2008     04:53:58     Data collection completed for session 1000000003416 EWALERT SolMan
         07/07/2008     04:52:45     Collection is for non-ABAP system <SID> 0020224025
         07/07/2008     04:52:45     Data collection started for session 1000000003416 EWALERT SolMan (non-ABAP)
         07/07/2008     04:52:45      > New data collection triggered using reference session TSKR000001012
         07/07/2008     04:52:45     Session download data requested using task 0000001887 by BATCHBASIS
Please guide..
On solman 4.0 SPS 15, ST-SER 700_2007_1 PATCH 1
Edited by: Kobby bryant on Jul 8, 2008 2:59 PM
Edited by: Kobby bryant on Jul 8, 2008 3:36 PM
Edited by: Kobby bryant on Jul 8, 2008 10:48 PM
Edited by: Kobby bryant on Jul 9, 2008 2:26 PM

Hello.
First of all, you must ensure that your solution manger has, at least, stack 13 of support package, in java and ABAP side.
Once you hace installed your agents in solution manager, you must to do different things in your satellite system.
- First of all, you must get sure that you have deployed LMSERVICE in your satellite system. And you must deploy -     JmxService7.1.P5NetWeaver.ear file.
- Secondly, you must install wily folder in /usr/sap/ccm . Willy folder is obtained in ISAGENT71_11-20002182.SAR file.
Into Wily folder, you must look for sap_IntroscopeAgent.profile file, and you need to modify it in order to be seen for your solution manager. To do this step, only find in this file the next item:
introscope.agent.enterprisemanager.transport.tcp.host.DEFAULT=
It will have value 'localhost' and you must delete 'default' and insert your solution manager host.
- Then, you must go to the next folder opening cmd:
\usr\sap\ccms\willy\connectors
There, execute the next command in order to create the necessary connector:
java -jar CreateAutoProbeConnector.jar -jvm C:\j                2sdk1.4.2_06 -output connector.jar
Get sure tou put your corresponding JDK
- You must install SMD agent in your satellite host, executing sapinst that is in CDSMDTOOLS21_0-10003537.SAR file.
- Once your agent is running go to \usr\sap\SMD\J98\component_analyzer and execute the command 'gather setup' . It will open to you a new window with some warnings. Double clicking in each warning and editing node, you can insert a value in order to correct these warnings.
- Then, you must insert different java parameters in your config tool. Parameters are the next:
-Xbootclasspath/p:K:/usr/sap/SMD/J98/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.7.1.P11-2007-09-27/wily/connectors/AutoProbeConnector.jar;K:/usr/sap/SMD/J98/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.7.1.P11-2007-09-27/wily/Agent.jar
-Dcom.wily.introscope.agent.agentName=<name of the agent : insert what you want>
-Dcom.wily.introscope.agentProfile=K:/usr/sap/SMD/J98/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.7.1.P11-2007-09-27/wily/sap_IntroscopeAgent.profile
-XX:+PrintClassHistogram
-XX:+HeapDumpOnCtrlBreak
- When you have done this, you must configure your system in SMSY following SAP guides and create the solution in solution_manager transaction.
- The next step is configure the system in SMD web:
1.- execute SMD upgrade.
2.- Setup diagnostics system
3.- Setup managed system
4.- in 'Trouble shooting' insert jdbc parameters
5.- In 'Introscope agent' you must load the parameters you configured in configtool.
6.- At this point will be necessary to restart your satellite system.
When you finishes all these steps you will be able to obtain EWA for java side.
Is so difficult to do this. We have done it in several environments and we have had lots of problems, but it's possible.
Any doubt, please, give me your mail and I'll be so glad to help you.
Best regards.

EWA on Non-ABAP System with Solution Manager EHP 1

Similar Messages

Maybe you are looking for