Solution manager configuration diagnostic host agent

Hi experts,
I am configuring the solution manager 7.1 SP9, I have one doubt whether our systems contains diagnostic host agent or not.
in sapmmc at the time of restarting the sap services i found that DAA is there.So i got this doubt. Please clarify what is diagnostic host agent and SAPHost agent and also please provide any material for solution manager configuration. I am not getting clarity from google.
Thanks&Regards,
Patan Thavaheer.

Hi,
I executed the given command successfully in daaadm user.In command prompt it is showing that "task completed with status success".But in solution manager it is not getting visible. I checked in log file SMDsystem.0.log , i found exception in the log.
find the exception
migsolman.milltec.com:8001 Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection on host: 192.168.140.47 and port: 8001]
Sep 16, 2014 10:55:55 AM [Thread[Agent Configuration Monitor,1,main]   ] Info       Detect possible changes in runtime.properties, reload data and restart the agent connection.
Sep 16, 2014 10:55:55 AM [Thread[Agent Configuration Monitor,1,main]   ] Info       SLD configuration not found to register the agent, SLD Agent Registration is skipped.
Sep 16, 2014 10:55:55 AM [Thread[Agent Configuration Monitor,1,main]   ] Info       Reconnection in progress...
Sep 16, 2014 10:55:55 AM [Thread[Agent Configuration Monitor,1,main]   ] Info       [SMDConnector.reset] in progress ...
Sep 16, 2014 10:55:55 AM [Thread[Agent Configuration Monitor,1,main]   ] Info       [SMDConnector.reset] invalid the agent handle com.sap.smd.agent.AgentHandle@1db9b30c.
Sep 16, 2014 10:55:55 AM [Thread[Agent Configuration Monitor,1,main]   ] Info       Reading JStartup environment...
Sep 16, 2014 10:55:55 AM [Thread[Agent Configuration Monitor,1,main]   ] Info       'SAPLOCALHOST' found, The value 'MIGDev' will be used to determine the Agent name.
Sep 16, 2014 10:55:55 AM [Thread[Agent Configuration Monitor,1,main]   ] Info       InetAddress Resolving for 'MIGDev' - FQN: migdev.milltec.com SQN: MIGDev IP: 192.168.140.45
Sep 16, 2014 10:55:55 AM [Thread[Agent Configuration Monitor,1,main]   ] Info       InetAddress Resolving for localhost - FQN: migdev.milltec.com SQN: MIGDev IP: 192.168.140.45
Sep 16, 2014 10:55:55 AM [Thread[Agent Configuration Monitor,1,main]   ] Info       [SMDConnector.reset] Done.
Sep 16, 2014 10:56:14 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] reset the p4 broker (close:true)
Sep 16, 2014 10:56:14 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] p4 broker closed.
Sep 16, 2014 10:56:14 AM [Thread[Connector,5,main]                     ] Info       Local P4 port opened on port '59704'.
Sep 16, 2014 10:56:14 AM [Thread[Connector,5,main]                     ] Info       Local P4 server configured with transport layer 'None'.
Sep 16, 2014 10:56:14 AM [Thread[Connector,5,main]                     ] Info       [P4ServerController] Remote object 'com.sap.smd.agent.remote.handle' (com.sap.smd.agent.AgentHandle@29bbbce6) is available in P4 Object Broker.
Sep 16, 2014 10:56:14 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] p4 broker initialized.
Sep 16, 2014 10:56:14 AM [Thread[Connector,5,main]                     ] Info       [p4://migsolman.milltec.com:8001] Checking server availability...
Sep 16, 2014 10:56:45 AM [Thread[Connector,5,main]                     ] Error      Failed to connect to SMD server - user: basisadm
Sep 16, 2014 10:56:45 AM [Thread[Connector,5,main]                     ] Warning    Connecting to SMD server p4://migsolman.milltec.com:8001 failed - error counter: 19 - com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: Cannot establish connection with any of the available instances:
migsolman.milltec.com:8001 Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection on host: 192.168.140.47 and port: 8001]
Sep 16, 2014 10:57:20 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] reset the p4 broker (close:true)
Sep 16, 2014 10:57:20 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] p4 broker closed.
Sep 16, 2014 10:57:20 AM [Thread[Connector,5,main]                     ] Info       Local P4 port opened on port '59704'.
Sep 16, 2014 10:57:20 AM [Thread[Connector,5,main]                     ] Info       Local P4 server configured with transport layer 'None'.
Sep 16, 2014 10:57:20 AM [Thread[Connector,5,main]                     ] Info       [P4ServerController] Remote object 'com.sap.smd.agent.remote.handle' (com.sap.smd.agent.AgentHandle@29bbbce6) is available in P4 Object Broker.
Sep 16, 2014 10:57:20 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] p4 broker initialized.
Sep 16, 2014 10:57:20 AM [Thread[Connector,5,main]                     ] Info       [p4://migsolman.milltec.com:8001] Checking server availability...
Sep 16, 2014 10:57:51 AM [Thread[Connector,5,main]                     ] Error      Failed to connect to SMD server - user: basisadm
Sep 16, 2014 10:57:51 AM [Thread[Connector,5,main]                     ] Warning    Connecting to SMD server p4://migsolman.milltec.com:8001 failed - error counter: 20 - com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: Cannot establish connection with any of the available instances:
migsolman.milltec.com:8001 Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection on host: 192.168.140.47 and port: 8001]
Sep 16, 2014 10:58:26 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] reset the p4 broker (close:true)
Sep 16, 2014 10:58:26 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] p4 broker closed.
Sep 16, 2014 10:58:26 AM [Thread[Connector,5,main]                     ] Info       Local P4 port opened on port '59704'.
Sep 16, 2014 10:58:26 AM [Thread[Connector,5,main]                     ] Info       Local P4 server configured with transport layer 'None'.
Sep 16, 2014 10:58:26 AM [Thread[Connector,5,main]                     ] Info       [P4ServerController] Remote object 'com.sap.smd.agent.remote.handle' (com.sap.smd.agent.AgentHandle@29bbbce6) is available in P4 Object Broker.
Sep 16, 2014 10:58:26 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] p4 broker initialized.
Sep 16, 2014 10:58:26 AM [Thread[Connector,5,main]                     ] Info       [p4://migsolman.milltec.com:8001] Checking server availability...
Sep 16, 2014 10:58:56 AM [Thread[Connector,5,main]                     ] Error      Failed to connect to SMD server - user: basisadm
Sep 16, 2014 10:58:56 AM [Thread[Connector,5,main]                     ] Warning    Connecting to SMD server p4://migsolman.milltec.com:8001 failed - error counter: 21 - com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: Cannot establish connection with any of the available instances:
migsolman.milltec.com:8001 Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection on host: 192.168.140.47 and port: 8001]
Sep 16, 2014 10:59:31 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] reset the p4 broker (close:true)
Sep 16, 2014 10:59:31 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] p4 broker closed.
Sep 16, 2014 10:59:31 AM [Thread[Connector,5,main]                     ] Info       Local P4 port opened on port '59704'.
Sep 16, 2014 10:59:31 AM [Thread[Connector,5,main]                     ] Info       Local P4 server configured with transport layer 'None'.
Sep 16, 2014 10:59:31 AM [Thread[Connector,5,main]                     ] Info       [P4ServerController] Remote object 'com.sap.smd.agent.remote.handle' (com.sap.smd.agent.AgentHandle@29bbbce6) is available in P4 Object Broker.
Sep 16, 2014 10:59:31 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] p4 broker initialized.
Sep 16, 2014 10:59:31 AM [Thread[Connector,5,main]                     ] Info       [p4://migsolman.milltec.com:8001] Checking server availability...
Regards,
Patan Thavaheer.

Similar Messages

System registered in SLD invisible in solution manager configuration

Hi
I have installed Solution Manager EHP1 / Oracle 10g / Win2003 on a VM. I ran into a issue in the Managed system configuration. The first step in the maanaged system configuration would help us select the satelllite systems which and configured in the SLD. Since systems were not yet added to SLD just the solution manager system shows up.
Here is the problem
I have added one system to the SLD using "Add Technical system" from http://localhost:50000/sld. This is a ABAP sysystem. The addition went through successfully however this does not reflect when I check the same in solution manager configuration "Managed system configuration"
As per the guide in the same page, I have checked on "Maintain Technical systems" Here too when I search for the system I created in SLD , I am not able to find it. Is there another way of manually maintaining the system in the SLD?
Any ideas as to why this might happen? Does one have to bounce the instance after adding systems to SLD/.... just wondering?
Ideas?
thanks
Ravi

Hi Rajeev
Thanks for your response however I fixed it. It looks like I had incorrectly mentioned the host in RZ70. Instead of mentioning the hostname of the solution manager I had mentioned the host name of the satellite system
The below link helped me fix the issue
http://help.sap.com/saphelp_nwpi71/helpdata/en/e7/01503ede925441e10000000a114084/content.htm
thanks
ravi

IT Service Management (Solution Manager - Configuration)

Dear Expert!
We are using SM 7.1 SP11.
The System Preparation and Basic Configuration has been done
Now, we want to configure the IT Service Management under the Solution Manager Configuration.
There are some steps are manual in the standard configuration;
1) Configure Manually
2) maintain Transaction Types
3) Configure Automatically
4) Perform Additional Configuration
5) Create Template users.
I don't aware by the manually steps, what should be provide in the manual configuration.
I have downloaded document ITSM Configuration Part 1 and 2 but material does not discuss about the steps to executed in the configuration.
Please advise
Regards

