Table of Contents

Search

  1. Preface
  2. Workflow Manager
  3. Workflows and Worklets
  4. Sessions
  5. Session Configuration Object
  6. Tasks
  7. Sources
  8. Targets
  9. Connection Objects
  10. Validation
  11. Scheduling and Running Workflows
  12. Sending Email
  13. Workflow Monitor
  14. Workflow Monitor Details
  15. Session and Workflow Logs
  16. Appendix A: Session Properties Reference
  17. Appendix B: Workflow Properties Reference

Workflow Basics Guide

Workflow Basics Guide

Configuring Connections

Configuring Connections

View the Connections settings on the Mapping tab to define target connection information. For relational targets, the Workflow Manager displays Relational as the target type by default. In the Value column, choose a configured database connection for each relational target instance.
For flat file and XML targets, choose one of the following target connection types in the Type column for each target instance:
  • FTP.
    If you want to load data to a flat file or XML target using FTP, you must specify an FTP connection when you configure target options. FTP connections must be defined in the Workflow Manager prior to configuring sessions.
  • Loader.
    Use the external loader option to improve the load speed to Oracle, DB2, Sybase IQ, or Teradata target databases.
    To use this option, you must use a mapping with a relational target definition and choose File as the writer type on the Writers settings for the relational target instance. The Integration Service uses an external loader to load target files to the Oracle, DB2, Sybase IQ, or Teradata database. You cannot choose external loader if the target is defined in the mapping as a flat file, XML, MQ, or SAP BW target.
  • Queue.
    Choose Queue when you want to output to a WebSphere MQ or MSMQ message queue.
  • None.
    Choose None when you want to write to a local flat file or XML file.

0 COMMENTS

We’d like to hear from you!