Move Websphere Commerce cache instances to eXtreme Scale: baseCache configuration

As explained in the previous post about WXS, we have an eXtreme Scale + Websphere Commerce infrastructure ready to use for functional tests.

In this post we move a step forward following the guidelines proposed in another developerWorks article

Configure WebSphere Commerce with WebSphere eXtreme Scale to improve performance, scale, and your competitive edge

To follow the general guidelines about WXS and WebSphere Commerce integration, I modified previous topology where catalog server were executed in a WebSphere application server JVM and I moved catalog server in a stand alone JVM.

This was quite easy: the installation steps are the same but when you configure the catalog server domain in the WAS console

Remote Catalog Server Domain

you have to choose the “Remote server” option

Remote Catalog Server Started in WAS Console


To startup the catalog server and the container you have to use the same grid configuration files used in the previous post



But this time you have to run the catalog server process manually first

startXsServer.bat catalogServer -serverProps C:\IBM\WebSphere\WXS\ObjectGrid\webspherecommerce\properties\

using the same properties file we used in the setup part

and executing the container

startXsServer.bat wccontainer1 -objectGridFile C:\IBM\WebSphere\eXtremeScale\ObjectGrid\webspherecommerce\etc\dynacache-objectgrid.xml -deploymentPolicyFile C:\IBM\WebSphere\eXtremeScale\ObjectGrid\webspherecommerce\etc\dynacache-deployment.xml -catalogServiceEndPoints localhost:4809 -listenerPort 6601

After augmenting the profile, to switch the baseCache to WXS is quite simple: you only need to change the provider on “Dynamic cache service”

WXS provider in baseCache

Using a very simple cachespec.xml to cache Aurora Home page only, we can check if the WXS provider is working as expected

Loading Aurora home page, a new entry appears on cache monitor

Cache entries Home page Aurora cache monitor

How can we check if those entries were correctly stored in the grid?

We can do a first check using cache monitor accessing to the WXS Mbeans

Cachemonitor access to the WXS mbeans

But to get a full view about grid usage, we have to use WXS web console.

We already created all the references (catalog server and catalog service domain) in the previous post and we only have to connect using a browser

First of all looking at the cache contents (be careful only first 500 results will be returned)

WXS web console cache contents

And then the grid usage for example

WXS web console grid usage

A general suggestion to close: upgrade your WXS environment to using FixCentral and open a PMR asking for the last cumulative fix available before starting a WXS implementation in a production environment.


Websphere Commerce and Portal Architect ✔ Motivated IT professional with more than ten years of experience, combining Java and JEE developer skills with systems and IBM products installation knowledge. ✔ Strong experience and skills on planning, architecting and implementing complex commerce and portal solutions based on IBM middleware products. ✔ Reliable with a strong network attitude, experience on leading developer's teams and manage international relationships. Specialties ✔ Pleasant manner, reliable. ✔ Ability to consider issues from different point of views. ✔ End-oriented work capacity and problem-solving attitude. ✔ Ability to work with deadlines and under pressure. ✔ Ability to prioritise tasks and manage people. ✔ Ability to increase the whole team skills. ✔ Ability to generate commercial leads

Tagged with: , , ,
Posted in cache, websphere application server, websphere commerce, websphere eXtreme scale

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: