Commvault Actions

Actions for Commvault #

• Send Data to Commvault. Sends a custom set of Lucidum data to Commvault.

Use Cases #

Below are the possible use cases for these actions:

• If you want to run Lucidum “headless”, you can send relevant data to Commvault on a regular schedule.

• You can send normalized, enriched Lucidum data to Commvault to be indexed, searched, and analyzed.

Prerequisites #

To execute Commvault actions, you must configure a Commvault API connection beforehand.

Workflows #

• Creating a new Configuration and a new Action
• Cloning an Existing Action
• Creating a new Action from the Location Results page
• Editing a Configuration
• Editing an Action
• Viewing Information about an Action

Commvault Configuration #

To create a configuration for Commvault actions:

• Configuration Name. Identifier for the Configuration. This name will appear in the Lucidum Action Center.

• URL. The URL of the API server for Commvault. For example, https://CommandCenterHostName/commandcenter/api. For details, see https://documentation.commvault.com/11.20/rest_api_authentication_post_login.html and https://api.commvault.com/docs/SP38/api/cv/AuthenticationOperations/login/.

• Username. User name for an account with read and write access to the API. For details, see https://documentation.commvault.com/11.20/rest_api_authentication_post_login.html and https://api.commvault.com/docs/SP38/api/cv/AuthenticationOperations/login/.

• Password. Password for an account with read and write access to the API. For details, see https://documentation.commvault.com/11.20/rest_api_authentication_post_login.html and https://api.commvault.com/docs/SP38/api/cv/AuthenticationOperations/login/.
• Max # of Records per Payload. The maximum number of records to send to Commvault in each action. The default value is “50”.

Create a New Action #

To create an action for Commvault, contact Lucidum customer care.