RFC monitoring

Hi All,
I have set up the RFC monitoring thru BPM in SOLMAN.Ihave set up alerts too. Now i get alerts whenver my RFC is down in the satellite system,but i should also get a alert in case no RFC fails also that every thing is fine.
How can i set that up ?
Regards
Kiran

Hello Kiran,
This doesn't make sense.
You want to be alerted when there is a problem.
A problem would be an exception. Something you do not expect to happen frequently, but when it does, you want to be notified/alerted.
The concept is everything is running smoothly most the time, and for those few instance when an alert is triggered you want to notice it and take some kind of corrective/remedial action.
Normally there should not be alerts. Most the time there should be no alerts. Because most the time everything should be fine.
If you trigger an alert when there are no issues with RFCs that are being monitored, you will be creating constant alerts that are useless, because they are just indicating that evertything is okay.
And each one will have to be checked, the thousands that tell you everything is okay. You will have to check each one, just to make sure its not a real alert based on a problem with the RFC's that are being monitored.
You do not set an alert when everything is okay. This defeats the entire purpose of being alerted to a problem . How would you know when there is a problem, when alerts are being generated all the time? This makes no sense and there is no useful purpose to doing so. I would strongly recommend you do not attempt this, and understand that no alert is your alert that everything is fine. That's the concept of alerts..alert on error condition, you don't alerts when everything is fine, because the fact there is no alert means everything is fine..
Regards,
Paul

Similar Messages

CCMS qRFC Monitoring: Missing Transactional and Queued RFC Monitoring Nodes

Hi ,
We are trying to create a Queued RFC monitoring for VERTEX Queued , but we are missing CCMS Monitor Templates,in monitor Communications -->Transactional RFC and Queued RFC in Dev and PROD ,but its present in QA System .
I have checked all system are at same level for support packs , kernel version .
I have refered following Notes - 441269,437187,455431, 485826
Can we create manually new one , but we are missing MTE class also ?
Can we create new monitoring template ?
We are running 4.6c with basis support pack level :
SAP_BASIS 46C 0054 SAPKB46C54
SAP_ABA 46C 0054 SAPKA46C54
Thanks
Hamendra

Hamendra,
Please make sure background dispatching is activated in your system. Go to tcode RZ21 and menu Technical Infrastructure --> Method execution --> Active background dispatching.
This should schedule a job called SAP_CCMS_MONI_BATCH_DP. This is the job that will run the function for building the ALE/EDI monitoring segment.
After scheduling the job check back in a few hours, if the ALE/EDI monitor is still not there try the following.
1. Go to tcode RZ21
2. In the topology section choose radio button "Segment overview" and click display
3. Go into change mode and delete the monitoring segments
This will force the system to recreate all the monitoring contexts.
Check back in a few hours and see if the monitor is working.
Tarkesh

RFC monitor with CCMS

Hello,
I'm implementing RFC monitor with CCMS and I have a problem.
I was able to implement the method with an auto-reaction method of send mail.
It is working fine but it doesn't repeat the alert! Let's say, imagine that the RFC isn't working since 3am... we are now at 13pm and the alert is not triggered anymore. In fact, in RZ20 I just see 1 Alert triggered at 3am.
Is there any way to set this alert to trigger every period of time?
thanks.
regards,
Filipe Vasconcelos

