Solution Manager EarlyWatch

Hi,
I have a test system setup for Solution Manager 4 and we also have a ECC6 test system setup. I am trying to setup earlywatch data transfer between the 2 systems. At the moment I have EWA data being gathered for solution manager in SDCCN and it is sent to SAP and that generates a report doc, which I can access. I can also see the data it has gathered in its raw form in SDCCN corresponding to its task. The ECC6 test system also has SDCCN activated and it seems that i can gather data for that system and send it to SAP without solMan. I thought that solman was to be used to schedule weekly EWA to the satellite system to request data and send this data to SAP from solMan. I was going to schedule a task on ECC6 to send data to Solution manager by creating a RFC link to solution manager from ECC6, which it can use but can someone please clarify this as i am a bit confused. I thought all data gathering from satellite systems should be done from solMan. Also i did look at note 207223 and 763561 for SDCCN.
Thanks in advance for the help,
Mani

Thanks David for your replies.
Yes the ECC 6 system is added to the solution landscape and it has a logical component assigned. In the smsy transaction it has pulled all the information from the ECC 6 system about clients and support pack info.
So what i understand from your reply is that the EWA data is gathered by the satellite system, as per task setup in SDCCN i.e. in ECC 6 and that is sent by the ECC6 system to solMan system. The solman system takes this data and compiles a report similar to the one available via sap marketplace or is it just raw data available in a tree drop down form?
Also how does transaction dwsp tie into this? Everytime i run a schedule in it, it fails. Does this create a session in SDCCN on the satelittle system or is it kept in syn either way when a earlywatch alert is created?
My understanding is that i need to run a periodic EWA alerts on the satelittle system (ECC 6), which sends session data to solman and no task needs to be setup to request data in solman.
sorry about the questions but i really so appreciate the help and do reward points in return for help.
Many thanks,
Mani

Similar Messages

Solution Manager - EarlyWatch Alert shows red flag for managed system.

Hi Guys,
I tried to fix EarlyWatch alert report for Managed systems of QA and Dev which showed red flag on SolMan in DSWP. While trying to generate BACK RFC Destination to SolMan for QA and Dev, it messed up the EarlyWatch alert reports of Prod which was successfully working upto this point. And now the red flag appears for Prod system on SolMan in DSWP instead of two bottle sign.
As for why Dev and QA did not work, I found out it was NONE internal RFC popped whenever I tried to choose the RFC to connect to SolMan while Prod which was working fine before always showed BACK rfc. That's why I tried to fix BACK rfc for Dev and QA.
Please help me to fix these EWA problems.
Thanks,
Modena

Hi Modena,
Please see the link below for this specific issue:
http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=228262728

Setting up EarlyWatch in Solution manager

