Understanding getTransactionLog elements and attributes
The following describes the elements and attributes used in the previous example:
- inquireFromDate
- The start date, or the date from which you retrieve the transaction log. This mandatory field is supplied to provide the day at which the user wants to start retrieving the transaction log information. If only this parameter is supplied, the transaction log is retrieved only for 00:00:00.0.000 to 23:59:59.0.000. If it is the current day, transactions will be retrieved up to the current time that day.
- inquireToDate
- The end date, or the date to which you retrieve your log. This is not a mandatory field.
- Regarding entering specific times with dates
- Time portions are accepted but not required for the dates. The
date and time must be of a format configured in the /IBM/DWLCommonServices/DateValidation/dateFormat configuration. If a time is not entered for an inquireToDate, the
default time is 23:59:59:0.000. If a time is not entered for an inquireFromDate,
the time is defaulted to 0:00:00:00. Times that are entered through
the XML request are accurate to the minute, to allow for the way that
the database InfoSphere® MDM is using-either DB2® or Oracle-handles time.
Note: If you enter an inquireFromDate only, you retrieve transactions for that day only. Any time entered is ignored and the log is retrieved for that day between 0:00:00.0 am and 23:59:59.0 pm.
- TCRMTxType
- The name of the transaction-for example, getTransactionLog
- TCRMTxObject
- The Name Of The Transactional Object-for example, DWLTAILRequestBObj
- DWLTxType (when use for DWLAdminService)
- The name of the transaction—for example, getTransactionLog
- DWLTxObject (when use for DWLAdminService)
- The name of the transactional object—for example, DWLTAILRequestBObj
- AdditionalDetailIndicator
- Either Y or N. This tag indicates whether additional information should be returned from InfoSphere MDM as a part of the transaction log. The AdditionalDetailIndicator is used only by InfoSphere MDM and has no meaning to the TAIL Service itself. For this release, only the results of a getFSParty or getContract are retrieved-inquiry levels for these audit transactions are defaulted to 3 for both. For example, if a PartyId or ContractId or both are placed into the TAILStackBObj as a key for the transaction being logged, these keys are used to spawn a getFSParty or getContract transaction.
- BusinessTransactionValue
- The transaction name filter. Results may be filtered by either name or type code; if both are entered they must match.
- BusinessTransactionType
- The transaction type code filter. Results may be filtered by either name or type code; if both are entered they must match.
- ClientSystemName
- An alphanumeric field to filter the returned TAIL objects by a specific client's system name which have issued the subject InfoSphere MDM transactions
- ClientTransactionName
- An alphanumeric field to filter the returned TAIL objects by a specific client's transaction name
- ExternalCorrelationId
- An alphanumeric field to filter the returned TAIL objects by a
specific external correlation identifier.
ExternalCorrelationIdis a field used for transaction traceability, that is, it is used to identify all InfoSphere MDM transactions which have been executed within the scope of a larger business process driven by another enterprise application. The enterprise applications can specify their ownExternalCorrelationId, viaDWLControlin single transactions and viaGlobalFieldsin Composite Transactions.ExternalCorrelationIdis stored in TAIL tables for later audit inquiries. - InquiryLevel
- Valid values are 0 or 1.
- An inquiry level of 0: Retrieves the TAILTransactionLogBObjs (data from the TransactionLog database table) and TAILExternalLogTxnKeyBObjs (data from the ExternalLogTxnKey table). A sample request and response for getTransactionLog inquiry level 0 may be found in this chapter.
- An inquiry level of 1: Retrieves the TAILTransactionLogBObjs and its associated Bobjs. For example, TAILExternalLogTxnKeyBObjs, TAILInternalLogBObjs, TAILInternalLogTxnKeyBObjs, and a point-in-time history response for either a getParty or getContract transaction, depending on whether a partyId or contractId had been logged for the transaction now being retrieved. A sample request and response for getTAIL inquiry level 1 may be found in this chapter.
- UserID
- This value entered for this filter is based on the value of the requester name in DWLControl object and allows for the filtering of transaction logs for the specific user that executed them.
- TAILRequestParamBObj
- Houses the request type and value required as filters for the TAIL retrieval.
- RequestType
- The element name that will be used as a filter parameter. PartyId, ContractId and ContractIdPK are examples of these. Other allowable values are pre-populated in the internalTxnKey table of the TAIL database.
- RequestValue
- Specifies the actual PartyId or ContractId value itself, for example, 1234567890.