Solution Manager 4.0 - RFC Connections

hi there,
While ago I configured all my RFC connections within Solution Manager 4.0, and wanted to make sure what are those for:
1. RFC BACK connection (SM_<SID>CLNT<Client no.>_BACK) is used for the SDCCN to collect the session data. But I realized it is also used for Service Desk when users attempt to create support messages from the satellite system. Is this OK?
2. The other RFC connections (SM_<SID>CLNT<Client no.>_LOGIN, SM_<SID>CLNT<Client no.>_READ, SM_<SID>CLNT<Client no.>_TMW, SM_<SID>CLNT<Client no.>_TRUSTED) I am not sure whether they are used and where.
Can somebody please give me a light in this matter? because I think this is bringing me issues in other solution manager features :-S
Thanks a lot.
regards
Katia.

Hi there again,
Thanks very much. It is more clera; just one last question. Then what RFC destination should I use in my satellite system, the one: SM_<SID>CLNT<Client no.>_BACK or SM_<SID>CLNT<Client no.>_TRUSTED ?
And using one of those, with no log on screen option, would make me add the corresponding user profile (for example for create support messages) to the user inserted in such a RFC connection in the "logon data" tab right?
I am using now SM_<SID>CLNT<Client no.>_BACK withtout log on screen option, and the user which is inserted in this RFC connection has the appropiate profiles, but message are created incomplete (I got this error message: "error in local system, message 0000165 incomplete"). I can see those messages from DNOTIF transaction but not from transaction monitor...
How you do this? Because it used to work using same RFC connection (SM_<SID>CLNT<Client no.>_BACK) but with log on screen, so the user was prompted for logging and messages were created succesfully; but then since this rfc connection is also used by SDCCN the data was not being collected, since the log on was required :-S
That is what I changed to no log on screen, and got confused about these RFC connections thing...
Do you have an idea about this?
And thank you very much in advance again.
regards,
Katia.

Similar Messages

Solution manager maxdb 7.6 connection problem

Hi,
after SSm installation, the ssm instance is up and I can work in solution manager system, but if i try to do transport or if I try to connect with Maxdbclinet to db I receive the following connection error:
ERROR => Connect to database failed, rc = -10709
(Connection failed (RTE:cannot create communication semaphore))
Someone can help me
Thanks in advanced
Marco

Hi,
Sorry Marco, here we go,
https://forums.sdn.sap.com/click.jspa?searchID=-1&messageID=928337
Feel free to revert back.
--Ragu

ERROR while CREATING RFC FOR SOLUTION MANAGER DIAGNOSTICS

Dear all,
Hi,
I am configuring solution manager 7.0.
In SPRO>basic setting >operation>solution manager diagnostics > create RFC for solution manager diagnostics i am getting this error
program WEBADMIN not registerred.
can any one tell me how to register this program in sap gateway.
best regards
azeem

Hi Azeem,
Just before creating the rfc connection do this step.
Set-Up Solution Manager Connection to Solution Manager Diagn
Use
Check the connection to function Solution Manager Diagnostics.
Default Settings
The function Solution Manager Diagnostics is installed on the Java instance of the Solution Manager system by default.
Activities
If the default values are correct, save the settings.
To run the Solution Manager Diagnostics in another system, enter the required data and save.
Also check that your java is active.
Regards
Ashok

Multiple Solution Manager Connectivity to 1 Satellite system

HI..
I have a requirement. There is already an existing landscape with solution manager ECC, BI etc. The solution manager is configured for EWA, Maintenance optimizer etc. I now have to install a new solution manager and connect it to the same set of satellite systems so that I receive the EWA, configure MOPZ again. Will this create any kind of a problem and technically how can we do it? I have two ideas for this scenario
1. Connect the new solution manager to the same satellite systems and do configuration as normal. Got this idea from the below link but not sure how it will work.
Re: send EWA report to more than one solution manager
2. Is it possible to push data from the existing solution manager to the new solution manager?
Would highly appreciate technical suggestions. Thx in advance for your help.

