Creating a data ingestion job

The quality and completeness of your organization’s application definitions are essential to Concert's ability to surface vulnerabilities, compliance issues, and other valuable insights. One way to share your application-related data with Concert is by creating an ingestion job.

An ingestion job pulls application-related data from a third-party resource, such as a repository or endpoint, into Concert. After you establish a connection with the third-party system and create an ingestion job, the resource appears in the component library where you can use it to define an application.

Before you begin

  • You must have an Admin or Manager access to the Concert instance to define an application through SBOM file upload.
    • For SaaS deployments, instance-level roles are defined in IBM SaaS Console.
    • For on-premises software deployments, instance-level roles are defined in IBM Cloud Pak® foundational services.
  • Establish a connection with a third-party tool or system for Concert to detect individual resources.

Instructions

  1. Go to Administration > Integrations.
  2. Click Create ingestion job.
  3. Enter a name for the ingestion job for internal reference.
  4. Add a description to provide details about this connection for internal reference.
  5. Select a Connection type. This is the third-party tool or service that contains the specific resource that you want to ingest.
  6. Select a Connection. If no connection is detected for the selected type, click Create one now. Refer to Connecting to a third-party system.
  7. Provide the Workflow reference, the sub path in the Concert Workflows https api to the desired workflow.
    Note: For ingesting certificate data into kubeadm cluster, provide Service authentcation which is the name of the authorization created in Concert workflows to access the kubeadm cluster.
  8. Click Create.
  9. Run the job to import the application components and details from the third-party service.

The new ingestion job appears in the list. After running the job, the corresponding application component appears in the component library where you can apply it to an application definition. Repeat this process for all of your application components.