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.

Similar Messages

IDOC to Non-ABAP-System

I am trying to send an IDOC to a Non ABAP system. The receiving system consists of an "IDOC Listener" which receives and sends. The RFC Destination for the connection between the PI and that system is type T (TCP/IP). When checking it in SM59 or IDX1 on the PI, everything looks fine - connection works. Still when I try to send a message, the adapter call fails with the message "RFC Destination incorrect". Is it necessary to have a type 3 (ABAP system) connection for the IDOC adapter and if yes, is there any way to bypass this? The scenario works fine if I communicate between a standard R/3 4.7 and the 3rd party system (even with the type T destination) - nevertheless PI is intended to be used in between for monitoring etc. - therefore the direct R/3 <-> 3rd Party scenario is no option for me. Any clues highly appreciated.
Cheers,
Andy

Hi,
>>>Is it necessary to have a type 3 (ABAP system) connection for the IDOC adapter and if yes, is there any way to bypass this?
I did a scenario like this (and the other way round) a year ago and as far as I remember I didn't use RFC dest type 3 .
there is an easy way to find it out - just use IDOC classes from service.sap.com/connectors
(server) in order to check what kind of RFC does it expect - I tested those libraries and they worked with PI
without any issues (and with corresponding RFC dest)
Regards,
Michal Krawczyk

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

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

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

Roles for Testing ChaRMs for Non-Abap Systems

Hi,
Can you please suggest what all authorizations are required for Testing the ChaRM functionality for non-abap systems
Thanks in advance
Regards,
Reddi

hi
check the link
Check the Configuration guide for the prerequisites.

Solution Manager System Monitoring for non SAP system

Dear Support,
I have configured the CCMS Agent (SAPCCMSR) for non-SAP system (Windows 2008R2).
The system information (e.g. CPU, Memory, Disks etc) has already showed in RZ20 of Central Monitoring system (e.g. Solution Manager).
How can I do to configure to display these information in the Alert Inbox tab on System Monitoring Workcenter?
Best regards,
Fan Hung

Hi,
Have you defined and added corresponding logical systems for the respective satellite systems?
Here is the sequence of steps you've to do:
in SMSY:
1) Define server, DB, Systems
2) Generate READ, TMW, TRUSTED RFCs to the satellite systems
3) define logical systems and assign the satellite system to it
in Solution_Manager:
1) define new solution
2) add the logical system into the solution
If these steps are successful, you should be able to see the satellite system in SYSTEM MONITORING in Solution_Manager.
Have you already done these steps?
After performing these steps:
Solution_Manager>choose relevant solution>operations setup>Solution Monitoring>System monitoring>Activate monitoring> choose the system and activate monitoring.
Your system will then appear.
Does this help any way?

EWA reports for non abap systems

Hello gurus,
I am facing a problem with configuration of EWA reports for SAP NW Portal.
I have already configured EWA for abap systems, and those are running good on weekly basis. but i have problem with configuration of reports for java systems.
So far, i have installed an SMD agent and CA on my EP-satellite system. I have also configured and SMD server on my Sollution Manager and registered the SMD agent on SMD server and installed Willy Introscope on SMD server.
I am using a central SLD which is running on different host as Solution Manager. I did all the configuration (smsy_setup, configuration of sld_data_supplier etc... )
I have also created the system in SMSY, matched the smsy with SLD (data source SLd)and assigned Logical component to java system.
>>> But when i want do define data collection in the SMD for Gargage Collection (task in scheduler) i cannot see host of my portal system in the SMD.
In the SMD i can see just the abap systems for which the EWA are being already generated.
(i have done also configuration>>connecting managed sytem to the SMD, but i still cannot connect my Portal system to SMD)
Do you have any idea, what i have done wrong?
My solution manager is running on Sap NW 7.0, SPS16,
Sattelite system , EP SPS 19
Thank you very much for your points!!

Hello Jagan,
I was following the enclosed guide from the note: 976054, but it doesn't help to solve my issue.
And when i want to permorm the setup for the managed systems,(http://<host><port>/smd -> diagnostic setup->managed systems ->setup wizard) i can not see there my Portal systems, just the abap systems.
Do you have any idea?
Thanks,
Best regards
Slavomir

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

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

Consuming ABAP Web Service in Non SAP system

Hi
I have created an ABAP web service form the RFC and configured it in the SOAMANAGER. I have tested it in Web Service Navigator using the URL and it is working fine.
Now I am trying to access it from the Non SAP system using Java Code. I am able to access the WSDL using the URL from the step 1 but not able to receive any output when providing inputs.
So I am not sure if I am missing any configuration on the Provider System (SAP) or on the Consumer system (Non SAP) to access the web service. As far I have not configured anything on the consumer system. Please let me know how to consume the web service in the Non SAP system.
Thank you,
Rohit

not necessarily an answer to your question, but i find that when creating SAP web services, before we create the code for consuming them, I always test them with the SOAPUI package. with this test suite you can import the WSDL, and run individual tests, seeing the input, output, exceptions, etc. This is a good way to check the connection, the flow and the service logic, before writing any code. This will also let you know whether it is a WS issue, or an issue with your code.
just a thought, from someone who has been there...
http://www.soapui.org is where you can find the SOAPUI. It helped me out a lot.
Dave

OTO information not complete for non ABAP instance of system &1 in SMSY

Hello,
We have just applied Stack 23 and stack 24 to our Solution Manager system. When we are executing action System Logon from a ticket we are getting the following error:
OTO information not complete for non ABAP instance of system &1 in SMSY
We checked that this new message was created in note Note 1427761 - ChaRM: incorrect target system for action "System Logon".
We went to the SMY transaction to the Product System definition for our system but we could not find which OTO information is missing there, where to load it, etc.
We appreciate your help.
Regards
Esteban Hartzstein

Hello,
We have not applied the note separately, but we applied the support packages, so all the changes were applied, and therefore we are getting this error message of "OTO information is not complete ....
We have updated as suggested the info regarding the system in the SMSY. We have read the Remote System Data.
We will run SOLMAN_SETUP again to review the setup, and then test again
We appreciate also if you provide any additional input.
Regards
Esteban Hartzstein

Monitoring of Non ABAP System

Similar Messages

Maybe you are looking for