Hi Guys
I am trying to configure Early Watch in solution manager(System Id u2013SOL , Installation No - 0020306432) for an satellite system (System Id -DEV u2013Installation No : 0020181089).
I have followed all the configuration steps listed below :
1.     Configuration RFCs to market place SAPOSS and to satellite Systems and RFC Back to solution manager. All RFC like SAPOSS and Back has been tested from SDCCN (Solution manager and satellite system)
2.     Configured SDCCN in solution manager and in satellite system except u201CGenerate Includes for Service data control centeru201D in SPRO of solution manager as this process is getting time out and not letting us to generate all the includes
3.     Activated Service data Control center locally and assign solution manager as u2018Master system for allu2019.
4.     Activated SDCCN in satellite system(DEV) ,Created Earlywatch Service in Solution manager for DEV system and also created/Started u2018Refresh Sessionu2019 in SDCCN of DEV(Satellite system)
5.     This successfully shows me Early watch link in u2018Waitingu2019 Status in solution manager.
6.     I click on u2018Start Service Processingu2019 to Schedule/Run u201CSM:EXEC SERVICESu201D background job .
Problem : Background job u201CSM:EXEC SERVICESu201D get cancelled after some time and throws a Dump which is pasted below.
Dump shows that an include u2018/1CAGTF/IF_LOGFUNC_000393u2019 is missing which should have been generated while activating the includes for SDCCN in SPRO of solution manager.
I found includes from u2018/1CAGTF/IF_LOGFUNC_000001u2019 to u2018/1CAGTF/IF_LOGFUNC_000353u2019 in the system as it seems that not all include have been generated .
*Could you please help me to provide some SAP note so that I would be able to generate all the includes . *
DUMP
Runtime Errors         SYNTAX_ERROR
Date and Time          24.05.2008 00:01:02
Short text
Syntax error in program "RDSVASAEW_ROOT_____________073 ".
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "RDSVASAEW_ROOT_____________073
" in include "RDSVASAEW_ROOT_____________073 " in
line 96:
"INCLUDE report "/1CAGTF/IF_LOGFUNC_000393" not found."
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
What can you do?
Please eliminate the error by performing a syntax check
(or an extended program check) on the program "RDSVASAEW_ROOT_____________073
You can also perform the syntax check from the ABAP Editor.
If the problem persists, proceed as follows:
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
The following syntax error was found in the program
RDSVASAEW_ROOT_____________073 :
"INCLUDE report "/1CAGTF/IF_LOGFUNC_000393" not found."
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 700
Application server... "mslsol"
Network address...... "192.168.193.154"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "2x Intel 801586"
Character length.... 16 Bits
Pointer length....... 32 Bits
Work process number.. 10
Shortdump setting.... "full"
Database server... "MSLSOL"
Database type..... "ORACLE"
Database name..... "SOL"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Aug 29 2006 00:18:21"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "OCI_10201_SHARE (10.2.0.2.0) "
Patch level. 75
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Memory consumption
Roll.... 8176
EM...... 29266272
Heap.... 0
Page.... 24576
MM Used. 24845128
MM Free. 236264
User and Transaction
Client.............. 600
User................ "BASISA"
Language key........ "E"
Transaction......... " "
Program............. "SAPLDSVAS_PROC"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "SAPLDSVAS_PROC" - in "EXECUTE".
The main program was "RDSMOPBACK_AUTOSESSIONS ".
In the source code you have the termination point in line 2146
of the (Include) program "LDSVAS_PROCCD0".
The program "SAPLDSVAS_PROC" was started as a background job.
Job Name....... "SM:EXEC SERVICES"
Job Initiator.. "BASISA"
Job Number..... 00384300
Source Code Extract
Line
SourceCde
2116
ls_stdparameter-versnr           = po_ctnode->versnr.
2117
ls_stdparameter-grp              = po_ctnode->grp.
2118
ls_stdparameter-id               = po_ctnode->id.
2119
ls_stdparameter-reference_versnr = po_ctnode->reference_versnr.
2120
ls_stdparameter-reference_grp    = po_ctnode->reference_grp.
2121
ls_stdparameter-reference_id     = po_ctnode->reference_id.
2122
else.
2123
ls_stdparameter-grp              = pf_grp.
2124
ls_stdparameter-versnr           = pf_versnr.
2125
ls_stdparameter-reference_grp    = pf_grp.
2126
ls_stdparameter-reference_versnr = pf_versnr.
2127
endif.
2128
2129
Formroutinen aufrufen
2130
loop at    actseq
2131
into ls_actrel
2132
where exec_time = pf_exec_time.
2133
check ls_actrel-exec_time ne gf_exec_time_event
2134
or ( ls_actrel-exec_time = gf_exec_time_event and
2135
ls_actrel-event     = pf_event               ).
2136
call function 'DSVAS_CDMNT_FORM_NAME'
2137
exporting
2138
pf_container_type = 'A'
2139
pf_form_number    = ls_actrel-action
2140
importing
2141
pf_form_name      = lf_form_name.
2142
perform (lf_form_name)
2143
in program (program)
2144
using ls_stdparameter
2145
if found.
>>>>>
endloop.
2147
endmethod.                    "execute
2148
2149
Collect_Known_Events
2150
method collect_known_events.
2151
data: ls_actseq type line of ltype_action_sequence_table,
2152
lf_event type dsvasactseq-event.
2153
2154
loop at actseq into ls_actseq
2155
where ( exec_time = gf_exec_time_event and
2156
event     ne space                 )
2157
or   exec_time = gf_exec_time_1
2158
or   exec_time = gf_exec_time_2
2159
or   exec_time = gf_exec_time_3
2160
or   exec_time = gf_exec_time_modus_close.
2161
if ls_actseq-exec_time = gf_exec_time_event.
2162
read table pt_events with table key table_line = ls_actseq-event
2163
transporting no fields.
2164
if sy-subrc ne 0.
2165
insert ls_actseq-event into table pt_events.
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
1
SY-TABIX
1
SY-DBCNT
0
SY-FDPOS
30
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
DSWP: Execute rule set
SY-MSGTY
E
SY-MSGID
FL
SY-MSGNO
046
SY-MSGV1
DSVAS_TOOLS_PACKAGE_GET
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080524
SY-UZEIT
000049
SY-XPROG
SAPCNVE
SY-XFORM
CONVERSION_EXIT
Active Calls/Events
No.   Ty.          Program                             Include                             Line
Name
11 FORM         SAPLDSVAS_PROC                      LDSVAS_PROCCD0                       2146
EXECUTE
10 METHOD       SAPLDSVAS_PROC                      LDSVAS_PROCCD0                       2142
LCL_ACTION_SEQUENCE=>EXECUTE
9 METHOD       SAPLDSVAS_PROC                      LDSVAS_PROCCTI                       1741
LCL_CHECK_TREENODE=>EXECUTE
8 METHOD       SAPLDSVAS_PROC                      LDSVAS_PROCCTI                       1792
LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE
7 METHOD       SAPLDSVAS_PROC                      LDSVAS_PROCCTI                       1806
LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE
6 METHOD       SAPLDSVAS_PROC                      LDSVAS_PROCSEI                       2025
LCL_SESSION=>EXECUTE
5 METHOD       SAPLDSVAS_PROC                      LDSVAS_PROCSEI                       1582
LCL_SESSION=>CONTEXT_INSTANCES_CREATE
4 METHOD       SAPLDSVAS_PROC                      LDSVAS_PROCSEI                       1995
LCL_SESSION=>EXECUTE
3 FUNCTION     SAPLDSVAS_PROC                      LDSVAS_PROCU02                        303
DSVAS_PROC_SESSION_OPEN
2 METHOD       CL_DSMOP_SOLUTION=============CP    CL_DSMOP_SOLUTION=============CM01P   184
CL_DSMOP_SOLUTION=>START_PERIODIC_SERVICES
1 EVENT        RDSMOPBACK_AUTOSESSIONS             RDSMOPBACK_AUTOSESSIONS                72
START-OF-SELECTION
Chosen variables
Name
Val.
No.      11 Ty.          FORM
Name EXECUTE
PF_EXEC_TIME
I
4
9
0
0
PF_EVENT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
PO_CTNODE
|
| 2000D000 |
| E0001C00 |
| PF_GRP |
| |
| 22222222222222222222 |
| 00000000000000000000 |
| 00000000000000000000 |
| 00000000000000000000 |
| PF_VERSNR |
| 00000 |
| 33333 |
| 00000 |
| 00000 |
| 00000 |
| <%_L02E>-EXEC_TIME |
| ??? |
| ?????? |
| ?????? |
| <%_L02F> |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| LS_ACTREL-EXEC_TIME |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| GF_EXEC_TIME_EVENT |
| E |
| 4 |
| 5 |
| 0 |
| 0 |
| SYST-REPID |
| SAPLDSVAS_PROC |
| 5454455455554422222222222222222222222222 |
| 310C43613F02F300000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| LS_ACTREL-EVENT |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| SY-SAPRL+0(4) |
| 70 |
| 33 |
| 70 |
| 00 |
| 00 |
| LS_ACTREL-ACTION |
| 108 |
| 333 |
| 108 |
| 000 |
| 000 |
| LF_FORM_NAME |
| ACTION_108 |
| 44544453332222222222222222222222 |
| 1349FEF1080000000000000000000000 |
| 00000000000000000000000000000000 |
| 00000000000000000000000000000000 |
| ME->PROGRAM |
| RDSVASAEW_ROOT_____________073 |
| 5455454455544555555555555553332222222222 |
| 243613157F2FF4FFFFFFFFFFFFF0730000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| %_DUMMY$$ |
| |
| 2222 |
| 0000 |
| 0000 |
| 0000 |
| LS_STDPARAMETER |
| EA6000000000255###ESESSION                                           00047EA_ROOT |
| 4433333333333330004545544422222222222222222222222222222222222222222223333344554452222222222222 |
| 516000000000255010535339FE00000000000000000000000000000000000000000000004751F2FF40000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| No.      10 Ty.          METHOD |
| Name LCL_ACTION_SEQUENCE=>EXECUTE |
| PF_EXEC_TIME |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| PF_EVENT |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| PO_CTNODE |
|
2000D000
E0001C00
PF_GRP
22222222222222222222
00000000000000000000
00000000000000000000
00000000000000000000
PF_VERSNR
00000
33333
00000
00000
00000
<%_L02E>-EXEC_TIME
<%_L02F>
I
4
9
0
0
LS_ACTREL-EXEC_TIME
I
4
9
0
0
LS_ACTREL-EVENT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LS_ACTREL-ACTION
108
333
108
000
000
LF_FORM_NAME
ACTION_108
44544453332222222222222222222222
1349FEF1080000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
ME->PROGRAM
RDSVASAEW_ROOT_____________073
5455454455544555555555555553332222222222
243613157F2FF4FFFFFFFFFFFFF0730000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LS_STDPARAMETER
EA6000000000255###ESESSION                                           00047EA_ROOT
4433333333333330004545544422222222222222222222222222222222222222222223333344554452222222222222
516000000000255010535339FE00000000000000000000000000000000000000000000004751F2FF40000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
No.       9 Ty.          METHOD
Name LCL_CHECK_TREENODE=>EXECUTE
PF_EXEC_TIME
I
4
9
0
0
PF_EVENT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
GF_EXEC_TIME_ATTRIBUTES
a
6
1
0
0
RSJOBINFO
00000000000000                                  ##
2222222222222222222222222222222233333333333333222222222222222222222222222222222200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
ME
|
| 2000D000 |
| E0001C00 |
| GT_OPEN_SESSIONS |
| Table IT_3668[1x44] |
| FUNCTION-POOL=DSVAS_PROCDATA=GT_OPEN_SESSIONS |
| Table reference: 1911 |
| TABH+ 0(20) = 807E0D3E000000000000000077070000540E0000 |
| TABH+ 20(20) = 010000002C000000FFFFFFFF0417010010040000 |
| TABH+ 40( 8) = 10000000A4318001 |
| store        = 0x807E0D3E |
| ext1         = 0x00000000 |
| shmId        = 0     (0x00000000) |
| id           = 1911 (0x77070000) |
| label        = 3668 (0x540E0000) |
| fill         = 1     (0x01000000) |
| leng         = 44    (0x2C000000) |
| loop         = -1    (0xFFFFFFFF) |
| xtyp         = TYPE#000007 |
| occu         = 16    (0x10000000) |
| access       = 4     (ItAccessHashed) |
| idxKind      = 0     (ItIndexNone) |
| uniKind      = 1     (ItUnique) |
| keyKind      = 3     (user defined) |
| cmpMode      = 8     (cmpManyEq) |
| occu0        = 1 |
| groupCntl    = 0 |
| rfc          = 0 |
| unShareable = 0 |
| mightBeShared = 0 |
| sharedWithShmTab = 0 |
| isShmLockId = 0 |
| gcKind       = 0 |
| isUsed       = 1 |
| isCtfyAble   = 1 |
| >>>>> Shareable Table Header Data <<<<< |
| tabi         = 0xC0AB0D3E |
| pgHook       = 0x00000000 |
| idxPtr       = 0x78F10D3E |
| shmTabhSet   = 0x00000000 |
| id           = 2504 (0xC8090000) |
| refCount     = 0     (0x00000000) |
| tstRefCount = 0     (0x00000000) |
| lineAdmin    = 16    (0x10000000) |
| lineAlloc    = 16    (0x10000000) |
| shmVersId    = 0     (0x00000000) |
| shmRefCount = 1     (0x01000000) |
| >>>>> 1st level extension part <<<<< |
| regHook      = Not allocated |
| collHook     = Not allocated |
| ext2         = Not allocated |
| >>>>> 2nd level extension part <<<<< |
| tabhBack     = Not allocated |
| delta_head   = Not allocated |
| pb_func      = Not allocated |
| pb_handle    = Not allocated |
| GF_EXEC_TIME_BEFORE_REPORT_GEN |
| R |
| 5 |
| 2 |
| 0 |
| 0 |
| GF_EXEC_TIME_INIT |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| ME->INITIALIZED |
| |
| 2 |
| 0 |
| 0 |
| 0 |
| GF_EXEC_TIME_AFTER |
| A |
| 4 |
| 1 |
| 0 |
| 0 |
| ME->ACTSEQ |
|
2000D000
C0003C00
SCREEN
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ME->HAS_TABLES
X
5
8
0
0
SYST
##########################A###P##############################################T###ÿ##### u####
0000000000000000000000100040005000000050000000007000000000000000000000000000105000F00050270000
1000101000001000000000E010101000000000C0000000004000000000000000000000000000604000F00080050600
0000000000000000000000000000000000000000000000001000000000000000000000000000000000000040000000
00000000000000000000000000000000000000000000000070000000000000000000000000000000000000D000000C
SY-REPID
SAPLDSVAS_PROC
5454455455554422222222222222222222222222
310C43613F02F300000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->CHECK_TABLES
|
| 2000D000 |
| 3000CC00 |
| No.       8 Ty.          METHOD |
| Name LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE |
| PF_EXEC_TIME |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| PF_EVENT |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| PF_CON |
| SESSION |
| 5455444222 |
| 35339FE000 |
| 0000000000 |
| 0000000000 |
| PF_INS |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| ME->DYNAMIC |
| X |
| 5 |
| 8 |
| 0 |
| 0 |
| ME |
|
2000D000
E0001C00
GF_SESSION_DEF_TYPE_MORE_DEV
L
4
C
0
0
ME->ACTIVE
X
5
8
0
0
GF_SESSION_DEF_TYPE_VERSION
V
5
6
0
0
ME->CON
SESSION
5455444222
35339FE000
0000000000
0000000000
ME->INS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->CHILD_CONDSEQ
F0000000
F0000000
GF_CONTEXT_SESSION
SESSION
5455444222
35339FE000
0000000000
0000000000
ME->CHILDREN
Table[initial]
LO_TNODE
|
| F0000000 |
| F0000000 |
| %_ARCHIVE |
| |
| 2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| No.       7 Ty.          METHOD |
| Name LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE |
| PF_EXEC_TIME |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| PF_EVENT |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| PF_CON |
| SESSION |
| 5455444222 |
| 35339FE000 |
| 0000000000 |
| 0000000000 |
| PF_INS |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| ME |
|
2000D000
F0000C00
ME->CHILD_CONDSEQ
|
| F0000000 |
| F0000000 |
| ME->CHILDREN |
| Table IT_3674[26x8] |
| DATA=CHILDREN
Table reference: 1919
TABH+ 0(20) = 68550D3E00000000000000007F0700005A0E0000
TABH+ 20(20) = 1A00000008000000800100000417010030080000
TABH+ 40( 8) = 10000000C1288001
store        = 0x68550D3E
ext1         = 0x00000000
shmId        = 0     (0x00000000)
id           = 1919 (0x7F070000)
label        = 3674 (0x5A0E0000)
fill         = 26    (0x1A000000)
leng         = 8     (0x08000000)
loop         = 384   (0x80010000)
xtyp         = TYPE#000029
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 4     (cmpSingleEq)
occu0        = 1
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
isCtfyAble   = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0xB0B10D3E
pgHook       = 0xF0882E3E
idxPtr       = 0x00000000
shmTabhSet   = 0x00000000
id           = 2508 (0xCC090000)
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 48    (0x30000000)
lineAlloc    = 48    (0x30000000)
shmVersId    = 0     (0x00000000)
shmRefCount = 1     (0x01000000)
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
collHook     = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
LO_TNODE
|
| 2000D000 |
| E0001C00 |
| LO_CTNODE |
|
2000D000
E0001C00
%_SPACE
2
0
0
0
No.       6 Ty.          METHOD
Name LCL_SESSION=>EXECUTE
PF_EXEC_TIME
I
4
9
0
0
PF_EVENT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
PF_CON
SESSION
5455444222
35339FE000
0000000000
0000000000
PF_INS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->ACTSEQ
|
| F0000000 |
| F0000000 |
| ME->GLOBAL_CHECK_GRP |
| EA_ROOT |
| 44554452222222222222 |
| 51F2FF40000000000000 |
| 00000000000000000000 |
| 00000000000000000000 |
| ME->GLOBAL_VERSNR |
| 00047 |
| 33333 |
| 00047 |
| 00000 |
| 00000 |
| ME->CHECK_TREE |
|
2000D000
F0000C00
GF_EXEC_TIME_MODUS_CLOSE
W
5
7
0
0
ME->RAISED_EVENTS
Table[initial]
GF_EXEC_TIME_LOGICAL_COMPLETE
L
4
C
0
0
No.       5 Ty.          METHOD
Name LCL_SESSION=>CONTEXT_INSTANCES_CREATE
LT_ZOMBIES
Table[initial]
LS_CTREL-TREENODE
F0000000
F0000000
LO_ZOMBIE
|
| F0000000 |
| F0000000 |
| LT_NEW_CONINS |
| Table IT_3670[1x100] |
| FUNCTION-POOL=DSVAS_PROCCLASS=LCL_SESSIONMETHOD=CONTEXT_INSTANCES_CREATEDATA=LT_NEW_CONINS |
| Table reference: 1920 |
| TABH+ 0(20) = 90C50D3E30F3DE3D0000000080070000560E0000 |
| TABH+ 20(20) = 0100000064000000080100000417010060140000 |
| TABH+ 40( 8) = 01000000C1248401 |
| store        = 0x90C50D3E |
| ext1         = 0x30F3DE3D |
| shmId        = 0     (0x00000000) |
| id           = 1920 (0x80070000) |
| label        = 3670 (0x560E0000) |
| fill         = 1     (0x01000000) |
| leng         = 100   (0x64000000) |
| loop         = 264   (0x08010000) |
| xtyp         = TYPE#000094 |
| occu         = 1     (0x01000000) |
| access       = 1     (ItAccessStandard) |
| idxKind      = 0     (ItIndexNone) |
| uniKind      = 2     (ItUniqueNon) |
| keyKind      = 1     (default) |
| cmpMode      = 2     (cmpSingleMcmpR) |
| occu0        = 1 |
| groupCntl    = 0 |
| rfc          = 0 |
| unShareable = 0 |
| mightBeShared = 1 |
| sharedWithShmTab = 0 |
| isShmLockId = 0 |
| gcKind       = 0 |
| isUsed       = 1 |
| isCtfyAble   = 1 |
| >>>>> Shareable Table Header Data <<<<< |
| tabi         = 0x08AB0D3E |
| pgHook       = 0x00000000 |
| idxPtr       = 0x00000000 |
| shmTabhSet   = 0x00000000 |
| id           = 2505 (0xC9090000) |
| refCount     = 0     (0x00000000) |
| tstRefCount = 0     (0x00000000) |
| lineAdmin    = 1     (0x01000000) |
| lineAlloc    = 1     (0x01000000) |
| shmVersId    = 0     (0x00000000) |
| shmRefCount = 1     (0x01000000) |
| >>>>> 1st level extension part <<<<< |
| regHook      = 0xB0F0BE3D |
| collHook     = 0x00000000 |
| ext2         = 0x00000000 |
| >>>>> 2nd level extension part <<<<< |
| tabhBack     = Not allocated |
| delta_head   = Not allocated |
| pb_func      = Not allocated |
| pb_handle    = Not allocated |
| <LFS_CONINS> |
| SESSION |
| 54554442222222222222222222222222222222222222222222 |
| 35339FE0000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| ME |
|
90006000
4000B000
<LFS_CONINS>-CON
SESSION
5455444222
35339FE000
0000000000
0000000000
<LFS_CONINS>-INS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SY
##########################A###P##############################################T###ÿ##### u####
0000000000000000000000100040005000000050000000007000000000000000000000000000105000F00050270000
1000101000001000000000E010101000000000C0000000004000000000000000000000000000604000F00080050600
0000000000000000000000000000000000000000000000001000000000000000000000000000000000000040000000
00000000000000000000000000000000000000000000000070000000000000000000000000000000000000D000000C
GF_EXEC_TIME_BEFORE
B
4
2
0
0
No.       4 Ty.          METHOD
Name LCL_SESSION=>EXECUTE
PF_EXEC_TIME
I
4
9
0
0
PF_EVENT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
PF_CON
2222222222
0000000000
0000000000
0000000000
PF_INS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->ACTSEQ
|
| F0000000 |
| F0000000 |
| ME |
|
90006000
4000B000
ME->LOGICAL_COMPLETE
2
0
0
0
GF_EXEC_TIME_COMPLETE
C
4
3
0
0
ME->COMPLETE
2
0
0
0
SY-XFORM
CONVERSION_EXIT
444545544454545222222222222222
3FE65239FEF5894000000000000000
000000000000000000000000000000
000000000000000000000000000000
No.       3 Ty.          FUNCTION
Name DSVAS_PROC_SESSION_OPEN
PF_HANDLE_TO_USE
0
0000
0000
PF_MAX_TREE
2
0
0
0
PF_MODE
C
4
3
0
0
PS_SESSION_NUMBER
EA6000000000255
443333333333333
516000000000255
000000000000000
000000000000000
PF_HANDLE
1
0000
1000
PF_HIDE_TREE
2
0
0
0
PF_MODE_USED
2
0
0
0
PF_NEXT_CHECK_GRP
22222222222222222222
00000000000000000000
00000000000000000000
00000000000000000000
PF_NEXT_CHECK_ID
00000
33333
00000
00000
00000
PF_NEXT_CON
2222222222
0000000000
0000000000
0000000000
PF_NEXT_INS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
PT_ERRORS
Table[initial]
PT_FRONTEND_TREE[]
Table[initial]
PF_LANGUAGE
E
4
5
0
0
<%_TABLE_DSVASSESSADMIN>
LF_BUNDLE_VERSNR
00038
33333
00038
00000
00000
DSVASRESULTSGEN-CLUSTR
0
00
00
PS_SESSION_NUMBER-SESSNO
6000000000255
3333333333333
6000000000255
0000000000000
0000000000000
LS_OPEN_SESSIONS-SESSION
|
| 90006000 |
| 4000B000 |
| LO_SESSION |
|
90006000
4000B000
LS_OPEN_SESSIONS
EA6000000000255C####k#
4433333333333334009060
51600000000025531040B0
0000000000000000000000
0000000000000000000000
SY-XPROG
SAPCNVE
5454454222222222222222222222222222222222
3103E65000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LS_SESSDEFGEN-MULTI_USER

