RegistryLookup node output: example 2
Example showing the structure of RegistryLookup node output for all possible values of the Depth Policy property for a query on a concept entity that has a number of user relationships to other concept entities.
This example shows the ServiceRegistry message trees that are stored in the LocalEnvironment when the Concepts shown in the following WebSphere® Service Registry and Repository graph are retrieved. The graph has been annotated with the relationship names to clarify the elements in the message tree.
The following ServiceRegistry message trees have some elements replaced by ...
to emphasis the structure of the tree. Likewise, the bsrURIs have been truncated.
The following shows the message trees for each possible value of the Depth Policy property:
- Return matched only (Depth =
0)
ServiceRegistry Entity type = sdo:GenericObject bsrURI = a2e62137a605 name = ConceptA2 ... - Return matched showing immediate relationships (For
compatibility only). The entities contain elements showing the details of relationships,
but only provide a list of the bsrURIs for the related child entities.
This value of the Depth Policy property is deprecated, so you should use of the other options. The output tree structure produced when using this value is not compatible with those from the other values for the Depth Policy property. In particular, note the namespace qualifications.
ServiceRegistry Entity type = sdo:GenericObject bsrURI = a2e62137a605 name = ConceptA2 ... ns1:userDefinedRelationships name = ContainsChildren targets = b2f73637f6e8 b3de6036e1af ns1:userDefinedRelationships name = ReferTo targets = zac084d6b804 - Return matched plus immediate related entities (Depth =
1). The entities contain elements showing the details of relationships, and the details of
the related child
entities.
ServiceRegistry Entity type = GenericObject bsrURI = a2e62137a605 name = ConceptA2 ... userDefinedRelationships name = ContainsChildren targetEntities Entity bsrURI = b2f73637f6e8 name = ConceptB2 ... Entity bsrURI = b3de6036e1af name = ConceptB3 ... userDefinedRelationships name = ContainsChildren targets = c26e43ac45a userDefinedRelationships name = ReferTo targets = zac084d6b804 userDefinedRelationships name = ReferTo targetEntities Entity bsrURI = zac084d6b804 name = ConceptZa ... - Return matched plus all related entities (Depth =
-1). The entities contain elements showing the details of relationships, and the details of
the all related child entities. ConceptD1 uses an EntityRef element to refer to its ancestor
ConceptC2. ConceptZa appears twice in the tree as it is referenced by both ConceptA2 and
ConceptB3.
ServiceRegistry Entity type = sdo:GenericObject bsrURI = a2e62137a605 name = ConceptA2 ... userDefinedRelationships name = ContainsChildren targetEntities Entity bsrURI = b2f73637f6e8 name = ConceptB2 ... Entity bsrURI = b3de6036e1af name = ConceptB3 ... userDefinedRelationships name = ContainsChildren targetEntities Entity bsrURI = c26e43ac45a name = ConceptC2 ... userDefinedRelationships name = ContainsChildren targetEntities Entity bsrURI = d16e43ac763 name = ConceptD1 ... userDefinedRelationships name = UsedIn targetEntities EntityRef bsrURI = c26e43ac45a name = ConceptC2 userDefinedRelationships name = ReferTo targetEntities Entity bsrURI = zac084d6b804 name = ConceptZa ... userDefinedRelationships name = ReferTo targetEntities Entity bsrURI = zac084d6b804 name = ConceptZa ...