Oracle ATG Web Commerce Business Intelligence uses components that listen for Java Messaging Service (JMS) messages to collect operational data from your web application. The following steps explain the data collection process.

  1. The event listener component receives JMS events from the Oracle ATG Web Commerce messaging system. See Event Listener Component. See information about the Oracle ATG Web Commerce messaging system in the ATG Platform Programming Guide.

  2. The event listener component passes event objects to an event queue component. This component holds the event objects until a third component writes the event data to log files. See Event Queue Component.

    Queuing the event objects and logging their data with a different component separates the log file writing action from the Java Virtual Machine (JVM) threads used by Web application visitors while they generate the operational data. This improves performance for Web application users.

  3. The data file writing component examines the event objects that are held by the event queue component and writes the data they contain to log files. See Data File Writing Component.

    The data loading components of Oracle ATG Web Commerce read the log files and load the data into the data warehouse database. The data loading components are not a part of the production Web application and are completely separate from the data collection process. See Configuring Fact Data Loading.

Copyright © 1997, 2013 Oracle and/or its affiliates. All rights reserved. Legal Notices