IBM® eXtremeIO (XIO) is a transport mechanism that replaces the
Object Request Broker (ORB).
Before you begin
If Version 8.6.0.2 is
installed on your servers that are running XIO and you have COPY_TO_BYTES
configured on the data grids, your WebSphere® eXtreme Scale Client installations must
also be at Version 8.6.0.2 or later.
To configure XIO, all of
your catalog and container servers must be at the Version 8.6 release
level. For more information, see Updating eXtreme Scale servers.
About this task
You can configure XIO for
all the container servers in your catalog service domain by enabling
XIO in the catalog servers. The container servers discover the transport
type of the catalog server and use that transport type.
Procedure
How you enable XIO
depends on the type of servers you are using:
- Enable XIO on
your stand-alone catalog servers.
XIO is enabled by
default when you start your catalog server with the startXsServer command. For more information, see Starting container servers that use the IBM eXtremeIO (XIO) transport.
- Enable XIO on
your servers that are running in WebSphere Application Server.
You can
enable XIO on your catalog service domain in the WebSphere Application Server administrative console.
Click . Select Enable IBM eXtremeIO
(XIO) communication. Apply your changes. For more information,
see Configuring the catalog service in WebSphere Application Server.
- Enable XIO on
your servers that run in the Liberty profile.
To enable XIO in a
Liberty profile server, set
transport attribute to
XIO in your
server.xml file. For example,
see the highlighted property in the following code example:
<featureManager>
...
<feature>eXtremeScale.server-1.1</feature>
</featureManager>
<xsServer isCatalog="true" transport="XIO" listenerPort="2809" ... />
Attention: The server must be a catalog server, and therefore, isCatalog must be set to true when you configure XIO. The listenerPort setting is not required; however, XIO can recognize
this port if you enable it. If you do not enable XIO, then the ORB
is used on that port instead.
Next, run the start command to start your Liberty profile servers. For more
information, see Starting and stopping servers in the Liberty profile.
You can use command-line arguments and server properties to configure
XIO behavior:
- Optional: Update the server
properties file for each container server in the configuration to
enable XIO properties. After you decide on the properties
that you want to set, you can set the values in the server properties
file or programmatically with the ServerProperties interface. For more information about the properties you can set,
see Tuning IBM eXtremeIO (XIO).
What to do next
You can also use IBM eXtremeMemory to help you avoid garbage collection
pauses, leading to more constant performance and predicable response
times. For more information, see Configuring IBM eXtremeMemory.