Hello,
You need the SMD Agent in order to have ABAP data going to the Solution Manager. Some RFCs are established directly from Managed System to the Solution Manager to extract E2E Change Analysis, Exception Analysis. The Workload Analysis and Host Information (SAPOSCOL) is extracted from WIly EM
Having that said, you can imagine that you cannot have only RFCs and you cannot have only data extracted from WIly EM.
I suggest you to take a look at the FWK Administration in the solman_workcenter, choose the Managed System tab, and start looking into the details of each extractor. Some have an RFC destionation, others have SOLMANDIAG. The SOLMANDIAG are coming from the Solution Manager Java stack, which is responsible to poll the Wily EM.
The reason you need two SMD Agents is because the SMD Agent connects to the ABAP stack, retrieves data, and then connects to the Wily Enterprise Manager. The Solution Manager polls data from the Wily EM and persists it in the BW.
The SMD Agent doesn't support connecting to two Wily EMs at the same time.
So it is required to have TWO SMD agents polling data from the ABAP stack, at the same time, one of them reporting to one Wily EM, and the other reporting to the other Wily EM.
Each solution manager has it's own Wily EM, and it will pull the ABAP data from the Wily EM.
It is not possible to make the two Solution Manager's connect to one Wily EM, since the setup framework needs to see a SMD Agent available to run the setup wizard and to create the destinations. So each Solution Manager needs a SMD Agent running in the physical host.
I hope it is clear for you.
Best regards,
Guilherme
Edited by: Guilherme Balbinot on Feb 6, 2012 9:44 PM
Edited by: Guilherme Balbinot on Feb 6, 2012 9:49 PM

Using more than one Solution Manager for different usages

Dear all,
we are using a solution manager system with >100 connected systems.
The system should primarily be used as service desk system, but is also used for BC issues (e.g. MOPZ,...) at the moment.
We have to implement a central monitoring system (CEN) using the CCMS infrastructure.
It is recommended to use a seperate system for this issue, because of high performance requirement and the requirement to have the newest support packages for CEN+MOPZ.
Because of that recommendation we are thinking about installation of a second solution manager system which should handle all BC and Monitoring (CEN+SolutionManager-Monitoring) issues.
Do you have any experience with such a landscape? Are there known problems respectively is such a landscape possible/workable? How should the systems be connected? ( client system<=>solman / solman<=>solman )
I regret that I could not find any official landscape recommendations from SAP for big landscapes (VAR environment)?
If you know any applicable documents, please let me know.
Thank you for your help.
Best regards,
Sascha

Hi Sascha
Technically Solution Manager is being billed as the Central system for everything Service Desk, MOPZ and CCMS - one central location for all scenarios
One of the reasons for this is lifecycle management -- monitoring or EWA scenario finds a problem, service desk raises the issue, charm or mopz implements the solution and it is tested and distributed and the whole lifecycle is documented one system. Indeed I am aware of no functionality to integrate scenarios between Solution Manager systems - each Solution Manager system in your proposal will be standalone for each scenario
I can't provide guarantees because SAP recommend 1 Solman PRD only, but it might be possible to use another PRD Solution Manager system (or client) for scenarios that not already setup in the existing Solution Manager system - this certainly is the most possible way to have 2 PRD Solution Manager systems (or clients) running in parallel.
The key thing to be aware of is RFC conflicts - as each scenario usually has its own RFC this might be avoided - however
do watch out for situations where scenarios share RFCs or you if find RFCs existing with the same name OR client and SID in any systems in the following landscape
Landscape 1 - Satellite System 1 to Solman System 1 Service Desk, MOPZ
Landscape 2 - Satellite System 1 to Solman System 2 CCMS, EWA
Best wishes
Stuart

Solution Manager information for Java stack systems

Hi,
Could someone please help with the setup of Solution Manager, and how to connect to the backend of a Java stack system. For our ERP systems this is working via RFC, but I was hoping to get more information on the procedure for java. I can specify manually via SMSY, but I am sure there must be a setup that can pull the information for the system itself. Could anyone shed some light on this if possible please.
Regards,
Chris

Dear Chris,
ABAP Stacks use RFC as you know for inter system communications.
Java stack systems use Solution Manager Diagnostics.
You will need to run Solman_Setup > Managed System Configuration
First you should visit the link http://service.sap.com/diagnostics
There you will see a link to the media library, and there you will find complete documentation.
Hope you find this information Helpful.
Regards,
Paul

Establishment of the RFC-connection

