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

Similar Messages

Monitoring of remote system's Transactional RFC and Queued RFC

Hello,
In our production system, in rz20- CCMS monitor templates- Communication-Transactional RFC and Queued RFc- outbound queues- Queues otherwise not monitored we can see blocked queues for each client.
System is connected to solution manager and we wish the central auto reaction is implemented in solution manager
However i am unable to find Transactional RFC and Queued RFC for the remote system, they exist only for solution manager itself
Tell me how can i do the central monitoring

Hello,
First you need to check with your Landscape in solman in order to monitor any kind of activities to do so pls follow these steps.
Go to SMSY in solman under Landscape components>Product systemsselect you satellite system example SAP ECC.
On the main screen you will find client for which you have generated RFC connection. Please check though connection are working fine, Go to edit mode and try to click on generate button there will be a pop-up, which gives a clear picture of RFC connection which already exists, and you can also re-generate this RFC connection by clean it up when you re-generate pls select under Actions after generation assign RFC dest for system monitoring.
But make sure there is no project impact on this RFC, like they are not using any logical components and already have some projects running on this RFC connection.
I would advise you to first you the option of assign and check RFC button which is next to generate icon.
Regards
JUDE

Remote system monitoring entry- data not relayed to Central system

Hello Folks,
I am trying to establish a central monitoring system for our client. I am trying to test it in the DEV environment first.
The central system is a Solution manager system (Dual stack- ABAPJAVA). I am trying to bring in monitoring data from the ECC development environment (ABAPJAVA).
First of, i created to RFC connections in Solution manager system, one for data collection and the other for analysis. I have maintained the host address of the ECC system as target.
Then i have created a remote system entry in Transaction RZ21--> technical infrastructure entered the 2 RFC names and have executed the function.
At this point i am only trying to bring in ABAP stack monitoring data form the ECC system so i have not generated the CSNCONF file.
Now when i look in Solution manager RZ20-->CCMS monitoring templates, i can't see any data for the the ECC system.
I guess i am doing something wrong. Am i looking in the wrong monitor set?
As additional information: Solution manager (SMD) and ECC (ECD) use different transport domains / transport groups. I dont know if this makes a difference.
Can some one please help.
Regards,
Prashant

Hi Prashant,
if I understand correctly your system shows only MTEs from R/3 Stack, not from the OS side, pls check your SAPOSCOL. Are the data in OS06 in your remote system correct and do you see the current data, refredhed all 10 seconds?
To check your environment, pls do the following:
in th efirst step check in RZ21 > in the Topology part the System Overview for your system connection to your back end system. Are the Read Destination Data RFC and the Destination Analysis RFC correct and works the authority chek fine?
In the second step pls check in RZ21 > in the Agents for Remotey SAP Systems part; are there registered your remote ccms agents correctly and works the connection test.
Stop the agents and in your RZ20 monitor pls enter STAT in your command field. Are there displayed for your MTE nodes the read RFC destinations?
Start the agents and and in your RZ20 monitor pls enter STAT in your command field. Are there displayed for your MTE nodes the CCMS Agent RFC destinations?
To rebuild the Monitor in the CEN system you could try to reset the node of your remote system in the warm up status > go in the remote system to RZ1 > go to local segments > change to edit > select your segments > reset segment in "WARMUP" status.
In the CEN system you coul try to go to the edit mode for the Agents for Remot SAP Systems > select your remote system and push the button Reinitialize Agents
In the back end system you can try to delete all MTEs in RZ21 > menu Technical Infrastructure > Reorgenize Segment Table > select the options with "ALL" in the CEN and the remote system to reorgenize all data.
Could you pls post for the missing MTEs a screenshot on the one side from the CEN system and on the other side from the remote system...
and last but not least you could try the following for missing OS MTEs
delete ALALERTS, ALMTTREE and ALPERFHI in /usr/sap/ccms/<SID>_<SNR> and check in the agents folder all trace and log files for errors.

Configuring ccms to monitor a remote system

Hi.
Im trying to configure my ccms system to monitor a remote epp 6.0.
As it is now, the epp has a ccms agent installed.
Question is:
how and where do I change the agent to send data to my ccms and not to the currently configured system.
and.
when I click "agent working dir" on the ccms system. (under agents for remote SAP system tab) I get this:
Cannot display information due to older age
I know this is sparse info, but what Im looking for are pointers to help me on the way...maybe someone has "the link" im looking for.
I have created an rfc to the remote system. A type T to program ID: host.sapccmsr.99 this hos is the reciepient of the agent data as it is configured now... this host now, collects all ccms data..what I want is, my system to get this info

