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

Compare with Current View Page History

« Previous Version 6 Next »

Contents:

Related pages:

 

 

SAPEX allows to extract SAP objects to a defined path outside the SAP server.  

Using this remote approach, you can donwload all the SAP objects to a remote machine where you can later execute Kiuwan Local Analyzer.

 

SAPEX scripts files are located at

  • <AGENT_DIR>/bin/sapex directory.

SAPEX  configuration files are located at

  • <AGENT_DIR>/conf/sapex directory.

 

Remote scripts use SAP Java Connector (JCo) version 3.

Please, visit Configure remote scripts and Install SAP JCo Connector library for instructions.

 

 

Extract source code

 

Launch SAPEX sapexCode.xml script, for source code extraction from a remote SAP system.

 

Usage:

  ant -f sapexCode.xml
    [-Dhost=HOSTNAME] [-Dsysnr=SYSNR_VALUE] [-Dclient=CLIENT_NAME]
    [-Duser=USER] [-Dpass=PASS]
    [-Dsap.connector=PATH_TO_SAP_JCO]
    [-Ddir.code=DIRECTORY_FOR_EXPORTED_CODE]

    [-Dtransportpattern=TRANSP] [-Dsubtransports=true/false]
    [-DpackagePattern=PACKAGE] [-Dsubpackages=true/false]
    [-Dprograms=true/false] [-Dprogrampattern=PROG_PATTERN]
    [-Dfunctions=true/false] [-Dfunctionpattern=FUNC_PATTERN]
    [-Dclasses=true/false] [-Dclasspattern=CLASS_PATTERN]
    [-Dwebdynpros=true/false] [-DwendynrpoPattern=WD_PATTERN]
    [-Dlanguage=LANG]
    [-Dcustomobjectsonly=true/false] [-Dcustomnamespace=CUSTOM_NS]

Example: 

ant -f sapexCode.xml -Ddir.code=/my/dir

 

  • Connection properties for target SAP server could be configured in sapex.properties file in ${AGENT_HOME}/config, or in this script directory.
  • Custom code extract config could be placed in a sapexCode.properties file located in ${AGENT_HOME}/config, or in this script directory. Any parameter passed at script command line overwrites a parameter with same name in sapexCode.properties. 
  • host, sysnr, client, user, pass and sap.connector are configuration values for target SAP system, and the location of the SAP JCo3 library. 
  • dir.code is the directory where exported code will be stored. 
  • For operation, you must add to target SAP system the function module ZKW_SAPEX_CODE_RPC (which must be RFC-enabled), program ZKW_SAPEX_CODE, and the utility classes.

 

  The program ZKW_SAPEX_CODE might be run in SAP as an alternative to this (remote) extraction script.

 

Extract metadata

 

Launch SAPEX sapexMetadata.xml script, for metadata extraction from a remote SAP system.

 

Usage:

ant -f sapexMetadata.xml
  [-Dhost=HOSTNAME] [-Dsysnr=SYSNR_VALUE] [-Dclient=CLIENT_NAME]
  [-Duser=USER] [-Dpass=PASS]
  [-Dsap.connector=PATH_TO_SAP_JCO]

  [-Ddir.metadata=DIRECTORY_FOR_EXPORTED_CODE]

Example: 

ant -f sapexMetadata.xml -Ddir.metadata=/my/dir

 

  • Connection properties for target SAP server could be configured in sapex.properties file in <AGENT_HOME>/config, or in this script directory. 
  • Custom code extract config could be placed in a sapexMetadata.properties file located in <AGENT_HOME>/config, or in this script directory. Any parameter passed at script command line overwrites a parameter with same name in sapexMetadata.properties. 
  • host, sysnr, client, user, pass and sap.connector are configuration values for target SAP system, and the location of the SAP JCo3 library. 
  • dir.metadata is the directory where SAP information files will be stored. 
  • For operation, you must add to target SAP system the function module ZKW_SAPEX_METADATA_RPC (which must be RFC-enabled), and program ZKW_SAPEX_METADATA, plus the utility classes 

 

The program ZKW_SAPEX_METADATA might be run in SAP as an alternative to this (remote) extraction script.

 

Run analysis

Once you have extracted Abap source code (and optionally, metadata), you can execute Kiuwan Local Analyzer on extracted source code.

For instructions on how to do it please visit Kiuwan Local Analyzer


 

  • No labels