Table of Contents

Search

  1. Preface
  2. Part 1: Introduction
  3. Part 2: Configuring Hub Console Tools
  4. Part 3: Building the Data Model
  5. Part 4: Configuring the Data Flow
  6. Part 5: Executing Informatica MDM Hub Processes
  7. Part 6: Configuring Application Access
  8. Appendix A: MDM Hub Properties
  9. Appendix B: Viewing Configuration Details
  10. Appendix C: Row-level Locking
  11. Appendix D: MDM Hub Logging
  12. Appendix E: Table Partitioning
  13. Appendix F: Collecting MDM Environment Information with the Product Usage Toolkit
  14. Appendix G: Glossary

Using Timeline Extract

Using Timeline Extract

You can run Timeline Extract by the following methods:
  • Run the Extract BVT Versions batch job in the Batch Viewer tool in the MDM Hub Console
  • Run the executeBatchExtractBVTVersions SIF API
After you run the Extract BVT Versions batch job, the extracted records are added to the following table:
  • E$_BO_NAME

Run the Extract BVT Versions batch job

For the effected base object, run the Extract BVT Versions batch job in the Batch Viewer tool in the MDM Hub Console.
You cannot specify a limit date when you run the Extract BVT Versions batch job in the Batch Viewer tool. The Extract BVT Versions batch job uses the current application server time for the limit date. To specify a limit date, run the executeBatchExtractBVTVersions SIF API.
For information about the Batch Viewer tool, see Running Batch Jobs Using the Batch Viewer Tool.

Run the executeBatchExtractBVTVersions SIF API

Request
The executeBatchExtractBVTVersions request contains the following parameters:
orsId
The Operational Reference Store name
tableName
The base object name
limitDate
The Extract BVT Version batch job operates on cross-reference records whose last update date is before the limit date.
Response
The executeBatchExtractBVTVersions response returns the following parameters:
Message
Contains a message regarding the status of the request.
RetCode
Contains the return code.
EJB Request Example
The following EJB request runs the Extract BVT Versions batch job:
SiperianClient sipClient = SiperianClient.newSiperianClient(new File( context.getTestPTTStartDir() + "siperian-client.properties" ) ); ExecuteBatchExtractBVTVersionsRequest req = new ExecuteBatchExtractBVTVersionsRequest(); req.setTableName(jobContext.getTableName()); // Pass BO name as a string req.setLimitDate(jobContext.getLimitDate()); // Pass limit date using java Date type ExecuteBatchExtractBVTVersionsResponse executed = (ExecuteBatchExtractBVTVersionsResponse) sipClient.process( req ); String errMessage = executed.getMessage(); int rc = executed.getRetCode();
SOAP Request Example
The following SOAP request runs the Extract BVT Versions batch job for the C_TIMELINE base object in the CMX_ORS10A Operational Reference Store:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:siperian.api"> <soapenv:Header/> <soapenv:Body> <urn:executeBatchExtractBVTVersions> <urn:username>admin</urn:username> <urn:password> <urn:password>admin</urn:password> <urn:encrypted>false</urn:encrypted> </urn:password> <urn:orsId>localhost-orcl-CMX_ORS10A</urn:orsId> <urn:tableName>C_TIMELINE</urn:tableName> <urn:limitDate>2015-10-29T12:59:14+02:00</urn:limitDate> </urn:executeBatchExtractBVTVersions> </soapenv:Body> </soapenv:Envelope>

0 COMMENTS

We’d like to hear from you!