Hi!
I am about to set up the RFC connection to SAP system from SAP Solution Manager.
The following connection between the systems/server was configured:
my server --> SAP Router 1 --> SAP Router 2 --> SAP System
How should the RFC-connection look like?
The errors I getting are:
Logon                     Connection Error
Error Details     Error when opening an RFC connection
Error Details     ERROR: timeout during allocate
Error Details     LOCATION: SAP-Gateway on host on host dzla9005 (wp 1)
Is there some special SAP notes for that issue?
Thank you very much!
regards

Hello Thom,
Facing the same issue.
Did you solve it ?
Regards,
Gidion

Why do we install Solution Manager on Different Server

Hi Everybody,
Please if anybody can help in clearing the doubt that why it is advisable to install Solution Manager on Different Server.
Thanks in advance!!
Pawan

Thanks Juan. Got the answer.
Infact i was reading somewhere and got these points -
SAP Solution Manager is designed to run in a central u2018monitoringu2019 system at the customer site where all other SAP systems and mySAP solutions (satellite systems) are connected:
u2022 The entire Solution Landscape can be documented (u2018living documentu2019) in a central system (in fact several Solution Landscapes can be managed)
u2022 SAP and Non-SAP Systems can be modeled
u2022 All core business processes can be graphically assigned to all available productive systems in a solution landscape
u2022 All connected SAP systems can be monitored by the central SAP Solution Manager system
u2022 Satellite systems submit data via RFC / agents into the central system
u2022 The system with the SAP Solution Manager installed has a connection to SAPNet R/3 Frontend and the SAP Service Marketplace to communicate with SAP Support Back Office
The SAP Solution Manager serves as a platform that includes several features in one application. The strength of the SAP Solution Manager is the strong integration into the mySAP.com Solution and the optimal knowledge transfer SAP-Partner-Customer including central monitoring features, mainly focusing on core business processes. However, additional features and tools (Support Desk, SAP Note Assistant, MS NetMeeting,u2026) that are integrated in the SAP Solution Manager, also play important roles within a customeru2019s solution management.
It is important to understand that it is not necessary or useful to always have all integrated SAP Solution Manager components installed on one system. For example it is possible to install the SAP Solution Manager on one system and connect to another System where the Support Desk is installed. The SAP Solution Manager then only serves as a portal to jump to the included Support Desk system without notice.
If the customeru2018s main focus is the management of core business processes through service roadmaps and monitoring via SAP EarlyWatch Alert, Service Level Management (reporting) and so on, SAP recommends the SAP Web Application Server as the best choice for the SAP Solution Manager installation as it is also the platform for the SAP Solution Architect and has fairly small hardware requirements.

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.

Can i use Solution manager ADS for ECC6 ABAP

Dear All,
We have landscape of ECC6 ABAP (Dev, Qua, Prd), can i install and configure ADS on Solution manager(ABAP+JAVA) and connect all Dev , qua and prd to same solution manger for Adobe interactive forms. is it possible ?
for production environment?.
Regards
Vinay

Hello!
This was already discussed. E.g. here ADS install in Solution Manager.
While it is technically possible (to connect several systems to one ADS) it is not recommended for productive environment for some reasons (security, stability, performance and easy of maintenance). I say you can use you ADS on SolMan for DEV, QAS and number of your training/demo systems, but install separate J2EE with ADS instance (better on separate server) for productive use. You can then check ADS updates/patches on SolMan first without breaking productive system and only then (if successful) update productive.
Regards,
Petr Perstnev

Solution manager and CCMS monitoring of remote database

I have Solution Manager 7 SP Basis 6 installed. I have oracle remote databases connected successfully. Under DBCockpit I see the instances I want to monitor. I can see the backup, tablespaces, etc. These remote instances are SAP Portal JAVA only version 7 but under the dbcockpit alerts only shows alert monitor. The database check and check conditions are in white. Is there a way to see these and be able to report on them? The CCMS tree under the local solution manager also shows these connected remote instances but they are also white in color as if inactive. All CCMS agents and saposcol are running perfectly on the remote systems. The stats tables have been built, the synonyms for the solution manager are in place. What am I missing?

