hai

I have created a composite test case for  business process through solar02 - test case tab. This test case is linked to development client.

I want make copy of this test case  and link to quality client .

Can any one tell me the steps to copy of test case document.

I tried copy document in test case tab in solar 02. It says ' This function is not supported for this object type'

Pls help

Regards

Jaya

End-to-End Monitoring and Alerting Infrastructure (MAI) System Monitoring contains various templates which contain the metrics, events and alerts (MEA), and their attributes. They also contain settings for Incidents, and notifications. You can base your own templates on the templates delivered by SAP, and adjust them to your requirements. You do this in the SAP Solution Manager Configuration (transaction SOLMAN_SETUP) in the step  Technical Monitoring  System Monitoring  Template Maintenance.

Incident Messages and notifications can be created automatically or manually. You can make the settings for the automatic creation of messages and notifications on the following levels:

Maintain Auto Incidents and Notifications Specific Settings with Global Switch ON

Incident Settings

To adjust the incident settings, proceed as follows:

Default Settings

1. Go to the Solution Manager Configuration (transaction SOLMAN_SETUP) step in the table above, for the level on which you want to make settings.
2. Go to change mode, and ensure that you are in the following tab, depending on the level:

3. In the drop-down list Automatic Incident Creation, choose Active or Inactive. If you choose Inactive, you can still create incidents manually from the Technical Monitoring Alert Inbox.

Note

You can also copy the general level settings on template and alert type levels. This is the default setting.

4. If automatic incident creation is active, go to the Incidents tab to make the detailed settings for the automatically created incidents: 

1. In the drop down list box Create Incident for, you can decide for which alert rating an incident should be created.
2. CRM transaction type
3. In Support Component, you specify the component to which the message is assigned.
4. In the drop down list Reported by, you can choose which ABAP user reports the incident.
5. In the drop down list Processor, you can choose which ABAP user is the processor of the message.
6. Category ID
7. The Incident Confirmation Confirms Alert flag specifies whether the corresponding alert is also confirmed when an incident is confirmed.

Advanced Settings

1. Mark the following advanced settings as required:
2. Update incident for new alerts and when alert is closed.
3. Enter a custom subject line if you want to override the default subject text.
4. Add an introductory text to the incident message long text, if you want to add any additional details about the alert.

Use implementation of BAdI with a filter value. If BAdI implementation was used, however, the subject and/or the long text returned by that would take precedence. Along with the standard text of incident, the custom subject and / or introductory text appears for BAdI implementation.

Notification Settings

To adjust the incident settings, proceed as follows:

Default Settings

To adjust the notification settings, proceed as follows:

1. Go to the Solution Manager Configuration (transaction SOLMAN_SETUP) step in the table above, for the level on which you want to make settings.
2. Go to change mode, and ensure that you are in the following tab, depending on the level:

3. In the drop-down list Automatic Notification, choose Active or Inactive. If you choose Inactive, you can still create notifications manually from the Technical Monitoring Alert Inbox.

Note

You can also copy the general level settings on template and alert type levels. This is the default setting.

4. If you have activated the automatic notification, go to the Notifications tab, to make detailed notification settings:

• To maintain recipients in Notification Management, choose Maintain Global Recipients, and make your changes there.
• If the recipients have been maintained in Notification Management, and you want to maintain recipient lists, choose Maintain Recipient Lists, and make your changes there.
• To add the recipient or recipient list to the default settings, choose Add, and make your changes there.
• In the drop down list Send Notification for, you can decide for which alert rating a notification should be created.
• In the input field Sender, you can choose which ABAP user should send the notification.
• In the Advanced Settings, you can choose whether another notification should be sent if the alert rating switches back to green. For details, see the quick help of the flag.

Note

To activate the quick help, right-click anywhere in the screen and choose Display Quick Help from the context menu. Screen elements for which there is quick help are underlined in green. To show the quick help, move the cursor across these underlined elements.

Advanced Settings

1. You can choose when to send notifications using the advanced settings.

2. Select the following check boxes as required.

