ATG framework in a nutshell
DPS is a smart prodcut, which leveraged the DAS and now can be integrated with other application servers as well. DPS was kind of the first JAVA personalization server in the market which really helped ATG move further. DPS's strength is its business engine architecture and simple to generate a business rules if you know how to use the DCC tool.
ATG Dynamo was considered to be one of the best application servers in the market especially among java developer communities. But later it was becoming too much for ATG and hence gave it up.
ATG's concept of "configuration layers" is not much seen outside and is a kind of boon. It means that you have a CONFIGPATH, and if there are two identically-named .properties files then any property definitions that occur later in the CONFIGPATH take precedence. This is very good for seggregating the different environment configuration .
ATG can do the same thing with XML files. Most of the "different" profile XML files are merged to get one combined Xml file during startup.
ATG is currently supporting J2EE applications and has many integration points with others. I remember that when they came with ATG 6 version they called it as Relationship Management Platform which provided most of the initial integrations with Siebel etc.
The ATG collection framework offers an event handling communication approach. Again this is simple to work with and powerful. Extending this framework to make your own dynamically configured listeners, senders and filters adds another poweful approach.
The Repository framework is something very special to ATG. It's incredibly deep and complex.
What do you say?
ATG Dynamo was considered to be one of the best application servers in the market especially among java developer communities. But later it was becoming too much for ATG and hence gave it up.
ATG's concept of "configuration layers" is not much seen outside and is a kind of boon. It means that you have a CONFIGPATH, and if there are two identically-named .properties files then any property definitions that occur later in the CONFIGPATH take precedence. This is very good for seggregating the different environment configuration .
ATG can do the same thing with XML files. Most of the "different" profile XML files are merged to get one combined Xml file during startup.
ATG is currently supporting J2EE applications and has many integration points with others. I remember that when they came with ATG 6 version they called it as Relationship Management Platform which provided most of the initial integrations with Siebel etc.
The ATG collection framework offers an event handling communication approach. Again this is simple to work with and powerful. Extending this framework to make your own dynamically configured listeners, senders and filters adds another poweful approach.
The Repository framework is something very special to ATG. It's incredibly deep and complex.
What do you say?
posted by Ashwini Bhat | 9:31 PM
|
6 comments
