When you are running a stand-alone WebSphere
eXtreme Scale configuration, the environment is comprised of catalog servers, container servers, and eXtreme Scale client processes. You must manually configure and start these processes.
Starting container processes
You can start eXtreme Scale from
the command line using a deployment topology or using
a server.properties file.
startOgServer script
The startOgServer script starts servers. You can use a
variety of parameters when you start your servers to enable trace,
specify port numbers, and so on.
Embedded server API
WebSphere eXtreme Scale includes application programming
interfaces (APIs) and system programming interfaces for embedding eXtreme Scale servers and clients within your existing Java
applications. The following topic describes the available embedded
server APIs.
Configuring ports in stand-alone mode
A Java™ virtual
machine that
hosts a catalog service instance requires four ports. Two ports are
used for internal use, the third port is used for clients and container
shards to communicate with Internet Inter-ORB Protocol (IIOP), and
the fourth port is used for Java Management
Extensions (JMX) communication.