Hello,
first it would be good to clarify which monitor are you implementing - there are multiple RFC monitors - for example:
Availability and Performance Overview Monitor :
http://help.sap.com/saphelp_nw70/Helpdata/en/ae/cd823bd26a5c42e10000000a114084/frameset.htm
Transactional RFC and Queued RFC Monitor
http://help.sap.com/saphelp_nw70/Helpdata/en/8b/ceea3b31aac554e10000000a114084/frameset.htm
Best to type the name of monitor as displayed in RZ20.
Based on the type of monitor you might find the answer here:
http://help.sap.com/saphelp_nw70/Helpdata/en/f6/c55c3bab977239e10000000a114084/frameset.htm
(for example for status monitor you can set option "When should a message trigger an alert?" to "Always (at every message)")
Anyway I am afraid that in case you are using performance monitor there is not much you can do. Possibility can be to check if data collection method (for example function) has parameter that can do this (but I am skeptical about this) - if not then you would have to adjust data collection method or implement the monitoring in another way.
Possibility can be to use some kind of "switch". You can activate option "Display All-Clears in Alert Browser" - this will generate green alerts. Then you can program your own autoreaction method that will perform the "switch operation" (simple insert/update/delete into some Z-table you will create - based on status of alert - red/yellow/green.) Then you can have batch job running another Z-program that is reading this value and constantly reminding use via email.
If you program this in a good way (abstract autoreaction method) - you can reuse this solution for other monitors as well and easily buid you own email notification functionality.
I hope it helps.
Best regards.

RFC MONITOR

Hi
When from a SAP/R3 system I call a BAPI program using the transaction SE37 to SAP XI and the awnser is correct, I can not see in the monitoring transaction (sxmb_moni) of XI the message I sent, but when the execution fail I can.
Can someone tell me why?
And how can I see in the transaction IDX5 the rfc messages?
Regards

Hi Gerardo
try this:
Displaying Inbound and Outbound Messages
Choose this option if you want to determine which XML messages entered or exited the RFC adapter according to particular selection criteria. Proceed as follows:
       1.      Choose RFC Monitor.
       2.      Select XML messages by specifying a time and date the messages were created, or enter a specific message GUID to determine a specific message to be selected.
       3.      Choose Inbound and Outbound in the group box RFC (default).
       4.      Specify your selection criteria in the group box RFC.
Selection Criteria:
Selection Criterion
Entry
Transaction ID
Transaction ID in RFC adapter
System ID
Name of sender or receiver SAP component (for example, BCE)
RFC Destination
Logical destination of original RFC call from sender
Function module
Name of function module called
Client
Client in sender or receiver SAP component
       5.      Choose Execute.
The system sorts and lists the XML messages according to the time that they were created. Messages that were routed through as RFC calls are listed together and are identified by the same message ID (GUID).
Besides the specified selection criteria, the system also displays the function calls for each LUW (Logical Unit of Work).
It is extracted from http://help.sap.com/saphelp_xi20sr1/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
Good luck!

RFC monitoring in CCMS if the patch level    R/3 release 4.6C ?

Hi all,
FOr RFC monitoring is possible in CCMS if the patch level   R/3 release 4.6C ?
    ST-PI 2005_1_46C
    ST-A/PI 01M_R3_46C
    SAP_NOTES 46C
    SAP_HR 46C
    SAP_BASIS 46C
    SAP_APPL 46C
    SAP_ABA 46C
Please let me know the requirements for configuration?
Regards,
Neni

Hello Neni,
It certainly seems possible to Monitor RFCs in relearse R/3 4.6C for tRRCs and qRFCs.
Check your CCMS setup guide
You can
1. Start TX RZ20.
2. Open monitor collection SAP CCMS Monitor Templates.
3. Open the Communications monitor.
4. Choose Extras -> Maintenance functions on.
5. Mark the MTE 'Transactional RFC and Queued RFC'.
There you can edit your hosts.
You can restart the Monitor immdiately with transaction RZ2.
Hope this is helpful.
Regards,
Paul

Transactional RFC Monitoring

hi all,
   Can anyone explain to me how transactional RFC works? As what i've understand it, the first transaction to get in is the first to be executed right?
   Here's my scenario. I always monitors the transactional RFC,and from time to time, I observe irregularities. For example, at arround 9:00 am, bunch of transactions are displayed and the status are "status recorded". By 11:00 am, transactions are added again but this time one of the status of transactions timed 11:00am is "status executing" even if there are still remaining transactions that are recorded by 9:00 am. The way i understand it, the "first in" "first out" here was not applied.
   Could anyone clear this? am i right about the "first-in first-out" scenario? if yes, how can i correct tmy problem? If not, can you explain??