Please replace the Service Definitions in your SAP Solution Manager
system as described in SAP Note 727998.
As of SAP Solution Manager 7.0 (= 4.0) Support Package Stack 15 (which
includes ST-PI 700_2005_1 SP06) you can trigger the required steps
within transaction SDCCN:
Menu Utilities -> Maintain Service Definitions ->
Select 'Delete and Replace Service Definitions -> Confirm this
selection-> Confirm that you want to delete the definitions -> Confirm
that a new task 'Service Definition Refresh' was created
Take a note of the task id -> Review the log for this task id when it
is completed. You should not see any errors for either the update
of a Service Definitions table or the generation of any re-import
include.
Reschedule SM:EXEC SERVICES and the reported dump will no longer
occur.

Autom. replication of EarlyWatch Alerts in 2nd Solution Manager possible?

Hi experts,
I just received a question from a customer whether it is possible to automatic replicate EarlyWatch Alerts generated for systems in SolMan A to SolMan B without having all satellite systems connected to SolMan B.
There are two reports available I know: BDL_GET_SESSION_DATA and BDL_GET_DATA_AND_CREATE_SESSIO
At least via the last report it is possible to read the session number in SolMan A and create a new session with this data in SolMan B. But it is not possible to assign the sessions to a solution or run it as daily job...
Do you know if there is such a functionality in SAP standard or do we need to build our own solution here?
Regards, Richard

Hello,
This is how you genrate an EWA for on Satellite system in two Solution Manager systems.
One will be created automatically via the Maintenance Package (providing you followed best practices) or periodic EarlyWatch of Solution Manager Task if you are not follwoing best practices.
Say we have Solution Manager A & B. In SDCCN in RFC Destinations, we define Solution Manager A as the Master.
So this will be where the EWA task created by the Maintenace Package task will be sent.
For the Solution Manager B you created a Earlywatch periodci task, only you make the RFC Destination the SM<SID>CLNT<NO#>_BACK (where the SID is the SID of Solman B) Yoy can refer to SAP NOTE 207223, which is the Note that explains how to send an EWA to SAP. Its the exactsame process, but the destination is changed to the second Solution Manager.
The data comes from the Satellite/managed system, but can be directed to different destinations.
But you can't send the data from Solution Manager A to Solution Manager B.
You can send the data to Solution Manager A & B and process the data on A and on B, or any other Solman system.
Regards,
Paul

No EarlyWatch Alert for Solution Manager task in SDCCN

Hello All,
We have configured SAP Solution Manager and managed system to generate EWA report.
In Solman, we have created the system, logical system and solution. We have activated the managed system in Setup EarlyWatch Alert in Solman.
In Managed system, we have activated SDCCN, assigned BACK RFC, created Maintenance package and refresh sessions.
However, after completing the Maintenance package task there is no EarlyWatch Alert for Solution Manager task created in managed system. We have reviewed the task logs and found no errors.
In Solman, when we create EWA for today's date the status is showing with an Hour glass stating that "Wait for session data: SAP EarlyWatch Alert and session number"
Kindly assist us in fixing this issue
Thanks in advance
Regards,
Satish

