No related posts.

This xpath will lead you to grandson node. All other things in the code are self explanatory. An xml specified in the code is also provided., make sure  you copy the xml(test.xml) in the same path mentioned in the java code. Hope the code snippet helps. This code will work fine within an ATG environment. I tried successfully.

Drawback:

This code will definitely help you find the value of known node, but wont help you in finding a dynamic node.Which means you need to specify the node name to get the value.Eg: you can’t read all “category” nodes of  “granddaughter” just by specifying xpath till “granddaughter”.

1 .     “testParsingXML.java”

import java.io.ByteArrayInputStream;
import java.io.File;
import java.io.FileInputStream;
import java.io.FileNotFoundException;
import java.io.IOException;
import java.io.UnsupportedEncodingException;
import java.util.Enumeration;

import org.w3c.dom.Document;
import org.w3c.dom.Element;
import org.w3c.dom.NamedNodeMap;
import org.w3c.dom.Node;
import org.w3c.dom.NodeList;
import atg.xml.tools.XMLToDOMParser;
import atg.xml.tools.apache.ApacheXMLToolsFactory;

public class testParsingXML{
public static void main(String[] argS){
		XMLToDOMParser xtdParser;
		ApacheXMLToolsFactory axtFactory = new ApacheXMLToolsFactory();
		xtdParser = axtFactory.createXMLToDOMParser();
		File xmlFile = null;
		FileInputStream fis= null;
		xmlFile = new File("E:\\test.xml");

		try {
			fis = new FileInputStream(xmlFile);	 // Should wrap with try catch block
			byte fileContent[] = new byte[(int)xmlFile.length()];
			fis.read(fileContent); 	// Should wrap with try catch block
			ByteArrayInputStream bis = new ByteArrayInputStream(fileContent);
			Document document = xtdParser.parse(bis ,false ,null);
			String xPath ="/root/daughter[@name=\"secondchild\"]/granddaughter[@name=\"three2tango\"]/category[@name=\"c1\"]";
			Enumeration nodes = axtFactory.createXSLQueryEngine().select(xPath, document, null);
			Node node = nodes.nextElement();
			if (node.hasAttributes())
			{
			NamedNodeMap attributes = node.getAttributes();
			System.out.println(attributes.item(1));
			System.out.println(attributes.getNamedItem("name").getTextContent());
			System.out.println(attributes.getNamedItem("value").getTextContent());
			}
		} catch (FileNotFoundException e) {
		} catch (IOException e) {
			e.printStackTrace();
		} catch (Exception e) {
			e.printStackTrace();
		}
	}
}

2. “test.xml”

     <root>
	<son name="firstchild">
		<grandson name="gs1" value="dileep"/>
		<grandson name="gs2" value="lloyd"/>
		<grandson name="gs3" value="vivek"/>
	</son>
	<daughter name="secondchild">
		<granddaughter name="three2tango">
			<category name="c1" value="java"/>
			<category name="c2" value="atg"/>
		</granddaughter>
	</daughter>
</root>

Related posts:

1. Droplet & A Repository Query
2. ATG Tag Library:DSP Tags
3. Installing a Decompiler plugin(JAD) for Eclipse

6.Set the “Path to Decompiler” as your “jad.exe” location.
7.Set the “Directory for temperary files “ as “D\.jadeclipse”
8. Restart eclipse once more to use JAD.

The decompiler will come handy when you are moving back and forth through ATG Out of the Box components. If JAD is there OOTB components and can be read and understood easily. Click ToDownload JAD Utility.

Related posts:

1. XMLDOM Parser:ATG
2. The Evolution Of Java

In the API documentation of ATG the class hierarchy is: atg.nucleus.GenericService —> atg.servlet.DynamoServlet. And the classes for sample droplets “Switch” and “ForEach” droplets are “atg.droplet.Switch” and “atg.droplet.ForEach” respectively. Before using the DSP tags in a page, it must be imported in the beginning of the page.

<%@ taglib uri=”/dspTaglib” prefix=”dsp”%>

DSP PAGE tag:
The dsp:page surrounds the content body of the JSP. It is required to use this tag as such whenever your pages include DSP tags.”dsp:page” tag initiates the page rendering process by creating an instance of the “DynamoHTTPServletRequest”. This tag is preceded only by the page directives and import statements.
["content of the page.It can be any dsp or jsp or html tags"]

DSP IMPORTBEAN tag:
dsp:importbean can import a servlet or java bean component into a JSP.It is usually given at the top of the page so that it facilitates reference to all other elements.The tag has 3 attributes BEAN,VAR and SCOPE, of which bean is a compulsory attribute and can’t be omitted.The bean attribute accepts a fully qualified nucleuspath and name of the servlet bean that we want to import. The VAR attribute names an EL variable so that it can be used by other tags in the page. If SCOPE is not mentioned a default page is used.SCOPE determines where the servlet bean specified by VAR is stored and who all can access it.PAGE,REQUEST,SESSION & APPLICATION are the various options available. Now a small eg: will serve a better understanding.
Sample Code:

<dsp:importbean bean="/atg/dynamo/droplet/Switch"/>
<dsp:importbean bean="/atg/dynamo/servlet/RequestLocale" var="requestlocale"/>
<dsp:importbean bean="/atg/dynamo/droplet/Redirect/>
<dsp:setvalue bean="${requestLocale.refresh}" value=" "/>
<dsp:droplet name="Switch">
  <dsp:param bean="${requestLocale.locale.language}" name="value"/>
  <dsp:oparam name="fr">
      <dsp:droplet name="Redirect">
        <dsp:param name="url" value="fr/index.jsp"/>
      </dsp:droplet>
  </dsp:oparam>
  <dsp:oparam name="default">
      <dsp:droplet name="Redirect">
        <dsp:param name="url" value="en/index.jsp"/>
      </dsp:droplet>
 </dsp:oparam>
</dsp:droplet>

Here the Switch, RequestLocale and Redirect droplets are imported to the page. The RequestLocale component is imported to a VAR attribute so that the dsp:setvalue and dsp:param tags can access RequestLocale with EL. EL is enumerated language so it requires the EL tag libraries as well(JSTL).*

* Not going into the details of JSTL as it will divert from the aim of this article, which is just to provide an understanding of the main DSP tags and attributes.

Related posts:

1. Droplet & A Repository Query
2. Understanding-ATG(The e-Commerce Framework)
3. How to Use RQL in JAVA,ATG

AutoSys Instance
An AutoSys instance is one licensed version of AutoSys software running as an AutoSys server with one or more clients, on a single machine or on multiple machines. An AutoSys instance is defined by the instance ID – a capitalized three-letter identifier defined by the $AUTOSERV environment variable. An instance uses its own event server and event processor and operates independently of other AutoSys instances. One could install multiple AutoSys instances. For example, you may want to have one instance for production and another for development. Multiple instances can run on the same machine, and can schedule jobs on the same machines without interfering or affecting the other instances.

Events
AutoSys is completely event-driven. That is, for a job to be activated by the event processor, an event must occur on which the job depends. For example, a prerequisite job has completed running successfully or a required file has been received. Events can come from a number of sources, including the following:
Jobs changing states, such as starting, finishing successfully, and so forth.
Internal AutoSys verification agents, such as detected errors.
Events sent with the sendevent command, sent from the Send Event dialog, the command line, or user applications.
As each event is processed, the event processor scans the database for jobs that are dependent on that event in some way. If the event satisfies another job’s starting condition, that job is either started immediately, or if necessary, queued for the next qualified and available machine. The completion of one job can cause another job to be started, and in this way, jobs progress in a controlled sequence.

Alarms
Alarms are special events that notify operations personnel of situations requiring their attention. Alarms are integral to the automated use of AutoSys. That is, jobs can be scheduled to run based on a number of conditions, but some facility is necessary for addressing incidents that require manual intervention. For example, a set of jobs could be dependent on the arrival of a file, and the file is long overdue. In such a case, it is important that someone investigates the situation, make a decision, and resolves the problem.

• Alarms are informational only.
• Alarms are system messages about a detected problem.
• Alarms are sent through the system as an event.
• Alarms have special monitoring features to ensure they will be noticed.

Utilities
To help you define, control, and report on jobs, AutoSys has its own specification language called Job Information Language, or JIL, for defining jobs, machines, monitors, and reports. This language is processed by the jil command, which reads and interprets the JIL statements that you enter and then performs the appropriate actions, such as adding a new job definition to the database. AutoSys also provides a set of commands that run essential utility programs for defining, controlling, and reporting on jobs. For example, the autorep command allows you to generate a variety of reports about job execution, and the sendevent command allows you to manually control job processing. Additional utility programs are provided to assist you in troubleshooting, running monitors and browsers, and starting and stopping AutoSys and its components. AutoSys also provides a database maintenance utility that runs daily by default.

<<Previous Post

NextPost>>

Related posts:

1. Autosys – Architecture
2. Overview of AutoSys
3. Basic UNIX Commands

The Search Indexer does all the indexing jobs create the .IDX and .STG files. The estore servers(Server-3 & 4) caters the store related requests. Each of the estore servers has many number of instances to handle large number of customer requests.

Related posts:

1. ATG Search Architecture
2. ATG SearchAdmin UI & How Indexing is done?
3. ATG Search: A few key things to note

• Event server (AutoSys database)
• Event processor
• Remote agent

Event Server
The event server or AutoSys database (the RDBMS) is the data repository for all system information and events as well as all job, monitor, and report definitions. Event server refers to the database where all the AutoSys information, events, and job definitions are stored. Occasionally, the database is called a data server, which actually describes a server instance. That is, it is either a UNIX or Windows process, and it is associated data space (or raw disk storage), that can include multiple databases or tablespaces.

High-Availability Option: Dual-Event Servers
AutoSys can be configured to run using two databases, or dual-event servers. This feature provides complete redundancy. Therefore, if you lose one event server due to hardware, software, or network problems, AutoSys operations can continue on the second event server without loss of information or functionality. For various reasons, database users often run multiple instances of servers that are unaware of the other servers on the network. When implementing AutoSys, the database can run stand-alone for AutoSys only, or it can be shared with other applications.

Event Processor
The event processor is the heart of AutoSys; it interprets and processes all the events it reads from the AutoSys database. Sometimes called the event_demon, the event processor is the program, running either as a UNIX process or as a Windows service that actually runs AutoSys. It schedules and starts jobs. After you start it, the event processor continually scans the database for events to be processed. When it finds one, it checks whether the event satisfies the starting conditions for any job in the database. Based on this information, the event processor first determines what actions are to be taken, then instructs the appropriate remote agent process to perform the actions. These actions may be the starting or stopping of jobs, checking for resources, monitoring existing jobs, or initiating corrective procedures.

High-Availability Option: Shadow Event processor
AutoSys lets you set up a second event processor, called the shadow event processor. This second processor should run on a separate machine to avoid a single point of failure. The shadow event processor remains in an idle mode, receiving periodic messages (pings) from the primary event processor. Basically, these messages indicate that all is well. However, if the primary event processor fails for some reason, the shadow event processor will take over the responsibility of interpreting and processing events.

Remote Agent
On a UNIX machine, the remote agent is a temporary process started by the event processor to perform a specific task on a remote (client) machine. On a Windows machine, the remote agent is a Windows service running on a remote (client) machine that is directed by the event processor to perform specific tasks. The remote agent starts the command specified for a given job, sends running and completion information about a
task to the event server, then exits. If the remote agent is unable to transfer the information, it waits and tries again until it can successfully communicate with the database.

<<Previous Post

Next Post>>

Related posts:

1. Autosys Machines, Autosys Instance, Events, Alarms, Utilities
2. Overview of AutoSys
3. Basic UNIX Commands

AutoSys Jobs
In the AutoSys environment, a job is a single action that can be performed on a valid AutoSys client machine. On UNIX, this action can be any single command or shell script, and on Windows, this action can be any single command, executable, or batch file. In addition, job definitions include a set of qualifying attributes.

Defining Jobs
Using AutoSys utilities, you can define a job by assigning it a name and specifying the attributes that describe its associated behavior. These specifications make up the AutoSys job definition. There are two methods available to create job definitions.

1. Using the AutoSys Graphical User Interface (GUI).
2. Using the AutoSys Job Information Language (JIL) through a command-line interface.

AutoSys Graphical User Interface
The AutoSys GUI allows you to interactively set the attributes that describe when, where, and how a job should run. The fields in the GUIs correspond to the AutoSys JIL sub-commands and attributes. In addition, from the GUI Control Panel, you can open applications that allow you to define calendars, monitors, and reports, and allow you to monitor and manage AutoSys jobs.

Job Information Language
AutoSys JIL is a specification language, with its own syntax, that is used to describe when, where, and how a job should run. When you enter the jil command, you get the jil command prompt, at which you can enter the job definitions one line at a time using this special language. When you exit the jil command-line interface, the job definition is loaded into the AutoSys database. Alternatively, you can enter the definition as a text file and redirect the file to the jil command. In this case, the jil command activates the language processor, interprets the information in the text file, and loads this information in the AutoSys database.

Next Post>>

Related posts:

1. Autosys Machines, Autosys Instance, Events, Alarms, Utilities
2. Autosys – Architecture
3. Basic UNIX Commands

A droplet is an ATG concept which is implemented with the help of java. We can say a droplet is complete when the java class and a properties file of the java class are combined. The scope of a droplet is always global. The droplet class extends DynamoServlet. It is same as that of a servlet class in java and it contains a service( ) method also. The two parameters of the service method are of type DynamoHttpServletRequest and DynamoHttpServletResponse. And it throws ServletException and IOException.
Following the previous example of an Employee table (refer), here also we are using the same itemDescriptor (employeeItemDescriptor) and same repository xml, for sake of clarity. Here the droplet is used to get the list of all employees (same names should not get repeated) and display it in dropdown list. A simple select query(select * from employeeTB) is used instead of using (select distinct EName from employeeTB). So the example will address both questions.

