System monitoring configuration in solution manager EHP1

Hi all
I am in a bit of fix
We have upgraded our solution manager devlopment to EHP1
Now I have added one system through SMSY in solution manager to configure system monitoring
I have generated all the RFC's,I have created the logical component and solution and assigned the system to the solution
When I check my solution it is looking fine
Now when I go within solution and click on the tab system monitoring
It shows me on the left hand side -> Set up system monitoring
when I click on Set up system monitoring on the left part of SAP screen,strangely it doesnt take me to the activation of screen monitoring,it just shows me the best practices documents on the right side but nothing more than that
I have checked many guides,blogs and SAP tutors anfd have followed them but strangely I am not been able to go to the screen for activating system monitoring
Are there any activities that need to be done after upgrading to EHP1?
Are there any services to be activated for system monitoring?
Please advice
Rohit

I'm not 100% sure that it is necessary, but it won't hurt.
Perhaps the essential adjustment you need for system monitoring is being done in there.
It won't hurt

Similar Messages

Solution Monitoring configuration with solution manager 4.0

Hi Friends,
I have to the Solution Monitoring configuration with solution manager 4.0.
Please provide steps or screen shot if any body having that.

Hi,
Check <a href="https://websmp108.sap-ag.de/sapidb/011000358700005479192006E.sim">this.</a> and <a href="https://websmp108.sap-ag.de/sapidb/011000358700006936062005E.sim">this</a>.
This will solve your problem.
Feel free to revert back.
--Ragu
Message was edited by:
Raguraman C

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

System Monitoring error in Solution Manager 4.0

Hi All,
I am configuring "System Monitoring" in Solution Manager 4.0.
I have successfully added satellite system through SMSY
as well as i have added system to the Logical Component, but when i open tcode solution_manager i am getting error Action Cancelled Internet Explorer was unable to link to the Web page you requested
ICM is running and I have also activated several services from SICF.
Please guide me in this scenario.
Points will be awarded
Thanks
Sachin

Hi,
Follow the below steps
1) Maintain the host file
Details of Solution manager in the following format
ipaddress host name fully qualified name
2) Internet explorer
Tools--> Internet options --> Connections --> Advanced settings
Maintain the bypass proxy there.
Since you are using GUI 710 your IE should be compatable. use IE 7.
If this answers your query, change the status of thread as Answered
regards
Naveen

A problem about system monitoring/administration of solution manager

Dear experts:
When I use solution manager system to monitor other systems, a strange phenomenon appears,that is I canu2019t open the detail log .anyone who can tell me why I can't open the alert? thanks

the problem has been solved,thanks

System Monitoring with Solution Manager Ehp1

Hi,
I'm Tomas Piqueres, and I'm working in a VAR SAP with Solution Manager.
Recently, we installed Solution Manager Ehp1 and we are trying to configure it for System Monitoring. When I worked with Solution Manager SP17 I used to go to transaction RZ21 to add the system I wanted to monitoring and then put the SID and RFCs of the system.
Now with Solution Manager Ehp1, when I create the system in transaction RZ21, first I have to set the Component Type to Be Monitored and then the SID, Message Server Logon Group, the client and user are set automatically, and the password I've set to user CSMREG.
when I fill all the entries, I can see the RFCs used for the monitoring of the system. Those RFCs are set automatically:
<SID>_RZ20_COLLECT
<SID>_RZ20_ANALYZE
I can't edit those RFCs, so I have to create it manually. I check that RFCs destination works fine and both pass the authorization test, so when I try to save the system at transaction RZ21, I see the following errors:
<SID>_RZ20_COLLECT_123539Error when opening an RFC connection
Error during remote call of SAL_MS_GET_LOCAL_MS_INFO function: Error when opening an RFC connection
Error during remote call of SALC function: Error when opening an RFC connection
Error during remote call of RFC1 function: Error when opening an RFC connection
I've been looking for information about those errors and how to monitoring with Solution Manager Ehp1, but I haven't found anything usefull.
Please, Could you help me?
Thanks and regards,
Tomas.

Tomas,
I need to configure EWA from my Solman system and I completed the steps (defining and creation of RFC destinations to the target systems from my Solman system). I downloaded the lates ccmsagent file from the market place based my target system configurations.
Herewith attaching the logs while I'm trying to check the profile parameter.
tqaadm@saptqa01:/usr/sap/TQA/SYS/exe/run 5> sappfpar check pf=/usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
================================================================================
== Checking profile: /usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
================================================================================
***WARNING: Unexpected parameter: DIR_EPS =/usr/sap/trans/EPS/----
***WARNING: Unexpected parameter: SAPSECULIB =/usr/sap/TQA/SYS/exe/run/libsapsecu.o
***WARNING: Unexpected parameter: abap/buffersize_part1 =1200000
***WARNING: Unexpected parameter: auth/auth_number_in_userbuffer =5000
***WARNING: Unexpected parameter: dbs/io_buf_size =100000
***WARNING: Unexpected parameter: rsau/local/file =/usr/sap/TQA/DVEBMGS30/log/audit/audit_++++++++
***WARNING: Unexpected parameter: rsau/selector1/class =35
***WARNING: Unexpected parameter: rsau/selector1/severity =2
***WARNING: Unexpected parameter: rsdb/rclu/cachelimt =0
***ERROR: Size of shared memory pool 40 too small
================================================================
SOLUTIONS: (1) Locate shared memory segments outside of pool 40
 with parameters like: ipc/shm_psize_<key> =0
SOLUTION: Increase size of shared memory pool 40
 with parameter: ipc/shm_psize_40 =1472000000
Shared memory disposition overview
================================================================
Shared memory pools
Key: 10 Pool
 Size configured.....: 642000000 ( 612.3 MB)
 Size min. estimated.: 637597428 ( 608.1 MB)
 Advised Size........: 640000000 ( 610.4 MB)
Key: 40 Pool for database buffers
 Size configured.....: 1048000000 ( 999.4 MB)
 Size min. estimated.: 1468229308 (1400.2 MB)
 Advised Size........: 1472000000 (1403.8 MB)
