Monitor RFC Destinations

Hi guys,
Couldn't find a way simply monitor RFC destinations with CCMS monitor. Specifically, I've RFC destination type T (http)
can't find a way to monitor it.
Please advice,
Dimitry

Hi
        Availability can be implemented using the RFC availability check for specific RFC destinations.
        Monitoring of specific and critical RFC destinations can be done by using the standard CCMS MTE
        class CCMS_RFCDest_Availability_Col
        Using the methods described above, alerts can be generated in the CCMS monitoring transactions
As specified above note 1069130 will help you in achieving it.
Thanks
Amit

Similar Messages

  • ** End-to-End Monitoring - RFC destination error while save config in RWB

    Hi Friends,
    We have 2 RFC destinations in our XI server. 1) PMI<client>001 2) PMI<client><client>800. First one is for XI server. Next one is for Sender/Receiver System.
    We want to activate End-to-End Monitoring in RWB. For this, when I save configuration, it throws the following error.
    Incorrect RFC Destinations: When the configuration is saved, an RFC destination is created on the monitoring server for each XI component to enable end-to-end monitoring of the respective XI component. However, the test call failed for the destinations listed. Therefore, you must check the call and the authorization on the monitoring server for the destinations concerned, by using transaction SM59. Also check whether RFC user used for the destination is maintained in the relevant XI component. Note that a component can only be monitored when its RFC destination is maintained correctly.
    I have checked the user in the above destinations. For the first destination, we have assigned PIRWBUSER of XI system. Test Connection is OK, but unable to login remote. At the same time, PIRWBUSER is not locked.
    For the second destination, I have assigned some login user of sender/receiver system. Test connection is OK. Able to login remotely.
    There is no RFC user in our XI system. (I tried using RFCUSER* thru SU01 tcode).
    There is no PIRWBUSER in the Sender/Receiver System.
    In RWB, Configuration, 3 components are there. 1) XIIntegrationServer 2) Business System (for Sender/Receiver System) 3) XI Adapter Framework. I selected last two. (First one is already selected). Monitoring Level : Medium (for all 3). Send and Receive Check box is selcted for the last two.
    So, what could be the problem for the above error?
    Could you kindly clarifiy friends.
    Thanking you
    Kind Regards,
    Jeg P.

    Hi friends,
    I have one RFC Destination PMI<sysid>001. (Abap Connction) in my XI system. This destination is for  XI server. Connection Test is OK. Remote Logon by using the PIRWBUSER is also ok.
    In the 'Configuration' tab of the Runtime Workbench, when we select 'Save Configuration', (Business System and Adapter Framework is not activated) with the default activation for XI Integration Server, the system throws the following error.
    Incorrect RFC Destinations: When the configuration is saved, an RFC destination is created on the monitoring server for each XI component to enable end-to-end monitoring of the respective XI component. However, the test call failed for the destinations listed. Therefore, you must check the call and the authorization on the monitoring server for the destinations concerned, by using transaction SM59. Also check whether RFC user used for the destination is maintained in the relevant XI component. Note that a component can only be monitored when its RFC destination is maintained correctly.
    When we save configuration, an one more destination is automatically created in the name as below.
    PMI<sysid>001<yyyymmdd>. For Example, PMIPID00120080207. 
    When we test  newly created RFC destination, connection is OK, but not able to remot login using the same user PIRWBUSER.
    The difference between old and new RFC destination, in old, we have selected Load Balancing is 'Yes', but in the new it is 'No'. The system also tells the error below.
    Name or Password is incorrect (repeat logon) - PMIPID00120080207
    But, still remote login is possible in the old RFC destination using the PIRWBUSER.
    So, What could be the problem ...?
    Kindly reply, friends.

  • Creating RFC Destination in SAP R/3

    Trying to create an RFC destination in SAP R/3.  Looked at few articles in creating them, but I am getting error while testing.  It says that the "Program" couldn't not be found.  I tried with all options, "Registered in Server Program", "Start on Application Server" etc.,
    Is there a place to register a "Program"?  Is this program specific to my XI server?  How should this program be created or registered.
    Any help is greatly appreciated!
    Thanks
    Satya

    one more hit:
    http://server:port/rwb/index.jsp
    message monitoring
    BTW
    you have created everything in XI repository & configured everything in xi directory haven't you?
    if not you can try this document:
    "Validating a Connection Between R/3 and SAP XI with RFC"
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/validating a connection between sap r3 and sap xi with rfc.pdf
    by Sridhar Rajan Natarajan
    Regards,
    michal
    Message was edited by: Michal Krawczyk

  • Transaction IDX1: Port SAPPRD, client , RFC destination contain errors

    Hi all,
    when I send an IDOC from Xi to R/3 I get the following message in XI monitoring:
    Transaction IDX1: Port SAPPRD, client , RFC destination contain errors
    ERROR= 2:IDOC_ADAPTER(151)
    However everything is maintained correctly (i think) in IDX1. I can upload the IDOC metadata with IDX2 from the R/3 system.
    I seems that Xi doesn't have the clientnumber available. (should be 600) but is not mentioned in the error.
    Did I miss something?
    Thanx Ron
    Message was edited by: Ron van der Sterren

    Hi Ron,
      Settings in XI side.
      1. Create the RFC Destination(SM59) with connection type 3, pass the target host pass is R/3 server name and logon tab enter the R/3 logon details.
      Test the connection is success and check the Remote login button it's connecting the R/3 system or not.
      2. Create the Port IDX1 and pass the client number is (R/3 client) and pass the RFC destination which you created above.
    R/3 side
       1. Create the RFC Destination(SM59) with connection type 3, pass the target host pass is XI server name and logon tab enter the XI logon details.
      Test the connection is success and check the Remote login button it's connecting the XI system or not.
      2. Create the TRFC port to transfer the IDOC'S and pass the RFC destination which you created above.
      3. create the logical system in BD54 this name should be same as XI logical system name.
      4. Create the partner profile (WE20) and partner type is 'LS' with inbound parameters and pas the appropriate values.
      Let me know if you have any issues.
    Regards,
    venu.

  • Alert on locked users in RFC Destinations

    Hi,
    I have setup availability of RFC Destinations but also need to monitor the user in the destination. We need to know if the user is locked or not. Any idea how I need to do this ?
    Thanks,
    Ann

    Hi Ann,
    the same can view in RZ20 ccms monitor templates-> availablity and performance overview ->availablity-> Rfc destinations.
    to assign the rfc destinatiion define the method in RZ21->method definition->choose CCMS_RFCDest_Availability_Col(availability of RFC destinations)->set RFC destination to parameter RFC_DEST, if you want to define more rfcs can define as new colloum.
    [Note 1069130 - RFC Destination Monitoring: |https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1069130]
    check the posiblities.
    Jansi

  • CCMS aler for RFC destinations availability

    Hi Experts,
    We have configured ccms alert autoreaction method for availability of RFC destinations.
    alert is configured with yellow thershold as 10% and red threshold as 5%.
    alert text is :&1 &3 < &2 &3  15 min. avg. value below threshold value (&4 measurements)".
    We are receiving mail alerts for CCMS red alert for RFC saying" 0 % < 5 %  15 min. avg. value below threshold value (1 measurements) ".
    But when we checked the corresponding RFC is working fine.
    Can anyone please explain how this RFCs destinations check alert will work and what is the meaning of alert text ":&1 &3 < &2 &3  15 min. avg. value below threshold value (&4 measurements)"."
    Thank you,
    Kavitha

    Hi
    I have done
    1. RFC connection from x to y and y to x
    In X system:
    1. In transaction RZ21, mark Method definitions, and choose Display overview
    Copyed standard CCMS_RFCDest_Availability_Col method definition to ZCCMS_RFCDest_Availability_Col
    Parameters tab
    For x
    Parameter name = RFC_DEST
    value = SM_XCLNT510_TRUSTED
    Parameter name1 = COLL_METHOD
    value = ZCCMS_RFCDest_Availability_Col
    Same in Y but for RFC_DEST give
    Parameter name = RFC_DEST
    value = SM_YCLNT100_TRUSTED
    Execution Tab
    Type of call = Function module
    Call SALK = SALK_RFCDEST_AVAILABILITY
    Execute method on = The local server of the MTE to be processed
    Execute method for = Individual MTE
    Control tab :
    Execute method for = Individual MTE
    Execute method = periodically in dialog process (short-running program)
    Startup method = Execute method immediately after monitoring segment start
    Execution location
    of startup method = Only on the central instance
    Start Tab:
    Execute method = Data Collection Method
    also try in so many way as in :Parameter Tab:
    RFC_DEST               SM_XCLNT510_TRUSTED
    COLL_METHOD            ZCCMS_RFCDest_Availability_Col
    MTE_CLASS              Availability_RFC_Destinations
    MTE_CLASS              CCMS_RFCDest_Availability_MO_Class
    MTE_CLASS              CCMS_RFCDest_Availability_Col
    COLL_METHOD            CCMS_RFCDest_Availability_Col
    RFC_DEST               CCMS_RFCDest_Availability_Col
    Problem:
    I am not able to  Reset the segment in WARMUP status
    not able to find the node in RZ20
    Regards,
    Neni

  • Monitoring RFCs on Remote Systems

    Hi,
    I am attempting to convert our CCMS monitoring to a central instance on solman. One of the things we monitor in the PRD system is availability of two RFC destinations.
    I am unable to figure out how these can be monitored from solution manager as a central system. When I set these up in solman under availability monitoring, it appears that solman is expecting these RFC destinations to be local to solman, rather than on the PRD system.
    How can I get solman to monitor the RFC on PRD? It does not appear that the RFC availability monitoring method allows you to specify which system the RFC resides on.
    Thanks much,
    Chris.

    Hi,
    ok I will try to explain how get to see the MTE's of ur PRD system.
    1.   TA: RZ20
    2.   change in maintenance mode (Extras -> Activate Maintenance Mode)
    3.   now u r able to create a new monitor set. So please do this by clicking on the create button.
    3.2 place a describing name and select who should be able to see this set. Click OK and now u will see ur new own monitor set
    4.   Click one time on that set and click one more time on the create button. Now u will get an list with all monitored Systems, that are connected to the solution Manager. Search in the PRD System the MTE u like to see and save ur new monitor with an discribing name.
    5. Hopefully if I'm forgottin' nothin u will see after save and activate ur objects from the managed System in the CEN System.
    So if anything is missing feel fre and contact me ...
    br Lars

  • An RFC destination could not be specified for the logical system

    Hello Experts,
    I am trying post goods receipt in EWM system in a simple inbound delivery process. It is not getting posted back in ECC. I have my RFC connection setup properly(I assume since I was able to transfer inbound delivery to EWM in first place).It seems some setting related to Outbound queue in EWM is missing.Can anyone tell me in detail what settings are required?Is it something to do with WE20 transaction?I am not sure what settings should be done there.The error log is as below-
    An RFC destination could not be specified for the logical system
    SB3CLNT011
    Message No. B1550
    Diagnosis
    An RFC destination should be specified for the logical system SB3CLNT011.
    This could not be done in this case. SB3CLNT011 is not your local logical system
    and this system is not included in the relevant Customizing tables.
    Procedure
    Check:
    RFC
    destination
    Port
    definitions
    oubound partner profile of
    message type SYNCH for this logical system
    Regards,
    Khushboo

    Hi Oritra and Suraj,
    I have checked remote connection in SM59 for both the logical system.It works fine.I understand this is more of a technical issue,but I don't have A local basis team to help me so reaching out to experts here.Can you guide me what technical settings could be checked for EWM-->ECC connection?When I execute BD82 for SB3CLNT011 it shows me green status with message "No messages have been defined for the selection conditions in the model".
    Although when I do this for EWM logical system SB3CLNT012 it shows me this with all green status-
    System SB3CLNT011 as a partner type already exists
    System SB3CLNT012 as a partner type already exists
    Port A000000018 with RFC destination SB3CLNT011 already exists
    Outbound parameters for message type SHP_IBDLV_CHANGE SHP_IBDLV_CHANGE01 already
    Outbound parameters for message type SHP_IBDLV_SAVE_REPLICA SHP_IBDLV_SAVE_REPLI
    Outbound parameters for message type SYNCH SYNCHRON already exist
    Am I missing something in WE20?
    Regards,
    Khushboo

  • Logical system and rfc destination

    hello all,
    what is the difference between logical system and RFC destination?
    thanks for ur help in advance.
    regards,
    vikas

    Hi,
    In any ALE scenario u need one sender and one receiver system.
    Logical systems are just logical representation of these systems but in case of RFC destination u specify technical parameters for those systems like IP address and username and password to connect to that system.
    Thus when u create port i.e.we21 u specify actual RFC destination for the system to which u want to connect and when u create partner profile for that logical system u specify this port so when u want to send data to this logical system i.e receiver system port will be used which in turn has RFC destination which will be used to connect to that system.
    In simple terms logical systems are logical representation of any system and RFC destinations are physical/techinical systems.
    Regards

  • Logical system and rfc destination related Query?

    Hi Dudes
    Do we need to define logical system and RFC destination if they are in different clients in same server
    Regards
    Raj Kumar

    Hi
    Both are client independent setting, so even if you define in one client, it would be available in other clients also.
    Regards,
    Sanjeev

  • RFC Destination Connection Pool requirement

    Hi Experts,
    I have a custom webdynpro java application to display number of work items pertaining to that particular user in a backend.
    There are users who dont use this functionality as well. But the requirement is to place this application in home screen.
    I have used both metadata and modeldata with hard coded user since we did not want error messages to appear for users who do not have backend access.
    Application & Access Details
    Application Location : Home Screen
    Concurrent Users     : 600 concurrent users maximum possible value
    Connection Usage    : Close connection immediately using disconnectIfAlive() method.
    Now I need to configure JCO Pool Size , Max Connections, Wait Time for the RFC destination.
    I have read a lot of post and documents but could not acheive clarity of thought on this.
    Kindly let me know what values I should give in these fields for optimal performance and no connection issue for users.
    Regards,
    Porselvan

    Hi Muthavudaiyan,
    Hope you are doing good.
    Basically from the JCo perspective, there are only 5 parameters that are involved here:
    jco.destination.pool_capacity:
    Maximum number of connections that are held open in the pool for reuse (default: 1)
    jco.destination.peak_limit:
    Maximum number of connections that can be obtained from a pool at peak usage times
    jco.destination.max_get_client_time:
    Maximum time to wait for a free connection if the peak limit is reached before exception is thrown
    jco.destination.expiration_time:
    Timeout period after which pooled idle connections can be closed (default: 600000ms = 10mins)
    jco.destination.expiration_check_period:
    Regular time interval for checking if pooled connections have expired and will be closed
    The values are determined by the application in question. The ideal values have to told to you by the application developer; there are no two ways about this.
    Thank you and have a nice day :).
    Kind Regards,
    Hemanth

  • Service desk RFC destination in the Satellite system

    HI All,
          can any body tell me the RFC destination that is to be maintianed in the satellite system so that the message reaches the solution manager service desk.
    I am creating messages they are being send to the service desk successfully but are not visible when I go into the service desk of the solution.
    But they are visible through the transaction code CRM_DNO_MONITOR .Can any body help the RFC destination to be maintaned in the BCOS_CUST table so that the message reaches the Service Desk.]
    Currently I am using the RFC destination to the service desk client in the solution manager ie SIDCLNT200
    Thanks in advance
    Regards
    Amit

    Hi Amit,
    I think your expectation is not correct. I understood, you can create a message in a satellite system and you can see the ticket in SolMan service desk. Then everything is configured correct. What you are now looking for is to see the ticket in a solution when the sat. system is part of the solution. This is not working. If you create out of a solution a service desk ticket, these ticket get a special attribute that they belong to this solution, all other tickets can not be selected by a solution.
    Sorry but I am quite sure that it is working like this.
    There is only one option, that you define special variants so you can see only tickets from special systems, but these variants can not be assigned to a solution.
    Regards,
    uDo

  • How to create a RFC destination for extracting data to HANA

    Hello All,
    Could someone help me in providing a document or note on how to create a RFC destination for extracting data from SAP data source to HANA using SAP LT replication server ?
    I am able to create a data base connection while transforming data from non SAP data source,but wasnt able to transform data which is from SAP abap tables .

    Hi Venkatesh,
    In SM59 t.code we create RFC destinations.
    Go thru the video link for creating RFC destinations step by step
    How to setup a trusted RFC connection between SAP systems: a step-by-step guide - YouTube

  • Unable to change RFC destination in IT Performance reporting wizard

    Hi Experts,
    I am setting up IT Performance Reporting in my Solman EHP1 system. In the first page of the PErformance reporting wizard, it asked me for RFC destination from BI to Solman(1st field) and Solman to BI (2nd field). I initially entered an existing RFC destination that we are already using in a separate application that has a user with very-limited authorization. Now, I am trying to change the RFC destination by running the same "Configure IT Performance Reporting" wizard but both fields are already GREYED out.
    I tried deleting the RFC destination previously defined in an attempt to reenable the fields but only the 2nd field was enabled. When I try to continue the setup, it results into a Shortdump because it is still looking for the initially defined RFC dest which is defined in the 1st field that cannot be edited.
    SAP has not yet provided us with a solution.Your help is greatly appreciated.
    Thank you very much.

    You canprovide the RFC destination in DOE administration portal. Goto Configurations link and search for "BACKEND DESTINATION" parameter in "BACKEND CONFIGURATION" link. Here you can provide RFC destination at SWCV level or at Data object level.
    After deleting RFC destination in SM59, it will never take you to backend system.

  • Communication failure : RFC Destination SALV_WD_EXPORT_PDF does not exist

    Hi Experts,
    I have one standard ALV report in ABAP Webdynpro.
    When i try to print the ALV Report it gives Communication failure : RFC Destination SALV_WD_EXPORT_PDF does not exist.
    Can you give solution for this one.
    Regards,
    Sri

    Hi Sri
    Please go through this..
    /people/bv.pillai/blog/2007/01/09/webdynpro-abap-alv-print-versionpdf
    also Have a look this note SAP NOTE 918236; you will need help from basis.
    Cheers,
    Kris.

Maybe you are looking for