Table of Contents

Search

  1. Preface
  2. Analyst Service
  3. Catalog Service
  4. Content Management Service
  5. Data Integration Service
  6. Data Integration Service Architecture
  7. Data Integration Service Management
  8. Data Integration Service Grid
  9. Data Integration Service REST API
  10. Data Integration Service Applications
  11. Data Privacy Management Service
  12. Enterprise Data Preparation Service
  13. Interactive Data Preparation Service
  14. Informatica Cluster Service
  15. Mass Ingestion Service
  16. Metadata Access Service
  17. Metadata Manager Service
  18. Model Repository Service
  19. PowerCenter Integration Service
  20. PowerCenter Integration Service Architecture
  21. High Availability for the PowerCenter Integration Service
  22. PowerCenter Repository Service
  23. PowerCenter Repository Management
  24. PowerExchange Listener Service
  25. PowerExchange Logger Service
  26. SAP BW Service
  27. Search Service
  28. System Services
  29. Test Data Manager Service
  30. Test Data Warehouse Service
  31. Web Services Hub
  32. Application Service Upgrade
  33. Appendix A: Application Service Databases
  34. Appendix B: Connecting to Databases from Windows
  35. Appendix C: Connecting to Databases from UNIX or Linux
  36. Appendix D: Updating the DynamicSections Parameter of a DB2 Database

Creating a Mass Ingestion Service

Creating a Mass Ingestion Service

When you create a Mass Ingestion Service, you must associate a Model Repository Service with the Mass Ingestion Service. A Model Repository Service cannot be associated with more than one Mass Ingestion Service.
You must create the Mass Ingestion Service in a domain that uses native authentication. If you create the Mass Ingestion Service in a domain that uses LDAP or Kerberos authentication, you cannot log in to the Mass Ingestion tool.
  1. In the Administrator tool, click the
    Manage
    tab.
  2. Click the
    Services and Nodes
    view.
  3. In the Domain Navigator, select the domain.
  4. Click
    Actions
    New
    Mass Ingestion Service
    .
    The
    New Mass Ingestion Service
    wizard appears.
  5. On the
    New Mass Ingestion Service - Step 1 of 3
    page, enter the following properties:
    Property
    Description
    Name
    Name of the service. The name is not case sensitive and must be unique within the domain. It cannot exceed 128 characters or begin with @. It also cannot contain spaces or the following special characters:
    ` ~ % ^ * + = { } \ ; : ' " / ? . , < > | ! ( ) ] [
    Description
    Description of the service. The description cannot exceed 765 characters.
    Location
    Domain and folder where the service is created. Click
    Browse
    to choose a different folder. You can move the service after you create it.
    License
    License object that allows use of the service.
    Node
    Node on which the service runs.
  6. Click
    Next
    .
  7. On the
    New Mass Ingestion Service - Step 2 of 3
    page, enter the following properties:
    Property
    Description
    Model Repository Service
    Model Repository Service to associate with the service.
    User Name
    User name that the service uses to access the Model Repository Service. Enter the Model repository user that you created.
    Password
    Password for the Model repository user.
  8. Click
    Next
    .
    The
    New Mass Ingestion Service - Step 3 of 3
    page appears.
  9. On the
    New Mass Ingestion Service - Step 3 of 3
    page, enter the following properties:
    Property
    Description
    HTTP Port
    Unique HTTP port number for the Mass Ingestion Service process when the service uses the HTTP protocol. Default is 9050.
    Enable Transport Layer Security (TLS)
    Enables the Transport Layer Security protocol to encrypt connections between the Mass Ingestion Service and external components.
    If you enable the TLS protocol, you must specify an HTTPS port and a keystore file. You do not specify an HTTP port.
    HTTPS Port
    Unique HTTPS port number for the Mass Ingestion Service process when the service uses the HTTPS protocol.
    When you set an HTTPS port number, you must also define the keystore file that contains the required keys and certificates.
    Keystore File
    Path and file name of the keystore file that contains the keys and certificates required if you use HTTPS connections for the Mass Ingestion Service.
    You can create a keystore file with a keytool. keytool is a utility that generates and stores private or public key pairs and associated certificates in a keystore file. You can use the self-signed certificate or use a certificate signed by a certificate authority.
    Keystore Password
    Password for the keystore file.
  10. To enable the Mass Ingestion Service, select
    Enable Service
    .
  11. Click
    Finish
    .
    The domain creates the Mass Ingestion Service. If you selected
    Enable Service
    , the domain enables the Mass Ingestion Service.
  12. In the
    Domain Navigator
    , select the Mass Ingestion Service.
  13. Click the URL to access the Mass Ingestion tool.