Customizing the Pipeline definition files - XML Modifications

-
Adding the ApproveOrder pipelinelink to the existing pipeine chain.

<pipelinechain name="executeValidateForCheckoutChain ">     
     <pipelinelink name="ExecuteValidateForCheckoutChain"
               transaction="TX_MANDATORY" xml-combine="replace">
          <processor jndi="/atg/commerce/order/processor/
                                ExecuteValidateForCheckoutChain"/>
            <transition returnvalue="1" link="ApproveOrder"/>   
      </pipelinelink>
      <pipelinelink name="ApproveOrder" transaction="TX_MANDATORY">
            <processor
            jndi="/atg/commerce/order/processor/ApproveOrder"/>
            <transition returnvalue="1" link="approverEmailIds"/>
       </pipelinelink>

Adding the processor Approve Order to the Pipeline Registry.

</pipeline-registry-configuration>
     ...........
  <processor-registry xml-combine="append-without-matching">
     <processor>
        <nucleus-
        path>/atg/commerce/order/processor/ApproveOrder</nucleus-
        path>
      <display-name>give a name ....</display-name>
      <category>Approve</category>
      <description>give a description</description>
    </processor>
  </processor-registry>
</pipeline-registry-configuration>

See the Java and Property files changes for a Component

Comments

  1. UnknownSeptember 10, 2013 at 12:50 AM

    What are the different transaction modes and why are they used ? For eg : transaction="TX_MANDATORY"

    ReplyDelete
  2. SebastianSeptember 10, 2013 at 9:21 AM

    you can refer atg oracle documentation for this http://docs.oracle.com/cd/E26180_01/Platform.94/ATGProgGuide/html/s1205transactionmodes01.html

    Generally a transaction mode mandatory is used when the section of code is a part of a larger transaction and in that it verifies a transaction is already in place.

    ReplyDelete

Post a Comment

Popular posts from this blog

BCC site status inaccessible Agent Production in error state

-
Image
The Error Message showing in BCC T he error logs is showing the below message /atg/epub/DeploymentServer Failed to connect to agent 'Production'. This agent not allowed to be absent for  a deployment. The server will continue attempts to  intialize the connection. Set loggingDebug to true for  continued exception and stacktrace logging. Analysis This happens when the target/Production instance is down for some  reason or the RMI configuration which points to the target/Production instance may not be correct one. Fix If this is happening  due to target/Production instance down  then we can restart the target/Production Server,Other wise  correct the RMI configuration from the BCC agent configuration page and reinitialise. Verify the RMI Port in Configuration.properties file.Usually this file will be located in the path C:\ATG\ATG10.2\home\servers\ATGProduction\localconfig\atg\dynamo\Configuration...
Read more

Weblogic Issues during EAR Deployment Exception in AppMerge flows progression

-
Unable to access the selected application Exception in AppMerge flows progression Bean already exists "weblogic.j2ee.descriptor.ModuleBeanImpl@..../Modules[weblogic.descriptor.internal.Descriptor.Beankey@....] This issue can happen in many scenarios, may be you need to check your deployment descriptors based on Application Servers used, this generally happens due to issue in XML files related to deployment. I got this issue when i mistakenly added the modules twice in the Manifest file, the module 'Store.Storefront' is added more than once in  'ATG-Required'  of my Manifest.MF file,due to this i am seeing the module 'storedocroot.war' is added twice in my application.xml which is located in the  path ATGProd.ear\META-INF\application.xml.Due to this i am not able to deploy my EAR file. I have removed the duplicate entry and deployed the application and everything working fine. ....... <module>         <web>  ...
Read more

Add a shopping cart button to the product page

-
Make sure you have ATG running with your Application  module. We are adding a jsp page fragment called addcart.jsp . This fragment will use two parameters passed from other jsp, skuInfo.jsp - skuId and productId . Add the form and inputs required to add an item to the order,  as shown in the sample code below: <dsp:input type="hidden" bean="CartModifierFormHandler.catalogRefIds" paramvalue="skuId"/> <dsp:input type="hidden" bean="CartModifierFormHandler.productId" paramvalue="productId"/> <dsp:input type="text" size="5" bean="CartModifierFormHandler.quantity" value="1"/> <dsp:input type="hidden" bean="CartModifierFormHandler.addItemToOrderSuccessURL" value="cart.jsp"/> <dsp:input type="submit" bean="CartModifierFormHandler.addItemToOrder" value="Add to Cart"/> Don't forget to import the /at...
Read more