Shared memories inside of pool 10
Key: 1 Size: 2500 ( 0.0 MB) System administration
Key: 4 Size: 523648 ( 0.5 MB) statistic area
Key: 7 Size: 14838 ( 0.0 MB) Update task administration
Key: 8 Size: 67108964 ( 64.0 MB) Paging buffer
Key: 9 Size: 134217828 ( 128.0 MB) Roll buffer
Key: 11 Size: 500000 ( 0.5 MB) Factory calender buffer
Key: 12 Size: 6000000 ( 5.7 MB) TemSe Char-Code convert Buf.
Key: 13 Size: 200500000 ( 191.2 MB) Alert Area
Key: 16 Size: 22400 ( 0.0 MB) Semaphore activity monitoring
Key: 17 Size: 2672386 ( 2.5 MB) Roll administration
Key: 30 Size: 37888 ( 0.0 MB) Taskhandler runtime admin.
Key: 31 Size: 4806000 ( 4.6 MB) Dispatcher request queue
Key: 33 Size: 39936000 ( 38.1 MB) Table buffer, part.buffering
Key: 34 Size: 20480000 ( 19.5 MB) Enqueue table
Key: 51 Size: 3200000 ( 3.1 MB) Extended memory admin.
Key: 52 Size: 40000 ( 0.0 MB) Message Server buffer
Key: 54 Size: 20488192 ( 19.5 MB) Export/Import buffer
Key: 55 Size: 8192 ( 0.0 MB) Spool local printer+joblist
Key: 57 Size: 1048576 ( 1.0 MB) Profilparameter in shared mem
Key: 58 Size: 4096 ( 0.0 MB) Enqueue ID for reset
Key: 62 Size: 85983232 ( 82.0 MB) Memory pipes
Shared memories inside of pool 40
Key: 2 Size: 31168040 ( 29.7 MB) Disp. administration tables
Key: 3 Size: 114048000 ( 108.8 MB) Disp. communication areas
Key: 6 Size: 1064960000 (1015.6 MB) ABAP program buffer
Key: 14 Size: 28600000 ( 27.3 MB) Presentation buffer
Key: 19 Size: 90000000 ( 85.8 MB) Table-buffer
Key: 42 Size: 13920992 ( 13.3 MB) DB TTAB buffer
Key: 43 Size: 43422392 ( 41.4 MB) DB FTAB buffer
Key: 44 Size: 8606392 ( 8.2 MB) DB IREC buffer
Key: 45 Size: 6558392 ( 6.3 MB) DB short nametab buffer
Key: 46 Size: 20480 ( 0.0 MB) DB sync table
Key: 47 Size: 13313024 ( 12.7 MB) DB CUA buffer
Key: 48 Size: 300000 ( 0.3 MB) Number range buffer
Key: 49 Size: 3309932 ( 3.2 MB) Spool admin (SpoolWP+DiaWP)
Shared memories outside of pools
Key: 18 Size: 1792100 ( 1.7 MB) Paging adminitration
Key: 41 Size: 25010000 ( 23.9 MB) DB statistics buffer
Key: 63 Size: 409600 ( 0.4 MB) ICMAN shared memory
Key: 64 Size: 4202496 ( 4.0 MB) Online Text Repository Buf.
Key: 65 Size: 4202496 ( 4.0 MB) Export/Import Shared Memory
Key: 1002 Size: 400000 ( 0.4 MB) Performance monitoring V01.0
Key: 58900130 Size: 4096 ( 0.0 MB) SCSA area
Nr of operating system shared memory segments: 9
Shared memory resource requirements estimated
================================================================
Nr of shared memory descriptors required for
Extended Memory Management (unnamed mapped file).: 64
Total Nr of shared segments required.....: 73
System-imposed number of shared memories.: 1000
Shared memory segment size required min..: 1472000000 (1403.8 MB)
System-imposed maximum segment size......: 35184372088832 (33554432.0 MB)
Swap space requirements estimated
================================================
Shared memory....................: 2050.4 MB
..in pool 10 608.1 MB, 99% used
..in pool 40 999.4 MB, 140% used !!
..not in pool: 34.4 MB
Processes........................: 716.8 MB
Extended Memory .................: 8192.0 MB
Total, minimum requirement.......: 10959.2 MB
Process local heaps, worst case..: 1907.3 MB
Total, worst case requirement....: 12866.5 MB
Errors detected..................: 1
Warnings detected................: 9
After checking the profile parameter I tried to run sapccm4x in /run directory but got the below error and I'm not able tomove further.
Pls have a look at these two and let me know what could I do to proceed further.
tqaadm@saptqa01:/usr/sap/TQA/SYS/exe/run 5> sapccm4x -R pf=/usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
INFO: CCMS agent sapccm4x working directory is /usr/sap/TQA/DVEBMGS30/log/sapccm4x
INFO: CCMS agent sapccm4x config file is /usr/sap/TQA/DVEBMGS30/log/sapccm4x/csmconf
INFO: Central Monitoring System is [SMP]. (found in config file)
 additional CENTRAL system y/[n] ? :
INFO: found ini file /usr/sap/TQA/DVEBMGS30/log/sapccm4x/sapccmsr.ini.
INFO:
 CCMS version 20040229, 64 bit, multithreaded, Non-Unicode
 compiled at Jun 28 2010
 systemid 324 (IBM RS/6000 with AIX)
 relno 6400
 patch text patch collection 2010/1, OSS note 1304480
 patchno 335
INFO Runtime:
 running on saptqa01 AIX 3 5 00069A8FD600
 running with profile /usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
INFO profile parameters:
 alert/MONI_SEGM_SIZE = 200000000
 alert/TRACE = 1
 SAPSYSTEM = 30
 SAPSYSTEMNAME = TQA
 SAPLOCALHOST = saptqa01
 DIR_CCMS = /usr/sap/ccms
 DIR_LOGGING = /usr/sap/TQA/DVEBMGS30/log
 DIR_PERF = /usr/sap/tmp
INFO:
 pid 4165682
