Exporting data

After setting up the migration utility, export data from AppScan® Source.

Exporting data happens in two parts:
  • Filters, user data, custom rules, scan configurations.
    Note: User data is exported for reference only.
  • Assessments
  1. If you want to export data from AppScan® Source to a non-default location (that is, not C:\temp\Ounce or /tmp/ounce), create that location and then define the environment variable transfer_staging_dir to point to the non-default location.
    • Windows:
      set transfer_staging_dir="<export data location>"
    • Linux:
      export transfer_staging_dir="<export data location>"
      Note: See "Export data locations" below for additional information.
  2. From the command line, navigate to the location of the migration utility.
  3. Run the utility with appropriate parameters to export filters, user data, custom rules, and scan configurations:
    • Windows:
      DBManager.exe 
          --export 
          [
          -Dsource-db-user=<username> 
          -Dsource-db-pass=<password> 
          -Dsource-db-host=<host IP> 
          -Dsource-db-connection-info=<tcp <IP> <PORT>> 
          -Dsource-db-connection-string=<LocalNetServiceName> 
          -Dsource-db-client=<1-solidDB, 2-Oracle> 
          -Dsource-tns-admin-path=<<path>\tnsnames.ora>
          ]
    • Linux:
      ./dbmanager 
          --export 
          [
          -Dsource-db-user <username> 
          -Dsource-db-pass=<password> 
          -Dsource-db-host=<host IP> 
          -Dsource-db-connection-info=<tcp <IP> <PORT>> 
          -Dsource-db-connection-string=<LocalNetServiceName> 
          -Dsource-db-client=<1-solidDB, 2-Oracle> 
          -Dsource-tns-admin-path=<<path>/tnsnames.ora>
          ]
  4. Run the utility with the assessments parameter to export assessments only:
    • Windows:
      DBManager.exe 
          --export 
          --asmt 
          [
          --start-date <dd-MMM-yyyy > [--end-date <dd-MMM-yyyy >]
          ] 
          [
          -Dsource-db-user=<username> 
          -Dsource-db-pass=<password> 
          -Dsource-db-host=<host IP> 
          -Dsource-db-connection-info=<tcp <IP> <PORT>> 
          -Dsource-db-connection-string=<LocalNetServiceName> 
          -Dsource-db-client=<1-solidDB, 2-Oracle> 
          -Dsource-tns-admin-path=<<path>\tnsnames.ora>
          ]
    • Linux:
      ./dbmanager 
          --export 
          --asmt 
          [
          --start-date <dd-MMM-yyyy > [--end-date <dd-MMM-yyyy >]
          ] 
          [
          -Dsource-db-user=<username> 
          -Dsource-db-pass=<password> 
          -Dsource-db-host<host IP> 
          -Dsource-db-connection-info=<tcp <IP> <PORT>> 
          -Dsource-db-connection-string=<LocalNetServiceName> 
          -Dsource-db-client=<1-solidDB, 2-Oracle> 
          -Dsource-tns-admin-path=<<path>/tnsnames.ora>
          ]
    Note: When the --asmt option is used, the migration utility does not export filters, user data, custom rules, or scan configuration. It is for exporting assessments only.
    Note: For help using export commands, run:
    • Windows:
      DBManager.exe --export --help
    • Linux:
      ./dbmanager --export --help

Migration utility export parameters

Parameter Value Default Required?
-Dsource-db-user The user account from which to export data. ounce No
-Dsource-db-pass The password associated with the specified user. ounce No
-Dsource-db-host The host location of the database from which to export data. localhost No
-Dsource-db-connection-info How the host is connected to the database. tcp localhost 2315 No
-Dsource-db-connection-string Local net service name No default Required when exporting from Oracle only.1
-Dsource-db-client The type of database from which data is being exported:
  • 1=solidDB
  • 2=oracle
1 No. Client is assumed to be SolidDB if not specified.
-Dsource-tns-admin-path File path of tnsnames.ora No default Required when exporting from Oracle only.1
--asmt [--start-date <dd-MMM-yyyy> [--end-date <dd-MMM-yyyy>]] Export assessments only, with date range specified in the format in the parameter If no date range is specified, all assessments are exported. Required when exporting assessments only. 2
  1. For example, exporting from Oracle might look something like this:
    C:\Program Files\HCL\AppScanSource\migration_util_win>DbManager.exe --export --asmt -Dsource-db-client=2 -Dsource-db-connection-string=10.111.11.11:1521/appscan -Dsource-tns-admin-path=C:\app\Oracle\product\19.0.0\client_1\network\admin\tnsnames.ora
  2. For example, exporting from SolidDB might look something like this, as SolidDB is the -Dsource-db-client default:
    C:\Program Files\HCL\AppScanSource\migration_util_win>DbManager.exe --export --asmt
    or, specifying dates:
    C:\Program Files\HCL\AppScanSource\migration_util_win>DbManager.exe --export -–asmt -–start-date 01-Jan-2020 -–End-date 01-Jan-2021
    

Export data locations

Exported data is placed in the C:\temp\Ounce directory (/tmp/ounce on Linux) unless you created a different directory and defined its location in step 1 above:

  • Exported filters, user data, custom rules, and scan configurations data are placed in the following locations:
    • Filters: C:\temp\Ounce\Filters
    • Scan configurations: C:\temp\Ounce\ScanConfig
    • Custom rules: C:\temp\Ounce\vdb
    • User data: C:\temp\Ounce\Users
      Note: User data is exported for reference only. It is not imported into AppScan® Enterprise with other data when using this migration utility.
  • Exported assessment content is placed in C:\temp\Ounce\Assessments.

Troubleshooting export

If you experience any issues while exporting data, refer to the dbmanager_exceptions.log file in the AppScan® Source data directory:
  • Windows:
    C:\ProgramData\HCL\AppScanSource\logs\dbmanager_exceptions.log
  • Linux:
    var/opt/hcl/appscansource/logs/dbmanager_exceptions.log