Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
| Info | |
|---|---|
Contents:
|
Delivery analysis
In remote use, i.e. when you execute the
...
Kiuwan analysis outside the SAP server, you can use the same approach of baselines to delivery analysis.
As you can read
...
on Remote use - Baseline Analysis, to perform an analysis
...
outside 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
| Info |
|---|
IMPORTANT : you must specify the id of the request/task transport order to export. Depending on the state of the request you will later specify the scope with Kiuwan Local Analyzer.
# 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
[-Dtransportpattern=TRANSP] [-Dsubtransports=true/false] |
Run analysis
| Info |
|---|
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) |
...
...
| Info |
|---|
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
Notes:
|
...
It's important also that you increase the memory |
...
of those analyses that use metadata. Please visit Out of Memory |
...
if you get errors when analyzing with metafiles. |