Skip to content
bnewport edited this page Sep 13, 2010 · 4 revisions

This project is a set of utility classes to make using IBM WebSphere eXtreme Scale easier. It includes bulk multi-partition get/put/remove methods as well as various flavors of parallel agent execution. It also includes code for starting servers or single JVM grids.

Configuring WXS to connect using a property file

Some projects in this repository use wxsutils to connect to grids. They typically use the WXSUtils.getDefaultUtils() method to obtain a client connection to the grid. This method uses a property file, wxsutils.properties, to obtain the actual connection information to attach to a grid.

Properties to connect to a remote grid

These properties must be specified to connect to a remote object grid.

cep property (string)

This is the list of catalog service endpoints. Typically this is a comma separated list such as “hostA:2809,hostB:2809”

grid property (string)

This is simply the name of the grid to connect to. The default is “Grid”

og_xml_path property (string)

This property specifies the location of the objectgrid.xml file on the classpath. It’s loaded as a class loader resource. It’s not a folder, it’s the actual file to use and it can have any name.

threads (int)

This sets the size of the thread pool used for bulk operations to the grid from this client. Default is currently 32.

Properties to start an intra JVM test grid

These properties are specified for test environments when you want wxsutils to start a self contained WXS grid within the client JVM for easier development and debugging. This will start a single catalog and container within the client JVM. The cep property must be commented out or not specified. If cep is specified then wxsutils will try to connect to a remote grid.

grid property (string)

This is simply the name of the grid to connect to. The default is “Grid”

og_xml_path property (string)

This property specifies the location of the objectgrid.xml file on the classpath. It’s loaded as a class loader resource. It’s not a folder, it’s the actual file to use and it can have any name.

dp_xml_path property (string)

This property specifies the location of the deployment.xml file on the classpath. It’s not a folder, it’s the actual file to use and it can have any name.