Hi Anwer,
Go to service.sap.com/instguides
from here you can go to S -> SAP Solution Manager -> on the right pane scroll down and click on
Planning, Installation, Upgrade Guides -> Look under Additional Guides - ITSM you will find the required documentation.

SAP Solution manager configurations

Hi Experts,
I need to do Solution manager configuration ,but i don't have idea about this.could you please help me and before start the configuration what is the prerequisites for configuration.
I need all above steps information what is the use of every one and tell me prerequisites for all steps.
Please help me any one.It is helpful for me.
Thanks
J Jana

Hi Janardhan,
Please download the System Monitoring and technical monitoring guide
https://websmp103.sap-ag.de/~sapidb/011000358700000409042011E
Please watch the EEM demo
https://websmp103.sap-ag.de/~sapidb/011000358700000383412011E/index.htm
Please watch demo for connection monitoring
https://websmp103.sap-ag.de/~sapidb/011000358700000479272011E/index.htm
Please Downlaod Technical Administration guide
https://websmp103.sap-ag.de/~sapidb/011000358700000592062012E.pdf
ITSM:Part 1
https://websmp103.sap-ag.de/~sapidb/011000358700000608542012E.pdf
Part 2: https://websmp103.sap-ag.de/~sapidb/011000358700000608872012E.pdf
Happy Learning.
Vinod Palli

