The following instructions describe how to set up ATG Commerce Service Center. If you are installing ATG CSC with an existing installation of ATG Commerce, refer to the Configuring ATG Commerce Service Center with ATG Commerce section. For an installation example, refer to Installing the Pioneer Demo.

Note: If you have installed ATG Service, you have already performed the first three steps. Continue to Step 4.

  1. Create the ATG Commerce Service Center databases. If you have not already done so during the installation of ATG Service, create both an Agent and a Production Database as outlined in the ATG Service Installation and Configuration Guide.

  2. ATG Commerce Service Center will use a similar schema configuration that you created for the installation of ATG Service. If you have not already run the installation process when setting up ATG Service, run the create-service-allscript in the <ATG9dir>/Service9.3/Service/install directory for your database type. This script runs a number of SQL files for your specific environment. You can use your own database tool to run the various SQL files outlined in the create-service-all script. Refer to the Creating Database Schema section of the ATG Service Installation and Configuration Guide for additional information.

  3. Ensure that your data sources are configured correctly. Refer to the Creating ATG Service Servers section of the ATG Service Installation and Configuration Guide for additional information on how to direct data sources.

  4. Install the ATG Commerce Service Center tables by running the following scripts. Refer to the list in the Required Databases and Users section for the list of specific DDL files.


    Run against this schema








    Data Warehouse

  5. Import the data by going to the <ATG9dir>/home/bin directory and entering the following commands:

    startSQLRepository –m DSS –repository
    /atg/userprofiling/InternalProfileRepository – import

  6. Execute the following files to import login and access rights data:


    Note: The -s <servername> argument is optional for the importDCSCSR and importDCSCSREvalSuperUser scripts. If the scripts are executed in the agent cluster, and you provide the -s <servername> parameter, the script assumes that the data source settings are setup on the server indicated.

  7. Create the EAR file by running a command similar to the following from <ATG9dir>/bin directory:

    runAssembler DCSCSR.ear –m DCS-CSR DCS-CSR.DW Fulfillment

    If you have made customizations to the DCS-CSR module and saved it as MyStoreDCS-CSR, add your store customizations to the EAR file after the DCS-CSR module:

    runAssembler MyStore.ear –m DCS-CSR MyStoreDCS-CSR DCS-CSR.DW Fulfillment

    Note: When starting the ATG Commerce Service Center server, you must include all the modules you use with your external site, plus the DCS-CSR module. The external site’s module must be specified before the DCS-CSR module. The following example installs the Pioneer Cycling demo, CSC and CSC reporting:

    startDynamoOnJBoss -m PioneerCyclingJSP DCS-CSR DCS-CSR.DW Fulfillment

  8. Deploy the EAR to the application server. Refer to your web application server documentation for information, as well as information for your web application server in the ATG Installation and Configuration Guide.

  9. Start the server according to the instructions in your application server documentation.

loading table of contents...