SAPEX Installation for Local Scenarios

Common Installation steps for Local and Remote scenarios

1. Create ZKW_SAPEX package

It is recommended to create a package named ZKW_SAPEX to hold all entities created for SAPEX.

To create the ZKW_SAPEX  package you can use the transaction SE80 as follows:

After creating the ZKW_SAPEX package, you can follow the next steps.

2. Install support classes 

Using the Class Builder (transaction SE24) in source code mode, create and activate all the ZKW_CL_* classes, and the ZKW_CX_* exception classes.

Toggle to Source Code - Based Class Builder and paste the content of the source file (substituting any previous content).

Switch back to Form-Based Class Builder to see the complete class.

After importing all the classes, you will see them under the ZKW_SAPEX package:

3. Install source code extraction programs 

Using the ABAP Editor (transaction SE38), create the ZKW_SAPEX_CODE and ZKW_SAPEX_METADATA programs

Open the Source view.

and paste the source code provided by SAPEX.

After saving, you will see all the SAPEX objects.

Note: Do not forget to activate all the created objects.

4. Create OS commands (ZKW_MKDIR and ZKW_RMDIR)

Using transaction SM69, create the following OS commands:

• ZKW_MKDIR
• ZKW_RMDIR

ZKW_MKDIR

Used for creating directories in the SAP system: 

• mkdir -p ? for Unix
• cmd /C mkdir ? for Windows

Note: The command configured must create all intermediate directories.

ZKW_RMDIR

Used for deleting a directory and all its contents in the SAP system: 

• rm -rf ? for Unix
• cmd /C rmdir /s /q ? for Windows.

Note: To ensure that a proper rmdir command is selected, register the ZKW_SAPEX_RMDIR_CHECK to avoid security issues. This ensures that the command is one of the allowed RMDIR commands and that the target directory is either sapex code or metadata directories, or a raw subdir under these directories.

ZKW_RMDIR performs a recursive deletion!
To avoid unintended deletions, be sure the target directory does not contain directories outside the SAPEX
code/metadata directories.

The result of creating the commands should be similar to the following:

Installation steps for Local scenario

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

Used for launching the Kiuwan Local Analyzer script.

This OS command will be used by ZKW_ANALYSIS program and CTS_REQUEST_CHECK BAdI implementation.

Use :

• <PATH_TO_KLA>/bin/agent.sh (Unix), or
• <PATH_TO_KLA>\bin\agent.cmd (Windows) 

as the name of the Operating System Command parameter in transaction SM69.