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

Application Service Guide

Application Service Guide

Source and Output File Directories

Source and Output File Directories

Configure the directories for source and output files in the Execution Options on the
Properties
view for the Data Integration Service.
The Data Integration Service accesses source files when it runs a mapping or web service operation mapping that reads from a flat file source. The service generates output files when it runs mappings, mappings included in a workflow, profiles, SQL queries to an SQL data service, or web service operation requests. Based on transformation cache settings and target types, the Data Integration Service can generate cache, reject, target, and temporary files.
When you configure directories for the source and output files, you configure the paths for the home directory and its subdirectories. The default value of the
Home Directory
property is
<Informatica installation directory>/tomcat/bin
. If you change the default value, verify that the directory exists.
By default, the following directories have values relative to the home directory:
  • Temporary directories
  • Cache directory
  • Source directory
  • Target directory
  • Rejected files directory
You can define a different directory relative to the home directory. Or, you can define an absolute directory outside the home directory.
If you define a different absolute directory, use the correct syntax for the operating system:
  • On Windows, enter an absolute path beginning with a drive letter, colon, and backslash. For example:
    C:\<Informatica installation directory>\tomcat\bin\MyHomeDir
  • On UNIX, enter an absolute path beginning with a slash. For example:
    /<Informatica installation directory>/tomcat/bin/MyHomeDir
Data objects and transformations in the Developer tool use system parameters to access the values of these Data Integration Service directories. By default, the system parameters are assigned to flat file directory, cache file directory, and temporary file directory fields.
For example, when a developer creates an Aggregator transformation in the Developer tool, the CacheDir system parameter is the default value assigned to the cache directory field. The value of the CacheDir system parameter is defined in the
Cache Directory
property for the Data Integration Service. Developers can remove the default system parameter and enter a different value for the cache directory. However, jobs fail to run if the Data Integration Service cannot access the directory.

0 COMMENTS

We’d like to hear from you!