Hi,
Please download that attachment "scripts_1139623.sar" provided in SAP Note 1139623 - Using transaction RZ20 to monitor remote Oracle databases.
Upon extraction of scripts_1139623.sar the following files you will get.
rz20_nonabap.sql
dbcheckora10_oltp.sql
dbcheckora.sql
Then Perform the below mentioned Steps to resolve your issue.
Step 1: Create tables DBCHECKORA and DBMSGORA:
sqlplus SAPSR3DB/<pwd>
SQL> @rz20_nonabap.sql
Step 2: Fill the table DBCHECKORA:
sqlplus SAPSR3DB/<pwd>
SQL> @dbcheckora10_oltp
Step 3: Create the synonyms (as user ora<sid>):
brconnect -u / -c -f crsyn -o SAPSR3DB
sqlplus "/as sysdba"
CREATE PUBLIC SYNONYM SAP_DBSTATC FOR SAPSR3DB.DBSTATC;
CREATE PUBLIC SYNONYM SAP_DBCHECKORA FOR SAPSR3DB.DBCHECKORA;
CREATE PUBLIC SYNONYM SAP_DBMSGORA FOR SAPSR3DB.DBMSGORA;
Step 4: Grant Privileges for OPS$<SID>ADM User for the above created Tables
sqlplus "/as sysdba"
grant all on SAPSR3DB.DBSTATC to OPS$<SID>ADM;
grant all on SAPSR3DB.DBCHECKORA to OPS$<SID>ADM;
grant all on SAPSR3DB.DBMSGORA to OPS$<SID>ADM;
grant all on SAPSR3DB.DBSTAIHORA to OPS$<SID>ADM;
grant all on SAPSR3DB.DBSTATHORA to OPS$<SID>ADM;
grant all on SAPSR3DB.DBSTATIORA to OPS$<SID>ADM;
grant all on SAPSR3DB.DBSTATTORA to OPS$<SID>ADM;
commit;
Step 5:
Now after successful execution of above mentioned Steps , in DBACOCKPIT (system configuration), try to save the Remote DB entry with "Collect Alert Data". It will be saved without any error.
If you find any errors, post the error contents as a reply of this thread message.
Regards,
Bhavik G. Shroff

BI & Solution Manager

Dear Expert,
We are in review of using the BI with solution manager.
I get to know that we have 2 options:
1. to use BI content that come with SAP solution manager (in different client)
2. to connect Solution Manager system to another NetWeaver BI system
Which option is the best, any impact on BI system, performance, system resource?
please advise.
thank you

Hi SH,
thank you for the reply.
Is there any guide that I can refer to setup the BI client in solution manager step by step?
e.g. what to activate in BI client of solution manager, how is the connection suppose to configure, Solution manager as source system for BI client, etc etc.
The SAP Library unfortunately do not contains the technical information that I need.
thank you very much

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é

RFC Connection Problem between Production Server & Solution Manager

Hi,
I want to make a RFC Connection between Production Server & Solution Manager.
But when go through Tcode- SM59 and click on Remote Logon from Production to connect Solution Manager it showing me a Client/Userid/Password window and when i connect go through Solution Manger to Production Server it connects normally. I already done the same process in both the clients, as i already mentioned Logon details in the Logon/Security tab but why it is showing me Client/Userid/Password pad when i am login through Production to SolMan?
+Tell me where the actual problem is! In my Solution Manager end or in my Production Server end +
I want to access Solution Manager from Production Server on just clicking once on Remote Logon from Tcode- SM59.
Thank you.
Edited by: varun@pcl on Jul 31, 2010 4:40 PM

Hi
Mention which Client u login and valid username and password from both PROD Server and Solman .
https://websmp201.sap-ag.de/support under Solman manager .
https://websmp201.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000633637&
Regards

EWA RFC connection SETUP - From Customer system to VAR solution Manager

Hi,
we are going to setup the EWA for our customers. So how I have to create the RFC from the customer system to our Solution Manager?
Thanks
Andrea

>
Andrea Taccolini wrote:
> we are going to setup the EWA for our customers. So how I have to create the RFC from the customer system to our Solution Manager?
Hi Andrea,
Have you already tried to use SMSY to generate the "Back" Destination from customer system to your SolMan?
Once you have selected the customer system in SMSY, you are able to use the RFC connection wizard.
Alternatively, you can define the RFC destination manually.
For easier tracking and trouble shooting, I would recommend to setup a communication user in your SolMan for each individual connected managed customer system.
Assign the appropiate profiles to the user in your SolMan system and create the RFC destination in the managed customer system.
Best regards,
Ruediger

Solution Manager 4.0 - RFC Connections

Similar Messages

Maybe you are looking for