INFO: Attached to Shared Memory Key 13 (size 200141728) in pool 10
INFO: Connected to Monitoring Segment [CCMS Monitoring Segment for application server saptqa01_TQA_30, created with version CCMS version 20040229, 64 bit single threaded, compiled at Oct 3 2008, kernel 6400_20020600_254, platform 324 (IBM RS/6000 with AIX)]
 segment status ENABLED
 segment started at Tue Sep 14 09:35:56 2010
 segment version 20040229
ERROR: Shared Memory misconfiguration ==> can not monitor SAP application server saptqa01_TQA_30
 Dispatcher Admin Shared Memory (Key 01) and CCMS Shared Memory (Key 13) both in pool 10.
 Please change configuration with profile parameters
 ipc/shm_psize_01 = -<different pool nr>
 xor
 ipc/shm_psize_13 = -<different pool nr>
EXITING with code 1

Adding existing systems to a new Solution Manager 7.0 Ehp1 system

Dear Experts,
We've just installed a new Solution Manager 7.0 Ehp1 system, we have a 3 system landscape in action, please need your help to connect these systems with this new Solution Manager system. The post installation Initial Configuration and Basic Configuration has been performed successfully. Also need your help with Maintenance Optimizer configuration and setting up EWA.
Please do share experiences, links and documents for the above.
Thanks in advance,
Best Regards,
basis-novice

Page 65-67 of Netweaver EHP2 Upgrade Guide found in service.sap.com/instguides.
You can use the explanation below to configure MOPZ and maintain systems in SMSY.
4.5.2Configuration of the Maintenance Optimizer
You have to configure the Maintenance Optimizer. For a list of configuration tasks, see the Maintenance Optimizer Configuration Guide.
Make sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully.
Related Documents
Available at...Maintenance Optimizer Configuration Guide http://service.sap.com /mopz (link at the bottom of the page)
4.5.3Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape. Therefore you have to maintain this data in SAP Solution Manageru2019s system landscape (transaction SMSY). In the following, you will find the description how to maintain this data. If you already have maintained the system landscape data, then check if the data is correct.
If you use the System Landscape Directory (SLD), then use it to capture the system data.
If you do not use the System Landscape Directory (for example, if you have a pure ABAP system), you use RFC connections to maintain the data.
Procedure
Maintaining the System Landscape Data Using SLD
1.
Register both Java systems and ABAP systems that you want to update in your central SLD.
The central SLD can either be on your SAP Solution Manager system, or you can have a separate system where you run the SLD (central runtime SLD). If you use a central runtime SLD, make sure that it is synchronized with the local SLD of your SAP Solution Manager system.
4.5.3Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape. Therefore you have to maintain this data in SAP Solution Manageru2019s system landscape (transaction SMSY). In the following, you will find the description how to maintain this data. If you already have maintained the system landscape data, then check if the data is correct.
If you use the System Landscape Directory (SLD), then use it to capture the system data.
If you do not use the System Landscape Directory (for example, if you have a pure ABAP system), you use RFC connections to maintain the data.
Procedure
Maintaining the System Landscape Data Using SLD
1.
Register both Java systems and ABAP systems that you want to update in your central SLD.
The central SLD can either be on your SAP Solution Manager system, or you can have a separate system where you run the SLD (central runtime SLD). If you use a central runtime SLD, make sure that it is synchronized with the local SLD of your SAP Solution Manager system.
4.
Create an RFC connection
1.
Choose the Client tab for your system.
2.
Maintain at least client 000.
3.
Create an RFC connection between the Solution Manager and the system you want to update using the RFC Assistant.
5.
Start the data transfer
To initiate the remote transfer of system data from the target system, choose the Read System Data Remote.
RECOMMENDATION
We recommend you to schedule automatic data transfers using transaction SMSY_SETUP.

Configuration of MOPZ on Solution Manager EHP1 ST 400 Patch 18

Dear Team,
Request you to let me know the Procedure to Configure MOPZ on Solution Manager EHP1 ST 400 Patch 18, i am struck in between, if any one can send me any document regarding this will be highly appreciated.
Regards,
Adarsh Kumar

