ATG and XML File Combination

An XML file might appear at several points in the CONFIGPATH. The ATG platform, at runtime, automatically combines all the XML files in the CONFIGPATH with the same name into a single composite file, which is then used by the appropriate component.

XML files are combined one tag at a time: in other words, tags are matched up, and the combination rules are applied to each pair of matched tags. XML file combination is controlled with an XML attribute named xml-combine. This attribute is used only in the preprocessing stage of XML file combination.

The xml-combine attribute can have the following values:

xml-combine = "replace"
xml-combine = "remove"
xml-combine = "append"
xml-combine = "append-without-matching" --> This is the same as xml-combine="append", except that embedded tags are not matched and combined recursively. The content is simply appended.
xml-combine = "prepend"
xml-combine = "prepend-without-matching"

Read more @ http://docs.oracle.com/cd/E23507_01/Platform.20073/ATGProgGuide/html/s0207combiningtwotags01.html

Samples :

Comments

Check your PF balance

You can check your PF balance from the site : http://www.epfkerala.in/ Go to the menu : “ My Epf Balance ” . This will lead to the url : http://www.epfindia.com/MembBal.html Select the EPFO office where your account is maintained and furnish your PF Account number.You will be asked to enter your name and mobile number. The given mobile number will be recorded along with the PF Account Number. On successful submission of above information, the details will be sent through SMS to the given mobile number. Please find below some screen shots:

ATG Search architectural flow : Search and Index

I would like to explain the high level ATG Search implementation architecture ( for an online store) through the above diagram. In this diagram 1.x denotes the search functionality and 2.x denotes the indexing functionality. I have given JBoss as the application server. Physical Boxes and Application Servers in the diagram ( as recommended by ATG ) : Estore ( Commerce ) Box --> The box with the estore/site ear (with the site JSPs and Java codes). Search Engine Box --> The box with the search engine application running. Indexing Engine Box --> The box with the indexing engine application running. CA (Content Administration) Box --> The box with the ATG CA ear ( where we could take CA -BCC - Search Administration and configure the search projects) . Search Indexer Box --> The box with the ATG Search Index ear ( to fetch the index data from repository). Note that the engine performing indexing will need access ...

ATG Search - performance decisions in Enterprise search

Read more about the basic design decisions for a commerce search setup @ http://tips4ufromsony.blogspot.in/2012/03/basic-design-decisions-for-commerce.html Read more about search engine tuning @ http://tips4ufromsony.blogspot.in/2012/02/atg-search-search-engine-tuning.html Following items will affect search performance: number of items to be searched, quantity of content for each item, number of meta tags, number of facets, Search Merchandising settings, constraints, number of returned results,... You could find a detailed analysis below : 1. Decide how many search engines you need : Based on the performance requirement of the ecommerce site, create the Search Project @ BCC - Search Admin and add the search engine hosts. Read more about search project creation and search engine host set up @ http://tips4ufromsony.blogspot.com/2012/01/atg-search-how-to-create-search-project.html . 2. Decide the search indexing properties : Search i...

Search engine shutdown call from the Estore instnace

When the estore or commerce instances are restarted the routing system service can send shut down requests to stale engines, this can be caused because of any of the following. 1. Some other instance marked the engine as stopped in the DB (This can be caused because the machine could not reach the host running the engine) 2. The eStore instance is using a different search schema that has data about the search engine host and is marked as stopped in that DB. To avoid this overrride \atg\search\routing\RoutingSystemService.properties by setting cleanUpStrayEng=false.

ATG Search - how estore(commerce instance) forms the search engine SOAP URL ?

The comminucation between the Commerce box and the Search engine is through SOAP. Read more about this architecture @ http://tips4ufromsony.blogspot.in/2011/11/atg-search-architectural-flow-search.html The commerce instance forms the SOAP url just like the below code: private URL getSearchEngineURL(SearchEngine engine) { SearchEnvironmentHost h = engine.getSearchEnvironmentHost(); SearchMachine hi = h.getSearchMachine() ; return new URL( "http://" + hi.getHostname() + ":" + engine.getPort() + "/AEXmlService/" ); } So the commerce instance need the hi.getHostname() and engine.getPort() to form the url. It is obtained as below: 1. The component / atg/commerce/search/refinement/ CommerceFacetSearchService has the siteName defined, which will be pointing to the environment name defined in the Search Project. Read more about this search project setup @ http://...

Tips from Sony Thomas

Search This Blog