The following table shows how to specify a target table or non-table target in a configuration file.
| Target | Target Specification | Description |
|---|---|---|
| Database table | tgt_owner.table |
The fully qualified name of a database table. For more information, see How to qualify object names. |
| Database sequence |
tgt_owner.sequence |
The fully qualified name of a sequence. For more information, see How to qualify object names |
| File | !file[:tgt_owner.table] |
The !file designator directs Post to write change operations to a file in SQL or SML format. The file name is applied internally by SharePlex. Optionally, you can specify the fully qualified name of a target table if the data will be consumed by a process that ultimately applies it to a database table. |
| JMS | !jms[:tgt_owner.table] |
The !jms designator directs Post to write change operations to a JMS queue or topic in XML format. The queue or topic name can be defined by using the target command. Optionally, you can specify the fully qualified name of a target table if the data will be consumed by a process that ultimately applies it to a database table. |
| Kafka |
!kafka[:tgt_owner.table] |
The !Kafka designator directs Post to write change operations to a Kafka topic in XML or JSON format. The topic name can be defined by using the target command. Optionally, you can specify the fully qualified name of a target table if the data will be consumed by a process that ultimately applies it to a database table. |
| Change history table |
!cdc:tgt_owner.table |
The !cdc designator directs Post to insert every data change to the table as a new row, rather than overlay the old data with new data. Specify the fully qualified name of the change history table. For more information, see Configure replication to a change history target. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 이용 약관 개인정보 보호정책 Cookie Preference Center
