cancel
Showing results for 
Search instead for 
Did you mean: 

BACK RFC to Solution Manager not available in Task Creation Request Session Data in Satellite SDCCN

Akshay_G
Contributor
0 Kudos

Hi SOLMAN Experts,

I am trying to configure EWA Report for a back-end system on Solution Manager 7.1

I have nearly completed all the requirements and I am almost done with the setup but I think I am stuck hard now and would appreciate the required kickoff.

I have completed the following tasks in order:

1) Latest ST-PI, ST-A/PI are patched on Managed System

2) Hourly Collector Jobs are running on Managed System along with the SAPOSCOL/HostAgent

3) RTCCTOOL requirements have been implemented successfully and everything is Green

4) Managed System is added to the Solution Manager's SMSY via LMDB via2 SLD

5) SDCCN is activated on the Managed System

6) BACK RFC (To SOLMAN) is present in Managed System's SDCCN and works Fine. SOLMAN is set as Master System

7) On SOLMAN, Managed System is added in the SOLMAN's SDCCN and SOLMAN is also set as the Master System

😎 On Managed System SDCCN, Task 'Refresh Service Defintions' has been run once successfully with RFC as BACK (To SOLMAN)

Now the subsequent steps as per what I understand are:

1) Create a 'Request Session Data' Task in SDCCN of the Managed System for Periodic EarlyWatch Alert which will collect the Data and send it to Solution Manager


2) Final and Last step, in SOLMAN Activate the EWA for Managed System under SMWorkCenter--> Sys Mon--> Setup --> EWA Config --> Config for Single Solution (Single Solution containing that Manged System has been defined)

   

Now, regarding point 1, when creating Task 'Request Session Data' for Periodic EarlyWatch Alert, in the SAP RFC Destination field I should select the BACK RFC (To the Solution Manger) so that the Data can be sent to SOLMAN. But I can't see any other RFC available other than RFC NONE as shown below


So what did I miss here?

I have checked the RFC Destinations, the respective BACK RFC i.e. SM_<SIDCLNT>_BACK is present in the Managed System and works fine.

I also checked the RFC Destinations entry in the SDCCN (SDCCN > Goto > Settings > Task-Specific > RFC Destination > Settings ) of both the Managed System and Solution Manager System. The master system flags are also in place. Below are the SDCCN RFC Settings:

LES is Managed System; LSM is Solution Manager

In Managed System (RFC to Solution Manager is defined as required with SOLMAN set to Master System)=>

In Solution Manager System (RFC to SAP [SDCC_OSS] Defined and no Master flag as this is the Solution Manger system)

Please let me know, what did I miss and how to get through this?

I didn't find any standard guide or procedure to set up EWA in Solman 7.1, yes there were best practices guides but that was of SOLMAN 7.0/7.01 and couple of things have changed now in 7.1 so I have just followed everyone's experience and posts on SCN to get EWA working. Hope the steps I have carried out are correct ones and are in correct sequence.

Please let me know.

Best Regards,

Akshay

Accepted Solutions (1)

Accepted Solutions (1)

Lluis
Active Contributor
0 Kudos

Hello Akshay,

If you setup the RFC "_BACK" on managed system that point to your solution manager and that RFC work, afer "sdccn resresh session task" you have to be able to see the ewa session, if after that you can't see the ewa sessión there will be different causes:

( that are some that i found myself )

1.- The system ID is different that you have on solution manager -> logical component

( i get that when customer make a change of the virtual host and install a new system on same vm )

2.- The installation of managed system is not the same that you have on your solution manager -> logical component -> system,

( that happen after a customer name change )

3.- the managed system don't have update the license key

Hope one of that can help your problem,

regards,

Luis

Akshay_G
Contributor
0 Kudos

Hello Luis,

Appreciate your feedback.

However, the issue is not with the creation of EWA Session (i.e. Task 'Request Session Data of Periodic EarlyWatch Alert type').

The issue is that while creating the task I am not able to select the BACK RFC to Solution Manager, there is no point in creating the Task if I am not able to send the collected data to Solution Manager from the Managed System.

All other settings are perfectly OK, because if I create the Task and use RFC NONE (For Test Purpose) or SDCC_OSS the session runs and collects the data hence no issue in Scheduling/Creating EWA Session. The real issue is in sending the data to appropriate target i.e. SOLMAN.

P.S.- BACK RFC is defined to SOLMAN in Managed System SDCCN and SOLMAN is set as the Master System.

Let me know, if you can think of anything else.

-Akshay

former_member118647
Active Participant
0 Kudos

Hello Akshay,

