Logo

Table of Contents:

HANA Readiness Assessments

Introduction

The User Interface

Installation

Latest release

This documentation refers to the latest release of the Gekkobrain SCI Extractor version 2.8

How to get an account

In order to get started with either a ‘Ready for SAP HANA’, you need to have an active Gekkobrain account and have access to this account as an Account Administrator. If you don’t have an account yet, then you can contact us at sales@gekkobrain.com or contact your Gekkobrain Partner. Then an account will be created, and you will receive the login details in an e-mail.

How to setup your first ‘HANAREADY’ project

Before you can start doing an assessment you need to setup the first project in the Gekkobrain Cloud. A project in the Cloud is always linked to a System-ID (which should match your SAP System-ID) for which you will do the HANA Readiness inspections. You can define multiple systems and projects in Gekkobrain for the same account.

Create a new system in Gekkobrain

  1. In the menu choose ‘New System’
  2. In the form you enter
    • The System-ID for the SAP system you want to inspect
    • A description for the system
    • Choose ‘Add New’

Go to the Menu ‘System List’ in the Menu - and you will see the newly created System-ID.

The system you have just created will get an API-key. You will need this API key when you send inspections to your Gekkobrain account.

Create a new ‘HANAREADY’ project in Gekkobrain

After you have created a system, the next step is to create a new “HANA Ready” project. You will need to link the project to the System ID, you have just created in the previous step.

  1. In the menu choose ‘New Project’
  2. In the form you enter
    • The System-ID you just created
    • Choose ‘HANAREADY’ as project template
    • A project description
  3. Choose ‘Add New’

You have now created a new HANAREADY project in Gekkobrain. Go to the Menu ‘Project List’ in the Menu, where you will see the newly created Project.

Finding the Account-ID in Gekkobrain

The final step you need to go through before you can send the first inspections to Gekkobrain is to get the Account ID. You will need this Account ID, when you start the extraction report in SAP. See FAQ

How to download and install the SCI Extractor release 2.8

System requirements for the Gekkobrain SCI Extractor

If your current SAP system is older than the listed requirements above, then you can export the code and execute the checks in a reference system(>= version 7.40 SP8) see note 2011106 or read the guide Help_executing_remote_static_checks

If you do not have a system of the required version, you could go to CAL.SAP.COM and create an instance of “SAP NetWeaver AS ABAP and SAP BW 7.50 SP02 on ASE [Developer Edition]”. You will install the Gekkobrain program on this machine. Export your source code from the development system import on the reference system. Follow the instructions regarding Manual inspection

Download the SCI Extractor

Log into your Gekkobrain account and go to the menu ‘Download Extractor’ to download the latest version of the SCI extractor. The system will download a zip file. In the file, you will find the components you need to get started. The Gekkobrain SCI Extractor only needs to be deployed into your DEV-System.

There are 2 different ways to upload the source code you need for Gekkobrain:

  1. Import the transports to your system from the ‘transports’ folder in the zip (see transport no. in readme.txt in the folder)
  2. Manual creation of the report/includes in SE38
    • The Code Inspector Extractor:
      • Open the file ‘zgekkobr_hanalyzer_send_https.txt’ - copy all the source code - and paste it into SE38 (as a new report). The report name in SAP should be ZGEKKOBR_HANALYZER_SEND_HTTPS
      • Open the file ‘zgekkobr_hanalyzer_batch_run.txt’ - copy all the source code - and paste it into SE38 (as a new report). The report name in SAP should be ZGEKKOBR_HANALYZER_BATCH_RUN
      • Open the file ‘zgekkobr_hanalyzer_lib.txt’ - copy all the source code - and paste it into SE38 (as a new include). The include name in SAP should be ZGEKKOBR_HANALYZER_LIB
    • Creation of Object Set and Variant for SAP Code Inspector
      • Open the file ‘zgekkobr_hanalyzer_sci_data.txt’ - copy all the source code - and paste it into SE38 (as a new report). The report name in SAP should be ZGEKKOBR_HANALYZER_SCI_DATA

How to setup and run the SCI Extractor

Select Communication method

In this very first step, you need to decide how you plan to send inspection data to Gekkobrain. You can use either web services or file transfer to send your inspection data to the Gekkobrain Cloud. We recommend that you use web services for the integration, but if the network settings in your setup does not allow for HTTP/HTTPS call from your SAP System, then you can use file transfer instead. You can use the SAP Standard report RSWF_TEST_HTTP to check if it is possible to send data using web services.
Start the report and enter the URL: “http://hanalyzer.gekkobrainhosted.com/api/object” and press F8. If the report returns HTTP Response Code 200 you can use web services for the transfer of inspections. If not, you can do a manual file transfer.

