See the WebSphere eXtreme Scale Wiki for links to eXtreme Scale Version 7.0 documentation.
If you log in
with your developerWorks ID, you can leave comments and feedback for the development team.
By deploying your ObjectGrid into a distributed environment, you can partition and replicate your data. ObjectGrid supports two types of distributed environments: dynamic and static.
Configuring ObjectGrid for deployment into a dynamic environment
Deploying ObjectGrid into a dynamic environment is the most flexible option. You are not required to predefine each ObjectGrid server in the dynamic environment, and you can add servers to this environment as required. The deployment policy XML file manages the deployment of an ObjectGrid into a dynamic environment.
To learn more about configuration with a deployment policy, see Configuring for deployment into a dynamic topology.
Configuring ObjectGrid for deployment into a static environment
You can deploy your ObjectGrid into a static environment when you know exactly how you want your ObjectGrid data to be distributed across a predefined set of servers. When you deploy into a static environment, you cannot add servers to the environment later without cycling the environment. The cluster XML file manages the deployment of an ObjectGrid into a static environment.
To learn more about configuration with a cluster XML, see Configuring for deployment into a static topology.
Configuring ObjectGrid for deployment with security enabled 
You can deploy your ObjectGrid into a static or deployment environment with security enabled. For a dynamic environment, you can provide a security.xml to the catalog server. For a static environment, you have two options: You can either provide a security.xml or you can directly configure security properties in the static cluster XML.
To learn more about security configuration with a security XML, see Configuring for deployment with security XML.
To learn more about security configuration with a cluster XML in a static environment, see Configuring for deployment into a static topology.
Configuring an ObjectGrid client
When application code establishes a connection to an ObjectGrid running on a set of servers, an ObjectGrid client is created. By default, an ObjectGrid client has the same configuration as its server side counterpart. For example, both the client and the server ObjectGrid will have the same number of buckets and the same evictor. However, you can alter some of the settings on your ObjectGrid client by passing an ObjectGrid XML file to the connect method.
To read more about configuring an ObjectGrid client, see Configuring an ObjectGrid client.
Additional information
© Copyright IBM Corporation 2007,2009. All Rights Reserved.
