Contents:
Related pages:
Delivery analysis
In remote use, i.e. when you execute the kiuwan analysis outside the SAP server, you can use same approach of baselines to delivery analysis.
As you can read at Remote use - Baseline Analysis, to perform an analysis otuside the SAP server you must use Kiuwan Local Analyzer.
Extraction of source code of a Delivery
To extract ABAP source code, please follow same instructions as with Baseline analyses:
- Remote use - Baseline Analysis outside the SAP Server - Extract source code
- Remote use - Baseline Analysis outside the SAP Server - Extract metadata
IMPORTANT : you must specify the id of the request/task transport order to export.
- using sapexCode.properties configuration file, or
# Name or pattern for the id of the request/task transport order to export.transportPattern=# if true, export sub request/task transport orders for matching request/tasks.subTransports=false- using command-line configuration options:
[-Dtransportpattern=TRANSP] [-Dsubtransports=true/false]
Run analysis
Once you have extracted Abap source code , you can execute Kiuwan Local Analyzer on extracted source code.
For instructions on how to do it (as well as to specify the delivery options - In progress or Resolved ), please follow instructions at:
If you are going to run an analysis with Kiuwan Local Analyzer be sure to specify the location of the extracted metafiles.
To do it, edit <AGENT_HOME>/conf/analyzer.properties, and search for :
# Directory for the repository data extracted by SAP Connector
abap.repository.dir=.
Notes:
- This property must contain the location of the directory with the extracted metadata files.
- Please note that by default is set to ".", i.e. the root of the source dir of the application to be analyzed.
- You can set to another location, either relative to source dir or absolute
Its quite important also that you increase the memory to those analyses that use metadata. Please visit Out of Memory page if you get errors when analyzing with metafiles.