3. Send notification for closed alerts, for first notification after a particular period of time, and additional notification after certain period of time.
4. Enter a custom subject text, if you want to override the default subject
5. Add an introductory text to the notification long text, if you want to add any additional details about the alert.

Use implementation of BAdI with a filter value. If BAdI implementation was used, however, the subject and/or the long text returned by that would take precedence. Along with the standard text of notification, the custom subject and / or introductory text appears for BAdI implementation.

Dear Gurus,

I would like to ask for 2 questions:

1. If I schedule a downtime for my Solman, in the Interactive Reporting (System

Availability) will show "Not available due to planned downtime". However it will show as
"No availability measurements" in all my child systems. How to automatic update the child

systems as well when the solman is having a downtime?

2. For any "Not available due to planned downtime" and "No availability measurements", can I

put a description on it (in the same page) the reason for the downtime? For example, in the
chart page, it will show 11 Sep 2014 having "No availabilty measurements", but I want to

include the reason description over there.

Your inputs are greatly appreciated.

Regards,
Stephan

Hello experts,

We are running solman 7.1 SP10 and we are configuring our Service Desk.

We have 2 roles: ZSOLMANPRO (1st and 2nd line helpdesk) & ZSOLMANREQ (endusers)

When the helpdesk creates an incident (role ZSOLMANPRO) we can add projects to the incident (transaction type ZINC).