Their is nothing wrong with the configuration of LES SDCCN. You are trying to generate the EWA for LES from LES itself, which is not allowed. The request for EWA for system under monitoring should come from solman. Thats the reason, you are not able to pick up back RFC in pop up while creating the EWA request. However if you want to send the EWA to SAP the you can use the SDCCN of system(LES) and pick up the SDCC_OSS rfc from pop up.

Now to send the EWA to solman

1) in solman, access the solman directory with tcode solman_directory and choose the solution in which logical component having your system LES is present. In right hand scrren, go to logical component in which your system LES is present and right click on the relevant cell(where LES is mentioned) and choose 'Put in solution'. this will turn the cell GREEN.

2) Create the EWA task for LES in the EWA setup via System Monitoring workcenter(in solman) or just by activating it via SOLMAN_EWA_ADMIN in solman

3)in LES system SDCCN execute- Maintenance Package: schedule this task to run daily. Within this task many others are triggered. A very important task triggered by the main-tenance package is task "Refresh sessions", which will read the EWA sessions created in the solution manager in order to find if there is an EWA session for the system LES. If a matching session is found then the refresh sessions triggers the creation of the EWA data collection task in the managed system LES.

With the SDCCN working the process should be performed automatically until the data is processed by job SM:EXEC SERVICES in your solution

manager.

Regards,

Suhel

Lluis
Active Contributor
0 Kudos

Check that Akshay,

sdccn -> task-specific -> rfc connections   ( i see that you already get it, but try to remove "master flag" before you create "refresh session" ) 

After you create the "refresh session", go back to rfc task management and add the flag again.

Regards,

Luis

Akshay_G
Contributor
0 Kudos

Hello Suhel,

Your observation was right-on with a eagle-eye view.

I have done the correction i.e. The Managed system LES is PUT IN SOLUTION for ERP Solution in SOLMAN and the respective cell is green now which was not earlier (I guess it was missed out anyhow earlier during the Solution maintenance, I have made a note of that for future)

Next, I have created the EWA Task for LES in SOLMAN > WORKCENTER > SYS. MON. > SETUP > CONFIGURE EWA > SINGLE SOLUTION > Select Solution and I have scheduled it for tomorrow i.e. Friday, 27th Sept and repeating weekly.

Next, I have deleted the existing scheduled Maintenance Package Task in LES SDCCN and re-created to run, beginning tomorrow morning 6AM and thereafter daily.

Finally to ensure the sequence, I have changed the Job SM:EXEC SERVICES on Solution Manager to run at 8AM Morning starting tomorrow and thereafter daily.

Finally I have checked the EWA Session in RDSMOP_MAIN & as well as Work Center, the EWA is scheduled for tomorrow i.e. 27th, Friday

I believe the EWA will be processed by tomorrow before I begin my day.

What are your thoughts on this? I will be updating again tomorrow.

Regards,

Akshay

Akshay_G
Contributor
0 Kudos

Hi Luis,

I am now able successfully schedule an EWA session as per my above reply to Suhel.

I will monitor the EWA processing, which is scheduled for tomorrow and make a final closure.

Appreciate your help.

Regards,

Akshay

former_member118647
Active Participant
0 Kudos

Things look great now I hope you will be able to generate your EWA report soon.

Answers (4)

Answers (4)

Akshay_G
Contributor
0 Kudos

Hi All,

Thanks a lot for your continuous support

I was finally able to successfully schedule an EWA session and generate the report.

After following above steps, when I was expecting the EWA to be ready, one final last piece was missing. Today at first when I checked, the EWA session was there with a red flag i.e. The data for this session is overdue which implied No data has yet been passed from the managed system to the Solution Manager.

I went back to check the SDCCN task logs in Manged System, it seemed to be have runned without any errors.

One final thing which I did, I created a new Task 'Refresh Sessions' which read to the Solution Manager and found a EWA session scheduled/missed and thereafter it created a new task in Managed System's SDCCN namely "SAP EarlyWatch Alert - Request Session Data". This task finally collected all the data and sent it solution manager.

Once this above spawned task "SAP EarlyWatch Alert - Request Session Data" was completed, I went back to Solution Manager to check the status of EWA Reports.

Voila! The data was available signified by icon of Two Bottles.

So finally, once SM:EXEC SERVICES job runs, this shall be over for now and all.

So anyways I went ahead and manually started the processing without waiting any further.

Once the job got finished the EWA reports were ready, with a rating Yellow (what a shame! )

Thanks all, for pitching in as this made me realize for myself how it works rather than reading and trying to understand everyone's say.

Regards,

Akshay

Former Member
0 Kudos

Dear Akshay,

Can you please send me the full document (screenshots is/are pressure-point) that depicts how you went ahead with ewa configuration.

arthurbbr@yahoo.co.in

