To collect data from your vRealize Automation, vRealize Orchestrator, or external vRealize Orchestrator source environment offline, use the data capture utility.

Using the data capture utility, you can bypass the need to deploy a full vRealize Automation instance to perform data collection and a migration assessment on your source environment. Although the data capture utility can be used for vRealize Automation and vRealize Orchestrator source environments, it is especially useful for external vRealize Orchestrator source environments. When run, the source data is collected and saved as a ZIP bundle.

Prerequisites

Java is required to run the standalone data capture utility.

Procedure

  1. Download the capture.jar file for the capture_utility project from the Getting Started Page on the Migration tab in Cloud Assembly.
  2. Run the java -Dcontext="shell" -Dspring.liquibase.enabled=false -jar capture.jar command.
    Note: By default, the command starts spring-shell on port 8080. To change the port used by spring-shell, run the -Dserver.port=<portid> command where <portid> is the name/identifier of the desired available port. With this modification, the initial command becomes: java -Dcontext="shell" -Dspring.liquidbase.enabled=false -Dserver.port=<portid> -jar capture.jar
    Note: If running on Windows, to override the default character set, run the -Dfile.encoding=UTF-8 command. With this modification, the initial command becomes java -Dcontext="shell" -Dspring.liquidbase.enabled=false -Dfile.encoding=UTF-8 -Dserver.port=<portid> -jar capture.jar
    The capture jar and spring-shell are started and the liquibase is disabled for database upgrade and check.
  3. Provide a properties file that includes the source environment server details:
    Server Details Value
    server vRA/vRO server fqdn or IP address
    vraUser vRA tenant user name
    vraPassword vRA tenant password
    vroUser vRO user name
    vroPassword vRO password
    Note: To capture external vRealize Orchestrator data, use the external vRealize Orchestrator details in the properties file.
    An example properties file:
    server=cava.n.88.087.eng.vmware.com
    vraUser=fritz@coke.sqa.horizon.local
    vraPassword=VMware1!
    vroUser=administrator@vsphere.local
    vroPassword=VMware1!
  4. To capture the desired source environment data, run the applicable commands:
    To collect data from ... Run ...
    Both vRealize Automation and vRealize Orchestrator capture
    vRealize Automation only captureVra
    vRealize Orchestrator only captureVro
    Note: For external vRealize Orchestrator, provide the port number with the server. For example, captureVro server:port
    Note: To view the help message, run capture --help after running the capture, captureVra, or captureVro commands.
  5. After running the capture or captureVra command, run the deployment capture command:
    Note: You must run a deployment command regardless of need to capture deployment information.
    Action Command
    To capture deloyments …

    capture --serverFile /tmp/server.txt --tenant qe --filepath /Users/bsopariwala/Desktop --deployments true

    captureVra --serverFile /tmp/server.txt --tenant qe --filepath /Users/bsopariwala/Desktop --deployments true
    To not capture deployments …

    capture --serverFile /tmp/server.txt --tenant qe --filepath /Users/bsopariwala/Desktop --deployments false

    captureVra --serverFile /tmp/server.txt --tenant qe --filepath /Users/bsopariwala/Desktop --deployments false

Results

Your source environment data is collected and saved as a source bundle. To run a migration assessment on your source bundle, see Run a Migration Assessment on a vRealize Automation Source Bundle.