Table of Contents

Search

  1. Introducing Mass Ingestion
  2. Getting Started with Mass Ingestion
  3. Connectors and Connections
  4. Mass Ingestion Applications
  5. Mass Ingestion Databases
  6. Mass Ingestion Files
  7. Mass Ingestion Streaming
  8. Monitoring Mass Ingestion Jobs
  9. Asset Management
  10. Troubleshooting

Mass Ingestion

Mass Ingestion

Defining basic task information

Defining basic task information

To define an
application ingestion
task, you must first enter some basic information about the task, such as the task name, project or project folder location, and load operation type.
  1. In Mass Ingestion, click
    New
    Application Ingestion Task
    .
    The
    Definition
    page of the
    application ingestion
    task wizard appears.
  2. Configure the following properties:
    Property
    Description
    Name
    Name of the
    application ingestion
    task.
    The name of the
    application ingestion
    task must be unique within the organization. The name can contain alphanumeric characters, spaces, periods (.), commas (,), underscores (_), plus signs (+), and hyphens (-).
    Task names are not case sensitive. The maximum length is 50 characters.
    If you include spaces in the name of an
    application ingestion
    task, the spaces do not appear in the name of the job associated with the task.
    Location
    Project or folder in which you want to store the task.
    Runtime Environment
    Runtime environment in which you want to run the task.
    You can run an
    application ingestion
    task only on a Secure Agent. The runtime environment can include a Secure Agent Group with only one agent.
    You cannot run
    application ingestion
    tasks on a Hosted Agent or serverless runtime environment.
    Description
    A brief description of the task.
    Maximum length is 4000 characters.
    Load Type
    Type of load operation that you want the
    application ingestion
    task to perform. You can select one of the following load types for the task:
    • Initial Load
      : Loads data read at a specific point in time from the source application to the target in a batch operation. You can perform an initial load to materialize a target to which incremental change data will be sent.
    • Incremental Load
      : Propagates source data changes to a target continuously or until the job is stopped or ends. The job propagates the changes that have occurred since the last time the job ran or from a specific start point for the first job run.
    • Initial and Incremental Load
      : Performs an initial load of point-in-time data to the target and then automatically switches to propagating incremental data changes made to the same source objects on a continuous basis.
  3. Click
    Next
    .

0 COMMENTS

We’d like to hear from you!