RFC configuration for system monitoring / Early Watch reports

Question

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.

Answer 1

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