Software provisioning manager (abbreviated with SWPM in this blog) offers many different processes, such as installation, system copy and system rename. Although we have a clear understanding how often our tools were downloaded, it is hard for us at SAP to tell which processes are used how often and with which runtime – which would help us to invest our efforts into improving those procedures you are using most.

 

To better understand how you are using the tool and to be able to identify possible hot spots concerning the runtime that we should investigate, we introduced a new option into the latest version of software provisioning manager. With this, the tool gathers statistical data of the runtime and offers you to send them to SAP.

 

In detail, as of SAPinst version 2014.09 (available as of September 2014), the success dialog of software provisioning manager offers a link to send feedback and statistical runtime data to SAP:

01_SLA_Success.png

This is the case for all processes supported by software provisioning manager, such as installation, system copy or system rename, as long as you are using the latest version of software provisioning manager (updated in September or earlier). Also, we are offering similar feedback options for other software logistics tools already today and plan to enable further software logistics tools accordingly.

 

But back to software provisioning manager – by clicking the feedback button on the success dialog pop-up window, an evaluation form is opened in your Web browser:

02_SLA_Form.png

Now, if you should be willing to support SAP in gaining more knowledge about the usage of our processes, you could read through the disclaimer, accept it by clicking the corresponding box and press the Send to SAP button, which would send the anonymous statistical runtime data gathered during the execution of software provisioning manager to SAP via email (prerequisite: the host where the GUI runs has access to the Internet – feedback cannot be sent when you run software provisioning manager in dark mode).

 

Optionally, you could enrich this statistical data with your feedback about the executed process by entering it in the fields below the send button. If you like, you could also enter a contact email address, so that we could contact you in case of questions concerning your feedback (once your feedback is dealt with, we would delete your email address from our records, so that no personal data is stored also in the final feedback).

 

 

What data is sent?

For us, it is important to provide full transparency about what information would be sent to SAP. So, before pressing the Send to SAP button, you can take a look at the Process XML field at the end of the form, listing the exact statistical runtime data that got collected during the run and that would be sent to SAP, if you press the button:

03_SLA_XML.png
Of course, sending any feedback or runtime statistics to SAP is completely voluntary and does not have any impact for you on support or in any other form.

 

In this course, we do not gather or send any business data or data that falls under data privacy protection (such as the IP address), but technical data about the actual procedure, the runtime and the used platform – for example:

  • Platform (OS/DB) –
    such as Linux plx291 2.6.32.36-0.5-default #1 SMP 2011-04-14 10:12:31 +0200 x86_64 x86_64 x86_64 GNU/Linux and HDB for SAP HANA
  • Start + end date of the executed process
  • Used SAPinst version
  • Executed service –
    such as SAP NetWeaver 7.4 Support Release 1 > SAP HANA Database > SAP Systems > Application Server Java > Standard System
  • Number of CPUs and CPU family –
    such as 24/x86_64
  • Statistical runtime data –
    such as
    <startdate>1396606912</startdate>
    <enddate>1396608552</enddate>
    <runtime>1640</runtime>

 

For what is this data used?

First, as mentioned above, we at SAP want to better understand how our tools are used – that is, which processes offered by software provisioning manager are used more often than others.

 

Also, we want to identify possible hot spots, such as procedures that run especially long, so that we could analyze them for issues or optimization potential.

 

 

And finally, we want to build up a knowledge base concerning expected runtimes our processes take on the supported platforms and products – think of something like an anonymous statistical database of executed processes.

 

Sample_Data.png

With this, we plan to better prioritize where to invest and where to optimize (for example, as one process is used very often or as it has a very long runtime that we would like to optimize).

 

 

In addition, this knowledge could allow us in the future to make predictions concerning the runtimes to be expected for the processes offered by our tools. Wouldn’t it be great, if you could start software provisioning manager, select a service and the tool would tell you in what range the runtime could be expected according to our knowledge of similar procedures on similar platforms and boundary conditions? This would help you to better plan the processes and with this, we hope that we can improve your satisfaction with the tools and processes we offer.

 

The figure on the right shows a mockup with sample data to give you an idea of the information we could provide in the future with your help.

 

Also, you can directly influence our development by providing feedback to the teams responsible for the procedures you were just using.

 

Overall, I want to encourage you to support us to increase the predictability and the quality of our processes by sending statistics and personal feedback to SAP after a run – it should not be much effort for you and I am confident that it will have an impact on our prioritizations, so that we can further optimize the procedures you are relying on. Thanks a lot for your support in advance!

 

What do you think of this option? Do you plan to use it?

To report this post you need to login first.

8 Comments

You must be Logged on to comment or reply to a post.

    1. Boris Zarske Post author

      Hello Karthik,

      You could take a look at INSTSLANA.XML in the software provisioning manager directory after a successful run by opening it in a Web browser (if you copy the file over to another host for opening it for example in Internet Explorer, you would also require the CSS file, I guess) – there, you would get some statistics about runtimes of sinlge steps of the executed procedure. Also, we offer Migtime for heterogeneous system copies, as described in SAP Note 784118. Apart from that, only the log file would be available.

      If this should not suffice, it would be interesting to know what other information you would expect.

      Thanks,

      Boris

      (0) 
  1. Christoph Ostrop

    i often use the feedback to SAP, but

    all the feedback-data and statistical data can not show,

    that the user has had 3 times of restart SWPM or SUM from scratch,

    so it will only show the last sucessful run of that tools,

    but not the pain before by resetting and restarting again and again.

    (0) 
    1. Boris Zarske Post author

      Hi Christoph,

      Sure, that is not something we could track automatically, but for this, you could use the feedback form and enrich the statistical data with your personal feedback (where we also ask how many incidents occurred during the procedure). So, we would be happy to get also feedback in this direction, which you could now provide. (But I understand your point that it would be better if you could provide this feedback right during the issues you were facing and not only after you managed to execute a successful run – nevertheless, this would have spoiled the statistics about how often the single options get used.)

      Thanks,

      Boris

      (0) 
  2. Akshay Gupta

    Hello Boris,

    I was wondering if this is available for the customers? You mentioned “And finally, we want to build up a knowledge base concerning expected runtimes our processes take on the supported platforms and products – think of something like an anonymous statistical database of executed processes.”

    I am planning to run an SAP System Rename of an SAP Application Server ABAP 7.31 on Linux/Oracle and wanted to find out if there are any estimates of the run time?

    Any reference would be appreciated.

    Best Regards,

    Akshay

    (0) 
    1. Boris Zarske Post author

      Hello Akshay,

      Sorry for not getting back to you earlier, but I just came back from a parental leave.

      Unfortunately, details are not clarified here, as we are still in the process to build up such a knowledge base (with the support of all the feedback you send us back) – then, based on the data we receive, we will decide how such information could be made available also to customers.

      Nevertheless, system rename normally is a very quick procedure, it normally does not take longer than 20-30 minutes (independent from database size, as the database is not changed there). If you are unsure, I recommend to perform a quick test run to find out the runtime to be expected.

      I hope this rough information helps – if you should already have executed the procedure, I hope you were fine with it!

      Best regards,

      Boris

      (0) 
      1. Akshay Gupta

        Hello Boris,

        No worries, hope things are good at your end.

        We haven’t been able to do the rename yet but the prospects to do now in near future look likely.

        How can i do a quick test run to get an idea of the timeline? Is it available in SWPM, would appreciate if you can elaborate as i would like to find more about it.

        Another thing, you mentioned that “database is not changed there”. Well I am kind of assuming that the SAP+DB Rename both. For ex – My current SAP/DB SID is CDF and i would like to rename that to PQR (Both SAP & DB including). Can you please elaborate on what you meant by no change in DB.

        Many thanks in advance for your precious time and efforts.

        Regards,

        Akshay

        (0) 
        1. Boris Zarske Post author

          Hello Akshay,

          Thanks a lot, everything fine :-)!

          Sure, you can perform a quick test run – for this, please just download Software Provisioning Manager from http://service.sap.com/sltoolset –> Software Logistics Toolset 1.0, system rename is offered as one service there, as described on the system rename SCN page: http://scn.sap.com/docs/DOC-32851. Again, according to my experience, the procedure is normally performed pretty quick.

          Sorry, my statement was misleading indeed. Of course, you can optionally also change the DBSID – what I meant with my statement was that the procedure does not change the data/technical configuration parameters stored inside the database, such as connectivity data. So, you would have to perform follow-up activities like required after a system copy, to adapt the system to its new identity (for example, if you have used the SAPSID as part of logical system names). So, the system would get new system IDs as part of the procedure (and also start up after the rename), but would require some follow-up activities. I hope this clarifies things – if not, please feel free to contact me again.

          Best regards,

          Boris

          (0) 

Leave a Reply