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

Bindings in WebSphere Integration Developer

Imports and exports in WebSphere Integration Developer need binding information. This binding information will contain the protocol or any other data required by other modules to use this export/import. The meaning of import binding is different from export binding.

Import binding talks about how to access an external service. The default binding method for import is SCA bindings.

An export binding talks about how the service will be published to other modules or other services. An export binding can be HTTP Binding, Messaging Binding(MQ Binding, JMS bindings, MQ JMS etc), SCA Binding and Web Service binding. If the modules are running in same server, it is recommended to use an SCA binding instead of web service or JMS bindings. It is more easy and fast.

Today I was trying to test a business process using the Integration Test client. First I right clicked on my module in the assembly diagram and clicked on Test Component to test my module. It showed me a message, its publishing the module and it gave me an error in my test client. The error was

com.ibm.wbit.comptest.common.utils.TestException: Could not find module XXX
	at com.ibm.wbit.comptest.controller.util.GeneralUtils.getModuleFor(Unknown Source)
	at com.ibm.wbit.comptest.controller.invocation.impl.Invoker.getModule(Unknown Source)
	at com.ibm.wbit.comptest.controller.invocation.impl.Invoker.managedRun(Unknown Source)
	at com.ibm.wbit.comptest.controller.invocation.impl.Invoker.run(Unknown Source)
	at com.ibm.wbit.comptest.controller.invocation.impl.BaseInvocationHandler.invoke(Unknown Source)
	..........................

I was not sure what the issue was. My module was there and it was showing as published. After few minutes search I got the solution. If your module is little big, first make sure that you have published your module and then start the test client. I think the test client does not have patience to wait for the module to be published and that was causing the problem

Receive choice activity or pick activity in WebSphere Process Server

A receive choice activity or pick activity is used for receiving different messages (or operations). This activity is extremely useful if you have an interface with more than one operation and you want this interface as the Interface partner for a business process. If you pass an interface with more than one operation to a normal receive activity it would throw you an error message saying “The process does not implement the operation ‘xxx’ of the port type ‘xxx’”. In this case the only option for us to use the interface is to use receive choice activity. To use a receive activity, follow the below steps.

1. Delete the existing receive activity
2. Drag and drop receive choice activity to your business process. A receive choice activity will be created with one choice in it.

3. Add a new receive by right click on receive choice activity and select ‘Add Receive’.

4. Select the first receive and go to Details tab in your properties window. Select your interface partner, operation and the input parameters. (Change the display name of receive if you want.).

5. Add a reply activity.

6. Repeat these steps for all the operation you have in your interface.

In my case I had two operations in my interface and after configuring receive choice activity my business process look like the one shown below.

If you are getting an error message saying, “The process is not startable. No receive choice or receive activity was found that creates a new process instance and does not have incoming links or preceding basic activities.”, make sure that you have checked the “Create a new process instance if one does not already exist” checkbox in the details tab of Receive choice properties window.