Your response is highly appreciated.
cheers,
Jay

Hi Jay,
As given in the RFC adapter help
Transactional RFC calls (tRFCs) in messages with quality of service Exactly Once (EO)
The tRFC in SAP sense means:
This scenario is suitable if the data being sent is not interrelated. A calling application (or client) in system 1 uses a tRFC connection to a called application (or server) in system 2. In this scenario, the data is transferred using tRFC. This means that each function module sent to the target system is guaranteed to be processed once. The order in which the function modules are executed, and the time they are executed, cannot be determined. If a transfer error occurs, a background job is scheduled that resends the function module after a defined period of time.
What you are talking abt is EOIO. As per the RFc adapter help, it supports:
Transactional RFC calls (tRFCs) in messages with quality of service Exactly Once (EO)
The receiver RFC adapter can also process messages with quality of service Exactly Once In Order (EOIO). They are mapped to transactional RFC calls (tRFC).
Hope this is of some help.
Regards
Vijaya

RFC Monitoring using CCMS

Hi All,
We need to configure RFC availablity Monitoring in CCMS of our Solman system for our PRD satellite system.
In PRD, We have created data collection method Z_CCMS_RFCDest_Availability_Trex which is using SALK_RFCDEST_AVAILABILITY as function module,
Parameters in collection method are :
COLL_METHOD            Z_CCMS_RFCDest_Availability_Trex
RFC_DEST                   TREX_ES3_NWPRFI
MTE_CLASS                Availability_RFC_Destinations_MA_Clas
CCMS agents are running fine in Solman and PRD. Now I expect that in Solman->rz20->PRD I should get Node like:
PRD\Availability\...\RFC-Destinations\TREX_ES3_NWPRFI
But I do not see any node there, It is blank screen on rz20 of this system.
Please suggest what I am missing to complete the configuration part.
Regards,
Shivam Mittal

Thanks Gary,
I haven't seen this no where would I find it. Had a quick look on the market place and can't find it!
Chris
Just to add were using Netweaver 2004s
Message was edited by:
        Chris Soden

Monitoring of RFC Connections

Hi Folks,
is there any option to monitor a TCP/IP RFC connection.
I need something like a heartbeat on a registered program connection.
Something like GRMG for http, just working for RFC.
Is there any standard way to do this or do I need to use OS level tools?
Thanks,
Bastian
Edited by: Bastian Schneider on Jul 3, 2008 9:15 PM

Hi
Please check this note for RFC monitoring
Note 1069130 - RFC Destination Monitoring: Separate Method for Each Dest.
And check for this link for Email configuration
/docs/DOC-8701#section12
Configuring the Sending of E-Mails as an Auto-Reaction

Daily Monitoring of PRD of BI, XI, ECC, through Solution manager

Dear all ,
I have only configured Earlywatch alert for BI , ECC 6.0 on Solman(every week monday i got EWA report and I have taken action as per the EWA report).
Now my question are ,
Daily Monitoring of PRD of BI, XI, and ECC is possible ?
Weekly Monitoring of DEV & QAS of BI, XI, ECC, ?
EWA for XI is possible ?
Finally how can i completely use Solman server for monitoring ,etc....
Kindly advise
Regards

Hello,
Daily Monitoring of PRD of BI, XI, and ECC is possible ?
Of course possible, what kind of monitoring are you looking for?
Using the System administration functionality you can perform the pro-active monitoring, which will also trigger auto reaction methods whenever the thresholds are reached, as per the setup performed.
There are SAP standard parameter monitoring available, in addition you can define your own parameters to be monitored in the System administration workcenter functionality.
Weekly Monitoring of DEV & QAS of BI, XI, ECC, ?
You can use the central system monitoring functionality which enables you to perform monitoring tasks as per the period/frequency specified.
You can also input your/teams monitoring notes/observations and generate it as a separate report.
EWA for XI is possible ?
It is possible; for ABAP stack, perform the same steps as you performed for other ABAP (ECC) systems, for Java stack of XI, configure the Solution Manager Diagnostics which will trigger the EWA for Java part. Finally you receive a consolidated (ABAP+Java) EWA next Monday.
Finally how can i completely use Solman server for monitoring ,etc....
EWA, SLR provide you with a reporting functionality which again is a result of monitoring your system over the previous week.
Using System administration and Central system monitoring you can leverage the monitoring capabilities.
Using SMD, Wily you can extend the monitoring of Java and dual stack systems
Using BPMon you can attain the Business process monitoring.
In addition, in the work center you can see additional monitoring options, like. RFC monitoring.
Hope this helps.

