Comments (5)
  • Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

1 Alan Chambers commented Permalink

Very clear and useful article - thank you.

It's worth noting that the commands given for installing Liberty Profile server and WXS must be used as described - i.e. using the java command to execute the jar files. It's tempting to just unpack the jar files with the jar command or similar and if you do this at first it appears to have worked. However, as well as unpacking the files the commands shown also result in the creation of a jvm.options file in wlp/etc, which points to the correct endorsed jar files for the IBM ORB etc., which is needed for a server to start without errors once the extreme-scale feature has been added.

2 ellisdp commented Permalink

A really useful article, thanks.

I don't seem able to find the "WXS wiki" or sample application referred to in the last paragraph - have these moved to a new location? If so it would be really helpful to update the link, which now just takes me to a generic IBM DeveloperWorks page.

3 JonMarshall commented Permalink

Hi - thanks for the comment about the link. The dev team has moved the content onto the new Elastic Caching Community, so the wiki has just been retired. I have updated the post.

4 LarsBesselmann commented Permalink

Before running a test client you can check the availability of the grid by using the commands:
bin]$ ./ -c showPlacement -cep localhost:2809
The output should look like this:
CWXSI0068I: Executing command: showPlacement
*** Show all online container servers for Grid data grid and defaultMapSet map set.
Host: localhost.localdomain
Container: wxsServer_C-1, Server:wxsServer, Zone:DefaultZone
Partition Shard Type Reserved
--------- ---------- --------
0 Primary false
Number of containers matching = 1
Total known containers = 1
Total known hosts = 1
CWXSI0040I: The showPlacement command completed successfully.

Before and after adding content to the grid check if it has really been added via command:
bin]$ ./ -c showMapSizes -g Grid -cep localhost:2809
Before the test the output should look like this:
CWXSI0068I: Executing command: showMapSizes
*** Displaying results for Grid data grid and defaultMapSet map set.
*** Listing maps for wxsServer ***
Map Name Partition Map Entries Used Bytes Shard Type Container
-------- --------- ----------- ---------- ---------- ---------
Map1 0 0 0 Primary wxsServer_C-1
Map2 0 0 0 Primary wxsServer_C-1
Server total: 0 (0 B)
Total catalog service domain count: 0
(0 B)
(The used bytes statistics are accurate only when you are using simple objects or the COPY_TO_BYTES copy mode.)
CWXSI0040I: The showMapSizes command completed successfully.

5 WillyG commented Permalink

to the point article!
I wasted some time figuring out where to store the folder grids, containing the file objectgrid.xml.
Maybe I can try to clarify, if others should run into same issue.

My installation location of liberty profile: c:\dev\tools\was_liberty_profile
my server name: defaultServer
correct location of folder grids, and file objectgrid.xml:
so generic should be:
[was liberty installation]/usr/servers/[servername]/grids/objectgrid.xml
see LarsBesselmann for command to verify succesful objectgrid configuration.
You do not want empty report,
[was liberty installation]/bin/xscmd.bat -c showPlacement
CWXSI0068I: Executing command: showPlacement
[You should see a report here, empty report means no valid objectgrid configuration]
CWXSI0040I: The showPlacement command completed successfully.