To run the data grid in a Liberty profile, you must configure WebSphere® eXtreme Scale servers to use Liberty profile configuration files.
<server description="eXtreme Scale Catalog Server with default settings">
<!-- Enable features -->
<featureManager>
<feature>eXtremeScale.server-1.0</feature>
</featureManager>
<com.ibm.ws.xs.server.config catalogServer="true" listenerPort="${com.ibm.ws.xs.server.listenerPort}" />
<logging traceSpecification="*=info" maxFileSize="200" maxFiles="10" />
</server>
Notice that the listenerPort element is referenced in the server.xml; however, you configure this value in the bootstrap.properties file. It can be useful to separate elements such as port numbers out of the server.xml so that multiple processes that run with an identical configuration can share the same server.xml file, but still have unique settings.
In the previous example, tracing is specified in the Liberty profile configuration, and the listenerPort attribute specifies a variable. This variable is configured in the bootstrap.properties file in the server configuration directory, wlp_install_root/usr/server/serverName. See the following example of the bootstrap.properties file:
# Licensed Materials - Property of IBM
#
# "Restricted Materials of IBM"
#
# Copyright IBM Corp. 2012 All Rights Reserved.
#
# US Government Users Restricted Rights - Use, duplication or
# disclosure restricted by GSA ADP Schedule Contract with
# IBM Corp.
#
# -------------------------------------------------------------------------------------------------
#
# port for the OSGi console
# osgi.console=5678
com.ibm.ws.xs.server.listenerPort=2809
In this example, the osgi.console port is commented out, which means that the Liberty profile listens on the specified port for telnet clients to connect to an OSGi console. This behavior is useful for diagnosing OSGi-related errors.
<server>
...
<com.ibm.ws.xs.server.config ... serverProps="/path/to/myServerProps.properties" ... />
</server>