Thanks already. (that's how I intimidate)

shriramcse
Participant
0 Kudos

Hi Akshay,

For scheduling Early Watch Alert you have to choose "Maintenance Package" Under Task-->Create.

Regards,

-Sriram

Akshay_G
Contributor
0 Kudos

Hi Sriram,

For EarlyWatch Alert the task type should be 'Request Session Data [REQUEST_DATA]'

Maintenance Package is already running as a daily task and it is for following purposes, not EWA:

1) Refresh Service Definitions from Master SOLMAN or SAP (OSS)

2) Refresh Sessions from all Maintained Systems (On SOLMAN Side)

3) Delete Old Session and Log Data

-Akshay

shriramcse
Participant
0 Kudos

Hi Akshay,

For EW report in SOLMAN below two tasks in SDCCN of Managed system is enough

– Maintenance Package task

– Service Preparation Check (RTCCTOOL)

I think you have not created any solution.

Have you created the solution and assigned the logical component in SMSY..?

Regards,

-Sriram

Akshay_G
Contributor
0 Kudos

Hi Sriram,

Totally agree with you.

Below two tasks are already running in Managed System SDCCN

  • Maintenance Package with Task System= SOLMAN
  • Service Preparation Check with Task System= Managed System

SAP Solution is also created and Logical Component is assigned as below:

-Akshay

shriramcse
Participant
0 Kudos

Hi Akshay,

Can you post the output of the report "rdsmop_main" after selecting solution "SAP ERP".

Regards

-Sriram

Akshay_G
Contributor
0 Kudos

Hi Sriram,

Here you go =>

I believe this is EWA Alert for Solutions, what we need is SAP EarlyWatch Alert for System (Managed System), something like this below (A working instance of EWA)

This same behavior I observed when doing SOLMAN_WORKCENTER > SYS MON. > SETUP > EWA Config --> Config for Single Solution (Then Selecting ERP Solution).

I feel like, I have missed something tiny yet crucial

-Akshay

shriramcse
Participant
0 Kudos

Hi Akshay,

Create the Logical component under SAP ERP not under EHP and assign it to solution SAPERP

Regards,

-Sriram

former_member185048
Participant
0 Kudos

hi Akshay,

I see the SDCC_OSS RFC only in solution manager system and not in managed system. Create the SDCC_OSS RFC destination in SDCCN > Goto > Settings > Task-Specific > RFC Destination > Settings in the managed system and also add the BACK  RFC again there. Now the BACK RFC should appear while creating tasks.

Thanks,

Karthik.

Akshay_G
Contributor
0 Kudos

Hi Karthikeyan,

Thanks for the response.

I ensured to created SDCC_OSS in Managed System SDCCN and removed destination SM_LSMCLNT700_BACK and again added it back and set it to be the master system.

Now as per the pop-up also, which I get after saving the Destinations, it says "This Destination will be available only for New Tasks" I should be able to select the SM_LSMCLNT700_BACK RFC for creating a new task, but still not possible.

Rather now I get NONE and SDCC_OSS but still no back RFC to Solution Manager.

RFC Destinations in Managed System SDCCN=>

I have also run 'Refresh Service Definitions' task once after saving above Destinations.

Then, while Creating new Task 'Request Session Data [REQUEST_DATA]' =>

Available RFC's in the above Selection =>

Another thing is that however the RFC SDCC_OSS is available now, it will send the data to SAP, but I want to send it to Solution Manager, so the RFC Destination has to be BACK RFC to Solution Manager, right?

Let me know what you think?

-Akshay

Former Member
0 Kudos

Hi,

Method:1

