Part 1: Solution Manager 7.2 - Installation and Configuration - I - Installations

Part 2: Solution Manager 7.2 - Installation and Configuration - II - Configurations

Part 3: Solution Manager 7.2 - Installation and Configuration - III - Changes from 7.1 to 7.2

Part 4: Solution Manager 7.2 - Installation and Configuration - IV - Managed System Config - General Info

Part 5: Solution Manager 7.2 - Installation and Configuration - V - Managed System Config - ABAP System

Part 6: Solution Manager 7.2 - Installation and Configuration - VI - Managed System Config - HANA DB



Solution Manager 7.2 is already in Ramp-Up.

 

I watched the video of the chearful team of Solution Manager 7.2.

As System Administrators we willl also be installing and configuring Solution Manager 7.2 from now on.

So I decided to install it on premise.

 

Cloud version of Solution Manager 7.2 is also available on SAP Cloud Appliance Library https://cal.sap.com/

(SAP Solution Manager 7.2 SPS01 on SAP HANA for Content Activation Evaluation of a Customer's Own Documentation)

 

I am going to try to write some series of blogs on Solution Manager 7.2 in terms of System Administration.

They will be about installations, configurations, changes and managed system configurations.

Below you can find the installation specific part of this series of blogs.

 

Preperation Steps

  • Since Solution Manager 7.2 is in Ramp-Up yet you need to apply for this. You can find detailed info about Ramp-Up in links Demystifying SAP's Ramp-Up process and SAP Ramp-Up
  • Prepare a system for installation. If possible find a system that you could install SM 7.2 on HANA DB. Unfortunately I did not have chance to use HANA DB. I installed my system on SQL Server 2012. My system is a virtual system with 4 vCPU and 32 GB of RAM and enough disks.
  • Download DVDs

       SM72_Blog_I_DVD.jpg

  • Obtain Master Guide and Installation Guides
  • Read SAP Notes about Solution Manager 7.2
  • Preperatory Steps on the system
    • Turn Off UAC
    • Turn off Automatic Updates
    • Turn off Windows Firewall
    • Turn off IE ESC
    • Timezone Settings
    • Regional Settings
    • Configure Hostname
    • Configure Page File Size
    • Configure DEP
    • Configure Folder Options
    • Configure Start Menu
    • Configure Command Prompt
    • Activate Telnet Client
    • Install Notepad++

 

 

After preperation steps I followed the Implementation sequence from Master Guide in below order.

 

Master Guide

 

For information on the installation of SAP Solution Manager go to link SYSTEM PROVISIONING - SAP SOLUTION MANAGER 7.2 SPS 01 BASED ON SAP NETWEAVER 7.4 ABAP +JAVA (from master Guide: see service.sap.com/instguides --> SAP ComponentsSAP Solution ManagerRelease 7.2 --> InstallationSystem Provisioning for SAP Solution Manager 7.2)

 

From PAM page you can go below links about Solution Manager 7.2

SAP Road Map

Product Homepage

Master Guide

Installation / Upgrade Guide

SAP Help Portal

Release Notes

Release Restrictions Note

Additional Release Information

SAP Community Network

 

Installation and Configuration

 

The installation of SAP Solution Manager 7.2 SP01 needs to be run in the following way:

 

1. Instal DB Software (Microsoft SQL Server 2012)

 

Installed DB Software Microsoft SQL Server 2012 SP1 and then updated to SP2.  (Upgrade to and Installation of SQL Server 2012 in an SAP Environment)

SM72_Blog_I_DB.jpg

SM72_Blog_I_DB2.jpg

   

2. Install the SAP Solution Manager 7.2 SP01 ABAP system with SWPM and the resulting stack.xml.

 

Followed below Guide for installing ABAP part of the system.

Installation of SAP Systems Based on SAP NetWeaver 7.1 to 7.5 Using Software Provisioning Manager 1.0: MS SQL Server, Operating System: Windows, Technology: ABAP

 

 

SID

SMA

Instance Numbers

00,  01

 

SM72_Blog_I_ABAP_1.jpg

SM72_Blog_I_ABAP_2.jpg

 

Post Installation Steps for ABAP:

 

    • Logon to System
    • Perform the automated initial setup
    • Install the SAP license
    • Perform the consistency check
    • Configure the Transport Management System
    • You perform post-installation steps for the application server ABAP
      • Upload and set system profiles using transaction RZ10

Configure your Solution Manager 7.2 profile parameters according to the note

2048519 - Profile parameters for SAP Solution Manager 7.2

      • Create logon and RFC server groups using transactions SMLG and RZ12
      • Create operation modes using transaction RZ04
      • Schedule standard jobs using transaction SM36
      • Configuration of SLD data supplier using transaction RZ70 (After installation of Java and configuration of SLD)
      • Perform load generation using transaction SGEN
    • If required, you install additional languages and perform language transport
    • SAP Kernel Release 7.40 and Higher: You perform IP Multicast Configuration
    • You configure the user management
    • You ensure user security
    • If required, you perform the client copy
    • SAP systems based on SAP NetWeaver 7.40 and higher only: If required, you change the keys for the secure storage
    • You apply the latest kernel and Support Packages

You run Maintenance Planner instead of Maintenance Optimizer transaction using the link   Maintenance Planner for applying SP Stack 01. You can have detailed information about planner using Maintenance Tools: Maintenance Planner and Maintenance Optimizer

These are the screenshots from maintenance planner. You can download stack.xml file on download files tab of the application.

SM72_Blog_I_Mplanner_1.jpg

SM72_Blog_I_Mplanner_2.jpg

You get stack.xml file and download Support Packages

 

Before applying the stack you should check below notes and according to directions you need to apply some of them before, some of them during update and some of the others after SUM update.

I advise you to read the notes carefully because this can effect the update and later configurations.

 

2084104 - Central Note - Software Update Manager 1.0 SP14 [lmt_005]

1595736 - Solution Manager: Overview on Release Information Notes

2229953 - Solution Manager 7.2 SP Stack 01S0014395147: recommended corrections

1668882 - Note Assistant: Important notes for SAP_BASIS 730,731,740

2248091 - Change to reimplementation handling

2087917 - SAP Solution Manager 7.20 SP1 - Basic functions

2216794 - ABAP Download Service: Correction of Transformation

2166856 - API roles: Maintenance of organizational levels

2189071 - DGP: Improved clean up for waiting export entries

1472465 - SAP Solution Manager 7.1 and 7.2 - System Landscape Setup Guide

2154957 - Unified Rendering for SAP_UI 740

 

You download SUM also to update the ABAP system and run the tool. You can see some screenshots from the tool below.
SM72_Blog_I_ABAP_SUM_1.jpg

SM72_Blog_I_ABAP_SUM_2.jpg

 

You can see initial and target stack SP versions and levels in below report of SUM.

SM72_Blog_I_ABAP_SUM_4.jpg

    • You perform a full system backup

 

 

3. Install the SAP Solution Manager 7.2 SP01 Java system with SWPM from the Java DVD.

 

Followed below Guide for installing Java part of the system.

Installation of SAP Systems Based on SAP NetWeaver 7.1 to 7.5 Using Software Provisioning Manager 1.0: MS SQL Server, Operating System: Windows, Technology: Java

 

SID

SMJ

Instance Numbers

02,  03

SM72_Blog_I_Java_1.jpg

SM72_Blog_I_Java_2.jpg

SM72_Blog_I_Java_3.jpg

 

Post Installation Steps for Java:

Java component patches shall be downloaded from the Support Portal at https://support.sap.com/swdc -> Software Download -> Support Packages and Patches -> Browse Our Download Catalog -> SAP Technology Components -> SAP Solution Manager -> SAP Solution Manager 7.2 -> Solution Manager JAVA Stack. After download, place the files corresponding to the below software component list, in a preferred folder in order to implement the patches. See the SUM guide for further details (see link above, 'Chapter: 7 Applying Single Component Updates and Patches Using a Manually Prepared Directory').

        • J2EE ENGINE SERVERCORE 7.40 -> OS independent: Patch 20 (or higher) for J2EE ENGINE SERVERCORE 7.40 SP 11
        • J2EE ENGINE LM-CORE 7.40 -> OS independent: Patch 5 (or higher) for J2EE ENGINE LM-CORE 7.40 SP 11
        • J2EE ENGINE CORE TOOLS -> OS independent: Patch 1 (or higher) for J2EE ENGINE CORE TOOLS SP 11
        • J2EE ENGINE APPLICATIONS -> OS independent: Patch 4 (or higher) for J2EE ENGINE APPLICATIONS SP 11
        • J2EE ENGINE FRAMEWORK 7.40 -> OS independent: Patch 6 (or higher) for J2EE ENGINE FRAMEWORK 7.40 SP 11
        • J2EE ENGINE FACADE 7.40 -> OS independent: Patch 1 (or higher) for J2EE ENGINE FACADE 7.40 SP 11
        • LMNWABASICCOMP 7.40 -> OS independent: Patch 1 (or higher) for LMNWABASICCOMP 7.40 SP 11
        • ENGINEAPI 7.40 -> OS independent: Patch 6 (or higher) for ENGINEAPI 7.40 SP 11
        • LM NWA BASIC APPS 7.40 -> OS independent: Patch 4 (or higher) for LM NWA BASIC APPS 7.40 SP 11
        • UME ADMINISTRATION 7.40 -> OS independent: Patch 6 (or higher) for UME ADMINISTRATION 7.40 SP 11
        • LM CONFIGURATION WIZARD 7.40 -> OS independent: Patch 1 (or higher) for LM CONFIGURATION WIZARD 7.40 SP 11
        • In case you do operate Introscope 9.5 (and not yet 9.7):
          WILY INTRO AGT 9.5 MIN J5VIASM -> OS independent: Patch 1 (or higher) for WILY INTRO AGT 9.5 MIN J5VIASM SP 06

 

Use SUM and apply the patches like below.

SM72_Blog_I_Java_SUM.jpg

    • You configure the user management
    • You ensure user security
    • You run automated configuration
      • SLD Configuration

Use http://<hostname>:<port>/sld/fun and enable SLD automatically.

 

SM72_Blog_I_Java_SLD_1.jpg

SM72_Blog_I_Java_SLD_2.jpg

 

    • You perform a full system backup

 

 

And this is the end of the installation phases of Solution Manager 7.2.

I will continue on Configurations blog coming soon.

 

See you soon.




In recent years we got again and again asked by customers whether it would be possible to track how intensive Business Process Analytics and Business Process Operations Dashboards  are used by the user community to which it was rolled-out. As of SAP Solution Manager 7.1 support package 14, this kind of usage analysis is available. This functionality will allow you to track, that you did not just activate another SAP Solution Manager functionality, but that this functionality is really used operationally.

 

If you access the Maintain BPO Reporting Infrastructure section from within your Business Process Operations work center, then you see a new tab strip Usage Analysis.

First you get an overview about the number of times that Business Process Analytics / Business Process Operations Dashboards got executed within a given time frame.

Then you get to see the top 5 users that executed the respective application most often.

Overview and top 5.png

 

After this you get detailed sections per application. In those sections you can also see which key figures were executed when.

Details.png

 

Then comes a section where you can see which key figures have been executed most/least often (no matter if the key figure was accessed via Analytics or Dashboard(s). You can also run an optional analysis if key figures exist where the data collection was activated, but where the collected data was never consumed so far.

Tops and flops and not used.png

 

The last section allows to check for a historic trend for a single selected key figure.

Historic trend.png

 

 

Further reading

You can find all necessary information about Business Process Analytics in this document. More information on Business Process Improvement for SAP solutions can be found here.

 

Frequently Asked Questions about Business Process Monitoring and Business Process Analytics are answered under http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Monitoring and

http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Analytics respectively.

 

The following blogs (in chronological order) provide further details about Business Process Analytics and Business Process Monitoring functionalities within the SAP Solution Manager.

Hello all, this is Evan Stoddard, one of the Product Managers for SAP Solution Manager.

 

SAP Solution Manager Product Management is pleased to announce that SAP Solution Manager 7.2 SPS01 on Linux/SAP HANA was released to customers and partners via the SAP Cloud Appliance Library (SAP CAL) today. This is the first time we have used SAP CAL for the SAP Solution Manager, and also the first time we have done this in the middle of a SAP Solution Manager Ramp-up.

 

The scope of this system is to provide customers and partners an environment where they can upload solution documentation from their own 7.1 systems to the 7.2 system in SAP CAL, and then perform and evaluation the content activation process to make their documentation visible in the new 7.2 solution documentation UI.

 

By using SAP CAL, it's possible to create a system in under 1 hour from a standard solution, and then log on an perform the upload and activation process. The system can be restored over and over from backup via the cloud infrastructure, so that the one-time activation process can be easily repeated.

 

See the official announcement in the SAP CAL SCN community here:

 

http://scn.sap.com/community/cloud-appliance-library/blog/2016/01/18/sap-solution-manager-72-coming-soon-to-sap-cal#

 

The training materials for this scenario are now available on the SAP Solution Manager Early Knowledge Transfer site at http://suppport.sap.com/ekt-solutionmanager -> SAP Solution Manager 7.2 Learning Maps -> Content Activation -> Preparation -> Test and Evaluate the Solution Documentation Activation Procedure With SAP Sol Man 7.2 in SAP CAL.

In 2011 the Business Process Operations dashboards were introduced. Those dashboards are especially used to track progress during business process improvement activities. As those dashboards also used by senior management in order to understand where progress is achieved and where it is not it is always a challenge to provide the right level of granularity. Many large companies who are operating all around the globe and where the organization is split into different markets, regions or business units asked how this can be reflected in our dashboards?! The special challenge is typically the fact that the markets or regions are not directly reflected as such in the respective SAP system, i.e. no company code, sales organization or plant represents a specific market or region. Instead a market comprises several different company codes, sales organizations or plants.

 

Since SAP Solution Manager support package 12, this challenge is solved by so called virtual characteristics. With the help of of those virtual characteristics you are now able to build dashboards that provide a global overview about all your markets, e.g. as shown in the dashboard below the data is split between the 4 markets America, Asia, Europe & Japan. Additionally you see one column comprising possible company codes that are not (yet) assigned to any market.

Dashboard overview.png

If you configured some additional parent child relationships between your panels, then a forward navigation is possible. So if you click on the cell for "Open and overdue FI-AR items" in America, then you get to see which company codes are part of the market.

Dashboard details.png

So how can you get your markets, regions shown in your dashboards?

 

Getting virtual characteristics into a dashboard


If you access your setup environment for Business Process Operations dashboards, then you have to assign the respective virtual characteristic on Analytical Key Figure Instance (AKFI) level to a Category or Drilldown dimension.

Use virt char in dashboard.png

 

Now if you look into your SAP Solution Manager you will not see any such virtual characteristic immediately. You have to create those first, before they can be used.


Defining new virtual characteristics

 

If you want to create and define virtual characteristics according to your needs, then please access the BPO reporting infrastructure from within the Business Process Operations work center. As of support package 12 you should find there one tab strip Virtual Characteristics which will help you with some kind guided procedure. As the data access to the generic Infocube/Twincubes in Business Process Analytics and BPO dashboards happens technically via so called Semantic IDs, you have to create such new Semantic IDs first. The semantic ID defines as an example whether the value '0001' in parameter 1 is representing plant '0001' or company code '0001' or sales organization '0001'. For our dashboard shown above we defined some new semantic ID 'ZVIRT_MARKET'.

1 define semantic ID.png

In a 2nd step we defined a new virtual characteristic ZVIRT_CHARSTIC_MARKET (the one that we assigned to an AKFI as seen above) and assigned to it the newly created semantic ID.

 

2 Map virt char and semantic ID.png

In the 3rd step we defined for our new virtual characteristic that the 'concrete values' for our markets are America, Asia, Europe & Japan. Those are the 4 markets displayed on the dashboard at the beginning of this blog.

 

3 create virtual char.png

 

In the 4th and final step we defined for every possible virtual characteristic value which "real values" from the SAP system are comprised, e.g. our market Europe consists of the company codes 3001 to 9999, DK01, FR01 and IT01. In case of sales key figures you would need to define another mapping for Europe which uses semantic ID ERP_VKORG in order to also map which sales organizations belong to market Europe.

 

4 map virtual to real.png

 

After this mapping definition and assignment of new virtual characteristics to your respective AKFIs used in the dashboard, you can lean back and enjoy your new dashboards which automatically split your data according to the newly defined markets, regions, business units etc.

 

Further reading

You can find all necessary information about Business Process Analytics in this document. More information on Business Process Improvement for SAP solutions can be found here.

 

Frequently Asked Questions about Business Process Monitoring and Business Process Analytics are answered under http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Monitoring and

http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Analytics respectively.

 

The following blogs (in chronological order) provide further details about Business Process Analytics and Business Process Monitoring functionalities within the SAP Solution Manager.

With SAP Solution Manager 7.1 support package 14 another puzzle piece has been added towards a complete "Business Process Improvement Suite" as I would call it. While we provided Business Process Analytics as the root cause analysis tool in 2010 (meanwhile also available in an ad-hoc version and as native iPad app) and added a dashboard layer on top in 2011, we now shipped a new SAPUI5 application called "Dependency Diagrams".

 

As we ship such a vast KPI content out-of-the-box with close to 1.000 KPIs, customers can easily lose the overview on what is measured and tracked in what way and for what purpose. With the help of the Dependency Diagrams you can build kind of KPI trees where you bring the different KPIs into some logical, hierarchical order. You can visualize the dependency chains of KPIs and get the "picture" updated with your live data.

 

The easiest way to access the new application, is to define a new favorite in the user menu. Just specify BSP application AGS_KPI_TREE and select WebContent/index.html from the value help as start page.

Note: Remember to activate the corresponding BSP service in transaction SICF.

Runtime BSP.png

 

When you then access the application you can select one diagram that must have been defined beforehand, e.g. looking at a diagram about the typical financial business KPI "Days Sales Outstanding (DSO).

 

Initial select.png

 

After selecting the diagram you get to see the root level (here Days Sales Outstanding itself) and the dependent level 1 KPIs. In our example all five level 1 KPIs are collected via Business Process Analytics, i.e. why you see an Analyze-hyperlink which allows a direct forward navigation into Business Process Analytics. The backend data from your SAP BusinessSuite or SAP S/4 HANA system can be shown as count of documents/items (e.g. 241 deliveries or 310 SD invoices) or as one accumulated monetary value (e.g. 2,7 million Euro or 311,3 million USD).

The tiles that you see could be

  • populated by Business Process Analytics data
  • populated by Business Process Monitoring data
  • populated via query from a connected SAP BW system
  • not populated with any data and just used for modeling/visualizing

 

Below SD Orders not billed and Open customer items we see a '+' icon, so we can further expand the tree in those areas.

 

Small tree.png

 

As we know that the majority of billing documents is created via billing run, we put another KPI below the SD Orders not billed. This additional KPI looks specifically at all error messages that were raised during billing due runs. One of the most typical error messages is the problem of incomplete sales order items and hence you can further expand to see Missing fields in SD documents.

Big tree.png

So with the help of this application you can

  • Bring business BW reporting and operational Business Process Analytics data for root cause analysis together in one view
  • Structure your KPIs in meaningful dependency diagrams, so that every manager and subject matter experts understands the leverage that one low level KPI might have on any (business) KPI on top, like DSO.
  • Set threshold values so that the numbers in the tiles get a green, amber or red rating
  • Decide if you put your focus on document numbers or monetary values (and which target currency)
  • Use the forward navigation to get from this overview into the actual root cause analysis with Business Process Analytics.

 

This application can be used on any device and any screen resolution, because of the SAPUI5 user interface.

 

Configuration

 

There are no diagram templates shipped with this application. Instead you have to model everything yourself. The configuration has some similarities to the configuration of Business Process Operations dashboards in SAP Solution Manager. So you have to create Analytical Key Figure Instances (AKFIs) first, where you define which data should be displayed from which source and define potential thresholds. Then you model the respective Dependency Diagram / KPI Hierarchy and bring the AKFIs into some logical order.

 

In order to access the configuration application it is easiest to create a new favorite in the user menu. For this specify AGS_RI_KPIHIERARCHY_SETUP as Web Dynpro application.

setup webdynpro.png

If you access the setup environment, there is always just one root. After this you always just specify which AKFI is child of which other AKFI (identified by technical name not description). You can always have more than one child for every parent tile. Based on these parent/child relationships the application calculates the hierarchy level automatically and arranges the tiles from top to bottom.

Diagram setup.png

 

So if yo have Business Process Analytics already up and running in your SAP Solution Manager 7.1 with support package 14, then you should be only a few clicks away from creating your own Dependency Diagram and show it to your management in order to get the budget for your desired business process improvement activities.

 

Further reading

You can find all necessary information about Business Process Analytics in this document. More information on Business Process Improvement for SAP solutions can be found here.

 

Frequently Asked Questions about Business Process Monitoring and Business Process Analytics are answered under http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Monitoring and

http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Analytics respectively.

 

The following blogs (in chronological order) provide further details about Business Process Analytics and Business Process Monitoring functionalities within the SAP Solution Manager.


AS ABAP SLD registration process:


You should perform ABAP SLD registration by executing transaction RZ70.



2016-01-21_13-19-54.jpg



in case you have problem with SLD_UC registration  (DETAIL: TP SLD_UC not registered!!!!) please consult this link (read comment from vijendar reddy  )!!



AS Java SLD registration process:



The properly configure this service, the following must be done.

Use the Destinations Service to:

 

1. Set up the registration by creating a destination called "SLD_DataSupplier" of type HTTP. Enter the following configuration settings. (Note: The specified user must have the user role "SAP_SLD_DATA_SUPPLIER" or higher on the target SLD Server.)

  • Appropriate URL (http://<host>:<port>)
  • Authentication should be set to BASIC
  • Appropriate User Name and Password

2. Set up the AS Java access to the SLD by creating a destination called "SLD_Client" of type HTTP.

Enter the same configuration settings as in the SLD_DataSupplier destination.

(Note: The specified user must have user role "SAP_SLD_GUEST" or higher. Aditional write access permissions may be required by certain applications. Refer to the corresponding application documentation for SLD access requirements.)



2016-01-21_13-00-43.jpg

 

2016-01-21_13-08-00.jpg

 

2016-01-21_13-09-17.jpg

2016-01-21_13-10-54.jpg

 

2016-01-21_13-11-03.jpg

 

 

Now you can start registration of yours AS Java in the SLD by executing following action:

2016-01-21_13-15-44.jpg

 

 

pls execute red box button

 

2016-01-21_13-16-28.jpg

 

 

At the ned go tyou SLD and check is there your AS JAVA and AS ABAP present/registered !!

 

Happy registering! 

 

BM

Changing the configuration of the Metrics and Alerts in the template and activating the changed settings can be done from front end applications like System Monitoring and Alert Inbox.  This functionality is provided from front end applications to reduce the number of steps in changing the configuration of Metrics and Alerts and to make the configuration change process fast and simple.

 

Note:The functionality mentioned in this blog is specific to Solution Manager 7.2 release. Also please note that when the document is viewed in the PDF format, Red rating icons are shown in dark blue and Yellow rating icons are shown in light blue.

 

 

Procedure for changing the Configuration from Alert Inbox

 

Settings that can be changed for an Alert from Alert Inbox


Following data can be changed for an alert from Alert Inbox.

  • Alert Active/Inactive status
  • Notification variant data
  • Incident variant data
  • Third part Component variant data
  • Auto Reaction variant data
  • Alert Active/Inactive status

 

 

Settings that can be changed for a metric from Alert Inbox

 

  • Metric Active/Inactive status
  • Threshold Type – It can be changed to Info only
  • Threshold Values

 

Scenario 1 – Custom template has been assigned to the managed object and an alert related to the managed object is available in Alert Inbox.

 

       1.     Navigate to Alert Inbox on “System & Application Monitoring” work center.

       2.     Select a record on System Alerts/Database Alerts/Host Alerts query and click “Change Configuration” button.

       3.     The following pop up appears when a custom template has been assigned to the managed object.

1.png

Following data can be changed for an alert from Alert Inbox.

  • Alert Active/Inactive status
  • Notification variant data
  • Incident variant data
  • Third part Component variant data
  • Auto Reaction variant data


Each wok mode is shown as a tab in which the selected alert is active. User can make the changes at the work mode level also.


Options “Apply changes to template <template name>” and “Apply changes on the managed object only” will be displayed on the pop up.


When a Custom template is assigned to the managed object, then user will have the option to change the settings at the managed object level or at the template level.


4.     Make necessary changes and select the option “Apply changes on the managed object only” and click on “Apply Changes” button.

The changes made are applied only at the managed object level.


5.     Select another record on System Alerts/Database Alerts/Host Alerts query where a custom template has been assigned to its managed object and there are no managed object specific settings and click “Change Configuration” button.


6.     Select the option “Apply changes to template <template name>” and click on Apply changes button.

The alert settings will be changed at the template level and the change is reflected for all the managed objects on which this template has been applied. The list of managed objects using the this template can be found on clicking the link “Show affected managed objects” next to the option “Apply changes to template <template name>”


Clicking on the “Close” button without performing any action on the pop up cancels the operation. Functionality is same as mentioned above while changing the configuration of alert from Alert Group details page.

Scenario 2 – SAP template has been assigned to the managed object and an alert related to the managed object is available in Alert Inbox.


                            The following pop up appears when a SAP template has been assigned to the managed object and the user had selected an alert in Alert Inbox and clicked on “Change Configuration” button.


2.png

User will have the option to change the settings only at the managed object level. Make the changes and click on “Apply Changes” button.


If managed object specific settings are maintained for the managed object already and if user wants to make further settings for the alert, then user will have the option to change the settings only at the managed object level.


            Functionality is same as mentioned above while changing the configuration of alert from Alert Group details page.

 

Scenario 3 – Custom template has been assigned to the managed object and the user would like to change the configuration of the metric from Alert Inbox.

 

On the Alert details table select a metric and click on “Change Configuration” button.

3.png

The following pop up appears when a custom template has been assigned to the managed object. All the Active work modes for the metric will be shown as separate tabs.

 

4.png

 

User will have the option to change the settings at the managed object level or at the template level.


Options “Apply changes to template <template name>” and “Apply changes on the managed object only” will be displayed on the pop up.


If the option “Apply changes to the template” is selected, the metric settings will be changed at the template level and the change is reflected for all the managed objects on which this template has been applied. The list of managed objects using the this template can be found on clicking the link “Show Managed objects where the changes take effect” next to the option “Apply changes to template <template name>”


If the option “Apply changes only on the managed object” is selected, changes made will be applicable only for the managed object.


Scenario 4 –SAP template has been assigned to the managed object and the user would like to change the configuration of the metric from Alert Inbox.

 

1.     If a SAP template is assigned to the managed object, then user will have the option to change the settings only at the managed object. Following pop up will be displayed, and the user should click on the “Apply Changes” button after making the specific settings on the pop up. The changes made for the metric will be at the managed object level.

5.png

2. If managed object specific settings are maintained for the metric then user will have the option to change the settings only at the managed object only. Following pop up will be displayed and the user should click on the “Apply Changes” button after changing the settings on the pop up.

 

6.png

Make necessary changes and click on “Apply Changes” button. The changes made are applied only at the managed object level.

 

3. Clicking on the “Close” button without performing any action on the pop up cancels the operation.

 

Procedure for changing the Configuration from System Monitoring

 

Settings that can be changed for a metric from System Monitoring

  • Metric Active/Inactive status
  • Threshold Type – It can be changed to Info only
  • Threshold Values


Scenario 1 – Custom template has been assigned to the managed object and the user would like to change the configuration of the metric from System Monitoring.

1.     Navigate to System Monitoring application on “System & Application Monitoring” work center.

2.     System Monitoring application is launched.


7.png


3.       Click on any tile shown on “Status Overview” panel and navigate to System View.

4.       Click on any Category icon on the tile related to the system and navigate to “System Hierarchy” view.

5.       Hover on a metric in the “Event and Metric” view.


8.png


6.       Click on “Change Configuration” link.


The following pop up appears when a custom template has been assigned to the managed object and no managed object specific settings exist for the metric.

9.png

    • All the Active work modes for the metric will be shown as separate tabs.
    • User will have the option to change the settings at the managed object level or at the template level.


Options “Apply changes to template <template name>” and “Apply changes on the managed object only” will be displayed on the pop up.

If the option “Apply changes to the template” is selected, the metric settings will be changed at the template level and the change is reflected for all the managed objects on which this template has been applied. The list of managed objects using the this template can be found on clicking the link “Show Managed objects where the changes take effect” next to the option “Apply changes to template <template name>”


If the option “Apply changes only on the managed object” is selected, changes made will be applicable only for the managed object.

 

Scenario 2– SAP template has been assigned to the managed object and the user would like to change the configuration of the metric from System Monitoring.

 

    • User will have the option to change the settings only at the managed object. Following pop up will be displayed, and the user should click on the “Apply Changes” button after making the specific settings on the pop up. The changes made for the metric will be at the managed object level.

10.png


    • If managed object specific settings are maintained for the metric already then user will have the option to change the settings only at the managed object only. Following pop up will be displayed and the user should click on the “Apply Changes” button after changing the settings on the pop up.

11.png

Make necessary changes and click on “Apply Changes” button. The changes made are applied only at the managed object level.

Clicking on the “Close” button without performing any action on the pop up cancels the operation.


 


This setting is global for all users!

 

1. Enter Workcenter "customizing mode"

 

Add "&sap-config-mode=X" to the end of the workcenter-URL:

 

Example:

ags_workcenter?sap-client=100&sap-language=DE&sap-config-mode=X

or

ags_workcenter?sap-config-mode=X



2. Right-click on one of the workcenter tab and select "Settings for current Configuration":

step2.png



3. Click on "Tabstrip Control"

step3.png


4. Click on "Re-Sort"

step4.png



5. Define the order of the tabs using the buttons "Up" and "Down"

step5.png

Hi to all,

during SUM deployment of SP01 of Solution Manage 7.2 I run in to problem where SUM process stopped in the process EHP_INCLUSION in the log file SPDA_EHP_INCLUSION.LOG you can find following line:

 

"2WETN607 The import of Prepackages is not allowed in this system"SAPK-74014INSAPGWFND""SAP_GWFND""740"Solman "

 

 

 

What you should do is following :

 

start the report RSSETPACKAGEDEPLOYMENT and put the following

 

for the Software component SAP_GWFND  :

 

- instead of T put P in the Maintenance  Type

 

sum_prob.jpg

 

I hope this was helpful!

ITSM & ChaRM – Reminder / Escalation emails using Date Management (Dates and Durations) Part 3

 

This is the continuation to the Part 1 and Part 2 blogs.

 

ITSM & ChaRM – Reminder / Escalation emails using Date Management (Dates and Durations) Part 1

 

ITSM & ChaRM – Reminder / Escalation emails using Date Management (Dates and Durations) Part 2

 

 

In this part, the Custom Duration field is made available in the Web UI configuration for the relevant document type.

The sample requirement discussed in Blog 1 and 2 is again used for Part 3.This is the sample requirement in context of Part 1/2 of the Blog –

 

When an Incident has been forwarded, the requirement is to send a Reminder/escalation email after a specific wait time if the Status is still unchanged.


 

 

Below are the Steps:


SPRO Configuration to enable the linking of the custom duration to the BTDateSET

blog-3-1.png

blog-3-2.png

 

 

Custom Enhancement has to be created for the Standard component (In my Case it is Incident) AIC_INCIDENT_H. This has to be done before proceeding with the required settings for the Custom Context nodes.

blog-3-3.png

**Refer the Blog by Harshit Kumar for completing the above step**

How To Enhance a Web UI Component in SAP CRM - CRM - SCN Wiki

 

blog-3-4.png

blog-3-5.png

 

Click Continue till reaching ‘Create Links to Custom Controller’ and then

 

blog-3-6.png

blog-3-7.png

 

The BOL relation as shown in the above screenshot is available only if it has been maintained in the SPRO as shown earlier in this document.

 

blog-3-8.png

 

 

The Superclass in the Context node’s Implementation class is changed to CL_CRM_UIU_BT_DATE_CN to handle dates.

blog-3-9.png

 

blog-3-10.png

 

Delete the Check for the errors (Remove the extra Base_Entity_Name attribute from the class) and activate.

blog-3-11.png

 

Log off and Logon to see the Attribute ‘Date’ available under the new custom node.

blog-3-12.png

 

**The Blog from Chand Shaik is used as the base reference for the next few steps**

Adding Date profile's Date type Fields as Context Attribute to the UI component

 

The below steps were done different from that of the blog to match to the DURATION specific requirement.

 

 

In the ‘ON_NEW_FOCUS’ method the replacement code was updated as below to refer the Z_FWDDURA duration created in SPRO date profile.

blog-3-13.png

blog-3-14.png

TIP : ***For Date, it is T and for duration, it is D for lv_category. The LV_date_type is the Date type or the Duration id defined in the Date Profile***

 

The GETTER and SETTER methods were activated for all the attributes below Date attribute (This may not be required- Did this as trial and error for getting troubleshooting ‘Not Bound’ text in the value of the field in the Web UI).

blog-3-15.png

blog-3-16.png

 

The Web UI configuration now will have the Custom node ZFWDDURA.

blog-3-17.png

blog-3-18.png

blog-3-19.png

 

<---------------End of the blog--------------->

ITSM & ChaRM – Reminder / Escalation emails using Date Management (Dates and Durations) Part 2

 

 

This is the continuation to the Part 1 blog -- ITSM & ChaRM – Reminder / Escalation emails using Date Management (Dates and Durations) Part 1

 

In this part the PPF action for the Email is configured for the below sample requirement discussed in Blog 1.

 

This is the sample requirement in context of Part 1 blog --

When an Incident has been forwarded, the requirement is to send a Reminder/escalation email after a specific wait time if the Status is still unchanged.

 

Below are the Steps:


Action Definition:

 

blog-2-1.pngblog-2-2.png

 

Here I have used the Smartforms mail option. If you want to use other email options like HTML mail forms check the blog from  Dolores Correa.

Incident Management and Change Request Manageme... | SCN

 

 

 

Conditions:


The Action for the email will be scheduled when the Status “Forwarded” is set. Below is the schedule action for that.

blog-2-3.png

 

The Email should be ready to be sent when the status is still in “Forwarded” and when the Current date & time is higher than the Maximum time limit.

blog-2-4.png

 

The custom date type parameters for the condition can be identified under the Deadlines set.

blog-2-5.png

 

I have also set the Time of Processing for the action as “Processing using Selection report”.

blog-2-6.png

 

The background job scheduled using Transaction CRMC_ACTION_JOB will handle the execution of the email action. This Job would process the Actions for the Incidents, which currently meets the Start conditions.

blog-2-7.png

 

***I have also written Part 3 blog. If you are interested in displaying the Wait time Duration as an editable field in the Web UI configuration for the relevant document type then you can refer it.***

 

ITSM & ChaRM – Reminder / Escalation emails using Date Management (Dates and Durations) Part 3

ITSM & ChaRM – Reminder / Escalation emails using Date Management (Dates and Durations) Part 1

 

In few of my previous projects, I have come across the requirement to send an Automatic Reminder or Escalation email. This email has to be sent automatically when the allowed time limit exceeds. There are Standard Reminder/ Escalation email Actions available under the Service Request management for SLA escalations. However, for General Reminders/Escalations on delays in Processing, etc., there is No Standard functionality currently available in Solution Manager – ITSM & ChaRM. I hope this blog would help to handle such requirements.

 

I have used a sample requirement for the context of this Blog. It goes like this -- When an Incident has been forwarded, the requirement is to send a Reminder/escalation email after a specific wait time if the Status is still unchanged.

 

Below are the Steps to do this:


Update the applicable Date profile with the Custom date types, date rules, and duration.

blog.png

 

The Custom duration is for saving the Maximum allowed time before the email could be sent.

blog-1-2.png

 

The below date types are for calculating the Clock Start Time and the Time it exceeds the allowed wait period.

blog-1-3.png

 

The Custom date rule is to calculate the maximum allowed/ wait time. In this example, it is for calculating ZFWD_LMT_MAX.

blog-1-4.png

 

The XML code for the date rule is updated as below.

blog-1-5.png

 

***If you want to use a different set of Date rules for your situation then you can refer the Blog written by Deepa Madyalkar in the CRM space Creation of Date rule using XML rules. - CRM - SCN Wiki

 

 

Assign the new Custom date types, date rules and durations to the applicable Date profile.

blog-1-6.png

blog-1-7.png

blog-1-8.png

blog-1-9.png

blog-1-10.png

blog-1-11.png

blog-1-12.png

 

The Duration can be assigned with a Default value (here I have assigned it as 24 hours) if the maximum Time limit is Fixed.

 

In order to maintain the duration as a variable value and make it available for edit in the CRM UI of the document check the ***Part 3 blog***.

 

ITSM & ChaRM – Reminder / Escalation emails using Date Management (Dates and Durations) Part 3

 

blog-1-13.png

 

The Settings related to SLA Escalation can be used for updating the duration.

 

The Current Date and time is assigned to the date type ZFWD_LIMIT when the status is changed to ‘Forwarded’. The below setting will do that. Then based on the date rule and the duration (Z_FWDDURA) the ZFWD_LMT_MAX will be calculated for the trigger point for the escalation or reminder email.

blog-1-14.png

blog-1-15.png

 

***The Configuration related to the PPF Action and conditions for the Escalation or Reminder email are explained in Part 2 blog***

ITSM & ChaRM – Reminder / Escalation emails using Date Management (Dates and Durations) Part 2

Hi All,

 

I am happy and excited to right my first ever blog on this community. I have taken so much from this great community while resolving many issues reading many wonderful blogs. Its time to return back something to help others. I am writing about an experience, which can be described as metric explosion as per CA.

 

How it started ?

Few days back our network team came up with information that network utilization between two servers (one was hosting MII application and other was hosting wily EM) is very very high and resulting into packet loss. Same day we got some alert for high memory utilization for MII application.

 

What was the Error?

While checking the Wily Introscope Agent logs (location /usr/sap/<SID>/SMD<XX>/SMDAgent/temp/IntroscopeAgent.<SID>_<Instance>_server<x>), I found below exception

 

[IntroscopeAgent] IntervalHeartbeat.execute threw executing: Remove Metric Data

java.lang.ArrayIndexOutOfBoundsException: 5047

    at com.wily.util.adt.CanonicalObjectPoolWithKey.removeCanonicalObjectWrapperInternal(CanonicalObjectPoolWithKey.java:357)

    at com.wily.introscope.agent.recording.MetricRecordingAdministrator.removeMetricFromThreadLocalCache(MetricRecordingAdministrator.java:1194)

    at com.wily.introscope.agent.recording.MetricRecordingAdministrator.removeMetricData(MetricRecordingAdministrator.java:1090)

    at com.wily.introscope.agent.recording.RemoveMetricDataWatcher.ITimestampedRunnable_execute(RemoveMetricDataWatcher.java:81)

    at com.wily.util.heartbeat.IntervalHeartbeat$BehaviorNode.execute(IntervalHeartbeat.java:944)

    at com.wily.util.heartbeat.IntervalHeartbeat.executeNextBehaviorAndCalculateSleepTime(IntervalHeartbeat.java:489)

    at com.wily.util.heartbeat.IntervalHeartbeat.access$300(IntervalHeartbeat.java:28)

    at com.wily.util.heartbeat.IntervalHeartbeat$HeartbeatRunnable.run(IntervalHeartbeat.java:665)

    at java.lang.Thread.run(Thread.java:761)

 

I noticed that before this exception , number of current live metrics were in range of 1000-14000, but after the exception number of live metrics started to grow up and reached above one million. (in the same file you can search for logs like below)

 

11/09/15 02:19:03 PM GMT [INFO] [IntroscopeAgent] Number of current, live metrics=1012

12/11/15 03:02:28 PM GMT [INFO] [IntroscopeAgent] Number of current, live metrics=1035158.

 

It was clear to me that this issue is causing high memory and network utilization.

 

On the below mentioned link (From CA support), I was able to find more information about interface mentioned in the exception and what is a metric explosion:

https://support.ca.com/cadocs/0/CA%20Application%20Performance%20Management%209%206-ENU/Bookshelf_Files/HTML/APM--NET%20Agent%20Implementation%20Guide/index.htm?toc.htm?1479622.html?intcmp=searchresultclick&resultnum=1993

 

How it was fixed?

To fixed the problem we restarted the sap java application and it resolved high network and memory utilization.

 

As of now I am not aware of the aware of the permanent solution but I am working on the same. I know there is a memory leak issue with ISAgent version 9.1.0.X but we were using ISAgent 8 when this issue occurred. Will update my blog when I will be having a permanent resolution for the same.

 

Thanks and Regards

Sachin Gupta

!!! Great News from SAP Solution Manager !!!

 

 

SAP Solution Manager 7.2 has started Ramp-Up successfully.

Watch the ramp-up video on YouTube.

 

Please refer to the SAP Help Portal for more information.

Early Knowledge Transfer (formerly known as Ramp-Up Knowledge Transfer) will be available soon at http://support.sap.com/ekt-solutionmanager.

Yes, that's right, automatically updating a system after a product upgrade is possible in SAP Solution Manager since a while now. Unfortunately many customers do not yet have this in place and are still doing everything manually where some automation is possible (not saying it's perfect in other words but the automation can help reduce efforts).


So here goes a small blogs post to hopefully inform more customers, partners, community members that this option exists.


I'm talking about the customizing that can be set in SAP Solution Manager by following the instructions of SAP NOTE 1832868 - Automatic Managed System Adjustment after Product Upgrade


An example:

You've got ERP 6 EHP6 and you update it to ERP 6 EPH7. If your system is well maintained and you don't run into an exception which is not covered (see SAP NOTE 1832868 mentioned above), the LMDB will automatically update the system so it's reflected that it has been updated to EHP7.


Figure out what went wrong


To figure out what went wrong when it doesn't work, you'll need to check the job log of SAP_LMDB_NOTIFY_LDB*


If you don't see much detail in there, you might not yet have SAP NOTE 2211344 - Enhancement of the SAP_LMDB_NOTIFY_LDB job log by detailed error descriptions


CR Content consistency (important)


One of the most common reasons why it would not work are CR content inconsistencies so to avoid those, you should read this blog post  by SAP Mentor Matt Fraser so you know how to check the content so you can keep it consistent.

Actions

Filter Blog

By author:
By date:
By tag: