AJAX sample implementation for WebSphere Commerce
Assuming the following design requirements:
  • The AJAX handler will be /AjaxPPTGiftCardsBalanceEnquiry
  • The command to serve the AJAX request will be com.ibm.commerce.payment.commands.ajax.DoPPTGiftCardsBalanceEnquiryCmd
  • The equivalent implementation class will be com.ibm.commerce.payment.commands.ajax.DoPPTGiftCardsBalanceEnquiryCmImpl
  • The store id is 10003
  • The AJAX request is required during checkout process and will be added to “OrderSummaryDisplay.jspf”
  • The AJAX call is used to verify GiftCard numbers along with their pin
  • High level implementation is shown in code snippets below with place holders on where to add your implementation

Follow the steps below to add an AJAX call to your site:
  • Add the following lines of code to OrderSummaryDisplay.jspf
    • It is important not to forget the call to e.preventDefault() or you will end up refreshing the whole page.
<form name="giftcardform" method="post" action="VerifyGiftCard" id="giftcardform" class="form_inline">
<label for="gift_card_number1"><span>Gift card no</span></label>
<input name="gift_card_number_1" id="gift_card_number_1" type="text" maxlength="20" />

<label for="gift_card_number_1"><span>Pin no</span></label>
<input name="gift_card_pin_1" id="gift_card_pin_1" type="text" maxlength="20" />
<script type="text/javascript">
function verifyGiftCard(e,num) {
console.debug("verifyGiftCard for Gift Card number: "+num);
giftCardNumber=dojo.byId('gift_card_number_1').value;
giftCardPin=dojo.byId('gift_card_pin_1').value;
console.debug("giftCardNumber: "+giftCardNumber);
console.debug("giftCardPan: "+giftCardPin);
var xhrArgs = {
url: "/webapp/wcs/stores/servlet/AjaxPPTGiftCardsBalanceEnquiry",
content:{
'dcGiftCardNumber':giftCardNumber,
'dcGiftCardPin':giftCardPin
},
handleAs: "json",
load: function(data) {
console.debug("AJAX call successful");
console.debug(data);
handleResponse(data);
},
error: function(error) {
console.debug("An unexpected error occurred: ");
console.debug(error);
}
}

//Call the asynchronous xhrGet
var deferred = dojo.xhrPost(xhrArgs);
e.preventDefault();
}

function handleResponse(data){
//Add business logic here to handle AJAX response
}
</script>
<fmt:message var="brandAccountCode" key="S_ACCOUNT" bundle="${storeFrontText}"/>
<input name="gift_card_verify" id="gift_card_verify" type="image" class="submit_button" alt="Verify Gift card no" src="<c:out value="${jspStoreImgDir}${vfileColor}checkout/btn_apply_nus_code.gif"/>" onclick="verifyGiftCard(event,1);"/>
</form>
  • Add the command class to project WebSphereCommerceServerExtensionsLogic
package com.ibm.commerce.payment.commands.ajax;
import com.ibm.commerce.command.ControllerCommand;
public interface DoPPTGiftCardsBalanceEnquiryCmd extends ControllerCommand{
}
  • Add the associated implementation Class for the command above to project WebSphereCommerceServerExtensionsLogic. The code is chopped off to show the important pieces only. Take the following into consideration:
    • You don't need to specify a view as all AJAX commands are served by one of two JSPs available by default, which are “AjaxActionResponse.jsp” when successful or “AjaxActionErrorResponse.jsp” in case of exception thrown.
    • Even if you tried to set a View, WebSphere commerce will ignore it and goes to the default views set for AJAX responses.
    • All parameters included in request or response are included in JSON response automatically for you
    • If you don't need any request parameter to be available in the response, just make sure to remove them out as shown below
