To use Oracle Commerce Business Intelligence, compile an EAR file that includes the following modules along with your applications:
Asset Management Server (also called publishing, management, or administration):
ARF.base,ARF.BIZUI,ARF.WSCAPProduction (also called customer-facing) server:
ARF.baseAgent server:
ARF.base, ARF.BIZUIData loader servers: Modules depend on the applications you are using; see the table that follows. Note that
ACO.Communication.DWcannot run in the same server as the other data loader modules.Product
Data Warehouse Module to Include
B2C Commerce
B2CCommerce
DCS.DW
DCS.PublishingAgent
DCS.CustomCatalogsB2B Commerce
B2BCommerce
DCS.DW
DCS.PublishingAgentB2B Commerce & Commerce Service Center
B2BCommerce
DCS-CSR.DW
DCS.PublishingAgent
For information on assembling applications, see the Platform Programming Guide.
Once you have assembled your EAR file, deploy it to the appropriate location, and start your Web application according to the instructions provided in your application server manuals.
Oracle Commerce Platform applications may be configured to write log files containing operational information for reporting. Data warehouse loader servers load that operational data into the data warehouse. See Components of Oracle Commerce Business Intelligence.
This section explains how to configure Oracle Commerce Platform applications so that they will write log files for reporting.
Note: The examples in this section are based on the server architecture described in the Multiple Application Integration Guide. This model includes an asset management server running ATG Content Administration and other administrative applications (sometimes called an administration or management server), an external-facing or production server on which your Oracle Commerce Core Commerce stores run, and two dedicated data loading servers for reporting.
Configure changes in the <ATG11dir>/home/servers/server_name/localconfig directory.