Using HTTPS for Cloud Communication

Its possible to use SSL for all cloud communication - see the following guideline to set it up.

Report /GEKKOBR/HANALYZER_SEND_HTTPS

The Account/System info Pane

Field description:

  1. Project (Select either HANAREADY or PERFORM project – depending on the project scope)
  2. Your API Key for the system (Where do I find the API Key - See section ‘Create a new system in Gekkobrain’)
  3. SAP System ID. This should be your SAP System ID defined in Gekkobrain (Where do I find the System ID? See section ‘Create a new system in Gekkobrain’)
  4. Your Account ID. (Where do I find the Account ID? See section ‘Finding the Account-ID in Gekkobrain’)

The Communication pane

Field description:

  1. Data transfer using http/https selected
    • SSL Client created with STRUSTSSO2 to enable HTTPS.
    • If you need to go through a proxy this is the host
    • If you need to go through a proxy this is the service
  2. Data transfer using files selected
    • Prefix all the files with this value
    • Select this option if you are saving files on the application server (Foreground and background)
    • Select the path created with transaction FILE
    • Select this option if you are saving files using the SAP GUI client (foreground only)
    • Path where the files will be saved using SAP GUI Client

How to extract and upload UPL or SCMON data to your assessment

On average 55-60 % of the custom source code in a productive system is not used. All this development does not need to be fixed for HANA Readiness or Performance improved. In order to filter out these objects, you must extract the UPL/SCMON information and get it uploaded to the Gekkobrain Cloud.

Download UPL from SOLMAN

If UPL is activated in production, the SAP system will collect the usage information. It will be transferred to SOLMAN (BI Cubes). To get the UPL you should therefore log into SOLMAN and start transaction RSA1.

In the list select ‘InfoProvider’ -> ‘SAP Solution Manager’ -> ‘SAP Solution Manager - Custom Code Lifecycle Management’.

Mark the InfoProvider ‘UPL Information (Year) 0SM_UPL_Y’ and select ‘Display Data’. First you need to define the fields relevant for output:

  1. Press ‘Fld Selectn Output’
  2. Mark ‘PGMID’ in the Program Group
  3. Mark ‘Object Name’ in the Object Group
  4. Mark ‘Object Type’ in the Object Group
  5. Mark ‘Object Executions’ in the Key Figs
  6. Unmark ‘Counter’ in the Key Figs
  7. Press ‘F8’
  8. Enter the custom name space in ‘Object Name’ in the Object group - e.g Z* and Y*
  9. Enter the Year(s) you want to extract in ‘Calendar Year’ in the Time group
  10. Mark ‘Use DB Aggregations’ in the Settings group
  11. Empty the field ‘Max. no. of hits’ in the Settings group
  12. Press ‘F8’
  13. Download as local file (unconverted)
  14. Send the downloaded file to the Gekkobrain team for Upload

Download SCMON from SOLMAN

If SCMON is activated in production, the SAP system will collect the usage information. It will be transferred to SOLMAN (BI Cubes). To get the UPL you should therefore log into SOLMAN and start transaction RSA1.

In the list select ‘InfoProvider’ -> ‘SAP Solution Manager’ -> ‘SAP Solution Manager - Custom Code Lifecycle Management’.

Mark the InfoProvider ‘UPL Multiprovider Year 0SM_UPLMY’ and select ‘Display Data’. First you need to define the fields relevant for output:

  1. Press ‘Fld Selectn Output’
  2. Mark ‘PGMID’ in the Program Group
  3. Mark ‘Object Name’ in the Object Group
  4. Mark ‘Object Type’ in the Object Group
  5. Mark ‘Object Executions’ in the Key Figs
  6. Unmark ‘Counter’ in the Key Figs
  7. Press ‘F8’
  8. Enter the custom name space in ‘Object Name’ in the Object group - e.g Z* and Y*
  9. Enter the Year(s) you want to extract in ‘Calendar Year’ in the Time group
  10. Mark ‘Use DB Aggregations’ in the Settings group
  11. Empty the field ‘Max. no. of hits’ in the Settings group
  12. Press ‘F8’
  13. Download as local file (unconverted)
  14. Send the downloaded file to the Gekkobrain team for Upload

Releases