ATG CSC and why I hate it

Home/Java/ATG/ATG CSC and why I hate it

I recently worked on upgrading a client from ATG 2006.3 to ATG 9.1. The upgrade included upgrading Commerce Assist 2006.3 to CSC 9.1.

Commerce Assist 2006.3 is the ATG Customer Service application for ATG 2006.3 which allows CSRs to work with user profiles and orders. Commerce Assist 2006.3 is a relatively simple straight forward application. It’s essentially a standalone module. It can run against the existing CORE schema. The UI is simple but generally effective.

In stark contrast the new CSC is dependent on ATG Service and the front end is actually presented within the ATG Service UI. The UI is amazingly complex, which I’ll go into shortly. It also requires a new separate Service schema. It also has it’s own CA instance to deploy UI data… to itself…. It also requires it’s own Search engines.

For what it’s worth, before I met CSC 9.1, CA and Search were my two least favorite ATG products. Now CSC not only takes the cake as my #1 most disliked ATG product, but also requires #2 and #3.

There’s actually enough about the new CSC that I dislike that I’m going to break this out into a few posts:

Installation and Schema

CSC now requires it’s own schema. It also requires a bunch of schema changes to be made to CORE. Unfortunately the database installation scripts aren’t clear about where they should be run. service_production_all.sql throws a ton of errors regardless of where it’s run. The install docs are lacking, and point you to Service docs, Search docs, CA docs, etc… You also can’t really upgrade from Commerce Assist, so you lose all your old CSR related data.

Also see:

By | 2017-05-18T15:15:55+00:00 August 30th, 2010|ATG|5 Comments

About the Author:

5 Comments

  1. Devon September 2, 2010 at 7:28 am - Reply

    Oh, don’t forget that the UI Framework data required to run CSC doesn’t appear to be available in SQL script form. This means you have to use CIM (which is buggy as hell and doesn’t work well at all for existing applications/existing environments) or setup all the DAS JDBC configs and use repository loader scripts (which is another pita).

    You then have to run the CSC’s CA to setup your site and local agent, and do a full deploy of this framework data before you can even access the CSC.

  2. […] This blog will contain content related to Java, Seam, Security, my sites and projects, as well as other technical subjects I am interested in. Comments and questions are welcome! « ATG CSC and why I hate it […]

  3. […] this is post three in my ATG CSC and why I hate it […]

  4. […] this is post three in my ATG CSC and why I hate it […]

  5. Frank Kim February 24, 2011 at 10:18 am - Reply

    I hate installing CSC too. :-)

Leave A Comment