IFSC and MICR code

For internet banking third party transfer you might need the IFSC or MICR code.

IFSC or Indian Financial System Code is an alpha-numeric code that uniquely identifies a bank-branch participating in the NEFT system.
MICR or Magnetic Ink Character Recognition is a character recognition technology used primarily by the banking industry to facilitate the processing of cheques.

Please find below some useful links to get the IFSC and MICR code for a bank branch:

http://rbi.org.in/scripts/neft.aspx
http://rbidocs.rbi.org.in/rdocs/content/docs/67440.xls
http://bankifsccode.com/
http://banks-india.com/ifsc-code.php
http://en.wikipedia.org/wiki/Indian_Financial_System_Code
http://en.wikipedia.org/wiki/Magnetic_ink_character_recognition

Comments

ATG - more about Forms and Form Handlers

An ATG form is defined by the dsp:form tag, which typically encloses DSP tags that specify form elements, such as dsp:input that provide direct access to Nucleus component properties. Find below a sample dsp:form tag. <dsp:form action="/testPages/showPersonProperties.jsp" method="post" target="_top"> <p>Name: <dsp:input bean="/samples/Person.name" type="text"/> <p>Age: <dsp:input bean="/samples/Person.age" type="text" value="30"/> <p><dsp:input type="submit" bean="/samples/Person.submit"/> value="Click to submit"/> </dsp:form> When the user submits the form, the /samples/Person.name property is set to the value entered in the input field.Unlike standard HTML, which requires the name attribute for most input tags; the name attribute is optional for DSP form element tags. If an input tag omits the n...

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.

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 - 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://...

ATG Order update - InvalidVersionException and ConcurrentUpdateException

ATG repository item descriptor can have the version property. The atg.adapter.gsa.ItemTransactionState holds this version information. For example consider the Order item-descriptor. It has the version property defined against the table dcspp_order. Means, the dcspp_order table has the column version which defines which version of order is currently in the DB. Each order update flow will update this column. <property name="version" display-name-resource="version" data-type="int" queryable="true" readable="true" column-name="version" hidden="false" category-resource="categoryInfo" expert="true" required="false" cache-mode="inherit" writable="true"> <attribute name="uiwritable" value="false"/> <attribute name="propertySortPriority" value="30"/> </property> ------------------------------- Du...

Tips from Sony Thomas

Search This Blog