Cloud Cruiser became HPE Consumption Analytics on Nov. 1st. You'll still see the old name in places while we update this site.

 

 

Consumption Analytics Documentation

Home > Cloud Cruiser 3 > Installing > Completing installation for Cisco Process Orchestrator

Completing installation for Cisco Process Orchestrator

Table of contents
No headers

If you selected Cisco Process Orchestrator in the Cloud Cruiser application installer, you must perform the following procedure after running the installer to enable Cisco Process Orchestrator collection.

  1. Launch the Cisco Process Orchestrator console.
  2. In the navigation pane, click Administration > Automation Packs .
    The list of existing automation packs appears.
  3. From the Actions menu, choose Import .
  4. Select the file <install_dir>/third_party_extensions/cisco/CloudCruiser_v2.3.tap and click Open .
    You might need to copy this file from your Cloud Cruiser server to a drive visible to your Cisco Process Orchestrator server to make it available for this step.
  5. In the Automation Pack Import Wizard, click Next twice without modifying any settings.
    The wizard imports the Cloud Cruiser automation pack.
  6. When the wizard completes, click Close .
    The Cloud Cruiser automation pack appears in the list in the console.
  7. In the navigation pane, click Definitions > Global Variables .
  8. Right-click the variable named Cloud Cruiser Usage Directory and choose Properties .
  9. Edit the Value to reflect the path where you want Cisco Process Orchestrator to write files for collection by Cloud Cruiser, then click OK .

    A batch job for collecting Cisco Process Orchestrator data is installed with Cloud Cruiser. The default Value \\CC\cc-working\usage_files\iac_orch is the location where that job is configured by default to collect. If your Cisco Process Orchestrator server is able to write files directly to the filesystem of your Cloud Cruiser server, you only need to replace the placeholder <CC> with the hostname or IP address of your Cloud Cruiser server.
    If your Cisco Process Orchestrator server is not able to write files directly to the filesystem of your Cloud Cruiser server, enter a path to another location. If possible, use a network drive that is visible to the Cloud Cruiser server.

  10. If necessary, set up an automatic process to copy files from this location to a location visible to the Cloud Cruiser server.
    You can use any method to copy these files. Schedule the copy to run just before the Cloud Cruiser job that collects Cisco Process Orchestrator data.
Last modified

Tags

This page has no custom tags.

Classifications

This page has no classifications.
© Copyright 2018 Hewlett Packard Enterprise Development LP