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

Eclipse plug-in to create Class and Sequence diagrams

ModelGoon is an Eclipse plug-in avaiable for UML diagram generation from Java code. It can be used to generate Package Dependencies Diagram, Class Diagram, Interaction Diagram and Sequence Diagram. You coud get it from http://marketplace.eclipse.org/content/modelgoon-uml4java Read more about it and see some vedios about how to create the class and sequence diagram @ http://www.modelgoon.org/?tag=eclipse-plugin Find some snapshots below which gives an idea about the diagram generation.

How to convert your Blogger Blog to PDF ?

You can use a website called "blogbooker" @ http://www.blogbooker.com/blogger.php to convert your Blogger Blog to a PDF . Please find the steps below : 1. Save your blog as an xml using Blogger Settings - Other - Export Blog option 2. Go to the website " http://www.blogbooker.com/blogger.php " and select this XML , give your blog address and select the options like date range, page size, font, ... 3. Click the "Create Your BlogBook" button to view and save your blog as PDF

ATG Search Indexing - behind the scene steps explained

Read more about the search indexing @ http://tips4ufromsony.blogspot.com/2011/11/atg-search-architectural-flow-search.html ATG search indexing involves index file creation, deploying and copying the index file to the search engine's box. The steps can be divided into Initial stage, Preparing Content, Indexing and Deploying. Please find below the detailed analysis of each step. 1. Initial stage: a. Check whether the folder deployshare configured correctly @ LaunchingService.deployShare ( \atg\search\routing\LaunchingService.deployShare ). Lets assume that it is configured to \Search2007.1\SearchEngine\i686-win32-vc71\buildedIndexFiles. b. Lets assume that the index file folder ( \Search2007.1\SearchEngine\i686-win32-vc71\indexFiles) has the following segments (folders) currently : 66900009 @ index engine box 66900010 @ search engine box c. Lets assume that the component SearchEngineService has the "

SSL configuration in JBoss

To configure an SSL port with keystore , check the following steps: 1. Generate the keystore with the following command ( using the java keytool command) keytool -genkey -alias tomcat -keyalg RSA -keystore NAME_OF_KEYSTORE -validity NUMBER_OF_DAYS ( For more details check the url http://download.oracle.com/javase/1.5.0/docs/tooldocs/windows/keytool.html ) 2. Copy the file into the jboss/server/<NAME>/conf/ directory 3. Edit the server.xml in the following path JBoss version 4.0.4 = jboss/server/<NAME>/deploy/jbossweb-tomcat55.sar/ JBoss version 4.2.2 = jboss/server/<NAME>/deploy/jboss-web.deployer/ 4. For JBOSS 4.0.4 the SSL-connector should be configured like: <!– SSL/TLS Connector configuration using the admin devl guide keystore –> <Connector port=”THE_PORT_YOU_LIKE” address=”${jboss.bind.address}” maxThreads=”100? strategy=”ms” maxHttpHeaderSize=”8192? emptySessionPath=”true” scheme=”https” secure=”true” clientAuth=”false” keystore

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 to the data it is indexing, which for production

Tips from Sony Thomas

Search This Blog