Hello,
You can have a look at the Maintenance Optimizer quick startup guide at the Wiki:
https://wiki.sdn.sap.com/wiki/display/SM/Overview
Please let me know if you have any comments / feedback about the Wiki.
Best regards,
Miguel Ariñ

Monitoring EWA in solution manager for EP

Hi
How to monitor and configure the EP 7.0 on solution manager 7.0 for SP 16
Can any body give the doc and steps to do.
Regards

Hi,
Follow Guides
Setting Up your Central Monitoring [original link is broken]
Notes
987835 - How to define Solutions in SMSY for Diagnostics
976054 - Availability of EWA for Non ABAP components
Prerequisites
The SAP EarlyWatch Alert is available for:
SAP systems based on ABAP stack of SAP Netweaver or SAP WebAS
SAP R/3 (minimum release 3.1H)
The Java stack of SAP Netweaver components with a J2EE Engine 6.40 or above (requires ST-SER 700 2007 1 or above on the Solution Manager)
The main prerequisites for using SAP EarlyWatch Alert are:
A remote connection between your SAP component and your SAP Solution Manager
On a ABAP stack system implement SAP Note 69455, run report RTCCTOOL and follow instructions.
For a Java stack system or a CRM system: setup of Solution Manager Diagnostics. For Java SAP Note 976054 describes the prerequisites.
The EarlyWatch Alert content is shipped on the Solution Manager with software component ST-SER u2018SAP Solution Manager Service Toolsu2019 and on the satelite systems (ABAP) with software components ST-PI u2018SAP Solution Tools Plug-Inu2019 and ST/A-PI u2018Application Servicetoolsu2019.
Chk Pdf
https://websmp201.sap-ag.de/~sapidb/011000358700002009362008E.pdf
/people/federico.babelis2/blog/2006/04/25/system-monitoring-configuration-guide-for-dummies
Hope it solves ur problem
Regards
Prakhar

Alert Mail configuration in Solution Manager 7.1 for Portal Runtime errors

Dear Friends,
We have EP7.01 SP5 installed on windows environment with Oracle DB. Also we have SAP EHP 1 for SAP Solution Manager 7.0.
Please help to provide steps to configure
proactive mail alert configuration ,
GRMG for High availability
Any portal runtime errors
for PORTAL services in Solution Manager.
Regards,
Venkat.

Hello Venkat,
You will have to include the Portal system in the Central System administration of your Solution Manager.
As the EP system will be monitored by a sapccmsr running with -j2ee option this one can be configured separately. The agent will be started using the monitoring segment of the J2EE instance and therefore can be started more than once.
Here you should also use the latest sapccmsr agents.
The following link provides details on the required agents:
http://help.sap.com/saphelp_nw2004s/helpdata/en/ca/118110ff542640b7c86b570cc61ae3/frameset.htm
Please refer the below notes.
214247 RZ20: Questions on configuration of monitoring data
704349 Activating the CCMS monitoring for TREX 6.1 (NW2004
Note the EP system can only be monitored by using the SAPCCMSR agents. and then by implement a central autoreaction method you can generate e-mails from CCMS.
Automatic emails will get generated when certain thresholds are met. You must configure the thresholds from the central monitoring system for the nodes that you want email to be generated.
Please follow the steps in the note to configure central auto reaction.
429265 CCMS monitor architecture: Central auto-reaction
In the central monitoring system ( Solution Manager in your case ), Goto RZ20, choose the monitor for the nodes that you are monitoring. Select the node, click properties, & check the threshold values.
Also refer to the following notes:
547024 - Transfer the EP 5.0 Monitoring-Data to SAP CCMS
644783 -P 6.0 Monitoring via CCMS / SolMan
Also, check the following link that has information on portal monitoring :
http://service.sap.com/~sapidb/011000358700002004322004E
I guess this is a whole lot of information to assimilate and will be helpful to you to setup what you intend to.
Regards
Amit

Regarding Monitoring Service for Solution manager

We need to configure "Monitoring" services in SAP solution manager 7.0.
Could somebody suggest us what are the main tasks we need to consider for doing Monitoring settings.
How many Minimum servers required to configure Monitoring services in solution manager system.
Also if any good document reference for this?
Thanks

Hi Jai,
welcome to sdn.
COMPONENTS & TOOLS OF SAP NETWEAVER
SAP Solution Manager
The SAP Solution Manager application management solution facilitates technical support for distributed systems u2013 with functionality that covers all key aspects of solution deployment, operation, and continuous improvement. A centralized, robust application management and administration solution, SAP Solution Manager combines tools, content, and direct access to SAP to increase the reliability of solutions and lower total cost of ownership.
With SAP Solution Manager, you can be sure your entire SAP solution environment is performing at its maximum potential. The toolset addresses your entire IT environment, supporting SAP and non-SAP software and covering current and forthcoming SAP solutions. And, as a customer of SAP, you have full access to the core SAP Solution Manager for no extra charge.
SAP Solution Manager targets both technical and business aspects of your solutions, focusing strongly on core business processes. It supports the connection between business processes and the underlying IT infrastructure. As a result, it eases communication between your IT department and your lines of business. And it ensures that you derive the maximum benefits from your IT investments.
SAP Solution Manager features and functions include:
SAP Business Suite implementation and upgrades u2013 SAP Solution Manager provides content that accelerates implementation. Configuration information and a process-driven approach to implementation speed the blueprint, configuration, and final preparation phases. SAP Solution Manager enables efficient project administration and centralized control of cross-component implementations.
Change control management u2013 SAP Solution Manager controls all software and configuration changes of the IT solution. This includes the approval process for change requests, the deployment of changes, and later analysis of changes. This ensures quality of the solution and enables traceability of all changes.
Testing u2013 SAP Solution Manager speeds test preparation and execution. It provides a single point of access to the complete system landscape and enables centralized storage of testing material and test results to support cross-component tests.
IT and application support u2013 The service desk included in SAP Solution Manager helps you manage incidents more efficiently and eases the settlement of support costs. Centralized handling of support messages makes the support organization more efficient.
Root cause analysis u2013 The diagnostics functions in SAP Solution Manager allow identification, analysis, and resolution of problems, even in heterogeneous environments. This helps to isolate general performance bottlenecks, to isolate exceptional situations, to record the activity of single users or processes, and to identify changes to the productive landscape. As a result, problem resolution is accelerated and business availability increased.
Solution monitoring u2013 SAP Solution Manager performs centralized, real-time monitoring of systems, business processes, and interfaces, which reduces administration effort. It can even monitor intersystem dependencies. Proactive monitoring helps you avoid critical situations, while automatic notifications enable fast response to issues.
Service-level management and reporting u2013 SAP Solution Manager allows easy definition of service levels and provides automated reporting. Service reporting covers all systems in the solution landscape and provides a consolidated report containing the information you need to make strategic IT decisions.
Service processing u2013 SAP Solution Manager makes appropriate service recommendations and delivers SAP support services. These include SAP Safeguarding, which helps you manage technical risk; SAP Solution Management Optimization, which helps you get the most from your SAP solutions; and SAP Empowering, which helps you manage your solutions.
Administration u2013 Administration tasks are mainly executed locally on the involved systems, but can be accessed and triggered from a central administration console. The administration work center in SAP Solution Manager offers a central entry point and unified access to all SAP technology.
SAP Solution Manager as the name suggests is for managing the whole gamut of SAP and Non-SAP solutions in the IT Landscape of an organisation. It provides you the tool, content and gateway to create, operate, manage and monitor your solutions over time.
It provides a range of scenarios to support this. Extending from project management to Solution Monitoring to Service Desk to E-learning Management, it provides an efficient way to carry out a plethora of business tasks.
SAP Solution Manager is the successor to ASAP ValueSAP. SAP Solution Manager helps in implementing and managing complex system landscapes. Globally systems are getting distributed across geographies and business processes cover more than one system. In such complex scenarios, integrating technical and business requirements is important for the success of IT. SAP Solution Manager provides SAP customers with an efficient means of handling both the technical and business process side of solution implementation .
As part of SAP Solution Management Solutions, the customers receive best practices relating to:
- Global Strategy and Service Level Management
- Business Process Management
- Management of MySAP Technology
- Software Change Management
- Support Desk Management
SAP delivers this using support programs during implementation of the system solution. Some of the benefits of using SAP's Solution Manager are that it helps:
- Manages the technical risk associated with the implementation of the solution ensuring technical robustness
- Helps leverage users core competencies in implementing solutions
- Ensures solution works as intended with best practices built in.
see these links...
http://www.ne-sap-solution-manager.com/
http://www.saptechies.com/category/sap-solution-manager/
thanks
karthik
reward me if usefull

Regading PI monitoring setup in solution manager

Hi Folks,
I am new to solution manager and I need to setup PI monitoring setup in solution manager...
I read some blogs and docs but not getting clear idea. all the remaning setup has been done in solution manager and only need to configure the technical monitoring thing in solution manager...
Please help me on this step by step guide...
Thanks,
Sreenivas

Hi Hareesh,
Thanks for your reply.
In Solution manager if I opend the technical monitoring I am getting below screen..
Can you please tell me what are the steps I need to do... For first i want to test this with one file communication channel later I will do remaining channels.
I am new to this setup.. help me on this..
Thanks,
Sreenivas

Prblem Service Desk configuration in Solution Manager 4.0

Hi All,
Here I have done the configuration of Service Desk in Solution Manager 4.0 by using the document which I have for release 3.2. However I have face some problem in Step Initially create and Assign the Satellite Systems as iBase C and Manually create and Assign the Satellite Systems as iBase Co .So I exclude above mention step. But still I am able to create the support message from Satellite Systems.
So can please let me know whether it will work fine in upcoming time or Do I need to test my Service Desk configuration for same.
Moreover please let me know how to test Service Desk configuration for real time environment.
Following are the step and problem which I face while doing the Service desk configuration.
STEP 1 #Initially Create and Assign the Satellite Systems as iBase C
To be able to use the Service Desk and Change Request scenarios in SAP Solution Manager, you need to define the Installed Base (iBase). An iBase component has to be created for each satellite system from which Service Desk messages will be sent to the SAP Solution Manager system.
The iBase components for the iBase structure SOL_MAN_DATA_REP (installation 1) can be created and assigned either automatically or manually. Note that these components and the assignments can only be created once automatically for every solution. To refresh your existing iBase data execute IMG activity Manually Create and Assign the Satellite Systems as iBase Components.
Requirements:-
You have defined your system landscape in the Solution Manager System Landscapes(transaction SMSY).
Activities:-
1. In transaction SOLUTION_MANAGER, open a solution.
2. Choose Operations -> Service Desk.
3. Choose Edit -> Initial Data Transfer for iBase.
The data is copied automatically. The iBase systems for the solution are automatically assigned to SOL_MAN_DATA_REP (installation "1"). An iBase component is created for each system installation number (which can be displayed by choosing System -> Status).
For each solution repeat these steps.
Problem in STEP1 :- I am not able to check the System  Status.
STEP 2 #Manually Create and Assign the Satellite Systems as iBase Co
In this IMG activity, you define the Installed Base (iBase) manually, i.e. for refreshing existing iBases after solutions have been changed.
An iBase component has to be created for each satellite system from which Service Desk messages will be sent to the SAP Solution Manager system.
Activities:-
1. In transaction Change Installed Base (IB52), use the input help (F4) to find the Installed Base with external ID SOL_MAN_DATA_REP.
2. Continue as follows:
 If SOL_MAN_DATA_REP does not exist:
a) Call transaction Create Installed Base (IB51).
b) Choose iBase Category 01 (Installed Base).
c) Choose Enter.
d) Specify the iBase header data in the iBase section.
e) Specify the external ID SOL_MAN_DATA_REP and enter a short description.
 If SOL_MAN_DATA_REP exists:
a) Choose iBase No. 1 (SOL_MAN_DATA_REP).
b) Choose the SAP WEB AS component.
3. To assign the systems as iBase components, go to the Text item tab.
Three components are included in the standard package.
4. Add all the satellite systems as text items to the table:
o Column Short text: Description of the system
o Column Identification: System ID, space, installation number
5. Save.
After changes have been made to a solution, repeat these steps to update system landscape data for iBase.
Note:-
Every system is only listed once in the iBases. That means a system is not listed in an iBase if it has been listed in another iBase before.
Problem in STEP2:- Here I am not able to find Text item tab as per point 3 .
STEP 3 # Assign Business Partners to iBase Components
You need to assign business partners to the new iBase components.
Activities:-
1. In transaction Change iBase (IB52), choose Goto -> Partner
2. Assign business partners with the following functions to the new iBase component systems:
o Administrator
o Key User
o Sold-to Party
3. Save.
4. Repeat these steps for each iBase component.
Problem in step3 :- In IB52 t-code screen there no any menu path like goto  partner
Thanks a lot,
Harshal

Hi Harshall,
You have to enter the value as 1 in Installed base field and then press enter.
You will be taken inside and then you will be able to see the Goto - Partner screen.
Hope this will help.
Please reward points suitably.
Regards,
Naresh.