How to determine:how many connections will be needed in RFC adapter setting

Hi XI guru,
We are working on following secnario:
1. JDBC sender selects data from Oracle database, and send this data to SAP XI, XI use async RFC receiver adapter to call a self made RFC, in this RFC, we will call some BAPI and process some ABAP code, then if the reture code is ok, nothing will happen( means data successfully import into SAP ). if the reture code is not ok, another RFC will be called from ABAP code, send an asyn message to XI, XI use RFC receiver to update the message back to Oracle with specific flag.
2. Why we use this secnario is, we want to avoid using BPM, this scenario are mass happening in our project, BPM will slow down the performance.
3. We also don't want to use sync RFC, because BAPI and ABAP code will take sometime to run, we don;t want XI want for the RFC reture message.
The question is:
We successfully run this secnario in unit testing, but when we work on stress testing,found some times we will miss the RFC call. For example:JDBC sender sends message to XI for 10 times in a very short time( we use fault data to make every message has a send back RFC message in stress testing), let's say poll interval 5 sec one time. but send back RFC only be called 7 or 8 times, 2-3 message were missing.
we get back to SXMB_MONI, see all JDBC sender 10 message are successful, and 7- 8 send back RFC messages also successful. No log in SM58 RFC monitor. Then we go to modify maximum connection, and set it to 5, means 5 RFC coconnection possible(as far as I know, this setting means like this, but of course I maybe wrong)
Question is: how can I know how many coconnections I need to setup, and if some RFC calls are missing, is there any place whatever in XI or R/3 can help me to monitor the log, then I can know they are not successful for some reasons,but not just simply miss as they never happened?
That will be helpful, if some one can tell the story of what happen RFC works at background.
Thank you very much for your time and effort on this

HI,
Maximum possible number of initial connections required between sender system and adapter. This value is limited internally to a maximum of 50
See the below links
http://help.sap.com/saphelp_nw2004s/helpdata/en/67/6d0540ba5ee569e10000000a155106/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/33/c6e63b60c25767e10000000a11402f/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/a4/db833d4c47ea4ea1a9b7af3c535ff2/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/6e/3f560a3e0f6f4a90fb1e7db1388d4d/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/25/90d038f58f863de10000000a11402f/frameset.htm
/people/swaroopa.vishwanath/blog/2005/03/11/rfc-migration-to-bapi-in-r3--step-by-step
Regards
Chilla

External RFC problem in BPM

Hi All,
i have configured External RFC monitoring using application monitor in BPM.
the problem is the max wait time given in setup is upto 25 seconds only. i have given the maximum.
the response time in operations that i am getting is 150 milliseconds maximum which is around .5 or so seconds.
but the RFC in which connection test is successful is getting red alert.
can any one pls let me know what exactly is the configuration am missing out.
Thanks,
Subhashini.

Hi
I am monitoring TRansactional RFC.
I was interested to know the type of the RFC used(from SM59), for example T, 3, I,G etc. Please let us know the RFC used and type and importantly systems involved to drill further.
Please check the following:
1) Logical component assignment against that step.
2) Existence of RFC on satellite system.
3) Connection test and Jumpin to that host.
4) The Read RFC you are using has got enough authorizations on that Satellite system.
Regards,
Jagan

Regarding BW precalculation server monitoring

Hi Experts, we have BW precalculation server configured in pur NW2004s BW system. My requirement is if i can monitor RSPRECADMIN using Solution manager. Like if precalc server goes down it should generate an alert.
Any inputs on the above would be much appreciated.
Thanks Amber S

