Logo

Table of Contents:

Installation

Latest release

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

How to download and install the SCI Extractor

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

The SCI Extractor is part of the Gekkobrain Extractor Framework. Use the following guideline to download the package

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:

The Communication pane

Field description:

The Inspection Pane

    • E: The selected object set (leave blank for use of ZHANALYZER) Use F4 search help for filling of fields D, E and F
    • F: Version of the object set selected

Initialize/RESET the Code inspector Variant and Object set

Execute the report /GEKKOBR/HANALYZER_SCI_DATA to create or reset the variants and object sets.

Run and transfer code inspection

Small Installations

The extractor uses SAP Code inspector to analyze the custom code. For installations with a small amount of custom code the extractor can create Variant, Object set and Inspections.

To do this start report /GEKKOBR/HANALYZER_SEND_HTTPS.

On the Account/system pane you need to enter the API Key (field B) and the Account ID (field D) from the Gekkobrain cloud.

On the communication pane leave http transfer (field A) selected and rest blank for plain http transfer. If you have created an SSL id in STRUSTSSO2 select this in SSL Client identity (field B) and you will use HTTPS. If you need to go through a proxy (fields C and D) enter the values given from your network administrator

On Inspection Pane select Field A for creation of a new inspection and leave rest blank on this pane to use object set ZHANALYZER and variant ZHANALYZER or ZGEKKOBR_PERFORM (depending on the project type you wish to transfer). These will be created if they do not exist.

This will take some time to execute so it should be done in background.

Larger Installations

Start by using transaction SCI. Name and Create a new inspection. Select object set ZHANALYZER (field A) and variant ZHANALYZER or ZGEKKOBR_PERFORM (depending on the project type you wish to transfer) (field B). Select the Execute… button.

If you want to run in background, select field C and choose a server group in field D and select field E. If you are using ATC and exemptions remember to check field H. A job is spawned you can see in transaction SM37 name is typically ‘RS_CI_PARALLEL’

If you want to run in foreground, select field F and field G. If you are using ATC and exemptions remember to check field H.

When the job is finished check the inspection with transaction SCI. Set your cursor to the Inspection name field and use the F4 search help. Look for your inspection and note that it should have a green light in the column executed.

If the inspection is finished successful follow the instructions below (Transfer existing inspection).

Transfer existing inspection

You can transfer an existing inspection with report /GEKKOBR/HANALYZER_SEND_HTTPS.

On the Account/system pane you need to enter the System ID and corresponding API Key (field B and C) and the account no (field D) from the Gekkobrain cloud.

On the inspection Pane select Existing inspection (field G) position cursor in Inspection (field I) and use F4 search help to select your newly created inspection

HTTP

On the communication pane leave HTTP transfer (field A) selected and rest blank for plain http transfer. if you have created an SSL id in STRUSTSSO2 select this in SSL Client identity (field B) and you will use HTTPS. If you need to go through a proxy (fields C and D) enter the values given from your network administrator

File

On the communication pane select Manual file transfer (Field E). Select whether to store files on the application server or use the client to store them. See The communication pane for further field description.

Manual inspection with remote objects

You can trigger a manual Code Inspection if needed. This is done using the SAP Standard Code Inspection Tool (SCI).

  1. Follow the instructions on how to create the variant and object set (See Initialize the Code inspector Variant)
  2. Create a new object set in SCI containing the remote objects you want to check e.g Z* and Y* (see the Help_executing_remote_static_checks.PDF in the ZIP)
  3. Create a new inspection - referring to the variant ‘ZHANALYZER’ or ‘ZGEKKOBR_PERFORM’ and the object set you created in step 3.
  4. Run the inspection
  5. Follow the instructions above in section “Transfer existing inspection”

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.

Use the following guideline to extract and upload either UPL or SCMON date to your assessment