public class DoPPTGiftCardsBalanceEnquiryCmdImpl
extends ControllerCommandImpl
implements DoPPTGiftCardsBalanceEnquiryCmd{

public void performExecute() throws ECException {
super.performExecute();
TypedProperty prop = getRequestProperties();

try {
String giftCardNumber=prop.getString(“dcGiftCardNumber”)
String giftCardPin=prop.getString(“dcGiftCardPin”);

//Cleanup - remove request parameters you don't need anymore
prop.remove(“dcGiftCardNumber”);
prop.remove(“dcGiftCardPin”);

} catch (ParameterNotFoundException e) {
//throw exception and handle situation appropriately
}

//Set the view to render
TypedProperty rspProp = new TypedProperty();
//Add any paramater you need to pass to the client as response

setResponseProperties(rspProp);

}
  • Update struts-config-ext.xml to add an action mapping for “/AjaxPPTGiftCardsBalanceEnquiry” as shown below, where:
    • Action mapping is set to “/AjaxPPTGiftCardsBalanceEnquiry”
    • Type is set to “com.ibm.commerce.struts.AjaxAction”
    • Parameter is set to “com.ibm.commerce.payment.commands.ajax.DoPPTGiftCardsBalanceEnquiryCmd”
 struts-config-ext.xml
 
  • Register the new command by running the following SQL command:
insert into CMDREG (STOREENT_ID, INTERFACENAME, DESCRIPTION, CLASSNAME, TARGET)
values (10003,'com.ibm.commerce.payment.ajax.commands.ajax.DoPPTGiftCardsBalanceEnquiryCmd',
'This is a new controller command for the PPT Gift cards balance verify AJAX command.',
'com.ibm.commerce.payment.commands.ajax.DoPPTGiftCardsBalanceEnquiryCmdImpl','Local');
Take into consideration that 10003 is the parent for other stores, so don't have to repeat this for every store. Or you can just associate it with store 0 which is parent for all in out-of-box WebSphere Commerce installation.
  • Add command access control policy using the Websphere commerce binary command acpload where WC7NEW is database name, username/password are those required to connect to the database and finally WSCADMIN is the schema name in capital letters (and it is usually equivalent to username) :
    • acpload WC7NEW <username> <password> AjaxPPTGiftCardsBalanceEnquiryCmdACPolicy.xml WCSADMIN
  • Sample content for AjaxPPTGiftCardsBalanceEnquiryCmdACPolicy.xml is shown below:
<?xml version="1.0" encoding="ISO-8859-1" standalone="no" ?>
<!DOCTYPE Policies SYSTEM "../dtd/accesscontrolpolicies.dtd">
<Policies>
<Action Name="ExecuteCommand" CommandName="Execute">
</Action>
<ResourceCategory Name="com.ibm.commerce.payment.commands.AjaxPPTGiftCardsBalanceEnquiryCmdResourceCategory"
ResourceBeanClass="com.ibm.commerce.payment.commands.AjaxPPTGiftCardsBalanceEnquiryCmd">
<ResourceAction Name="ExecuteCommand"/></ResourceCategory>
<ResourceGroup Name="AllSiteUserCmdResourceGroup" OwnerID="RootOrganization">
<ResourceGroupResource Name="com.ibm.commerce.payment.commands.AjaxPPTGiftCardsBalanceEnquiryCmdResourceCategory" />
</ResourceGroup>
</Policies>
  • According to infocenter, you have to update struts configuration in the register as shown below. Personlly I don't think it makes a difference but you can do it anyway.

Update registry

  • Restart WebSphere Commerce server
  • Test your new AJAX calls using FF and FireBug plugin to make sure the AJAX call is successful and you get a JSON response back which contains what ever parameters you put in the response back to client.
  • If you wish to implement AJAX model using a normal command of type BaseAction instead of AjaxAction, so you can have different views for different AJAX calls instead of a master view for all of your calls, you need to do those extra steps (high level steps):
    • Change the action type from AjaxAction to BaseAction
    • Define a view in action mappings and global forwards
    • Update your command impl to forward to the new view
    • Add access control policy for the view
    • Make sure that the JSP associated with the view you created, sends the right format back to the client which is usually either JSON or text (which is used if you are sending back HTML fragments to update the DOM)

Comments

Post a Comment

Popular posts from this blog

Dataload Utility In WCS

Data can be loaded into WCS tables using data load utility.   WCS Data Load utility performs the following functions in a single operation: 1.              Reads the data from the input source file. 2.              Transforms the source data to WebSphere Commerce business objects. 3.              Allocates and resolves WebSphere Commerce business objects to physical data. 4.              Loads the physical data into the database. There are three configurations files and a input source file required to complete the data loader setup. WCS supports only CSV File Reader for other input source you have to write your own Reader Class. This means that if you are using OOB CSVReader then your input file must be a CSV file. The three configuration files are listed below. 1.              wc-dataload-env.xml 2.              wc-dataload-loader.xml 3.              wc-dataload.xml wc-dataload-env.xml holds the environment settings such as database name,encrypted password,data
Read more

10 Steps to Configure Email – Websphere Commerce Server

10 Steps to Configure Email – Websphere Commerce Server Websphere Commerce Server – Configure Email Follow 10 steps for configuring email in Websphere Commerce Server Step 1: Create a JSP ( eg:- AbcEmailNotify.jsp) Create a JSP, lets name it AbcEmailNotify.jsp AbcEmailNotify.jsp will be used for displaying contents of email to recipient. Note: Currently keep AbcEmailNotify.jsp as blank (without any code) Step 2: Create View ( eg- AbcEmailNotifyView) Make an Entry in Struts-Config.xml file for AbcEmailNotify.jsp as below < action path=’/AbcEmailNotifyView’ type=’com.ibm.commerce.struts.BaseAction’> < set-property property =’authenticate’ value =’10101:1′/> < set-property property =’https’ value =’10101:1′/> < /action> < forward name=”AbcEmailNotifyView /10101/-3″ path=”/< location of JSP file >/AbcEmailNotify.jsp” className=”com.ibm.commerce.struts.ECActionForward”> < set-property property=”implClassName” value=”com.i
Read more

WebSphere Commerce

Image
1. Explain WCS Archetecture WebSphere Commerce functional architecture Descriptions: Controller layer The conductor of operations for a request. It controls the transaction scope and manages the session related information for the request. The controller first dispatches to a command and then calls the appropriate view processing logic to render the response. Presentation layer The presentation layer displays the result of command execution. The presentation layer can use JSP pages, or other rendering technologies. Business Context Service (BCS) A service that manages contextual information used by business components. The contexts include such information as globalization and entitlement. Business logic facade This generic interface is implemented as a stateless session bean which the controller calls to invoke controller commands. Controller commands A controller command business process logic such as
Read more