Solution Manager Configuration

Hi All,
I want to configure Solution Manager for Support Activities and their reporting like creation of tickets by end user, resoultion time according to category. I need a documentation on the same if possible some configuration document.
Help on the same!!!!
Anurag

Hi Raghav,
Kindly check missing authorizations of user solman_btc.
Regards,
Varenyam Trivedi

Solution manager configuration for EHP4 install (Product Version Problem)

Hi guys!
I'm new on SAP and SDN is a help all days and this time i really need some help from you guys!
Im installing EHP 4 and need the XML Stack file, so i go to the solution manager to generating them. But after configuring the logical components, make the associations, etc. on create maintenence transaction, the product version dropdownlist is empty...
It is configured but it dont appears... Anyone had this problem before and could give me some help!
I will appreciate that!
My regards,

Hi,
In SMSY, the system should have product version as SAP ERP 6.0.
Next the logical component created for ECC Server should also reflect this version.
The solution you create in DWSP should include this logical component via the Solution Landscape definition. Here again the logical component should show the product version.
If all above are in place, the MOPZ for the respective solution should have the product version list populated.
Regards,
Srikishan

Solution manager configuration for SRM

Hi all
we are goin to configure SAP SRM 5.0. we need to configure standard business scenarios in solution manager for the same.can somebody provide relevant links and documents regarding where to find these in solution manager and how to go about this?this would be really helpful.points would be awarded immediately.

Hi Harsa,
Here you can find the Webex recorded sessions
https://websmp207.sap-ag.de/~sapidb/011000358700000429402008E
Hareesha

Reset Solution Manager configuration

Hello experts,
We are setting Solution Manager up for incident management but the configuration was started without SP15 and many things were manually done so now, there are a lot of users and even systems that weren't succesfuly created... bottom line, the configuration is a mess. Is there any way to reset this configuration and start over? I specially want to delete ibase's, systems and bp's.
What would you suggest?
Thanks in advance

