Extracting data

The Transaction Server can be used to extract data according to user-defined configurations. The extraction process is primarily controlled by using an XML file, which is referred to as the extraction profile. For more information about the extraction profile file, see Extraction profile. More extraction configurations can be defined in the Transaction Server properties file as described in Extraction Properties.

Data extraction within the Transaction Server is started in several ways:

Transaction Server scheduler events: Events that are generated within the Transaction Server can be intercepted by a handler and can start a data extraction. Default extraction handlers are included with the Transaction Server. These events cannot be configured for more than a single Transaction Server instance.
Transaction Server scheduler tasks: Tasks can be set up to start data extractions on a scheduled, or timed, basis. Default extraction tasks are included with the Transaction Server. These tasks cannot be configured for more than a single Transaction Server instance.
Services Framework tasks: Services Framework tasks to do entry allocation, marking, and CPCS TXS extraction are provided by Transaction Entry Services. These tasks can run concurrently in multiple Services Framework engine session threads or engines. For more information about using these Services Framework tasks, see Transaction Entry Services.

Note: When you need to start a CPCS TXS extract, the only method that is supported is to use an EntryMarkerTask Services Framework task that is configured to run the CPCSTxsExtractTask Services Framework task. The task can be run by a Transaction Server scheduler event, by scheduling it in Services Framework, or manually from the Task Operation page. For more information, see Transaction Entry Services.