Hi
the task "early watch alert for solution manager" created automatically when did you perform the task "refreh session" or "Maintenance Package"
please create the relevant task, via : SDCCN -> Task -> Create ->Request session data ->Periodic -> Earlywatch Alert -> Continue.
'Schedule' the start date of the first session and - Task -- create Click on 'Refresh sessions' - Press 'Enter' - Select 'Now', to schedule the job 'immediately. once you create the relevant tasks you go by, in the Menu - Goto -> start - to activate the Earlywatch alert session Now, you can check the finished EWA task in 'done' tab.
Login to Solution Manager, goto trx. DSWP --> Select your solution, Solution Monitoring - Earlywatch alert - Click on Earlywatch alert --> start service processing --> Press 'OK' to start the background job - click 'Refresh'
Now, you can see the 'Early watch alert' in the green colour .
more further refer here [EWA guide|http://forums.sdn.sap.com/servlet/JiveServlet/download/156-1701991-9166329-1518/EWA_Activation.pdf]
jansi

Solution Manager 3.1/3.2 - EarlyWatch Alert report problem

Hi,
I installed two Solution Manager system, both 3.2 and 3.1   However ,the problem(issue) is same one,I can't get EarlyWatch Alert report(MS word file).
In a Solution, I choose ->'SAP EarlyWatch Alert' -> 'Start Service Processing' . monitor it by selecting System->Own jobs. then i got the ABAP error log as following.
Does anyone know the reason and help me to solve it?
Regards,
Runtime errors         SYNTAX_ERROR
       Occurred on     22.07.2005 at   17:57:08
Syntax error in program "RDSVASAEW_ROOT_____________062 ".
What happened?
The following syntax error occurred in the program
RDSVASAEW_ROOT_____________062 :
"INCLUDE report "/1CAGTF/IF_LOGFUNC_000426" not found."
Error in ABAP application program.
The current ABAP program "SAPLDSVAS_PROC" had to be terminated because one of
the
statements could not be executed.
This is probably due to an error in the ABAP program.

Hi,
I have same problem.
I can't get EarlyWatch Alert report(MS word file).
Runtime errors SYNTAX_ERROR
What happened?
The following syntax error occurred in the program
RDSVASAEW_ROOT_____________067 :
"The field "FB_DLDINSTPAR_TAB001155" is unknown, but there is a field w"Error in ABAP application program.
System environment
SAP Release.............. "620"
Application server....... "hhisol"
Network address.......... "10.100.13.111"
Operating system......... "HP-UX"
Release.................. "B.11.23"
Hardware type............ "ia64"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 11
Short dump setting....... "full"
Database server.......... "hhisol"
Database type............ "ORACLE"
Database name............ "SOL"
Database owner........... "SAPSOL"
Character set............ "en_US.iso88591"
SAP kernel............... "640"
Created on............... "Nov 6 2005 20:36:36"
Created in............... "HP-UX B.11.23 U ia64"
Database version......... "OCI_920 "
Patch level.............. "99"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.., ORACLE
10.1.0.."
SAP database version..... "640"
Operating system......... "HP-UX B.11"
Please help me to solve it!
Regards,

Two earlywatch reports for same instance in one Solution manager

Hi
i am trying to create two solutons for early watch reports for same instance. let me explain here.
In SAP Solution Manager: Active Solutions >>> i have two solutions like this
Solution                                                          Early Watch Alert Reports
Avnet Global Solutions         >>>> here i have configured the PR1, PB1 PCB instances
PR1                                      >>>>>here i configured the only PR1 instance.
so i have configured the same instance in two solutions.
i am not gettting the early watch report automatically after after configuring like this . but manually working fine.
when i kick of the report manually working fine.
here my question is ... do i can create two early watch reports in one solution manage for same instance or not. if yes then why i am not getting report automatically.
Thank you
Vish

Dear Paul,
Thank you for your response
this is what i got from SAP.
Hello Vish,
You can have the same system in different solutions. With regards
to why the report is not generating automatically, please review
SDCCN on the satellite system.
I dialed into the system and found that the SDCCN for PB1 is not
downloading the sessions from Solution Manager.
I would recommend that you deactivate and then activate SDCCN.
Tcode SDCCN -> GoTo - Settings - Task Processor - Deactivate
Tcode SDCCN ->Utilities -> Activate
Then create a Refresh Session task and verify if the upcoming sessions
are getting pulled down to PB1.
If you need help with this, please let me know if it is fine with you
if I make the necessary changes to get the system working.
Thank you in advance and best regards,
Jared Singh
SAP Active Global Support - Netweaver Web Application Server
could i know your comment

Earlywatch On 4.6B with No Solution Manager

Hi all,
We are running a 4.6B with no solution manager installed. Is there any possible way to do the early watch without Solution manager?

Sorry,
But you have to do your own part of the work or you will never learn anything.
Don't ask to be spoon fed.
Use the SAP standard menu, experiment and you will find all the needed transactions by yourself...
Regards,
Olivier

Solution Manager EWA - cannot create session in satellite system

"Hi,
I want to configure EWA self service using Solman 4.0. I succesfully did the following :
a. Maintained SMSY and create the required trusted RFC connections from SM to satellite system. All connection and authorization passed in SM59. I used SAP_ALL/SDCCN_ALL role and assigned objects S_RFC*.
b. Assigned the system to a logical system.
c. Created the a new solution and activate "Solutions Monitoring > Earlywatch Alert"
d. Activated and maintained required RFC in SDCCN in satallite system.
My problem is that the create EWA alert request (Red Flag with a specific session number ) coulnd be pass to the satelitte system even though all the trusted RFC and authorization is set. When i execute the SESSION_REFRESH in the satellite system, the session is not created.
Did I miss out any steps. Can any one share any help ?
FYI, there is no connection to SAPOSS yet, so i did not manage to run RTCCTOOL completed, but i doubt this is required for EWA self service."
I have the same problem as Solution Manager EWA - cannot create session in satellite system
tried all of solutions, but it does not help... Created the CM (high) for SAP, but get 1 response for 1 week from them:(

Dear Sapbcer,
Have you tried the following option :
Execute SMSY and from the Server entry Execute the "Read System Data Remote" option in change mode.
Save the data captured and then try using Refresh Session Task from SDCCN of the satellite system. Do select the RFC for Solution Manager while performing this task.
Hope this helps.
Regards
Amit

Solution Manager does not get service definitions from SAP in self diagnosi

Hi,
In our production solution manager transaction solution_manager, self diagnosis we are getting a warning message on our development solution manager.
Solution Manager XXX does not get service definitions from SAP.
The production Solution Manager is the master in SDCCN for the test Solution Manager. In the test Solution Manager, the scheduled task REFRESH SERVICE DEFINITIONS has task System ID of O01. It is pointed to RFC destination SDCC_OSS, not the production Solution Manager system.
It gives the same warning if I point the task to the production Solution Manager system.
Has anyone seen this before? Any ideas?
Best regards,
Russ

Hi,
i guess have you activated SDCCN from your solution manager system too?
if not please activate. since that setup helps solman retrive the service definitions used in SDCCN from SAP (SAPOSS).so this ultimately allows you to set solution manager system as Master, so all the satellite system get the service definition from solman and do not need a direct SAPOSS connection.
and Please check this Note 1143775 - SAP service content update
the wiki for trouble shoot ["EarlyWatch Alert is Red Flagged - how to resolve" |http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=228262728]
please check.
Thanks,
Jansi

Issue in configuring EWA using solution manager

Hi
I am configuring the Early watch alert for my ECC system, I am facing couple of issue in it.
Soultion manager version 7 with SP14.
1. not able to see Setup EWA tab in Solution setting under Solution directory
2. I am not able to activate system under CCMS Monitoring of EWA in solution setting under solution directory, it does not give any error.
3. I dont see "Early watch Alert" service option when i try to create service under solution monitoring -> EarlyWatch alert -> create new service session
Also like to know the difference between Early watch alert for solution and EarlyWatch alert. In my one of the solution i can see both option and allowing me to create the same.
Regards,

Hi Rajesh,
Have you setup your Solman system as a master system in the remote ECC system in SDCCN? i am still struggling to understand and get EWA working but i have managed to get EWA report for my ECC test system but not Solman itself.
Have a look in SMSY to see if your systems are in a green box, if they are then monitoring is activated for that system then you should be able to see that system in DSWP when scheduling EWA processing.
Also have a look at OSS Note 1257308 - FAQ: Using EarlyWatch Alert. there is a PDF file which shows how to setup EWA according to best practice.
regards,
Mandeep

Abour Solution Manager RFC connection

Hi, All
About soulation manager 4.0, I got configuration guide to setup "Real time system Monitoring"
as per user guide -> create RFC connection and setup system monitoring, it make me little bit confousing
currently Solution manager setup for earlyWatch report and works fine.
WHAT I WANT ?
To seutp/configuration "REAL TIME SYSTEM MONITORING" for XI 3.0 and CCMS monitoring in Solution manager
T-code: SMSY shows this screen:-
There are 5 different types of Tab after apply SMSY
1. Landscape Components
2. Database
3. System Group and Logical Components
4. Product Definitions
5. Overview
I am not sure where I create RFC connection and what value will i put in it?
1. Landscape components shows under: all others server name list
   SERVER
     shows server host name: (r5wxw0) and right side windows shows
     data source RFC
     and Technical Data Tab shows all others value (that system I like to monitor)
2. DataBASE (all others application server name)
     IDV
       Header Data Tab
       Data Source: TMS/RFC
3. System Group and Logical Components (under)
   Project Landscapes
   Solution Landscape - operation
   Logical components
4. Product Definitions (under)
   lot of product list
5. Overview
     Server
     Database
     Systems
Now where sould I go to configure CCMS monitoring ?
Thanks in Advanced
Travis

Hi user issue2008 issue
actually i can't connect to solman, but i think it was under 3.
When you select a component, i.e. Dev R/3 or so you should have several clients.
There you can define RFCs and also there you can define Solution Monitoring.
But I think there should be already RFC-Destinations, when you had configured the EWA.
Then you should check the client with the RFC-Destination and Checking Destination.
In Edit-mode you can check the box for Solution Monitoring and save and ok.
After that it should be activated.
Hope it helps you.
Regards,
René

System Monitoring Setup in Solution Manager

Hello Experts,
We are going to implement and configure Solution Manager - System monitoring setup for pre testing purpose
Currenly we have installed below SAP Systems
1.Solution Manager Server
2.ECC server (Without Ides) - Abap
3.CRM Server (Without Ides) -Abap + Java
We need to setup below tasks in Solution Manager
1.Early watch alert
2.System Monitoring
3.Central System Administration
4.Business Process Monitoring
5.Service Level reporting
1.Is it possible to setup the solution manager -above mentioned tasks without Ides system ?
Could you please someone give input reg this.
Thanks
Thirumal
Edited by: Thiru Thirumal on Aug 6, 2008 4:56 AM
Edited by: Thiru Thirumal on Aug 6, 2008 4:57 AM

Hi,
Q. Is it possible to setup the solution manager -above mentioned tasks without Ides system ?
A. Yes.
Check with links for
1.Early watch alert
This process helps you to identify potential problems early, avoid bottlenecks, and monitor the performance of your ABAP and JAVA systems and your most important business processes, regularly, automatically and effectively. The data collection infrastructure comprises the ABAP Service Data Control Center and the JAVA function module Data Provider. The SAP EarlyWatch Alert in the SAP Solution Manager is a service provided by SAP.
To be able to use it, you have:
maintained the non-ABAP systems correctly in the system landscape maintenance (transaction SMSY)
RFC u2013 Connections between: and an RFC u2013 Connections established.
your satellite systems and the SAP Solution Manager system
SAP Solution Manager and the SAP Service Marketplace
Solution Manager system and Solution Manager Diagnostics
Cf: Solution Manager IMG (transaction SPRO).
checked the availability of the tools required for the SAP Service sessions (add-on ST-A/PI), with the report RTCCTOOL.
activated Alert Monitoring and set-up the Automatic Session Manager (ASM) in the Service Data Control Center (SDCCN) of your satellite systems, for all SAP satellite systems and the central SAP Solution Manager of your solution
set-up your systems in a solution landscape in the SAP Solution Manager
configured Solution Manager Diagnostics
2.System Monitoring
The system monitoring in the SAP Solution Manager is, as described above, like a system-wide central CCMS. It can also contain the central CCMS (CEN) of satellite systems. These CENs can then monitor other components.
The graphical display in the SAP Solution Manager gives you access to the alerts of all systems in a solution. You can go to the local or central CCMS of the satellite systems.
The system proposes the most important alerts in the CCMS monitor collection, according to SAP experience, and their alert thresholds, for each system in the solution, in the system monitoring Session. You can activate or deactivate these alerts. The connection between the local CCMS and the SAP Solution Manager allows you to maintain the alert thresholds directly in the SAP Solution Manager, overwriting the values in the local CCMS.
3.Central System Administration
You activate the customizing for business processes in your solution, in the Business Process MONITORING session in the SAP Solution Manager. A monitoring tree element (MTE), or a monitor collection, u201EBPMu201C of several monitoring objects, is created in the local or central (CEN) CCMS of the satellite system.
The data is collected for the monitoring types of the business process monitoring in contrast to system monitoring, as follows:
● The system collects performance (dialog transactions), posting cancellations (V1 and V2) and u201EOther CCMSu201C and interface data, in the local CCMS of the satellite systems.
● The system collects background processing, application list, application monitors, delivery lists, and document size data, in the central SAP Solution Manager CCMS.
The SAP Solution Manager system copies the data from the local CCMS.
The graphical display in the SAP Solution Manager simplifies access to the alerts for the business processes, business process steps or the interfaces between the systems in a solution. You can go to the local CCMS of the satellite systems.
The connection between the local CCMS and the SAP Solution Manager allows you to maintain the alert thresholds directly in the SAP Solution Manager. These overwrite the values in the local CCMS.
4.Business Process Monitoring
The system and business process monitoring (including interface monitoring) in the SAP Solution Manager, both use the Computing Center Management System (CCMS) (transaction RZ20) architecture. This means that system alerts which occur in the local CCMS, are passed to the SAP Solution Manager via RFC connections between the SAP Solution Manager and the satellites. The system shows these alerts in a graphic or in Sessions. You can also handle the alerts centrally, without having to go to the local CCMS of the satellite systems.
You can see the alerts from several systems in a solution landscape in the SAP Solution Manager, in a graphical overview, in contrast to the local CCMS of the SAP Solution Manager satellite systems. This is the view of a central CCMS (CEN). You can also monitor non-SAP systems in a central CCMS (CEN) of a satellite system
5.Service Level reporting
http://service.sap.com/solutionmanager for all solman tasks as given below.
http://www.asap.net.cn/homepage_en/Solution%20Manager%20EN.pdf
http://help.sap.com/saphelp_sm32/helpdata/en/1b/f02c41ab78f66fe10000000a1550b0/content.htm
http://help.sap.com/saphelp_sm32/helpdata/en/9f/1f46570f8a4a268b3154e0e0f07280/content.htm
Regards,
Srini Nookala

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.

FAQ - SAP Solution Manager for VARs

You can find further technical questions around configuration & functionalities in a comprehensive
FAQ to SAP Solution Manager for VARs.
This FAQ covers questions and answers around:
    > SAP Solution Manager, enterprise edition
    > SAP Solution Manager VAR setup: configuration of Service Desk
    > Work Center Service Desk: functions & configuration
    > Work Center System Monitoring: setup of SAP EarlyWatch Alert
You can access the FAQ directly thru the following link [FAQ - SAP Solution Manager for VARs|http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000722612&_OBJECT=011000358700000490172009E].
Navigation path: SAP Service Marketplace > SAP Support Portal > SAP Support Infrastructure > SAP Solution Manager > SAP Solution Manager for Partners > Information for Service Provider > Training and HowTo Documents > Administrator
Please notice: The FAQ will be updated from time to time.
Edited by: Susanne Schlehf on May 4, 2009 2:48 PM
Edited by: Susanne Schlehf on May 18, 2009 12:56 PM

Hello Richard,
(1) regarding network connections see document [Draft:Technical Support Network Connections for VAR Scenario|http://service.sap.com/~form/sapnet?_SHORTKEY=00200797470000089947&_OBJECT=011000358700000880802009E] as overview and with a lot of detailed information.
(2) yes, you have to setup once all your customer connections at the beginning but then only add/remove with customer contract changes
(3) the workaround by sending by email can handled a anexception. EWA has to be done for productive systems like nowadays done by SAP. Additional EWA services could meas additional business case for a VAR - that's contract between VAR and customer.
(4) whatever you think may be a business to sell - do it ! (and get a monetary bonus from your boss
Kind regards
Heinrich

Solution Manager EarlyWatch

Similar Messages

Maybe you are looking for