As indicated [earlier here in SDN|How to monitor Bi Precalculation?;,there is no MTE for monitoring Precalc. The work-around is to monitor the BI RFC PREC_<SID>. This provides a better end-to-end check than simply checking the Windows service on the Precalc server. Rather than monitor the RFC on the remote system, I simply created a duplicate of the RFC on the Solution Manager system, and monitored that.
See [Monitoring Availability of Services|http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/70531389-0c01-0010-2a95-c019524764ae] (PDF) for a description of RFC monitoring.
Also, here are some notes on data collection method CCMS_RFCDest_Availability_Col:
SAP Note:0570083 CCMS: RFC Destination Monitoring does not work
SAP Note:0771455 CCMS: Incorrect MTE Class in RFC Destination Monitoring
SAP Note:0696194 CCMS: MTE class specification in SALK_RFCDEST_AVAILABILITY
SAP Note:0762183 Monitoring the SAP SCM optimizer in CCMS (RZ20)
SAP Note:1069130 RFC Destination Monitoring: Separate Method for Each Dest.
SAP Note:1439088 CCMSPING: ccms_ni_ping_collect Does Not Work / Router
Regards,
Sean

Central System Administration - Monitoring question

We are trying to setup the Central System Administration/Monitoring in solution manager. However, when we go into the setup of the tasks, such as "Checking for ABAP Short Dumps", when we click on the "Start ST22" button, it doesn't do anything.
Has anyone had an experience with figuring out how to get those buttons to work and to connect directly into the system we are doing the task?
We did follow Note 128447 to setup the Trusted RFC's between the systems, but that doesn't seem to working correctly either. Could that be the reason that this isn't working correctly?
Thanks in advance for any replies.
Dale Dingmann

Hi,
May I know how did you configure your CEN monitoring, using agents, or using RFC.
And where you are checking the ABAP dumps on Workcenter?? will you able to get the other details like Job failure, if you click that, wil you able to reach the satellite system.
and check below are available.
SM_<SID>CLNT100_READ
SM_<SID>CLNT100_TWM
SM_<SID>CLNT100_TRUSTED
if you use RFC monitoring these 2 also required,
<SID of the monitored_system>_RZ20_COLLECT
<SID of the monitored system>_RZ20_ANALYZE
Thanks,
Jansi

What are the importent transaction codes in edi

what are the importent transaction codes in edi

hi,
=>sale - ALE Customizing
=>bale - Distribution Administration (ALE)
=>wedi - IDOC Type and EDI Basis
=>shdb - BDC (Transaction Recorder)
=>lsmw - LSMW
=>bapi - BAPI
=>spau - Display Modified DE Objects
=>spdd - Display Modified DDIC Objects
=>sara - central idoc archiving
=>stms - Transport Management System
=>wedi - IDOC Type and EDI Basis (IDOC Configuration)
=>bd21 - Analyze change pointers - create IDOC from change pointer
=>bd10 - Send Material Master
=>bd12 - Send Customer Master
=>bd14 - Send Vendor Master
=>bd50 - Activate Change Pointer for Message Type
=>bd55 - Conversion rule user exit (Link conversion rule user exit to the different system \ partner combinations)
=>bd54 - Maintain Logical Systems
=>bd71 - Distribute Customer Model
=>bd87 - Process Inbound IDOCs
=>bd88 - Process Outbound IDOCs
=>bdm2 - Cross-system IDOC Reporting
=>bdm7 - ALE Audit - statistical analyses
=>bdm8 - ALE Audit - sending confirmations
=>bd61 - Activate Change Pointer generally
=>bmv0 - Direct Input Data Transfer Administration
=>rz04 - Operation Mode
=>rz12 - RFC Server Group Maintenance
=>sar3 - Archiving object customizing
=>s001 - SAPoffice Inbox
=>s010 - Standards Texts (SAP Script)
=>se01 - Transport Organizer (Extended View - Performing and managing the transport of development object across different systems)
=>se09 - Transport (Workbench) Organizer (Controlling and keeping track of Development work and Development Objects)
=>se78 - Administration of Form Graphics (Import Graphics into SAP System)
=>se84 - ABAP Repository Information (search for SAP objects)
=>su01 - User Maintenance (Security)
=>su02 - Maintain Authorization Profiles
=>su03 - Maintain Authorizations
=>sm36 - Background Job Scheduling
=>sm37 - Background Job Monitoring (display batch jobs)
=>sm31 - Table Maintenance
=>sm30 - Calling View Maintenance
=>sm35 - Batch Input Monitoring (Error Logs)
=>sm50 - Process Overview
=>sm58 - Transactional RFC Monitoring
=>sm59 - Maintain RFC Destinations (Define RFC Configuration)
=>snro - Number Range Objects (for IDOCs)
=>we02 - Display IDOC
=>we05 - IDOC lists
=>we07 - IDOC statistics
=>we12 - Inbound processing of outbound file - convert outbound to inbound file
=>we14 - Process (dispatch) IDOCs through Port - RSEOUT00
=>we15 - Outbound IDOC from NAST - message control
=>we16 - Inbound File
=>we18 - Generate status file
=>we19 - Test tool
=>we20 - Add new Message Type to Partner Profile
=>we21 - Maintain Port Definition
=>we30 - IDOC Type development
=>we31 - IDOC Segment development
=>we41 - Process Code Outbound
=>we42 - Process Code Inbound
=>we46 - IDoc Administration
=>we47 - Status Code Maintenance
=>we57 - Assign function module to logical message and IDoc type
=>we63 - IDOC Type for Parser Output
=>we82 - Assign IDOC to Message Type
=>we60 - IDOC Documentation - IDOC Types
=>we61 - IDOC Documentation - IDOC Record Types
=>we81 - Create new IDOC Message Types
=>we82 - Assign IDOC to Message Type
=>pa20 - Display HR Master Data
=>pa30 - Maintain HR Master Data
=>bd59 - Create and assign Filter Object Type for Message Type
=>bd64 - Maintenance of ALE or any other Distribution Model
Hope this helps, Do reward.

IDOC Status, Tracking in SAP PI/PO Single Stack

Hi All,
My PO version: 7.4, SP4. I am not sure my questions below are still a limitation in current PI/PO single stack systems, and hence requesting your help for the same.
1) Is there a way we can track outbound idocs in SAP PI/PO single stack similar to PI abap stack IDX5? ( Note:- I couldn't find any option in IDOC monitoring in single stack SAP PO 7.4, SP4)
2) IDOC status is always 0 in SAP PO 7.4 single stack IDOC monitoring. I am not sure if this status is just specific to my PO system. Any setting needs to be applied?
ps: Please post only relevant answers/solutions
Thanks,
Praveen Gujjeti
Message was edited by: Praveen Gujjeti

Hi All,
As per SAP help: Comparison of IDoc Adapter (IE) and IDoc Adapter (AAE) - SAP NetWeaver PI Reference Documentation - SAP Library idoc status and tracking not supported in current PO versions. May be SAP will add this feature in upcoming PO versions
Auditing, Monitoring ,and Tracing Functions
Attribute/Feature
IDoc Adapter (IE)
IDoc Adapter (AAE)
ALE Audit
Supported
Supported
IDoc tracing
Supported (transaction IDX5)
Not supported
IDoc monitoring
Transaction IDX5
Integration with channel monitor and message monitor (as part of Advanced Adapter Engine monitor)
Status tracking -SYSTAT
(analysis and further processing of messages that have not been processed)
Not supported
Not supported
RFC monitoring
Supported
Not supported
Message persistence in the IDoc adapter
Supported
Message correlation information can be stored in IDoc adapter.
Not supported.
Message is persisted in messaging system with correlation data persisted in adapter.
Regards,
Praveen Gujjeti

RFC monitoring

Similar Messages

Maybe you are looking for