Some Java, JEE and WebSphere stuffs | Something about JEE and WebSphere. Java, JEE and WebSphere tips and tutorials

WebSphere Commerce Feature pack installation

WebSphere Commerce Feature pack installation is a straight forward job. Follow the below steps for installation of Feature packs in your machine. In order to install feature packs our WCS installation needs to be in some desired fix level. So the first thing is to apply the required fix levels in our WC installation.

We need WebSphere Commerce Update installer for installing WCS fix packs. So follow the below steps to install WebSphere Commerce update installer.

1. Download WebSphere Commerce Update installer from location

http://www.ibm.com/support/docview.wss?uid=swg24013502

2. Extract the contents and double click on install.exe and follow onscreen instructions. Please make sure that there is no space in your directory structure.

Too simple? Yeah we are done with the installation of WCS update installer. Now let us apply the fix packs to make our WCS installation to the required level.

3. Download the latest WCS fix pack from http://www-01.ibm.com/support/docview.wss?rs=3046&uid=swg21246009. I have downloaded fix pack 9 (6.0.0-WS-WCDeveloper-FP009.pak) from here.

4. Save the fix pack to %WCS_UPDATE_INSTALL_DIRECTORY%/maintenance directory.

5. Open WebSphere Commerce update installer.(Just double click on the update.bat from %WCS_UPDATE_INSTALL_DIRECTORY% )

6. Specify the WebSphere Commerce Developer installation directory, and click next.

7. Select Install Maintenance Package. Click Next.

8. Select the %WCS_UPDATE_INSTALL_DIRECTORY%/maintenance directory and click next.

9. Select the 6.0.0-WS-WCDeveloper-FP009.pak file and click next.

10. You are prompted to update the database. Select Yes to update your database automatically.

11. On the summary page, review the information and click Next.

12. Fix pack installation begin and the final screen will be displayed with a success message on the screen. If it failed please check the log files for trouble shooting. Click on Finish from this screen

13. Download the WebSphere Commerce feature pack package and extract to a temporary location

14. Double click on install.bat. The installation wizard opens. Click on Next

15. Accept the license agreement. Click on Next

16. Production selection page opens. Select the location where you have installed WebSphere Commerce Developer on this page. Click On Next

17. Installation summary page will be displayed. Click on Next

18. Click on Finish in installation result page

We have successfully installed the WCS feature pack in our machine.

WebSphere Commerce URLs

This post is more to me. I usually find it difficult to remember different WebSphere Commerce URLs like commerce accelerator, org admin console etc. So I just want to keep all these URLs together in one place so that any time I can access it anytime I want

Administration Console Logon
https://localhost:8002/webapp/wcs/admin/servlet/ToolsLogon?XMLFile=adminconsole.AdminConsoleLogon

WebSphere Commerce Accelerator Logon
https://localhost:8000/webapp/wcs/tools/servlet/ToolsLogon?XMLFile=common.mcLogon

Organization Administration Console Logon
https://localhost:8004/webapp/wcs/orgadmin/servlet/ToolsLogon?XMLFile=buyerconsole.BuyAdminConsoleLogon&storeId=0

DB Access
http://localhost/webapp/wcs/admin/servlet/db.jsp

Advanced B2B Direct starter store
https://localhost/webapp/wcs/stores/servlet/AdvancedB2BDirect/index.jsp

Consumer Direct starter store
https://localhost/webapp/wcs/stores/servlet/ConsumerDirect/index.jsp

Commerce Plaza starter store
http://localhost/webapp/wcs/stores/servlet/CommercePlaza/index.jsp

Supply chain starter store
http://localhost/webapp/wcs/stores/servlet/CommercePlaza/index.jsp

Madisons Web2 store
http://localhost/webapp/wcs/stores/servlet/Madisons2/index.jsp