Three key parts while addressing the questions are,
1. JSP file where the employee names (EName) are displayed.
2. The droplet class or the java class (employeeNamesDroplet.java).
3. The corresponding properties file of the class (employeeNamesDroplet.properties)

1.JSP File(test.jsp)

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<%@ taglib uri="/dspTaglib" prefix="dsp"%>
<%@ taglib uri="/dspCoreTaglib" prefix="core"%>
<dsp:importbean bean=" Folder Structure/employeeNamesDroplet "/>
<dsp:importbean bean="/atg/dynamo/droplet/ForEach" />
<dsp:page>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title> Sample Page </title>
</head>
<body>
<%-- page content --%>
<div>
	<div> Employee Name </div><div>
   <dsp:select bean="testFormHandler.eName" id="ddlENAME">
    <dsp:option value="-1" selected="selected" >Select</dsp:option>
    <%--Our droplet --%>
	<dsp:droplet name="folderStructure/employeeNamesDroplet">
        	  <dsp:oparam name="output">
     <%--ATG OUT OF THE BOX DROPLET --%>
      	<dsp:droplet name="/atg/dynamo/droplet/ForEach">
        	 <dsp:param name="array" param="enameslist"/>
	 <dsp:oparam name="empty">
 <dsp:option value="There are No Employee Names in DB"></dsp:option>
	 </dsp:oparam>
	 <dsp:oparam name="output">
<%--eid, employeename are property values from SampleRepositoryXML file --%>
           <dsp:getvalueof id="en" param="element.eid">
	    <dsp:option value="<%=en%>">
	    <dsp:valueof param="element.employeename">
	    </dsp:valueof>
	    </dsp:option>
	 </dsp:getvalueof>
	</dsp:oparam>
        	</dsp:droplet>
       </dsp:oparam>
      </dsp:droplet>
     </dsp:select>
   </div>
</body>
</dsp:page>
</html>

2.“employeeNamesDroplet”

import java.io.IOException;
import java.util.ArrayList;
import java.util.List;
import javax.servlet.ServletException;
import atg.repository.Query;
import atg.repository.Repository;
import atg.repository.RepositoryException;
import atg.repository.RepositoryItem;
import atg.repository.RepositoryView;
import atg.servlet.DynamoHttpServletRequest;
import atg.servlet.DynamoHttpServletResponse;
import atg.servlet.DynamoServlet;

public class employeeNamesDroplet extends DynamoServlet
{
private static final String OUTPUT = "output";
private static final String EMPTY = "empty";
private static final String E_NAMES="enameslist";
private Repository repository;
private String ItemDescriptor;

public void service(DynamoHttpServletRequest DHSRequest,DynamoHttpServletResponse DHSResponse) throws ServletException, IOException
{
   List eNamesList = getNames();
   if (eNamesList.size() > 0)
  {
       	DHSRequest.setParameter(E_NAMES, eNamesList);
         	DHSRequest.serviceParameter(OUTPUT,DHSRequest,DHSResponse);
   } else {
	DHSRequest.serviceParameter(EMPTY,DHSRequest,DHSResponse);
	}
}

private List getNames(){
  List tempNames = new ArrayList();
  List eNames = new ArrayList();
  if(getRepository() != null){
	RepositoryView rView;
	Query query;
	try{
	rView = getRepository().getView(“employeeItemDescriptor”);
	query = (Query) rView.getQueryBuilder().createUnconstrainedQuery();
	RepositoryItem[] rItems = rView.executeQuery(query);
   for(int ri=0; ri < rItems.length; )
   {if(tempNames.contains((String)(rItems[ri].getPropertyValue("employeename")))= = false)
    { tempNames.add((String)(rItems[ri].getPropertyValue("employeename")));
      eNames.add((RepositoryItem)rItems[ri]);
      ri++;
    }else{
 ri++;}
   	 }
}
catch(RepositoryException re)
{
System.out.print(“..”+re);
}
catch(Exception ex)
{System.out.print(“..”+ex);
}
}
return (List)eNames;
}// end of getnames method

public Repository getRepository() {
return repository;
}
public void setRepository(Repository repository) {
this.repository = repository;
}

}// end of the class

3.Properties File of the Droplet(“employeeNamesDroplet.properties”)
$class=droplet. employeeNamesDroplet
$scope=global
Repository = Give the name of your repository here.

Related posts:

1. How to Use RQL in JAVA,ATG
2. ATG Tag Library:DSP Tags
3. Understanding-ATG(The e-Commerce Framework)

Picture looks a bit blurred in the site but if you save it to your machine the claritty is better,regret the inconveniance.Also the pictures are numbered

[View with PicLens]

Related posts:

1. Ideal Production Environment for an e-commerce site
2. ATG Search Architecture
3. ATG Search:A brief note