But endusers (role ZSOLMANREQ) cannot add this field because this field is not available in the viewconfiguration (see attach addview.png for the field we want to add => it's properties). How can we add this field so it is available in the viewconfiguration for endusers? (see attach availablefields.png for fields who are available in role ZSOLMANREQ

Many thanks in advance!

Rgds,

Kenny

Hi, am having an issue with Solution Manager, i can't get what really is the issue with it not being unreachable. it displays the attached message:

Can someone please advice on what could be the issue with this? and any possible solutions are welcomed too.

Purpose of MAI Consumer Variants

Maintaining variants helps in reducing the overhead of maintaining notification, incident, third-party and auto-reactions related data multiple times in multiple places such as templates and alerts.

Example: Template A and Template B uses the same data related to Notifications (email users, advanced settings…); Template C and Template D would like to use the other set of data. If Variants are created, the overhead of maintaining the same data 2 times in Template A and Template B will be reduced. User can select the variant which he/she would like to use in each template and all the required data will be populated automatically.

Note:

This feature is available from Solution Manager 7.1 SP 12 release onward only.

Procedure for Creating Variants

1. Go to the Solution Manager Configuration (transaction SOLMAN_SETUP) step in the table above, for the level on which you want to make settings.
2. Select System Monitoring from Technical Monitoring section.
3. Select the Default Settings (2.3) step.
4. Select Notifications tab.
5. You can launch the Consumer Variant Maintenance tool from the following tabs: Incidents, Notifications and Third-party Component
6. On the Consumer Variant Maintenance tool, under Incidents tab, click Edit.
7. Select the tab Incidents.
8. Click Edit and then Create.
9. A new row is added to the table and is editable. You need to enter the Name and Description of the Variant. In the “Auto-Incident” drop down list, you need to select “Active” or “Inactive” status. 
10. If you select “Active” status, all the fields related to the Incident are displayed. You then enter the required data.
11. After entering the data, click Save.
12. A new variant is created with the provided data. The newly created Variant is available in the Incident Variant list on the “Incidents” tab at the different levels (Global, Template, Alert and Managed Object Specific).
13. You repeat the steps for Notifications, Third-Party Components and Auto Reactions in the respective tabs.
14. If you want to delete a variant, select that particular Variant and click Delete. The deleted variant disappears from the Variant list on the respective tab at the different levels (Global, Template, Alert and Managed Object Specific).                              

Procedure for Checking the Variants usage at different levels:

• SAP/Custom Template
• Alerts
• Template level for work modes
• Alert level for work modes

Variant settings used at SAP/Custom Template level

1. Navigate to Template Maintenance step.
2. Select SAP/Custom template.
3. Repeat the steps 4 to 10 on the Template Maintenance step to maintain the settings at the template level.
4. At the SAP/Custom template level, select variants whose status is Active on the tabs “Notifications” Incidents” and “Third-Party Components”.
5. Select Alerts tab and make sure that at least few alerts are using Template Settings. Make note of the alerts which are using Template Settings.
6. Save the changes.
7. On the DefineScope, select a MO for which the above SAP/Custom template can be assigned.
8. Navigate to SetupMonitoring step.
9. Assign the template and click on ApplyandActivate button.
10. Click on DirectoryBrowserbutton.
11. Select the Alerts tab for the MO on Directory Browser. The settings maintained in the variants at the Template level should be available on the Incidents, Notification and Third party Component tabs of the alert.

Run time behavior– If the settings are maintained for the notifications and incidents only at the Template level, then during the run time when an alert is raised, the incident and notification settings will be taken from the Template level.

Variant settings used at Alert level

1. Navigate to Template Maintenance step.
2. Select SAP/Custom template.
3. Select Alerts tab.
4. Repeat the steps 4 to 10 and performing checks in the Default Settings step.
5. At the Alert level, select variants whose status is Active on the tabs “Notifications” Incidents” and “Third-Party Components” and “Auto-Reactions” tab. Variants can be maintained for Auto Reactions also.
6. Save the changes.
7. On the DefineScope, select a MO for which the above SAP/Custom template can be assigned.
8. Navigate to SetupMonitoring step.
9. Assign the template and click on ApplyandActivate button.
10. Click on DirectoryBrowserbutton.
11. Select the Alerts tab for the MO on Directory Browser. The settings maintained in the variants at the alert level should be available on the Incidents, Notification, Third party Component and Auto Reactions tabs of the alert.

Run time behavior– If the settings are maintained for the notifications and incidents only at the Alert level, then during the run time when an alert is raised, the incident and notification settings will be taken from the Alert level.

Variant settings used at Template level for Work modes

1. Navigate to Template Maintenance step.
2. Select Custom template.
3. Ensure the user is in Expert Mode. Work Mode specific settings can be maintained when the user is in Expert Mode.
4. Select Incidents, Notifications, and Third-Party components tabs. 
5. Variants can be selected at the Work mode Level also. Perform all the relevant checks here as performed for the Incidents/Notifications and Third-party components in the above mentioned steps.
6. At the template level, select variants whose status is Active on the tabs “Notifications” Incidents” and “Third-Party Components“for a work mode.
7. Select Alerts tab and make sure that at least few alerts are using Template Settings. Make note of the alerts which are using Template Settings.
8. Save the changes.
9. On the DefineScope, select a MO for which the above SAP/Custom template can be assigned.
10. Navigate to SetupMonitoring step.
11. Assign the template and click on Apply and Activate button.
12. Click on DirectoryBrowserbutton.
13. Select the Alerts tab for the MO on Directory Browser. The settings maintained in the variants for a work mode at the template level should be available on the Incidents, Notification, and Third party Component of the alert when the corresponding work mode is selected.

Run time behavior– If the settings are maintained for the notifications and incidents at the Template - work mode level, then during the run time when an alert is raised while work mode is in progress, the incident and notification settings will be taken from the Template-work mode level

Variant settings used at Alert level for Work modes

1. Navigate to Template Maintenance step.
2. Select Customtemplate.
3. Ensure the user is in Expert Mode. Work Mode specific settings can be maintained when the user is in Expert Mode.
4. Select Alerts tab.
5. Select Incidents, Notifications, AutoReactions and Third-Party components tabs.        
6. Variants can be selected at the Work mode Level also. Perform all the relevant checks here as performed for the Incidents/Notifications, Auto Reactions and Third-party components in the above mentioned steps.
7. At the alert level, select variants whose status is Active on the tabs “Notifications” Incidents” and “Third-Party Components“for a work mode.
8. Save the changes made.
9. On the DefineScope, select a MO for which the above SAP/Custom template can be assigned.
10. Navigate to SetupMonitoring step.
11. Assign the template and click on Apply and Activate button.
12. Click on DirectoryBrowserbutton.
13. Select the Alerts tab for the MO on Directory Browser. The settings maintained in the variants for a work mode at the alert level should be available on the Incidents, Notification, and Third party Component of the alert when the corresponding work mode is selected.

Run time behavior– If the settings are maintained for the notifications and incidents at the Alert - work mode level, then during the run time when an alert is raised while work mode is in progress, the incident and notification settings will be taken from the Alert-work mode level.

Hello experts,

In the Solution manager service desk 7.1SP10, is there a way to remove the text "IRT exceeded" and "MPT exceeded" in the user status text? We do want to keep the SLA function with the green, orange and red dots. It's only the text we want to remove.

So no more "New IRT Exceeded MPT Exceeded" => this has to be just "New"

Thanks!

Kind regards,

Kenny

Hello all,

I need to configure SolMan to connect via Mobile Apps (iOS or Android). Anyone has a documentation about it?

I already found this: Solution Manager 7.1 Mobile Apps - Setup and Troubleshooting Guide

but doesnt exist a documentation?

Thx

Chris

Dear Gurus,

We have SAP SOLUTION MANAGER 7.1 Stack Level 12 (07/2014 - which is quite the latest). For

the Interactive reporting for child systems availaibilty are working fine for all ABAP

systems. However for all my child J2EE systems, the system availabilities are missing.

I am quite a newbie here, please advise me on how to check it.
Thanks.

Regards,
Stephan

Hi Experts,

I'm having an issue in deleting a technical system from Managed system configuration. I checked in LMDB and in SLD, however the technical system do not exist there.

I'm assuming that it could be in the LMDB Cache. Any idea how we can see what systems are there in LMDB Cache.

Thanks,

Haseeb Ahmed.

Dear all,

I have a requirement to adjust multi-level category when need to in ZMIN - and - by doing this make all downstream documents (ZMCR, ZMHF) to receive a new copy of categorization from ZMIN.

For now it works like this:

I create incident with 4-level categorization filled in

then create ZMCR from it - the categorization got copied over

then create ZMHF from ZMCR - the categorization got copied over

Now I am changing categorization in ZMIN, and at this point nothing happens in ZMCR, ZMHF - categorization stays old in the follow-on documents.

Is there any additional action or something I can schedule to get category updated ?

Thank you

Elena

Hi,

I have an error in Managed System configuration from the step 7. Configure Automatically.

I managing the config in Java systems.

I am trying to execute Introscope Host Adapter in Step7, but i got an error like this.

On instance : <hostname>
Connection to SMDAgent <hostname> could not be established! Reason: Smd agent Service 'Implementation as null of object entities:com.sap.smd.agent.application.wilyhost.WilyHostService is not available' not available.

On instance : <hostname>
Connection to SMDAgent <hostname> could not be established! Reason: Smd agent Service 'Implementation as null of object entities:com.sap.smd.agent.application.wilyhost.WilyHostService is not available' not available.

com.sap.smd.ServiceNotAvailableException: Smd agent Service 'Implementation as null of object entities:com.sap.smd.agent.application.wilyhost.WilyHostService is not available' not available.
at com.sap.smd.core.runtime.Runtime.getService(Runtime.java:179)
at com.sap.smd.agent.AgentContext.getService(AgentContext.java:607)
at com.sap.smd.agent.AgentContextp4_Skel.dispatch(AgentContextp4_Skel.java:183)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:721)
at java.lang.Thread.run(Thread.java:761)

