Database Reference
In-Depth Information
(find_<searchingEntity>.serServiceKey(serviceKey))) , and
tModelKey (find__<searchingEntity>. addTModelKey
(tModelKey))) . We can also define any String qualifier in our search, such as
find_tModel.addFindQualifier(findQualifier) , when preparing the
find object. This gives us some freedom in defining our search criteria, but we must be
certain about what we are looking for and the parameters available to define our search in
the SBDH-compliant Message Header. These parameters are marked in bold in the full
version of MessageHeader in the following code. So, some of them can be categorized
as Service Entities, while most of them qualify as tModels for the taxonomy we are about
to build:
<?xml version="1.0" encoding="UTF-8" ?>
<urn:CTUMessage
xmlns:urn="urn:com:telco:ctu:la:ctumessage:v01"
xmlns:urn1="
urn:com:telco:ctu:la:messageheader:v01"
xmlns:urn2="
urn:com:telco:ctu:la:processheader:v01"
xmlns:urn3="
urn:com:telco:ctu:la:payload:v01"
xmlns:urn4="
urn:com:telco:ctu:la:messagetrackingdata:v01">
<urn:MessageType>EBO</urn:MessageType>
<urn:Version>0.1</urn:Version>
<ns11:MessageHeader xmlns:ns11="
urn:com:telco:ctu:la:messageheader:v01">
<ns11:RefId>604244_1</ns11:RefId>
<ns11:RequestId>CMSA697</ns11:RequestId>
<ns11:MsgId> EBM109 </ns11:MsgId>
<ns11:RefDateTime xsi:nil="true"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<ns11:Sender>
<ns11:SenderCode xsi:nil="true"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<ns11:CountryCode> BR </ns11:CountryCode>
<ns11:Affiliate xsi:nil="true"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<ns11:Instance> BR_IP </ns11:Instance>
Search WWH ::




Custom Search