IBM WebSphere eXtreme Scale

WebSphere eXtreme Scale Getting Started readme

The getting started sandbox is provided for a quick introduction to eXtreme Scale functionality and basic operation. It consists of shell and batch scripts designed to start a simple grid with very little customization needed. In addition, a client program, including source, is provided to run simple create, read, update, and delete (CRUD) functions to this basic grid. Eclipse project metadata for the client program is provided.

For information on loading and running this client in Eclipse, refer to the ECLIPSE_README document that is provided.

Table of contents

Software requirements

Getting the sample

This sample is located in the directory.

This sample is in the <objectgrid_root>/gettingstarted directory.

Sample files

This sample provides four scripts. One set is for UNIX platforms and one set is for Windows platforms:

Running the sample

This section describes the basic steps for starting your first grid and running a client to interact with it.

  1. Open a terminal session or command-line window.
  2. Type cd install_root/gettingstarted

    Substitute install_root with the path to the eXtreme Scale installation root directory or the root file path of the extracted eXtreme Scale trial.

  3. Run an eXtreme Scale catalog service process on localhost:

    UNIX: runcat.sh

    WINDOWS: runcat.bat

    The catalog service process runs in the current terminal window.

  4. Run an eXtreme Scale container server instance in the new terminal window:

    UNIX: runcontainer.sh server0

    WINDOWS: runcontainer.bat server0

    The container server will run in the current terminal window.

  5. Open another terminal session or command-line window and repeat step 5, using a different server name to start additional container servers.
  6. Run some client commands in the new terminal window:
    1. Add some data to the grid:
    2. Important: If your system is using DBCS (double byte character sets), when inserting data into the grid with the runClient script, the data may display as garbled or corrupted text. This can display in the output or in the cache. A possible workaround is to update the java call in the runClient script to include the JAVA VM argument -Xargencoding, and then specify the DBCS as a unicode character set. For example, using the command: \u runClient i key\u2e81 Hello\2e84World

      UNIX: runclient.sh i key1 helloworld

      WINDOWS: runclient.bat i key1 helloworld

    3. Lookup and display that value:
    4. UNIX: runclient.sh g key1

      WINDOWS: runclient.bat g key1

    5. Update the value:
    6. UNIX: runclient.sh u key1 goodbyeWorld

      WINDOWS: runclient.bat u key1 goodbyeWorld

    7. Delete the value:
    8. UNIX: runclient.sh d key1

      WINDOWS: runclient.bat d key1

  7. Use Ctrl+c to stop the catalog service process and container server in the respective terminal windows.

More information