Hi Maria,
There isn't an easy way to whipe everything out and start fresh. However, you can archive messages, update your iBase, retire BP's and fix your system landscape. You can even delete BP's if they are not assigned to messages. If they are, I read of a fix where someone replaced the BP's in the tables and then was able to delete them. If you can't delete your iBase it's because you don't have an SAP note installed.
If you browse the forum for each of the items you want to fix, you'll find the info.
regards,
Jason

Transport Solution Manager configuration between systems

Hello all,
I created a configuration project for service desk on spro_admin on development environment. Then configured all the basic steps for service desk. Now how can move things to quality system and then to Prodution? Is it enough to create a project transport or do I need anything else? Because when I created a project transport (from spro_admin) it only added a few things to it, not all objects I've customized. My concern is that BC sets for example won't be imported in the other systems or so.
Any guides on this?
Regards,
Ricardo

Hi,
>
Ricardo Dias wrote:
Is it enough to create a project transport or do I need anything else?
Create a Project Transport? what do you want to do? If there is anything in a Transport request it can be obviously imported into your QAS and to PRD, you need to decide if you have completed the config.
>
Ricardo Dias wrote:
Because when I created a project transport (from spro_admin) it only added a few things to it, not all objects I've customized.
> Ricardo
What did you actually do? were the changes not imported completely?
Feel free to revert back.
-=-Ragu

Configuring the Alert monitoring of Solution Manager 4.0

Dear all,
How can I notify from the central monitoring system when alerts happened?
I have already create and assign auto-reaction method to specific monitor attribute with alerts, but nothing happend. I even looked at the table CSMCENTOOL where the alert data suppose to stored, and the table is still empty.
I will be greatfull if anyone can provide me appropriate document in this matter, or guide me with a list of things that need to be done.
Kind regards,
Yagel

Hi Kai,
Thanks for your quick response.
I have already create and assign the central auto-reaction method exactly as in the example,
and when I try to start the auto-reaction method I receive the alert information "Cannot determine data for method DUMMY_TOLL_FOR_DOUBLEHOP".
I have overcome this alert information by changing the excute method of the defined central auto-reaction from Only in central system, trigged by CCMS agents to Periodically in process(Short running program), and still, nothing notify when alert happened.
Should I configure the "Related Solution Manager configuration guides on SDN" which describe in the bottom blug as well?
I also didn't understand you when you say to send from SAP-System to another account?
Thanks in advance,
yagel.

Configuring Solution Manager: Alternative Role to SAP_ALL

This is a general question regarding configuring Solution Manager and note 834534. I am configuring Solution Manager 7.0 at a client site. The main components that I am configuring are on the Monitoring and Operations side; for example, System Monitoring, Service Desk, Issue Management, and Change Management for Maintenance Optimizer. CHaRM will follow later on. Additionally, the client would like to use the project side of Solution Manager.
When I took training for Solution Manager from SAP, the SAP instructor advised the class to have SAP_ALL when configuring Solution Manager The problem I am having is that the client will not issue me SAP_ALL in the Solution Manager instance, regardless of the recommendation in note 834534. I can understand the client's reluctance to issue SAP_ALL, even though Solution Manager is not a financial system in of itself, however, I have found that I am constantly having to ask for authorizations as I step through the wizards and the Scenario-specific settings. When I run into issues which require further investigation by running transactions to check certain settings that are not specifically tiedd to a wizard or scenario-specific setting transaction, I run into further delays as I ask for additional authorizations to troubleshoot issues.
We have implemented the roles and assigned them to my ID in Solution Manager as outlined by the SAP Solution Manager Security Guide to the fullest extent possible; and I have been issued "Basis Roles" that the client issues to their Basis team. Regardless of these actions, I still run into authorization issues.
My question is, apart from the SAP Solution Manager Security Guides recommendations (which does not mention SAP_ALL), is there a role being developed, or has been developed that can be assigned to the Solution Manager configurator in lieu of SAP_ALL (as per note 834534)? I would think that this issue has been raised before, particularly since many companies have implemented SOX controls and are skittish about issuing SAP_ALL.
Your feedback is most appreciated.

