Performance Considerations
Each business object contains one or more data objects maintained in a hierarchy. The entire set of data objects under a business object is referred to as a business object tree. Since QXO must search up and down the tree for different functions—at least for business objects that do not employ DDP—each tree is validated in both directions during the initial load of business objects. If the available indexes in one of the source application tables does not sort the records correctly for the searches being performed, whole-index search may occur. In these instances, the entire index may be scanned. The search still works but takes much longer to complete. When you are populating a business object tree with a data set—for example, during a forced load of data from your source application to one or more subscribers—QXO knows the business objects required, but not all the data objects. In this case, it searches down the tree. Where the indexes are inadequate, a whole-index search occurs. However, these are generally one-time events and are not a performance concern.When an event occurs in a source application, QXO knows which data objects are impacted, but not which business objects they belong to. In this case, the search goes up the tree. These searches occur during production processing and are of greater concern. Where the indexes are inadequate, a reverse whole-index search occurs.Note: In the case of event data for business objects that use DDP, the raw business object is published to QXO and performing a search is not required, significantly reducing processing time.