I was try to restart DAA via sapmmc console and check from the os side drive:\usr\sap\DAA\SMDA98\work

file name jvm_smdagent.out

[p4://<Solman_host>:50004] Agent ready.

Exception occured. Please check log files.[Exception ID: 1411743394858 ]

Exception occured. Please check log files.[Exception ID: 1411743394863 ]

Exception occured. Please check log files.[Exception ID: 1411743394876 ]

Exception occured. Please check log files.[Exception ID: 1411743394890 ]

Exception occured. Please check log files.[Exception ID: 1411743394926 ]

9/26/14 09:56:37 AM COT [INFO] [IntroscopeAgent] Introscope Agent Release 8.2.4.0 (Build 476771)

9/26/14 09:56:37 AM COT [INFO] [IntroscopeAgent] Using Java VM version "SAP Java Server VM 1.6.0_65" from SAP AG

9/26/14 09:56:37 AM COT [INFO] [IntroscopeAgent] Trying to load agent profile based on system property "com.wily.introscope.agentProfile"

9/26/14 09:56:37 AM COT [INFO] [IntroscopeAgent] Trying to load file from E:\usr\sap\DAA\SMDA98\SMDAgent\applications.config\com.sap.smd.agent.application.wilyhost\IntroscopeSapAgent.profile

9/26/14 09:56:37 AM COT [INFO] [IntroscopeAgent] Loaded file from E:\usr\sap\DAA\SMDA98\SMDAgent\applications.config\com.sap.smd.agent.application.wilyhost\IntroscopeSapAgent.profile

9/26/14 09:56:37 AM COT [INFO] [IntroscopeAgent] Agent Metric Aging is turned off

9/26/14 09:56:37 AM COT [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.heartbeatInterval is set to 1800

9/26/14 09:56:37 AM COT [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.dataChunk is set to 500

9/26/14 09:56:37 AM COT [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.numberTimeslices is set to 3000

9/26/14 09:56:37 AM COT [INFO] [IntroscopeAgent] Looking for agent profile property "introscope.agent.extensions.directory" to locate the extensions directory.

9/26/14 09:56:37 AM COT [INFO] [IntroscopeAgent] The agent extensions directory E:\usr\sap\DAA\SMDA98\SMDAgent\applications.config\com.sap.smd.agent.application.wilyhost\ext was successfully located

9/26/14 09:56:37 AM COT [INFO] [IntroscopeAgent] Introscope Agent startup complete.

9/26/14 09:56:37 AM COT [INFO] [IntroscopeAgent] The Agent will attempt to determine its name.

9/26/14 09:56:37 AM COT [INFO] [IntroscopeAgent] Using the Agent name "SAP HostAgent SMDA98" based on the value of the System Property "com.wily.introscope.agent.agentName".

9/26/14 09:56:37 AM COT [INFO] [IntroscopeAgent] Started Error Reporting service

9/26/14 09:56:37 AM COT [INFO] [IntroscopeAgent] Initial agent name set to SAP HostAgent SMDA98

9/26/14 09:56:37 AM COT [INFO] [IntroscopeAgent.Isengard] Initiating connection attempts to the Introscope Enterprise Manager.

9/26/14 09:56:37 AM COT [INFO] [IntroscopeAgent.Isengard] The Agent reconnection delay is set to 15 second(s).

9/26/14 09:56:37 AM COT [INFO] [IntroscopeAgent] Waiting for the agent server connection to set the sampling per interval and samples per intervals

9/26/14 09:56:37 AM COT [INFO] [IntroscopeAgent.IsengardServerConnectionManager] Connected Agent to the Introscope Enterprise Manager at <solman_host>:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory. Host = "<host>", Process = "SAP HostAgent Process", Agent Name = "SAP HostAgent SMDA98".

Exception occured. Please check log files.[Exception ID: 1411743398671 ]

9/26/14 09:56:38 AM COT [INFO] [IntroscopeAgent] add filters called

Initialization done.

Exception occured. Please check log files.[Exception ID: 1411743586277 ]

Exception occured. Please check log files.[Exception ID: 1411743609233 ]

[]

Exception occured. Please check log files.[Exception ID: 1411745308670 ]

Exception occured. Please check log files.[Exception ID: 1411745331190 ]

[]

I was try to find and research like this error but i'm not lucky to get the solution. =(

Is there's anyone who encountered the same error, please share your solution, so i can proceed my last part in managed configuration.

Many Thanks in advance.

Erwin

Hi experts,

I have the following problem.

In technical monitoring I have one managed system, on which the DB availability check is not working.

The DB is a Sybase ASE 15.7

In solman_setup->system config the DB connection is configured well (green status).

Also if I open the dbacockpit of solution manager, I can see the DB of the managed system and the connection checks are working fine.

But in technical monitoring, I get the alert that the DB is not available and also that "DBA Cokcpit Connection Status" = failure.

If I go to the details of the alert, I also can't see the problem.

I did already remove and add the system more often. Further I also did remove the connection in dbacockcpit and created it again.

But now I don't have any further ideas.

Hopefuly somebody can help me.

Thank you

Hello experts, I have a question we already have the ZMIN TT created, and now we want to work with the ZMPR, when I am copying the SMPR TT, it brings the fields that you can see in the image attached, my concern is about the last three fields, it brings:

Text Det. Procedure: ZMPR0001

Date Profile: ZMPR00000002

Status Profile: ZMPR0001

If the source TT SMPR is defined in this 3 fields as

Text Det. Procedure: SMIN0001

Date Profile: IT0000000002

Status Profile: SMIN0001

Should I change those 3 fields in the ZMPR TT as:

Text Det. Procedure: ZMIN0001

Date Profile: ZMPR00000002 (????)

Status Profile: ZMIN0001

Thanks for your help,

Paul

Hi,

We are trying to execute the solution manager basic configuration steps after the support pack upgrade. We executed ibase creation ( Step 7) which created lot of activity logs & there after the step doesn't load. When we click on the step, it times out. Please advice if there is an option to clear the logs through a program or any other options.

Thanks,

Hi, i am configurating ITSM on Solution Manager SP11. The latest configuration guide I got is the 2013, prepared for  SP08. Will there be a newer version?

There are steps of Solman_setup indicated in Guide of SP08 that are not visible on solman_setup of SP11.

Thanks in advance,

Argenis

Hi,

We are having a requirement of seting up offline approval procedure in Request for Change i.e. an automatic notification will be triggered to
approver with option Approve or Reject., the approver will reply the mail with "Approve" or "Reject" and based on the response the RfC status has to be automaticaly changed to "Approved" or "Rejected".

I was searching for the soultion and found offline approval functionality is provided in SRM. Please help If anyone have done this in Solman

Thanks in advance.

Suraj

Hi Expert,

I have an authentication issue using specific services in sap solution manager. In particular when a tried to use the following services :

crm_ui_start and ags_work_change_man the following error appear:

"sso logon not possible no login ticket due to incorrect configuration"

I performed all the steps indicated in the basic configuration of the solution manager and in particular the following parameters has been

configured in the instance profile:

login/create_sso2_ticket : 2

login/accept_sso2_ticket : 1

icm/host_name_full : sman71.accenture.com

SAPGLOBALHOST: sman71

icm/conn_timeout : 8000

icm/HTTP/j2ee_0:PREFIX=/,HOST=localhost,CONN=0-500,PORT=5$$00

icm/server_port_0:PROT=HTTP,PORT=80$$,TIMEOUT=3000,PROCTIMEOUT=3000

ms/server_port_0: PROT=HTTP,PORT=81$$

Please could you help me to resolve this issue and then avoid the doublevautentication for these services?

Thanks in advance for collaboration

gio

Dear Gurus,

I would like to ask for 2 questions:

1. If I schedule a downtime for my Solman, in the Interactive Reporting (System

Availability) will show "Not available due to planned downtime". However it will show as
"No availability measurements" in all my child systems. How to automatic update the child

systems as well when the solman is having a downtime?

2. For any "Not available due to planned downtime" and "No availability measurements", can I

put a description on it (in the same page) the reason for the downtime? For example, in the
chart page, it will show 11 Sep 2014 having "No availabilty measurements", but I want to

include the reason description over there.

Your inputs are greatly appreciated.

Regards,
Stephan

Hi, am having an issue with Solution Manager, i can't get what really is the issue with it not being unreachable. it displays the attached message:

Can someone please advice on what could be the issue with this? and any possible solutions are welcomed too.