Summary of runtime Open Hub Extract

Detailed below is an overview of the extraction process.

  1. An extraction can be started in two ways:
    • Start a Process Chain from SAP BW - Starting a Process Chain configured with a third party InfoSpoke will start an extraction in SAP BW and run a compiled job.
    • Start a IBM® InfoSphere® DataStage® job containing an Open Hub Extract - The Open Hub Extract starts a SAP BW Process Chain and waits for the extraction to finish. In this case, the Open Hub Extract will receive a log ID from SAP BW. This log-ID is associated with the current instance of the Process Chain run. The Open Hub Extract might use this log ID to check on the Process Chain's status and to retrieve associated logs.
  2. After an extraction successfully completes in SAP BW, it triggers a message signifying the availability of the data to the "Third Party System". The InfoSphere DataStage RFC server corresponding to the "Third Party System" intercepts the message.
  3. The RFC server starts the appropriate InfoSphere DataStage job designed to retrieve the extracted information from SAP BW.
  4. The Open Hub Extract stage obtains the metadata associated with the execution and compares it with the metadata saved during the job definition. The job aborts if there is any discrepancy in the metadata.
  5. If the metadata is identical, the Open Hub Extract stage retrieves the data from the SAP BW system.
  6. At the conclusion of the extraction, the Open Hub Extract updates the third-party extraction status in SAP BW, using the Request ID stored by the RFC server. The extraction status conveys to SAP BW the success or failure of the data retrieval operation in DataStage.