Big Problem With Solution Manager EHP1 ?

Dear all,
I have already installed SAP Solution Manager EHP1, after the installation sucessfuly. I check the function: Project Administration ( T code : Solar_Project_Admin), then select New project button.
The program inform that:
"Runtime Errors: Message Type Unknow
What happened:
Error in ABAP Application program
The current ABAP program "SAPLSPROJECT_SYSTEM_LANDSCAPE" had to be terminated because
it has come across a statement that unfortunately cannot be excuted.
etc
Do you know about this problem, what is the errors ?
Thanks all.

Dear all.
With Solution Manager EHP1
SAP Basis: SAPKB7001-SAPKB70016, SAPKB70101-SAPKB70102
SAP ABA: SAPKA7001-SAPK70016, SAPKA70101-SAPKA70102
Detail log as below:
Runtime Errors MESSAGE_TYPE_UNKNOWN
Date and Time 28.04.2009 16:47:15
Short text
Message type " " is unknown.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLSPROJECT_SYSTEM_LANDSCAPE" had to be terminated
because it has
come across a statement that unfortunately cannot be executed.
What can you do?
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
Only message types A, E, I, W, S, and X are allowed.
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"MESSAGE_TYPE_UNKNOWN" " "
"SAPLSPROJECT_SYSTEM_LANDSCAPE" or "LSPROJECT_SYSTEM_LANDSCAPEU28"
"SPROJECT_SYSL_CHECK_CENTRAL_SY"
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.
Information on where terminated
Termination occurred in the ABAP program "SAPLSPROJECT_SYSTEM_LANDSCAPE" - in
"SPROJECT_SYSL_CHECK_CENTRAL_SY".
The main program was "SAPLS_IMG_TOOL_5 ".
In the source code you have the termination point in line 29
of the (Include) program "LSPROJECT_SYSTEM_LANDSCAPEU28".

CPS on Solution Manager EHP1?

Folks,
Any idea whether we can install CPS in Solution Manager EHP1 (7.01) system with Java EHP1 (SP4)?
The CPS software is available under NW 7.0.
Regards
Chandu

Hello Cheeti,
you can install SAP CPS on SAP Solution Manager and SAP CPS is actually quite independent on Java support package (but choose the right NW release 7.01), i.e. you do not always have to update you SolMan system if you install a new CPS release.
However, if you read through the SAP CPS Installation Guide (Scheduling) you will find the recommendation to install SAP CPS on a separate server. That might not necessarily be the case for test or demo installations and of course also depends on your utilization of SAP CPS.
Have you considered these things:
Sizing: How does the ressource consumption of SAP Solution Manager influence you SAP CPS scheduler? Will important jobs be delayed?
Are there sufficient RFC resources for all application? (SolMan, Wiley, CPS all these application need to communicate with the managed systems)
Do you want to entangle the lifecylce management of SAP CPS with SAP Solution Manager? Which production do you want to update more/less frequently? Can you accept additional down times?
Kind regards,
Martin

System monitoring configuration in solution manager EHP1

Similar Messages

Maybe you are looking for