Table of Contents

Search

  1. Preface
  2. Analyst Service
  3. Content Management Service
  4. Data Integration Service
  5. Data Integration Service Architecture
  6. Data Integration Service Management
  7. Data Integration Service Grid
  8. Data Integration Service Applications
  9. Metadata Manager Service
  10. Model Repository Service
  11. PowerCenter Integration Service
  12. PowerCenter Integration Service Architecture
  13. High Availability for the PowerCenter Integration Service
  14. PowerCenter Repository Service
  15. PowerCenter Repository Management
  16. PowerExchange Listener Service
  17. PowerExchange Logger Service
  18. SAP BW Service
  19. Search Service
  20. System Services
  21. Test Data Manager Service
  22. Web Services Hub
  23. Application Service Upgrade
  24. Application Service Databases
  25. Connecting to Databases from Windows
  26. Connecting to Databases from UNIX
  27. Updating the DynamicSections Parameter of a DB2 Database

Data Integration Service Applications Overview

Data Integration Service Applications Overview

A developer can create a logical data object, physical data object, mapping, SQL data service, web service, or workflow and add it to an application in the Developer tool. To run the application, the developer must deploy it. A developer can deploy an application to an application archive file or deploy the application directly to the Data Integration Service.
A developer can create a logical data object, physical data object, mapping, or workflow and add it to an application in the Developer tool. To run the application, the developer must deploy it. A developer can deploy an application to an application archive file or deploy the application directly to the Data Integration Service.
As an administrator, you can deploy an application archive file to a Data Integration Service. You can enable the application to run and start the application.
When you deploy an application archive file to a Data Integration Service, the Deployment Manager validates the logical data objects, physical data objects, mappings, SQL data services, web services, and workflows in the application. The deployment fails if errors occur. The connections that are defined in the application must be valid in the domain that you deploy the application to.
When you deploy an application archive file to a Data Integration Service, the Deployment Manager validates the logical data objects, physical data objects, mappings, and workflows in the application. The deployment fails if errors occur. The connections that are defined in the application must be valid in the domain that you deploy the application to.
The Data Integration Service stores the application in the Model repository associated with the Data Integration Service.
You can configure the default deployment mode for a Data Integration Service. The default deployment mode determines the state of each application after deployment. An application is disabled, stopped, or running after deployment.