Thanks for the reply, Nesimi.
While I appreciate that you do not use SAP_ALL, is that the case when you are configuring a brand new, clean system? Are you using the Configuration Wizards with out SAP_ALL? I ask this because when I ran the first configuration wizard, one of the steps is to create a "configuration user", which creates a user with SAP_ALL. However, I cannot use that wizard generated user ID because it has the role SAP_ALL.
In general, I am operating on 3 sources of information that says I need SAP_ALL to configure the system (not necessarily to operate it):
1. An SAP Instructor for the Solution Manager Operations and Monitoring Class
2. The IMG Activity "Create Configuration User" documenation in SPRO
3. Note 834534
I will review the english version of the link http://help.sap.com/saphelp_smehp1/helpdata/de/40/8ac473d40943ddb23def12bdb33437/frameset.htm that you have thoughtfully provided.
With respect to note 123640, I am not sure if that solves my problem or answers the fundemental question that I have in that given the 3 sources I quoted above. It seems to me that SAP's approach in indicating clearly that they prefer that the configuration user should have SAP_ALL is flawed given today's corporate governence policies. Clearly this recommendation is only for the initial configuration, and SAP_ALL can be taken away and replaced by the roles and recommendations in the SolMan security guide; to maintain Solution Manager. But when it comes down to the question "what do you need to configure Solution Manager, because we won't give you SAP_ALL", I am hard pressed to give an answer despite literally spending hundreds of hours researching "documenation" which does not give clear cut answers. I think SAP needs to address this issue instead of taking the easy way out and saying you need "SAP_ALL" as illustrated in the 3 sources of readily available information cited above.

Solution Manager Diagonostic Agent:Start Error

Hi All,
We are facing problem while starting SMD agent in Solution Manager System in I series.
The Landscape browser in the Solution Manager Diagnostics shows SMD Agent Status : Agent not found.
We tried starting the same through: \usr\sap\SMD\J98\script but while doing so we were getting following error:
Starting at 2010/01/14 16:24:21
Startup Profile: "/usr/sap/SMD/SYS/profile/START_J98_SPLBWPRD"
Starting Programs
14.01.2010 16:24:21
ShmDetach
FAIL: NIECONN_REFUSED (Connection refused), NiRawConnect failed in plugin_fop
en()
(2465) Spawning program "/usr/sap/SMD/exe/jcontrol pf=/usr/sap/SMD/SYS/profil
e/SMD_J98_SPLBWPRD" asynchronously...
Any inputs are much appreciated.
Regards,
Prasad

I just saw a different forum with NIECONN_REFUSED, his was fixed after the port number was corrected.
Try 5xx04.
Edited by: Ryan Cossette on Jan 18, 2010 6:47 PM

Solution manager charm configure

hello everyone
i want to configure the charM scope with our R3 and BW at two domain .
R3 landscape
                    DEV(101sandbox,201-develop,301-customizing ,800unit testing)
                    QAS(800- testing)
                    PRD(800-prduct)
tranport   from DEV TO QAS and delivery to PRD ,also you can export the object from QAS to PRD for special .
domain controller is PRD
BW landscape BWD(client 100)--BWQ(client 880)BWP(client 880)
domain controller is BWP
if we use the charM for manager the change requst ,how we configure in all system for prepare the charM like the stms configure .
we notice our test system and prd system have same client number ,so it is ok for configure ?
expect your help!
thanks a lot!
frank

Hi,
1 QAS client and PRD client can be the same(need not to be different).
2. Make sure that the system landscape you mention under system landscape tab of SOLAR_PROJECT_ADMIN should match with TMS configuration of Solution Manager.(This is very important).
You should create a maintenance project with system landscape DEV-201->QAS-200->PRD-200 using SOLAR_PROJECT_ADMIN. Repeat this step for BW also.
   You need to configure TMS of Solution Manager in Client 000 as follows:
    SLM->DEV-201->(Consolidation Route)QAS-200->(Delivery Route)PRD-200
    SLM->BW-100->(Consolidation Route)BW-880->(Delivery Route)BW-880
No more document is required better than SPRO. Just follow this SPRO path to configure TMS:
SPRO->SAP Solution Manager->Configuration->Scenario-Specific Settings->Change Management
->Change Request Management->Standard Configuration->Transport Management System(Read IMG activity of each step).
Let me know if you have aby issues.
Regards,
Sanjai

