Skip to main content

Webpshere Commerce Registry

Registry is an another solution for those which can’t be cached using Dyna cache. Another use would be to store configuration data for a store. By using registry, you don't need a server restart every time as organization admin console provides an interface to refresh registry. The new custom registries will be appearing in the admin console under the registry section.




Steps to create a new custom registry in WCS
Step 1. Register the registry in wc-server.xml.

<Registries>
......
.....
<registry
name="TestRegistry" regClassName="com.wcs.registry.TestRegistry "/> 
</Registries>
Step 2.Create  a class that implements   interface com.ibm.commerce.registry.Registry
package com.wcs.registry;
import java.util.HashMap;
import com.ibm.commerce.exception.ECException;
import com.ibm.commerce.registry.Registry;
import com.ibm.commerce.registry.RegistryManager;
  
public  class TestRegistry  implements Registry {
private HashMap sampleRegistry ;
/** * @return Returns the hashSampleRegistry. */
 public Hashtable getSampleRegistry() 
{
 return sampleRegistry ;
 }
                  
/**
 * This method initializes the registry. It is being called when server starts. 
 */
public void initialize() throws Exception {
RegistryManager.singleton().addRegistry("TestRegistry  ", this);
try {
this.initialRegistry();
} catch (ECException e) {
e.printStackTrace();
}
}
/**
*This method is used to refresh the registry. It is being called when user updates the registry through Site Admin console. 
*/
public void refresh() throws Exception {
try {
//Write the business  logic to fetch  data  and put it  in a variable
RoleAccessBean rab = new RoleAccessBean();
rab = rab.findByName("Site Administrator");
sampleRegistry .put(rab.getRoleId(), rab.getName());
} catch (ECException e) {
   e.printStackTrace();
}
               
}
/**
* This methods refreshes the registry with initial data.
*/
private void initialRegistry() throws Exception {
 //Write the business  logic to fetch initial  data  and put it  in a variable
                               
}
}
Step3: Create the  Data bean which will be used for reading registry values.
package com.wcs.registry;
public class TestRegistryBean extends SmartDataBeanImpl     implements     SmartDataBean
 
private HashMap registry;  
public void populate() throws com.ibm.commerce.exception.ECException {   
TestRegistry   testRegistry  ;  
testRegistry   =( TestRegistry  )(RegistryManager.singleton().getRegistry("TestRegistry"));
//Set  the Registry
setRegistry(testRegistry .getSampleRegistry()); 
}
public Hashtable getRegistry() 
{
return registry;
 
public void setRegistry(HashMap mapRegistry) {
this.registry = mapRegistry; 

}
Step4: Print the registry values  in Jsp using the data bean
<jsp:useBean id="testRegistryBean" class=" com.test.registry. TestRegistryBean" scope="page"> <%com.ibm.commerce.beans.DataBeanManager.activate(testRegistryBean,request); %>
</jsp:useBean>
<c:forEach var="registry" items="${testRegistryBean.registry}">  
c:out value="${registry.value}"/>
< /c:forEach>

Comments

Popular posts from this blog

How to read applied promotions codes

The below snippet will give you to read the promotions codes which are applied to order number, String orderId = "978593958"; OrderKey orderKey = new OrderKey(new Long(orderId)); PromotionArgumentSessionBeanPersistenceManager promoManager = new PromotionArgumentSessionBeanPersistenceManager(); PromotionArgument promArg = promoManager.load(orderKey); Iterator prmoExeRecds = promArg.getPromotionExecutionRecords(); while(prmoExeRecds.hasNext()) { PromotionExecutionRecord promotionExeecutionRecord = (PromotionExecutionRecord) prmoExeRecds.next(); Promotion promotion = promotionExeecutionRecord.getPromotion(); System.out.println("Name: " + promotion.getName()); System.out.println("Admin description: " + promotion.getDescription(commandContext.getLocale(), com.ibm.commerce.marketing.promotion.Description.SHOPPER_SHORT_DESC)); }

Dataload Utility

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 Web Sphere Commerce business objects. 3.                Allocates and resolves Web Sphere 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 CSV Reader then your input file must be...

IBM Websphere Commerce V8.0

IBM Websphere Commerce V8.0 is Announced and its Here: Just in case if you have missed the announcement on Oct 1st, 2015 of IBM Websphere Commerce Version 8.0. Here is the  Link . IBM WebSphere Commerce-powered stores are going to get a lot of up-gradation. As IBM releases its  WebSphere Commerce V8.0 enhancements, Merchandisers can expect a richer, easier experience for users and marketers deepen customer engagement, drive customer loyalty, increase revenues, and improve profitability with an improved business user environment. Help deliver a better customer service and support experience. Provide a software platform upgrade to the latest web application server, database, and integrated developer environment, and incorporate earlier WebSphere Commerce V7.0 feature pack capabilities. Key things to know about IBM WebSphere Commerce V8.0: DHTML (Dynamic HTML) :   In Version 8.0, the Management Center is updated to use  Dynamic HTML (DHTML) . ...