Configuring WCS V7 toolkit basecache with eXtreme Scale Cache Provider - Part 2

In Part II of this two part series we will go through WXS server installation and configuration with WCS server.

For this demo we will be installing a standalone version of extreme scale server, this would mean we can run eXtreme scale in a non WAS environment.

Step 1:

Step 2:

Step 3:
Use following script to stop and start catalog server

C:\IBM\WebSphere\eXtremeScale\ObjectGrid\bin>startOgServer.bat catalogServer -listenerHost <HOSTNAME>  -listenerPort 2810

C:\IBM\WebSphere\eXtremeScale\ObjectGrid\bin>stopOgServer.bat catalogServer -catalogServiceEndPoints 
<HOSTNAME>:2810HOSTNAME: You can not use localhost or 127.0.0.1, instead use the machine name if you are running everything on the same host machine, ensure you have an entry in your etc\hosts file as follows

127.0.0.1 <HOSTNAME>

Step 4:

Configure the catalog server in WAS admin console as shown in the screenshot below.

Step 5:

Make sure WAS is able to connect to catalog server

Step 6:

Next we define few custom JVM properties that will be used by extreme scale client, define them as shown in the screenshot below.

Step 7:

Start and stop the container service using the default config provided with the base install of eXtreme Scale

startOgServer.bat container1 -objectGridFile C:\IBM\WebSphere\eXtremeScale\ObjectGrid\dynacache\etc\dynacache-remote-objectgrid.xml -deploymentPolicyFile C:\IBM\WebSphere\eXtremeScale\ObjectGrid\dynacache\etc\dynacache-remote-deployment.xml -catalogServiceEndPoints localhost:2810

C:\IBM\WebSphere\eXtremeScale\ObjectGrid\bin>stopOgServer.bat container1 -catalogServiceEndPoints <HOSTNAME>:2810

http://publib.boulder.ibm.com/infocenter/wxsinfo/v7r1/topic/com.ibm.websphere.extremescale.admin.doc/rxsstopcmd.html

Step 8:

Enable eXtreme Scale as the cache provider.

During server start up you should see similar lines which indicates successful integration of WAS + WCS + WXS 

[12/21/11 21:51:30:826 CST] 00000000 ClientDomainC I   CWOBJ1126I: The ObjectGrid client has connected to the DYNACACHE_REMOTE grid in the DefaultDomain domain using connection 0.
[12/21/11 21:51:30:841 CST] 00000000 ObjectGridImp I   CWOBJ4700I: The map name IBM_DC_PARTITIONED_baseCache matched the regular expression of template map IBM_DC_PARTITIONED_.*.  The IBM_DC_PARTITIONED_baseCache map has been created for ObjectGrid DYNACACHE_REMOTE.
[12/21/11 21:51:30:908 CST] 00000000 CacheProvider I   CWOBJ4508I: The WebSphere eXtreme Scale provider has created a Dynamic Cache instance with name baseCache using topology remote.

Now output the mapsizes and you should see something similar in output.

C:\IBM\WebSphere\eXtremeScale\ObjectGrid\bin>xsadmin.bat -mapsizes

This administrative utility is provided as a sample only and is not to be

considered a fully supported component of the WebSphere eXtreme Scale product

Starting at: 2011-12-21 21:56:28.000000885

Connecting to Catalog service at localhost:1099

************Displaying Results for Grid - DYNACACHE_REMOTE, MapSet - DYNACACHE_R

EMOTE**************

*** Listing Maps for container1 ***

Map Name                     Partition Map Entries Used Bytes Shard Type

IBM_DC_PARTITIONED_baseCache 0         2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 1         2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 2         2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 3         2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 4         2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 5         2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 6         2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 7         2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 8         2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 9         3           3 KB       Primary

IBM_DC_PARTITIONED_baseCache 10        2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 11        3           3 KB       Primary

IBM_DC_PARTITIONED_baseCache 12        2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 13        2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 14        2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 15        2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 16        2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 17        2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 18        2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 19        3           3 KB       Primary

IBM_DC_PARTITIONED_baseCache 20        2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 21        3           5 KB       Primary

IBM_DC_PARTITIONED_baseCache 22        2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 23        2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 24        2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 25        2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 26        2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 27        2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 28        2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 29        3           4 KB       Primary

IBM_DC_PARTITIONED_baseCache 30        2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 31        3           4 KB       Primary

IBM_DC_PARTITIONED_baseCache 32        4           9 KB       Primary

IBM_DC_PARTITIONED_baseCache 33        2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 34        2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 35        3           5 KB       Primary

IBM_DC_PARTITIONED_baseCache 36        2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 37        2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 38        2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 39        2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 40        2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 41        3           4 KB       Primary

IBM_DC_PARTITIONED_baseCache 42        3           5 KB       Primary

IBM_DC_PARTITIONED_baseCache 43        2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 44        2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 45        2           1 KB       Primary

IBM_DC_PARTITIONED_baseCache 46        3           3 KB       Primary

Server Total: 106 (94 KB)

Total Domain Count: 106 (94 KB)

(The used bytes statistics are accurate only when you are using simple objects o

r the COPY_TO_BYTES copy mode.)

Ending at: 2011-12-21 21:56:30.000000027

This was a very short introduction to installation and configuration of WXS with WCS toolkit / server additions, there are more advanced configuration options available with WXS and WCS. I hope this helps you get started and unleash power of extreme scale cache.


Reference

http://www.redbooks.ibm.com/abstracts/sg247683.html

https://www.ibm.com/developerworks/wikis/display/extremescale/Configure+WebSphere+Commerce+to+use+WebSphere+eXtreme+Scale+for+dynamic+cache+to+improve+performance+and+scale

Pituluik Media

Blogger | Freelancer |Operations Manager | Marketing and Sales Manager | Lancer Evo 4 Community. Indonesian Bloggers Who Become Bloggers Because of Hobby. Feel free to connect with me on Social Media Instagram @alberandesko

Share this post