Diagnostics agent not getting registered in Solution Manager

Hello SAP Experts,
I am using Solution Manager 7.1 SP Stack 12. I installed diagnostics agent on one of the managed systems and fired the command below for registering it in Solution manager (since I did not do this during diag agent installation):
/usr/sap/DAA/SMDA<instance no>/script/smdsetup.sh managingconf hostname:"sapms://<FQDN of Solman>" port:"81<instance no of Solman>" user:"smd_admin" pwd:"<password"
This command returned successful message. However, when I login to Solution manager and go to Agent administration, I am unable to see the above managed system diagnostics agent. Please help.
Thanks & Regards,
Kunal.

Hi Adi,
Thanks for the reply. I found the below SMDSystem.7.log at location /usr/sap/DAA/SMDA98/SMDAgent/log
Apr 24, 2014 1:21:05 PM [Thread[Connector,5,main] ] Error Failed to connect to SMD server - user: smd_admin
Apr 24, 2014 1:21:05 PM [Thread[Connector,5,main] ] Warning Connecting to SMD server ms://<hostname>/P4 failed - error counter: 1690 - com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: there are no access points for service: P4 registered on the message server]
Regards,
Kunal.

How to start the Solution Manager Implementation

Hi Gurus , I am in Solution manager implemnetation project , and i wanted built the exsisted landscape into Solman so any one can help me out in this like where to and how to start.

Hi Gurus, i wanted to implement these concepts
Configuring Solution Manager
Configuring Solution Manager
1)      Solution Monitoring
a       SAP EarlyWatch Alert
a1      Setting-Up EarlyWatch Alerts    Y
a2      Manually Executing Downloads    Y
a3      Create Report and Display Session Details       Y
a4      Save, Retrieve and Archive EarlyWatch Alert     Y
b       Service Level Reporting
b1      Service Level Reporting Change Mode     Y
b2      Maintain General Settings       Y
b3      Specify Systems and Contents for Service Level Report   Y
b4      Select Business Processes for the Service Level Report Y
b5      Select Business Processes from the Business Process Monitoring Y
b6      Process Service Level Report Data Manually      Y
b7      Create Service Level Report     Y
b8      Create, Save and Archive Service Level Report Manually Y
b9      Process Service Level Report Session    Y
b10     Send E-Mail Automatically       Y
b11     KPI Calculation Y
2       Configuring Alert Monitor
       Central System Administration (Part of ALERT Monitor)
c2.1    MTE Classes and Attribute Groups        Y
c2.2    Methods Y
c2.3    Operating the Alert Monitor     Y
c2.4    Actions in the Alert Monitoring Tree    Y
c2.5    Selecting Nodes in the Alert Monitoring Tree    Y
c2.6    Elements of the Alert Monitor   Y
c2.7    General Properties of Monitoring Tree Elements Y
c2.8    Properties of Monitoring Objects and Attributes Y
c2.9    Customizing the Alert Monitor   Y
c2.10
Changing Properties in the Alert Monitoring Tree
       Y
c2.11
Changing Properties in Customizing Transaction RZ21
       Y
c2.12
Triggering a Heartbeat Alert if No Values Are Reported
       Y
c2.13
Changing the Frequency of Method Execution
       Y
c2.14   Defining, Releasing, and Transporting Methods
       Y
c2.15
Assigning Methods to MTE Classes or Individual MTEs
       Y
c2.16   Assigning Methods to MTE Classes or Individual MTEs     Y
c2.17
Editing Monitors and Monitor Sets
       Y
c2.18
Creating and Editing Monitor Sets
       Y
