Welcome to the IBM Websphere Commerce Hub


Welcome to the IBM Websphere Commerce Hub

Come join me in my journey to explore the various features and capabilities of IBM Websphere Commerce and understand how retailers can benefit from its really cool out-of-box functionality.

Showing posts with label WCS6. Show all posts
Showing posts with label WCS6. Show all posts

Tuesday, October 22, 2013

Websphere Commerce Data Cache

  • The WebSphere Commerce data cache can be configured to use DistributedMap object caches, by defining specially named.object caches in the cacheinstances.properties file.
  •  Object caching in specified DistributedMap instances causes each type of data to be cached in its corresponding DistributedMap object.
  • Takes precedence over the dynamic caching configuration specified in cachespec.xml - the configurations are no longer read from the cachespec.xml for the objects cached using the object caches - hence priority, timeout, or inactivity settings cannot be fine-tuned using cachespec.xml and need to be defined using various DistributedMap attributes in the cacheinstances.properties file.
  • Can be configured in two ways :
    • Define DistributedMap objects with the default JNDI names in the cacheinstances.properties file
    • Use the WebSphere Application Server Integrated Solutions Console. From the left menu, click Resources > Cache instances > Object cache instance
  •  The DistributedMap cache objects cannot be viewed in Dynamic Cache Monitor which comes packaged with WAS. The Extended Dynamic Cache Monitor need to be installed. The steps and download can be found in the here

Related Reading:
 IBM WCS 7.0 Infocenter

Sunday, January 27, 2013

Business Object Document : Websphere Commerce Web Services

The WebSphere Commerce BOD command framework architecture uses well defined interfaces to decouple the implementation of the presentation layer, business logic layer and persistence layer. From the business logic layer perspective, OAGIS messages are used as the interface for making requests to retrieve business data or invoke business logic. The BOD command framework provides the capability to process these BOD requests and responses.

Found this really nice pictorial description of the various assets and processes involved in the BOD development in the  IBM Red Book (sg247619)

More to come to BOD Command Framework... 

On reader's requests -

See Also:

 

Thursday, April 19, 2012

Paypal Integration with WCS 6.0

PayPal is one of the most well-known worldwide payment service providers. The flow for PayPal is different from traditional payment gateways, such as Visanet®. During shopping, an online store redirects the shopper to the PayPal web site to process the payment. PayPal Express Checkout is PayPal's premier checkout solution, which streamlines the checkout process for buyers and keeps them on the merchant's site after making a purchase.

The Express Checkout button gives buyers another way to pay, and it complements merchant’s existing payment solution. Online shoppers appreciate the convenience and security of PayPal, where they can pay with their PayPal balance, bank account, or credit card.

Key Features of Express Checkout

Express Checkout is a fast, easy way for buyers to pay with PayPal. Express Checkout eliminates one of the major causes of checkout abandonment by giving buyers all the transaction details at once, including order details, shipping options, insurance choices, and tax totals.
Studies show that adding the Express Checkout button to your website can increase your sales up to 18 percent.

For more details , refer PayPal Express Checkout Integration Guide

PayPal Plug-in for Websphere Commerce

IBM WebSphere Version 6.0 Plugin
The plug-in supports Express Checkout web flows and APIs. The plug-in has been developed by PayPal in collaboration with IBM's Commerce architects using WebSphere Commerce's payment plug-in API.

It supports:
  • SALE, AUTH, and ORDER transaction types
  • Multiple auth and captures - useful for orders that have multiple shipping addresses or associated back orders
  • Refund transactions
  •  All PayPal supported currencies.
The plug-in can be downloaded from the PayPal Integration Center using the link 

The integration steps can be found inside the downloadable itself.

PayPal Checkout Flow

Typical order flow for WebSphere Commerce

As shown in figure below, a typical order flow for a shopper is:
1. Checks out from the shopping cart page.
2. Provides shipping and billing address information
3. Chooses the Shipping Method
4. Reviews the order, chooses the payment method and pays for it.
5. Receives an order confirmation.




PayPal order flow with WebSphere Commerce

In an Express Checkout flow, a buyer still checks out at the beginning of the flow. However, after the buyer chooses the PayPal payment method, the buyer is re-directed to the PayPal web site for authentication. After that, the buyer is re-directed back to the WebSphere Commerce store to finish the left order flows.

In the Express Checkout flow, the shopper:
1. Checks out from the shopping cart page.
2. Provides shipping and billing address information
3. Chooses the Shipping Method
4. Reviews the order , chooses the PayPal as the payment method
5. Logs into PayPal to authenticate his or her identity.
6. Reviews the transaction on PayPal.
7. Confirms the order and pays from the site.

Figure below shows the Express Checkout flow:


References:

https://cms.paypal.com/us/cgi-in/?cmd=_rendercontent&content_ID=developer/e_howto_api_ECGettingStarted

http://publib.boulder.ibm.com/infocenter/wchelp/v6r0m0/index.jsp

Related Posts:
PayPal Integration with Websphere Commerce 7