Hi
I'm getting exactly the same error message when playing back the script I've recorded. Albeit in our SAP system (not BW system)
I'm in our Development System at the moment and want to reply back into the same System that I have created the eCATT in and created the recording to run the eCATT in.
Did you manage to resolve this?
If so could you share
Thanks
Steve

File- XI- RFC produces no output on remote system...

My RFC call is not producing the output I expected.
(scenario: file ->XI->remote RFC call)
When I go into the debugger for the RFC and plug in the
same values as in my text file, I get no error messages, and
I get my desired output (creates a Purch Request on remote system).
However, when set up to run from within XI, there is no output.
Questions --
1. Where on the remote system can I look for possible error msgs?
    ABAP dump analysis shows no entries for this RFC
    SM58 RFC log has no entries.
2. SXMB_MONI on XI shows no error msgs. Where else can I look?
    No dumps on XI either.

>. Check if the RFC needs explicit commit, if so handle the same in the receiver RFC adapter.
   Commit is in the RFC. It works, at least when run in debug mode on remote system.
>2. Check if there is any conversion exit needs to be done for any field.
     I found some earlier problems with the input file, but fixed them.
     Plugging the same exact values into the debugger nets a result.
>3. For testing purpose you can try with a sync call so that you will have the return parameter as response so you can debug easily.
      Haven't tried this one yet.
>4. Did you check the Adapter /communication channel monitoring and is it succesful?
     Yes, the commx channel is working. I know the RFC is being run, since I had previous
     errors that showed up in the remote systems dumps. Fixed those problems, but now
     I get no feedback and no output.

RFC destinations for system monitoring could not be assigned

Hi,
I am having 2 system landscape DEV (DEV/QA), PRD. I want to monitor both system from Solution manager and created both system, db, server & logical component in SMSY.
Problems:
1. System not allowing to assign RFC for (PRD) system monitoring where as it is working for DEV system.
2. When running System monitoring setup only PRD is showing there, both server/system should be shown ?
3. When i am tring to assign system in RZ21 manully then also system giving error in case of PRD server. where as DEV system is created in RZ21 -->> Technical Infra. --->>> Display topology (Error when calling the underlying C function (function 'SALS_MS_GET_LOCAL_MS_INFO')
Message no. RA336)
Please help me to solve this issue.
Thanks & Regards,
Tejinder

Hello Arwel,
if the solution manager should monitor itself via EWA, you have to set "mySAP.com Support Workplace system" to "NONE". To get there, start transaction SDCC in you solution manager system -> Maintenance -> remote enviroment -> default target system.
Hope that will help you.
regards,
Marco

File to RFC - error while processing message to remote system:com.sap.aii.

Hi
i m working on File to RFC scenario. the records are getting displayed in sender CC and receiver CC. But in receiver CC i m also getting the following error:
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: JCO.Exception while calling ZRFC in remote system (RfcClient[CC_RIS_STC_PIMASTER_RECEIVER]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Screen output without connection to user.
Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: JCO.Exception while calling ZRFC in remote system (RfcClient[CC_RIS_STC_PIMASTER_RECEIVER]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Screen output without connection to user.
It was working fine few hours earlier but showing this error now. i was giving a SUBMIT program , but stopped that now.
But still facing the same problem. and in SXMB_MONI its showing recorded for Outbound processing.
could anyone help.

Hi
I am Facing Following Error When I am trying to call SAP Screen through JCO.jar
com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Screen output without connection to user
Please Guide Whethere it is possible to call SAP screen Through JCO.jar ot NOT
Please HELP if it is possible to Call SAP screen through JCO.jar with step and Code
Thanks
Vivek

RFC login and user creation to remote system

Hi there,
Hopefully this is the related forum for this question. We have a scenario where we need an automated process to create users on one system and then create just the same account on a remote system with deactivated password.
How is this best handled in ABAP code where the system account info/password of the remote system is not listed in the abap code. Should a SM59 connection be created and then somehow this is referenced from abap code ?
Also, this will be a SM37 job stream running on the local server under one name running the job and in the code it should be using a different name (destination) for the remote connection to create the user.
I am a security person, not abaper. Input /best practice appreciated.
Thanks !

> I am a security person, not abaper. Input /best practice appreciated.
Actually this is a security question, so I have moved it to the security forum...
If the password is to be deactivated in the target system but not in the source ("master" system) then you can use several standard user provisioning mechanisms for this (CUA, GRC-CUP, IdM, UME configuration...) and configure the target system to deactivate the password itself. There are also several ways of achieving this, without any coding required necessarily.
The most obvious one which jumps to mind is RZ11 parameter login/password_change_for_SSO.
Alternately if your scenario is better suited to it, you can also use login/password_max_idle_initial.
Also see transaction RSUSR200.
Etc...
> Should a SM59 connection be created and then somehow this is referenced from abap code ?
No. It should be referenced from configuration of the application which calls the RFC connection, defined in SM59. You can also optionally use the "current user" setting and alternate authentication methods to (saved) passwords. This I would generally recommend.
Cheers,
Julius
Edited by: Julius Bussche on Feb 23, 2010 10:36 PM

Get interface of RFC function modules in a remote system

Hi,
my goal is to write a report which checks if DDIC structures in two systems fit together when I use RFC`s.
I have the destination and the name of the RFC.
Can somebody tell me if I can get a list of the Importing/Exporting Parameters of this RFC? Maybe even with a typedescribtion?
Thanks for you help.
Best regards
Lars
Edited by: Lars-Eric Biewald on May 21, 2008 8:39 AM

Hello ,
Thank you for your quick help.
Here I have 3 ECC 6 system .
1 Central systen
2 Slave system
Data will be updated to 2 slave system using RFC function module .
We've already the SAP address, Client, User name , Password.. of the remote system
So here how we will create RFC in SM59 to be used in the RFC call ?
We will transfer the username, password , client in the RFC function module/..
Here I do not know how to create RFC connection in SM59 and how to use them in ABAP
Could you please help me ????
Thanks

RFC configuration for system monitoring / Early Watch reports

Hello Basis Gurus:
Please help me out.....
The early watch reports in the solution manager of my system are failing consistently to execute.This is happening for all the 3 systems DEV,QAS,PRD.when i click on individual earlywatch reports it takes me to a screen which says "data for this report is overdue.....go to your satellite system SDCCN to see why the data was not sent...."
It says ...check the following things.....
"The RFC connection for the SAP Solution Manager system is not working.
The 'Task Processor' background job, which collects the session data, has been changed.
Problems arose while data was being collected (see the detail log for the task that collects the session data).
A periodic 'SDCC Maintenance Package' task has not been scheduled to check whether your SAP Solution Manager system requests session data."
I can see the task processor job , and the periodic Maintenance package scheduled everyday and completed sucessfully.So is it the RFC which is causing the problem.
Im SM59 of the solman, i can see system generated RFCs for the PRD,DEV,QAS and SND (...3 for each of these systems...).
say for PRD, these are the 3 RFCs.
1.)SM_PRDCLNT<client#>_READ.
2.)SM_PRDCLNT<client#>_TMW.
3.)SM_PRDCLNT<client#>_TRUSTED.
I am not sure which RFCs among the 3 for any given system does the solman use to communicate to the satellite systems.
*The user id section in the Logon Data of any of these RFCs is blank.and the password says "is initial"...*is this correct.Does the user id have to be a communication type of user...
PLeaase advise as to what could be going wrong..
Regards.

Hi,
The system uses ABAP Connection (Connection Type 3) to connect to different Systems to execute Functional Calls.
Now in your case, there are 3 different connections meaning your Basis Team has used 3 connections for different connection activities. This is totally a business dependent scenario.
Now each time you create a RFC Connection, the system will need the following information to remotely call another system, they are:
Host Details of Target System
Logon Details to remotely login
For RFC Connections the User Type has to be Communications User. But there are companies which use Dialog User Types as well to remotely login for some cases. When the User ID is created for an RFC User and a Password is assigned to it, this Password is considered as the Initial Password by the system. This Password is taken as the Initial Password in the RFC Connection as well.
There can be cases where the system is Trusted and there is no need of a password, but an Username is mandatory in all cases. Remember if you set the system as Trusted, the password option gets deactivated and the connection wont work, if the system does not have the Trusted status.
But in any case you must assign the Username alongwith the Client and Language Details in the RFC Connection for it to work.
Hope this helps.
/Manoj

RFC user not able to log-in to remote system

Dear All,
We are facing an issue when sending data from BI 7.0 system to Windows NT server. It was working fine in BW 3.5 version.
The issue is because the password for RFC connection which we have created is being encrypted in BI 7.0 version. In old BW 3.5 version SM59 --> Logical RFC Conne --> Log on and security, we had checkbox for Unencrypted password.
This checkbox is no more visible in BI 7.0 version and password are encrypted mandatorily.
I want to decrypt this password and send to remote system. Does anyone have any idea how to achive this.
Regards,
Niraj

Hi Niraj,
I am not sure whether this solves your issue or not.But try setting login/password_downwards_compatibility parameter to 1
Check the link for more information [http://help.sap.com/saphelp_nw2004s/helpdata/en/22/41c43ac23cef2fe10000000a114084/content.htm]
Regards,
Kalyan

SYSTEM monitoring , RFCs

Hi All
I want to setup system monitoring from solution manager 7.0 for other satellite systems (4.6) .
Satellite systems have already been added in the System landscape (Tcode -SYSY) and also I have already enabled EWA , SL reporting and they are getting generated properly in solution manager .
Do we need to create RFCs for CCMS read destination and CCMS Login destination to enable system monitoring for those satellite systems . If yes, then are they will be created for client 000 ??
Waiting for suggestions.
Links and documents will also be appreciated...
Still waiting for your suggestion , Experts
Edited by: Rocky on Jun 9, 2008 1:53 PM

As recommended by some colleagues I am also investigating Customer Center of Excelence as a reference to define roles and responsibilities, particularly in the concept of Application Lifecycle Management.
Any other input is welcome.
Regards
Esteban

RFC\BAPI to login into remote system with user id's in that system

Dear Friends,
I have a requirement to run a job .In that job, i need to login into other remote system with the user id's in that system.
May I know, is there any remote function module or BAPI available.
Let me know how to solve this issue.
Regards,
Madhu..!!

Hi Divakar,
As far as I know, there isn’t this feature of remote test in VS2013.
I suggest that you could submit this feature request:
http://visualstudio.uservoice.com/forums/121579-visual-studio. The Visual Studio product team is listening to user voice there. You can send your idea there so the others can vote it. If you submit this suggestion, you might post that link here which will
benefit others who has the similar issue
Regards
Starain
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Error while processing message to remote system

Hi,
I am trying to load the data from flat file to R/3. I am using the file adapter to pick the file and RFC adapter to transfer into R/3. I am getting the success status in the sxmb_moni and adapter framework(green for both the adapters). But when i check the status in the RWB message monitoring, I am getting the error.
I am using the message interface defined in the software component for R/3 system which has a different namespace. When i am trying to upload data, i am getting the error as namespace missing in RWB. The detailed error in RWB is as follows:
Exception caught by adapter framework: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: could not get functionname from XML requst: com.sap.aii.af.rfc.RfcAdapterException: failed to read funtionname from XML document: missing namespace declara
Delivery of the message to the application using connection AFW failed, due to: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: could not get functionname from XML requst: com.sap.aii.af.rfc.RfcAdapterException: failed to read funtionname from XML document: missing namespace declara.
The previous thread relating this is:
Process Integration (PI) & SOA Middleware
Requesting for a solution.
Regards,
Raghavendra

Hi,
>>><i>So i tried creating a RFC(using sm59)in the R/3,
When i try to import the RFC i have created, I am not able to see the one i have created.</i>
In your R/3 system, go to se38, enter your RFC name. Go to attributes tab, and click on the radio button named "remote enabled"
This will enable your RFC to be called by an application outside the R/3 system.
>>><i>Can you please let me know as to what is it that it is connecting to the R/3(destination) and why am i not able to find my RFC.</i>
You are tyring to log on to your R/3 system, from xi, in order to import the RFC that you have created. Hence you are asked for user id and password.
You are not able to find your RFC since it has not been remotely enabled or has not been activated.
Regards,
Smitha.

"Program terminated in remote system NONE: Logon failed" when adding a new table

Hello,
I set up a replication flow from a SAP ERP 6.0 EHP7 with SAP ASE 16.0 source to SAP HANA 1.0 rev 82 target
I am using a standalone SLT system NetWeaver 7.0 with DMIS 2011_1_731 (with SP 1 to 7).
I have 100 tables to replicate.
I succeeded to set up replication for 57 tables. These tables are replicating properly.
Whenever I try to add a new one (with LTRC transaction, Data Provisioning -> Start Replication), the new table is marked as 'Failed' after a little while.
When I press 'Show Error Log' button I got an obscure error message:
"Program terminated in remote system NONE: Logon failed "
I do not understand this message. I checked both on SAP ASE source and SAP HANA target. I am still able to connect against both source and target.
Can you please tell how to troubleshoot this error.
Thanks in advance,
Christian

First thank you for answering my questions. I really appreciate your answers.
I rechecked the documentation.
"Application Operations Guide SAP Landscape Transformation Replication Server Document Version: 2.3 – 2014-07-08"
Page 29 - 30
3.5.2.2 Data Transfer Jobs
This section explains the relationship between the number of data transfer jobs and the number of available background work process.
Data transfer and data transformation processing on SLT server system is accomplished by the background work processes of the underlying SAP NetWeaver ABAP application server. Each job occupies 1 background work process in the SAP LT Replication Server system. For each configuration, the parameter Data Transfer Jobs restricts the maximum number of data load job for each mass transfer ID (MT_ID). In total, a mass transfer ID (MT_ID) requires at least 4 background jobs to be available:
 One monitoring job (master job)
 One master controller job
 At least one data load job
 One additional job either for the migration objects definition, access plan calculation or to change configuration settings in the Configuration & Monitoring Dashboard
Example
If you set the parameter Data Transfer Jobs to 04 in a configuration “SCHEMA1”, a mass transfer ID 001 is assigned. As a result, the following jobs should be in the system:
1 Master controller job: /1LT/IUC_REP_CNTR_001
 At most 4 parallel jobs for MT_ID 001: /1LT/IUC_LOAD_MT_001_001/~002/~003/~004
When configuring your data load or replication scenario, consider the following:
 Do not define more data transfer jobs than the number of available application server background work processes. If all available background work processes are already occupied by jobs, any other job will have to wait until a free work process becomes available. This can lead to long wait times until a new activity (for example creating triggers) can start, and can also result in significantly increased latency times for data replication.
 The number of dialog work processes in the source system corresponds 1:1 with the number of data transfer jobs in the SAP LT Replication Server system.
 Besides the work processes allocated by the data transfer jobs you need to provide additional available work processes for controller and monitoring jobs, the migration objects definition, access plan calculation or to perform configuration changes, and so on.
Sizing for SAP LT Replication Server involves determining how many work processes are required to perform the initial load of data into the target system within an acceptable timeframe, and accomplish the change capturing and the transfer of data changes to the target system within expected latency times.
Ensure that you add enough additional work processes to allow other required SAP LT Replication Server jobs to run.
Finally, you map the number of required application server work processes to their system resource consumption (CPU, memory, disc space) using the formulas provided by the SLT Sizing Guide.
With the simple formula below, you can calculate the number of required application server work processes (WPs) on the SLT Server for each active SLT configuration.
The number of required work processes can be determined by adding
 The Number of required data transfer jobs ,
 plus one background work process for Central Master (Monitoring) Job (only one per system!),
 plus one background work process for Master Controller Job,
 plus 3-5 additional empty background work processes (recommended per configuration),
 plus approx. 3 dialog work processes (recommended for each configuration).
Note: A lack of available free application server work processes can negatively affect the data load or data replication processes.
To summarize everything, the number of 'Data Transfer Jobs' must be set depending of the number of source tables, it is not the actual number of tables.
Assume that for my 100 tables I use 10 'Data Transfer Jobs' :
- The number of work processes on the SLT server would be 20. I took the simple formula of the documentation:
10 data transfer jobs ,
+ 1 background work process for Central Master (Monitoring) Job (only one per system!),
+ 1 background work process for Master Controller Job,
+ 5 additional empty background work processes (recommended per configuration),
+ 3 dialog work processes (recommended for each configuration).
- The number of dialog processes on the source server would be 10 ( equal to the number of 'Data Transfer Jobs')
Am I correct ?
Regards,
Christian

Monitoring RFCs on Remote Systems

Similar Messages

Maybe you are looking for