English | Deutsch | Español

InterfaceProfiler: Getting it up and running!

January 15, 2019 | From Dr. Oleksandr Panchenko

Hey guys, you probably have already read or heard about the InterfaceProfiler and are wondering what would it cost to get it in terms of time and effort investment. Let’s talk about this topic today.

Virtual_Forge_InterfaceProfiler_ScreenI have no fixed number of hours for you because it mainly depends on three things:

  • Size of your software system landscape. Basically, the number of systems you want to monitor.
  • Simplicity and speed of IT processes in your organization. For example, how long will it take to transport a role into a system and to assign this role to a user?
  • Your expectations about the quality of the data sources. Do you need more data to answer all your questions? Do you want to add another data sources?

InterfaceProfiler has a central architecture: there is a central system where the data is collected and processed. All other systems that have to be monitored are connected to this central instance of the InterfaceProfiler to regularly ship the collected data. So, it is required to setup the connection between them, thus obviously you will need to touch each connected system. I have two good news for you: first, it is not required to do all it simultaneously, you can start with few systems and extend the scope of the analysis by connecting further system whenever it fits into your plan; second, the actual "net" time to connect a so called source system is probably an hour or two. You will need to import a role into the system, create a communication user, assign this role to the user and configure an RFC destination from the central system to the source system. If SAP workload monitor is already active – you are done with the installation, if not – you will need to switch it on. That’s it!

In case you want to collect more data and monitor file operations on the application server or download/upload operations triggered by SAP GUI you will have to connect such system as so called satellite system. To have this option, a small piece of InterfaceProfiler code will be transported into the satellite system. After this is done you will need to enhance few SAP standard development objects and switch our data collectors on. An experienced ABAP developer will handle it in less than an hour. It is done in a development system anyway and then transported into the productive part of the system landscape. Now, you can add some overhead depending on the smoothness of your IT processes and multiply this by the number of the systems you want to observe.

After you have done this, InterfaceProfiler can immediately start collecting data for you. In order to be able to analyze the data properly InterfaceProfiler will need some human input – host names or IP addresses could be named and given some metadata: what type of server it is? is it used in the productive environment? does it belong to a group of other servers? From our project experience it can take a day to prepare a rough description of a system landscape including major communication partners. I need to admit that to make it done most probably it will be required to check with other departments and obtain some expert knowledge here and there. But hey! This is exactly what InterfaceProfiler was made for! It provides a solid data base about the system landscape and communication ways in it and makes the necessary pre-processing steps – decisions should be made by humans.

Topics: UnderstandYourRisk