I have written a previous post on migrating to WAS 6.1 under WebSphere Commerce 6, this allows you to then utilise WebSphere Extreme Scale. But there are then quite a few pieces that you need to pull together to get things going, so hopefully I can give some pointers on what to do. If it saves you the time and aggravation then its a good thing, if you find anything different then let me know.
First of all I ran up a test environment a standalone 6.1 WAS instance at 6.1.0.31, Commerce at 6.0.0.10 and WebSphere Extreme Scale at 7.1. Ok right now this is not supported but I could see no reason why it would not work. We had the WAS/WC environment running on AIX 5.3 and the WXS was remote and installed under Ubunto 6. We wanted to use the standalone environment for WXS to save us money (no WAS license), and create quite a simple configuration.
Setting up the WAS Side
The first step is to ensure you are patched to the latest levels of WAS 6.1 because of the Commerce migration I had done then the site was running 6.1
Restore the WXS installer onto the environment, and run the installer.
Setting up the Remote Extreme Scale Server
Catalog Server
The catalog
Catalog Container
Extreme Scale Console
The extreme scale console is new in WXS 7.1 and can be used to monitor the environment.
It is started from the <installpath>/ObjectGrid/bin directory using the command startConsoleServer.sh. one thing I did notice under Ubuntu is that because the install of the software was performed under root, if I used the standard profile it did not now have authority to create the directory structure required under <installpath>/ObjectGrid/console where it wanted to create a number of objects. This includes a Derby database and a number of files. I have ended up using sudo to start the console server, but it will be something to address the simplest thing will be to set the right authority.
One the server is started in the browser goto https://<hostname>:7443, use admin and admin as the password and profile. My first thought is this is quite a nice interface it looks good and the first step is to add the catalog sever. Enter the hostname the JMX port, which should default to 1099 and the listener port 2809. No connection will exist until you then create an Extreme Scale Domain. At first I was unsure should go here because the 7.1 domain documentation only talks about WAS 7.1, but the domain name can be anything. Once the domain name is added then on the right hand side of the screen add the catalogue server. The status in the top right hand corner should now go to connected. If you click around the Commerce site and then go into Monitors > Data Grid Overview you should see DYNACACHE_REMOTE, click that and you will get some details of what is taking place in the cache.
In the environment I am first setting up with a single catalog server and container, then I need to define