How to set up Gekkobrain for SAP HANA
Table of contents:
In order to get started with Gekkobrain for SAP HANA you need to have an active 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 email@example.com or contact your Gekkobrain Partner. Then an account will be created and you will receive the login details in an e-mail.
Before you can start doing an assessment you need to setup the first project in Gekkobrain. A project in Gekkobrain 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.
In the menu choose ‘New System’
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.
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.
In the menu choose ‘New Project’
In the form you enter
The System-ID you just created
Choose ‘HANAREADY’ as project template
A project description
Choose ‘Add New’
You have now created a new project in Gekkobrain. Go to the Menu ‘Project List’ in the Menu, where you will see the newly created Project.
The final step you need to go through before you can send the first inspection to Gekkobrain is to get the Account ID. You will need this Account ID, when you start the extraction report in SAP.
In the menu choose ‘Account Information’, where you will find your account id.
SAP NetWeaver 7.02 as of SAP_BASIS SP14
SAP NetWeaver 7.31 as of SAP_BASIS SP09
SAP NetWeaver 7.40 as of SAP_BASIS SP02
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 “Help_executing_remote_static_checks.PDF”.
If you do not have a system of the required version you could goto 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
Log into your Gekkobrain account and go to the menu ‘Download Extractor’ to download the latest version of the extractor. The system will download a zip file. In the file, you will find the components you need to get started. The Gekkobrain extractor only needs to be deployed into your DEV-System.
There are 3 different ways to upload the source code you need for Gekkobrain:
Import the transports to your system from the ‘Transport’ folder in the zip (see transport no. in readme.txt in the folder)
Manual creation of the report/includes in SE38
The Code Inspector Extractor:
Open the file ‘zhanalyzer_send_https.txt’ - copy all the source code - and paste it into SE38 (as a new report). The report name in SAP should be ZHANALYZER_SEND_HTTPS
Open the file ‘zhanalyzer_lib.txt’ - copy all the source code - and paste it into SE38 (as a new include). The include name in SAP should be ZHANALYZER_LIB
Creation of Objectset and variant for SAP Code Inspector
Open the file ‘zhanalyzer_create_sci_data.txt’ - copy all the source code - and paste it into SE38 (as a new report). The report name in SAP should be ZHANALYZER_CREATE_SCI_DATA
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.
Project (Only HANAREADY exists so leave as is)
Your API Key for the system (Where do I find the API Key - See section ‘Create a new system in Gekkobrain’)
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’)
Your Account ID. (Where do I find the Account ID? See section ‘Finding the Account-ID in Gekkobrain’)
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
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
Select this Option if you want to have this report create and run the inspection
Responsible user of the selected variant (leave blank for global)
The selected check variant (leave blank for use of ZHANALYZER) Use F4 search help for filling of fields B and C
Responsible user of the object set (leave blank for global)
The selected object set (leave blank for use of ZHANALYZER) Use F4 search help for filling of fields D, E and F
Version of the object set selected
Select this option if you want to transfer an existing inspection
Responsible user of the inspection (leave blank for global)
The selected inspection. Use F4 search help for filling of fields H, I and J
Version of the inspection selected
Check this and you will send the version with the highest number available of the selected inspection
Execute report ZHANALYZER_SEND_HTTPS. Variant ZHANALYZER and objectset ZHANALYZER will be created. The object set will contain development packages starting with Z, Y and all namespaces registered for development.
You can also execute the report ZHANALYZER_CREATE_SCI_DATA to create or reset the variant and objectset.
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, Objectset and Inspections.
To do this start report ZHANALYZER_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 objectset ZHANALYZER and variant ZHANALYZER. These will be created if they do not exist.
This will take some time to execute so it should be done in background.
Start by using transaction SCI. Name and Create a new inspection. Select objectset ZHANALYZER (field A) and variant ZHANALYZER(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 succesful follow the instructions below (Transfer existing inspection).
You can transfer an existing inspection with report ZHANALYZER_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
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 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.
You can trigger a manual Code Inspection if needed. This is done using the SAP Standard Code Inspection Tool (SCI).
Follow the instructions on how to create the variant and objectset (See Initialize the Code inspector Variant)
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)
Create a new inspection - referring to the variant ‘ZHANALYZER’ and the object set you created in step 3.
Run the inspection
Follow the instructions above in “Transfer existing inspection.”
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. In order to filter out these objects, you must extract the UPL information from SOLMAN and get it uploaded to Hanalyzer.
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:
Press ‘Fld Selectn Output’
Mark ‘PGMID’ in the Program Group
Mark ‘Object Name’ in the Object Group
Mark ‘Object Type’ in the Object Group
Mark ‘Object Executions’ in the Key Figs
Unmark ‘Counter’ in the Key Figs
Enter the custom name space in ‘Object Name’ in the Object group - e.g Z* and Y*
Enter the Year(s) you want to extract in ‘Calendar Year’ in the Time group
Mark ‘Use DB Aggregations’ in the Settings group
Empty the field ‘Max. no. of hits’ in the Settings group
Download as local file (unconverted)
Send the downloaded file to the Hanalyzer team for Upload
For additional assistance please contact the Gekkobrain team on firstname.lastname@example.org
When the Extractor in SAP has completed the transfer of inspections, you are now ready to go. Log into Gekkobrain and see the first assessment of your inspections.
In the menu and choose ‘Project List’
Find the entry with the ‘Project/System id’ you wish to see the assessment for
Choose ‘Project Cockpit’
You will then see the first assessment of your inspections.
In order to understand the findings, feel free to contact us on email@example.com, or refer to our online blogs and whitepapers.