c2.19   Transporting Monitor Sets and Monitor Definitions       Y
c2.20   Copying, Renaming, and Deleting Monitors        Y
c2.21   Creating and Changing Monitors Y
c2.22   Rule Node: Rule Description and Use     Y
c2.23   Defining Monitors with the DEFINE_R3_SYSTEMS/GET_MTE_BY_CLASS Ru        Y
c2.24   Defining Monitors with the Rule GET_MTE_BY_CLASS_AND_OPTIONS    Y
c2.25   Defining Monitors with the Rule GET_MTE_BY_CLASS_AS_VIRTUAL     Y
c2.26   Copying a Monitoring Properties Variant Y
c2.27   Create Monitoring Properties Variant    Y
c2.28   Change Monitoring Properties Variant    Y
c2.29   Activating a Monitoring Properties Variant      Y
c2.30   SAP-DEFAULT     Y
c2.31   Creating a New SAP-DEFAULT Variant      Y
c2.32   Monitoring Multiple Systems     Y
c2.33   Monitoring Multiple Systems: Defining RFC Connections   Y
c2.34   Monitoring SAP R/3 3.x Systems Y
c2.35   Creating the CSMREG User        Y
c2.36   Monitoring Multiple Systems with an Identical System ID Y
c2.37   System Groups in the Alert Monitor      Y
c2.38   Deactivating and Reactivating Monitoring Tree Elements Y
c2.39   Deleting and Restoring Nodes in the Alert Monitoring Tree       Y
c2.40   Display Options of the Alert Monitor    Y
c2.41   Saving and Resetting the Layout of a Monitor    Y
c2.42   Extending the Shared Memory Area        Y
c2.43   Setting Up a Central Data Cache         Y
c2.44   Configuring the Caches of the Monitoring Architecture   Y
c2.45   Working with All-Clears (Green Alerts) Y
c2.46   Displaying the History of the Threshold Values of Performance No        Y
c2.47   Availability Monitoring with CCMSPING   Y
c2.48   Installing Availability Agent CCMSPING Y
c2.49   Changing the Monitoring Frequency and Timeouts of CCMSPING      Y
c2.50   Adding Systems to the Availability Monitoring Manually Y
c2.51   Finding and Correcting Errors with CCMSPING     Y
c2.52   Configuring Availability Monitoring     Y
c2.53   Creating and Changing Monitoring Rules Y
c2.54   Changing Monitoring Setting of Servers and Groups       Y
c2.55   Using Multiple CCMSPING Agents Y
c2.56   Creating and Changing a Monitoring Pause        Y
c2.57   Monitoring System Groups with CCMSPING Y
c2.58   Availability and Performance Overview Monitor   Y
c2.59   Monitoring Log Files with CCMS Agents   Y
c2.60   Structure of the Log File Template of the Log File Agent        Y
c2.61   Example Log File Templates      Y
c2.62   Logfile Monitoring Monitor      Y
c2.63   Monitoring Selected Processes with SAPOSCOL     Y
c2.64   Monitoring Response Times of Transactions or Clients    Y
c2.65   Monitoring Database Tables with the Alert Monitor       Y
c2.66   Self-Monitoring of the Alert Monitor    Y
c2.67   Selected Alert Monitor Methods Y
c2.68   Forwarding Alerts to Alert Management (ALM)     Y
c2.69   Interpreting a Text Attribute as File Name/URL and Display Content      Y
c2.70   Displaying a Subtree as ALV Grid Control        Y
c2.71   Defining an Automatic Alert Notification        Y
c2.72   Auto-Reaction Method: Execute Operating System Command Y
c2.73   Setting Up Central Auto-Reaction Methods        Y
c2.74   Installing CCM4X        Y
c2.75   Activation in the background,if the Host restarts       Y
c2.76   Creating RFC Connection Y
c2.77   Copying File from Solution manager to agents    Y
c2.78   Copying version for SAPCCM4X    Y
c3      Central User Administartion(CUA)
c3.01   Create manaintain landscape     Y
c3.02   Creating RFC    Y
c3.03   Create Logical clinets in SM1   Y
c3.04   Field distribution parameters   Y
c3.05   Transfering users from child system     Y
2       Service Desk
a       Set-Up Message Creation in Web Browser Y
b       Create support messages with NOTIF_CREATE       Y
c       Process Messages in Service Desk        Y
d       Search for Solutions to Support Messages        Y
e       Copy Support Message into Solution Database     Y
f       Forward Support Message to SAP Y
g       WebClient Interaction Center    Y
h       Create Messages with Interaction Center WebClient       Y
i       Process Messages in the Interaction Center WebClient    Y
j       Service Desk for IT Service Providers   Y
k       Using an External Service Desk Y
l       Connect an External Service Desk        Y
m       Service Desk Customizing Error Analysis Y
it's very high prioriety
Cheers

Solution manager configuration diagnostic host agent

Similar Messages

Maybe you are looking for