CNTR0031W: Error starting CMP bean wcfull#WebSphereCommerceServerExtensionsData.jar#XXXX: 
 javax.naming.NameNotFoundException: Context: localhost/nodes/localhost/servers/server1, name: jdbc/Default: First component in name Default not found.  Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
	at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.do_resolve_complete_info(WsnOptimizedNamingImpl.java:968)
	at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.resolve_complete_info(WsnOptimizedNamingImplBase.java:1431)
	at com.ibm.WsnOptimizedNaming._NamingContextStub.resolve_complete_info(Unknown Source)
	at com.ibm.ws.naming.jndicos.CNContextImpl.cosResolve(CNContextImpl.java:3493)
	at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1521)
	..............................
 
JDBCPersister W CNTR0032W: Error creating CMP persister using datasource: jdbc/Default
BeanMetaData  E CNTR0035E: EJB container caught com.ibm.ejs.container.ContainerException: ; nested exception is: 
	com.ibm.websphere.cpi.CPIException: Persister creation failed.The bean's J2EEName is wcfull#WebSphereCommerceServerExtensionsData.jar#XXXX. The data source name is jdbc/Default.; nested exception is: 
	javax.naming.NameNotFoundException: Context: localhost/nodes/localhost/servers/server1, name: jdbc/Default: First component in name Default not found. [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]
	at com.ibm.ejs.container.BeanMetaData.completeInitialization(BeanMetaData.java:1299)
	at com.ibm.ws.runtime.component.EJBContainerImpl.createBeanMetaData(EJBContainerImpl.java:1039)
	at com.ibm.ws.runtime.component.EJBContainerImpl.createModuleMetaData(EJBContainerImpl.java:830)
	at com.ibm.ws.runtime.component.EJBContainerImpl.createMetaData(EJBContainerImpl.java:1575)
	at com.ibm.ws.runtime.component.MetaDataMgrImpl.createFactoryMetaData(MetaDataMgrImpl.java:115)
	......................

This was the exception I got when I tried to start my WebSphere Commerce Full Test environment after creating a new EJB. Even though the solution was very simple, for me it took some time to figure it out what exactly went wrong. If any of you facing the same problem, then here is the fix.

Open your ibm-ejb-jar-bnd.xmi file. Search for jdbc/Default. Here jdbc/Default is the name of the data source that was not found by the server. You will be able to see an entry like

	<defaultDatasource xmi:id="ResourceRefBinding_1242722240919" jndiName="jdbc/Default"/>

Just to remove the above line and your server will again start properly.

Alert in Tools Framework

Tools Framework uses its own JavaScript function to display an alert message instead of JavaScript alert function. The normal JavaScript alert function does not use UTF-8 encoding to display any message. So double byte character messages will not be displayed correctly. So to address this issue, Tools Framework uses its own JavaScript functions for displaying any messages to the client.

The Tools Framework JavaScript function for displaying an alert is

alertDialog("Alert Message");

Commerce Accelerator Customization

I was customizing WebSphere Commerce Accelerator for that last couple of weeks. We are adding a new feature for configuring a product dynamically. WCS does not provide any product configurator OTB and hence no screen was available in Commerce Accelerator to manage the Product Configuration. Our business wants to manage the Product Configuration from commerce accelerator. So the only option available to us was to customize Commerce Accelerator. Customizing WebSphere Commerce Accelerator is a very difficult task. Commerce Accelerator uses a framework called Tools Framework which manages all the state using JavaScript. If someone wants to learn Object oriented JavaScript the best thing to do is to customize some of the Tools Framework components. The biggest issue with Commerce Accelerator customization is JavaScript debugging. CA works only in IE and there are no good debuggers available for JavaScript debugging in IE.

Every time I customize Tools Framework I will think to document how to do this customization. However unfortunately it never happens. So next time when I started customization I need to do the same research again and again. So this time I kept some notes on how to create Wizard, Notebook, Dialog, Tree etc.

I am thinking of some posts that contain these notes on customizing and debugging of commerce accelerator whenever I get some time.