Configuring transports

Transports enable the exchange of objects and data between different server processes in your configuration.

About this task

If you are using eXtremeMemory, a new transport that is called eXtremeIO is used. With eXtremeMemory, cache entries are stored in native memory. Native memory does not go through garbage collection, leading to more constant performance and predicable response times. Objects are serialized into bytes on the container server. For more information, see Configuring IBM eXtremeIO (XIO).

[Version 8.6 and later]Two options exist for transports within WebSphere® eXtreme Scale: the Object Request Broker (ORB) or IBM eXtremeIO (XIO).

ORB
When you use the ORB transport, communication between clients and servers, and between servers within the environment, is handled by the ORB.
[Version 8.6 and later]Deprecated featureDeprecated: The Object Request Broker (ORB) is deprecated. If you were not using the ORB in a previous release, use IBM eXtremeIO (XIO) for your transport mechanism. If you are using the ORB, consider migrating your configuration to use XIO.
[Version 8.6 and later]XIO
[Version 8.6 and later]When you use the XIO transport, communication between clients and servers, and between servers within the environment, is handled by a transport mechanism that is designed specifically for WebSphere eXtreme Scale. The eXtremeMemory and eXtreme data format (XDF) features require the XIO transport.