Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 45 Next »

 

SAP Server Requirements

 

Icon

To analyze ABAP code in Kiuwan, source code and information from SAP system need to be exported previously to be analyzed by Kiuwan.

SAP Extractor (SAPEX) for Kiuwan performs these tasks.

NOTE: SAPEX is expected to run in any SAP NetWeaver 7.4+ platform.

Please read How to know the SAP NetWeaver version if you need to know the SAP NetWeaver verion your are using.

Contact Kiuwan Technical Support Kiuwan Support for previous platform versions.

 

How to know the SAP NetWeaver version

Using SAPGUI to check the version of NetWeaver (ABAP Application Server)

  1. Log on to the system using SAPGUI 
  2. On the main menu, choose System > Status… 
  3. In the System: Status window you’ll see a section in the middle-right called SAP System data 
  4. Click the icon next to Product version to show the details of all the components installed on your system 



  5. The component you need to look for is called “SAP_BASIS” and is usually at the top of the list. 



  6. Release is used to identify the major release of NetWeaver, and SP-Level is used to identify the support pack installed.

 

 

What are the permissions needed to run SAPEX in SAP

Depending on your use of SAPEX (Remote or Local) the permissions are different.

Remote usage of SAPEX means that SAPEX functionality is executed within an external system. This means that you will use KLA to remotely connect to the SAP Server to extract the code and analysis it. In this remote scenario, SAP Server acts as a pure server host that provides the needed APB source files so KLA can execute the analysis on them. Therefore, KLA will use a SAP user to connect to SAP server to extract the code (i.e. to invoke the SAPEX RFCs).

In a Local usage of SAPEX, you will need to configure a SAP user with permissions to run the code extraction and execute the SAPEX programs.

Common permissions for both (Local and Remote) usage

Regardless of local vs remote usage, there are some common permissions the SAPEX user needs to be granted: 

 

Object : S_DATASET 

  • ACTVT = 06, 33, 34 

  • FILENAME = DIR_HOME/sape4k/*  

  • Note: if you configure the SAP instance to be balanced to a group of SAP servers, you will need to configure this permission in every SAP server (because DIR_HOME will be different for every SAP instance)

 

Object : S_LOG_COM 

  • COMMAND = 'ZKW_MKDIR', 'ZKW_RMDIR' 

  • OPSYSTEM  = Operating System type ( SY-OPSYS system variable)  established for SM69 commands (for example, Linux, UNIX, ANYOS, Windows NT, etc… )

  • HOST = SAP server where above commands will be executed ( "*" or SY-HOST system variable, recommended * )


Object : S_RZL_ADM 

  • ACTVT = 03

  • Needed to remove export temporary directories of SAP server 



Permissions for Remote usage

For SAPEX remote usage, SAP user must be type B  ("system") .

A type B user with above privileges should also be granted next authorizations:

 

Object : S_RFC 

  • ACTVT = 16 

  • RFC_TYPE = ‘FUGR’ 

  • RFC_NAME = ‘ZKW_SAPEX_FG’, ‘SYST’,’ RFC1’,’ SDIFRUNTIME’ 



Above permissions displayed in SAP:



Permissions for Local usage

In a Local scenario, SAP user must be type A ("dialog").

Besides common authorizations (above explained), this SAP user must also have next ones:

 

Object : S_TCODE 

  • To execute SAPEX transactions :
    • ZKW_COD,

    • ZKW_MET

    • ZKW_ANA 


Object : S_PROGRAM 
  • To execute ABAP programs thru SA38 : 
    • ZKW_SAPEX_CODE

    • ZKW_SAPEX_METADATA

    • ZKW_ANALYSIS

    • ZKW_ANALYSIS_TO

 

Distribution of SAPEX as a Transport Request

Icon

SAP Extractor for Kiuwan (SAPEX) is distributed as a Transport Request.

This way, you can easily install all the required SAPEX source programs importing the transport request into your target SAP system.

SAPEX binary files (data-file and co-file) are contained into sapex_transport.zip (located at $(AGENT_HOME)/resources/abap directory of your Kiuwan Local Analyzer installation).

 

Note: If you cannot use this installation mechanism you can also install SAPEX by manually installing source code ( please visit Manual Installation of SAP Extractor)

 

How to import SAPEX Transport Request

In this section we will import the Transport Request for SAPEX that is included in your Kiuwan Local Analyzer distribution.

 

1. Get the Transport Request files

Find the Transport Request as a zip file (sapex_transport.zip) in the $(AGENT_HOME)/resources/abap directory of your Kiuwan Local Analyzer installation.

Unzip the file into your local system. This will extract two files :

  • a data-file: R900039.NPL 
  • a co-file:    K900039.NPL

Please note that the last 3 digits of the transport numbers might be different in the most recent versions.

2. Copy the Transport Request files to your SAP System

Icon

Next, you need to copy the extracted co-file and data-file to your SAP System. 

  • K900039.NPL to your /usr/sap/trans/cofiles directory
  • R900039.NPL to your /usr/sap/trans/data directory

Please note that destination directories are for a unix sap system. In case of a SAP Windows system, it typically is <drive>:\usr\sap\trans

 

If you have direct access to your SAP system, you can copy them directly.

Otherwise, execute SE37 and execute the ARCHIVFILE_CLIENT_TO_SERVER function. Click on Test/Execute

 

Then select the files you want to import (in your local machine) and the target path (in the SAP server), check the Uppercase/Lowercase and Execute it.

 

In order to confirm the copy, you can use AL11 to check the transfer was done to the correct places.

Execute it and double click on DIR_TRANS row.

 

For cofiles, you should see something like the below image. Similarly to data directory.

 

3. Import the Transport Request files

Next, the SAPEX Transport Request must be imported into your SAP system


Execute STMS and click on Import Overview

 

Then you will see your Import Queue(s).

 

Double-click on the queue and you will see the requests for that queue.

 

Now you should add the SAPEX Transport Request (Extras >> Other Requests >> Add

 

Click Transp. Request to see available Transport Requests:

 

Select it

Click Yes.

 

Then you will see the SAPEX Transport Request, select it and click Import Request.

 

Select the Options tab as below.

 

 

Once the import process is finished, you can check it using SE09

 

Finally, use Object Navigator (SE80)... And you will see SAPEX installed on your SAP System.

 

 

4. Create OS Commands (ZKW_MKDIR and ZKW_RMDIR)

After importing SAPEX Transport Request, you must create OS commands (ZKW_MKDIR and ZKW_RMDIR)

To do it, please follow instructions at Create OS commands (ZKW_MKDIR and ZKW_RMDIR)

 

Additional steps for local execution 

5. Create OS command to launch the analysis (ZKW_KLA_AGENT)

Only in case you decide a local scenario, you must create OS command (ZKW_KLA_AGENT)

To do it, please follow instructions at Create OS command to launch the analysis (ZKW_KLA_AGENT)

 

 

 

  • No labels