After create the back RFC in the managed system, in SMSY -> Environment -> solution maanager operation -> Adminstration SDCCN -> active the managed system( it will set the back rfc in managed system for Session Data')

Method:2

Goto managed system SDCCN -> Goto ->settinds-> task specific ->Rfc destination -> click the setting box -> edit the Rfc destination -> add the back rcf in the screen and continue the configuartion

http://scn.sap.com/docs/DOC-45842

Note 763561 - Service Data Control
Center (SDCCN) - FAQ

http://wiki.scn.sap.com/wiki/display/SM/The+EWA+workflow+-+a+closer+look

remaining step same in 7.01 EHP version -https://websmp208.sap-ag.de/~sapidb/011000358700001873212008E

Rg,

karthik

Akshay_G
Contributor
0 Kudos

Hi Karthik,

Appreciate your response.

However I checked what you mentioned, as per below:

Method 1:

The Managed System SDCCN is already active in the Solution Manager.

Respectively BACK RFC has been generated in the managed system for Session Data, but that is not available while creating the Task as per what I mentioned above.

Method 2:

BACK RFC is already Present in managed system SDCCN -> Goto ->settinds-> task specific ->Rfc destination -> click the setting box (Already mentioned above in the Screen-shot)

Let me know, if you can think of anything else.

-Akshay

Former Member
0 Kudos

Hi Akshya,

During the SDCCN active in solution mananger system in SMSY -> Environment -> solution maanager operation -> Adminstration SDCCN -> active the managed system( it will set the back rfc in managed system for Session Data')

It automaticall set the back RFc as master if have proper authorization.

But why u r checking the solution manager SDCCN , it not required for EWA configuration for other managed system configuration.

If u r configuring EWA for solman system, create Back rfc in solman system using managed system setup and active the SMSY -> Environment -> solution maanager operation -> Adminstration SDCCN -> active the solman system also

it will set automatically set back RFC in the solman SDCCN as master.

Also let me know if i have misunderstood your issue.

Rg,

Karthik

Akshay_G
Contributor
0 Kudos

Hi Karthik,

I have a managed System LES and a Solution Manager LSM.

My objective is to run EWA for LES System processed by LSM.

I am not aiming to run EWA for LSM itself right now, I am concerned about the satellite systems.

Hope this eradicates the doubt.

-Akshay

Former Member
0 Kudos

Hi Akshay,

Then why u r try to set the master back rfc in LSM.

In Solution Manager System (RFC to SAP [SDCC_OSS] Defined and no Master flag as this is the Solution Manger system)

In the below screen( LES system) , click the set default and click the RFC destination and select the back rfc for SM59 and create the refresh session.

It will schedule the  /BDL/TASK_PROCESSOR job.

Managed system - /BDL/TASK_PROCESSOR job will collect the data and send to the solution manager through back RFC

In solution manager - SM:EXEC SERVICES job will scedule on every day, it will collect the date from managed system and trigger the alert on weekly basis.

Rg,

Karthik

Akshay_G
Contributor
0 Kudos

Hi Karthik,

Regarding the first point I was trying to imply that, LES System is Defined in LSM's SDCCN Admin and LSM is master for LES. Basically, figuratively speaking the below screen shots:

For the subsequent mentioning:

Karthik Paramasivam wrote:

In the below screen( LES system) , click the set default and click the RFC destination and select the back rfc for SM59 and create the refresh session

.


Please clarify which task are your referring?

Refresh Session or Request Session Data (As the screen above in Subject is for Request Session Data)

But anyways still, I had have done both as below:

1) I have already ran 'Refresh Sessions' once with Target RFC SM_LSMCLNT700_BACK

2) The mother of the original problem is, "When Creating task Request Session Data, I can't select the RFC SM_LSMCLNT700_BACK as it is not displayed. Only NONE & SDCC_OSS are available RFC's when I do F4.

The Refresh Sessions Task spawned job /BDL/TASK_PROCESSOR0000000020 with Target RFC SM_LSMCLNT700_BACK as below:

And here's the BDL Job Log:

Next, on SOLMAN side, Job SM:EXEC SERVICES is scheduled for daily run.

However, I have again run the program accountable after doing Sessions Refresh on Satellite

Here's the output=>

Getting this notification "

Solution <000000003970000> "SAP ERP..." is being edited (Setup)"

Where can I dig next now?

Appreciate your insights

-Akshay


Former Member
0 Kudos

Hi ,

For EWA only required refresh session, not refresh session data.

Normally if u configure EWA from Solman, it will schedule the maintenance package, it contain

Subtask :1-  Session Refresh

Subtask :2 - Service definition refresh

Subtask :3 - delete old session.

So maintenance package will take care of EWA data collection , because Session refresh is triggered in this package.

So Request Session Data is not required for EWA, i think all configuartion is done in your system.

check the EWA schedule for system wise in the worcenter or RDSMOP_MAIN whether EWA is generating or showing any issue in schedule ?

Rg,

Karthik

Akshay_G
Contributor
0 Kudos

Hi Karthik,

Thanks, I was able to schedule an EWA session successfully now.

You are absolutely right, on Satellite System SDCCN, only task required is Maintenance Package Task which will take care of everything.

Earlier we dis-agreed big time on "Request Session Data' due to the fact that I was following couple of below contents on SCN, where it wasn't mentioned as correctly as it should be, and it insisted on what i was doing incorrectly.

1) http://scn.sap.com/docs/DOC-43932

2) http://scn.sap.com/message/14257064

Well anyways, I guess not every information is correct or generic. So I have finally done the adjustment as per my reply to Suhel Khan

The EWA is scheduled to run for tomorrow, I hope it processes it finally.

Appreciate your help through out.

Will again update once it completed.

Thanks,

Akshay